Meta Tag & Open Graph Generator
Build title, description, canonical, Open Graph and Twitter Card tags from a form, with a live Google snippet and X / Facebook card preview and warnings.
Fill in a title, description, URL and image and get the complete head markup: title, meta description, canonical link, Open Graph properties and Twitter Card tags. The page renders a live preview as a Google search snippet and as an X or Facebook card while you type, and flags the problems that are easy to miss, such as an over-long title, a missing og:image, an http image URL or an absent canonical.
// Meta Tag & Open Graph Generator: Features
Title tag and meta description length
Google cuts titles at roughly 60 Latin characters and descriptions at around 155 to 160, but the real limit is pixel width, so a title full of wide capitals is cut earlier than one in lower case. The practical rule is to front-load the words that identify the page, so that whatever is truncated matters least, and to put the site name at the end. The generator counts characters against these thresholds and the search preview shows where the text actually breaks. For precise counts in several units, the Character Counter is available.
Open Graph tags and Twitter Cards
Open Graph is the protocol Facebook defined and almost everything else adopted: Slack, Discord, LinkedIn, iMessage and most chat apps read og:title, og:description, og:image and og:url when a link is pasted. X reads its own twitter:card family but falls back to the Open Graph values when the twitter: versions are absent, so a single twitter:card line on top of a complete Open Graph set is enough for most sites. The generator can also emit explicit twitter:title, twitter:description and twitter:image for cases where you want X to show different text.
Why the og:image does not show up when shared
When a shared link renders without an image the cause is nearly always og:image. A relative path is not resolved by the platform fetching it; an http URL is refused by most of them; an image smaller than about 600 pixels wide is dropped or demoted to a small thumbnail. The recommended size is 1200 by 630 pixels, which also gives the 1.91:1 aspect ratio that summary_large_image expects. Platforms cache what they fetched, so after fixing the tag you need to re-scrape the URL in the X Card Validator or Facebook Sharing Debugger before the change is visible. The generator warns about missing, relative and http images.
The canonical tag and og:url should match
The canonical link tells search engines which URL is the definitive one when the same content is reachable at several addresses: with tracking parameters, with and without www, over http and https, with and without a trailing slash. og:url does the same job for social platforms, which use it to merge share counts and to decide which URL to display. Both should carry the same clean, absolute URL, which is why the generator derives them from a single field. Enforcing the canonical form at the server is the job of the .htaccess & Nginx Redirect Generator.
noindex meta tag versus robots.txt
To keep a page out of search results, use a robots meta tag with noindex. Disallowing the path in robots.txt is not the same thing: it stops crawling, but the URL can still be indexed from external links, usually without a description. Worse, a page that is both disallowed and marked noindex never has its noindex read, because the crawler is not permitted to fetch it. The generator offers index, noindex and noindex, nofollow as options and warns when noindex is selected. Crawl rules themselves are built with the robots.txt Generator.
// Meta Tag & Open Graph Generator: FAQ
What size should the og:image be?
- 1200 by 630 pixels, giving a 1.91:1 ratio, is the size every major platform recommends and renders without cropping. Keep the file under about 1 MB and use PNG or JPEG. The small summary card on X uses a square crop of the same image, so a 1200 by 630 image still works there; the centre is what survives.
How long should a title tag be?
- Aim for 50 to 60 characters. Google truncates by pixel width at about 600 pixels, so the exact count varies, but 60 is a safe ceiling for mixed-case Latin text. Put the page-specific words first and the site name last, so that the part that gets cut carries the least information. The search preview in the generator shows the truncation.
Does the meta description affect ranking?
- Not directly. It affects click-through rate from the results page, which matters more than most on-page signals. Google rewrites or replaces descriptions it judges to be a poor match for the query, so a description that accurately summarises the page is more likely to be shown as written. Leaving it empty guarantees an auto-generated snippet.
Do I need twitter:title and twitter:description?
- No. X uses the og: values when the twitter: ones are absent. They are worth adding when you want different text on X, or as insurance for scrapers that do not implement the fallback. The checkbox "Also emit twitter:title / description / image" toggles them.
Which og:type should I use?
- website for home pages and index pages, article for posts and news items. The choice has little visible effect on most platforms, and many ignore og:type entirely. When unsure, website is fine.
What goes in og:locale?
- The language and region of the page in the form en_US or ja_JP. Facebook uses it to choose how to present the card; other platforms mostly ignore it. It defaults to en_US when omitted, so it matters mainly for pages in other languages.
Why does the link preview still show the old Open Graph data?
- The platform has cached its previous fetch. Re-scrape the URL in the X Card Validator or the Facebook Sharing Debugger to refresh it. Slack and Discord refresh on their own after some hours or days; appending a throwaway query parameter such as ?v=2 makes the link count as a new URL and shows the new tags immediately.
Should the canonical point to the page itself?
- Yes, that is the normal case. Every page should declare its own clean URL as canonical, so that copies with tracking parameters, alternate hosts or syndicated versions resolve back to it. Use the same trailing-slash and www convention as the rest of the site.
Should I include charset and viewport here?
- Only when they are not already in your template. Ticking "Include charset / viewport" prepends the two lines that belong at the very top of the head, which is useful when writing an HTML file from scratch or a static-site template. The charset declaration must appear within the first 1024 bytes of the document.
Is anything I type sent to a server?
- No. Tag generation and the previews run entirely in your browser, so unpublished titles, URLs and descriptions stay on your machine. The one exception is the image preview: your browser fetches the og:image URL you enter directly, so that image server sees the request.
// How to Use Meta Tag & Open Graph Generator
-
Enter the title, description and URL
Fill in the page title, description, canonical URL and site name. The character counters change colour when a limit is exceeded; check the search preview to see where the text is cut.
-
Add the image and social settings
Paste the absolute https URL of a 1200 by 630 image into og:image, choose the X card type and add your X handle. Switch the preview to X or Facebook to see the resulting card.
-
Resolve the warnings and copy
Missing images and malformed URLs appear as warnings. Once they are clear, copy the output into the head of the page. After publishing, re-scrape the URL in each platform's debugger to refresh its cache.
Category SEO