Writing Open Graph Tags That Share Well: Titles, Descriptions and Images
A page without Open Graph tags still gets shared, but the preview it produces is left to each platform's fallback logic, which may pick a navigation label as the title, a cookie notice as the description, or no image at all. Writing the tags deliberately takes a few minutes and gives the publisher control over the first impression a link makes. The Open Graph Meta Tag Generator produces the tag markup for a page from the title, description, image and address you supply, so the result can be pasted into the page's head section. It generates markup from your inputs; it cannot check whether the image address is reachable or whether the page's content lives up to the description, so those checks remain the publisher's job.
Four tags carry almost all of the value. The og:title should be the page's headline, written to stand alone, since many readers will see it without any surrounding context. The og:description should summarise the page in one or two sentences and give a reason to click, without repeating the title. The og:image should be a relevant, legible image at an absolute address, because relative addresses fail on some platforms. The og:url should be the canonical address of the page, so shares, likes and comments accumulate on one address rather than splitting across tracking variants of the same page.
How it works
A generator takes the four values, plus optional extras such as the site name and the content type, and emits the corresponding meta elements in the format platforms expect. The content type matters more than it appears: an article type tells platforms the page is a piece of writing, while a website type suits a homepage or landing page, and the wrong type can change how the card is rendered. The site name tag, og:site_name, adds the publication's name to the card, which helps readers recognise the source at a glance, especially when the title alone does not identify it.
How it works
Length discipline is what makes generated tags work in practice. Titles that run far beyond sixty or so characters are cut off on many cards, sometimes mid-word, and descriptions beyond roughly 150 to 160 characters are truncated with an ellipsis that can strand a sentence half-finished. Writing within those limits is not about dumbing the content down; it is about choosing the strongest short version of the title and description, so the card shows a complete thought rather than a fragment. The generator can count characters for you, but the editorial choice of what to cut remains yours.
Worked example
Worked example with sample values. Suppose a page has the headline 'How to Prune Roses in Spring', which is 30 characters, and a description of 148 characters summarising the method in one sentence. The generator emits 5 tags: og:title, og:description, og:image, og:url and og:type, plus og:site_name, which makes 6 tags in total. Checking the output against 4 rules, title under 60 characters, description under 160 characters, image address absolute, and URL canonical, gives 4 passes out of 4, or 100 percent passing. If the description had been 210 characters instead, it would exceed the limit by 50 characters, and the fix would be to cut one clause, not to hope the platform shows the whole text. These are sample values for illustration.
Worked example
The image choice in the same example shows the second kind of decision a generator cannot make for you. Suppose two candidate images exist: a wide garden shot 1200 pixels by 630 pixels, and a close-up of a single rose 800 pixels by 800 pixels. The wide shot matches the ratio most cards display, so it survives cropping, while the square close-up would lose its top and bottom on a wide card. The generator will accept either address, so the publisher must pick the one that survives the card's crop, and the way to decide is to view each candidate at the size the card will actually show.
Mistakes to avoid
One common mistake is copying the page's search-engine description into the Open Graph description without editing it. Search descriptions and share descriptions serve different readers: a searcher is comparing results, while a social reader is deciding whether to interrupt their feed, so the share description should be more direct and self-contained. Another mistake is pointing og:image at an image that requires sign-in or blocks external fetching, which leaves the card imageless on every platform. A third is forgetting to update the tags when the page's headline or image changes, so the card advertises an older version of the content.
Mistakes to avoid
A further mistake is generating tags for pages that should not be shared, such as confirmation pages, private dashboards, or pages containing personal data, where a rich preview in a chat thread can expose information the page was meant to keep private. For those pages, the correct choice is no preview tags at all, or a robots restriction, not a polished card. Also avoid stuffing keywords into the title tag: a card that reads like a keyword list is less likely to be clicked than one that reads like a headline, and it damages the publication's credibility with every share.
Putting it into practice
Make tag generation part of publishing: when a page's headline and image are final, generate the tags, paste them into the head section, and verify them with a checker before announcing the page. Keep a short house style for titles and descriptions, including the character limits, so authors do not have to rediscover them each time. After any template change, regenerate and re-check the tags on the most-shared pages, and remember that fixing tags is only half the job: platforms that cached the old preview need a refresh before readers see the new card.
Related tools and reading: Related tools and reading: the Social Card Preview and the Open Graph Checker cover neighbouring checks that pair naturally with this one, and the guide at [/blog/seo-titles-meta-descriptions/] extends the same topic with further background and examples for readers who want to go deeper.
Key points
- The four essential tags are title, description, image and canonical URL
- Keep titles short and descriptions near 150 characters to avoid truncation
- Use an absolute image address in a ratio that survives card cropping
- Do not generate preview tags for private pages that should not be shared
In short: t.he four essential tags are title, description, image and canonical URL
One habit ties all of this together: re-check after every change. A result is only as current as the input it was run on, so a fix, a redesign, or a new version of the underlying material deserves a fresh run rather than reliance on an old report. Keep the previous result alongside the new one, note what changed between them, and treat any new finding as a question to investigate rather than a verdict to accept or dismiss. That loop of checking, fixing, re-checking and recording is what turns a one-off test into a reliable routine, and it costs far less time than debugging a problem that a second check would have caught early.