How to use it
This tool can’t fetch your page, because nothing here talks to other websites: your HTML stays in your browser. So paste the source instead. Open the page and press Ctrl U (⌘ ⌥ U on a Mac), or in DevTools right-click the <head> element and choose Copy, then Copy outerHTML. The whole page works, and so does just the head.
Problems show at the top of the previews. Click one to jump to it in your HTML. “Use the corrected tags” (or ⌘ Enter) swaps your tags for the corrected block, and ⌘ Z puts them back. The fix keeps your own wording. It fills gaps from tags you already have, makes relative addresses absolute, removes duplicates and leaves your other tags alone.
The previews are generic, not copies of any particular app, and images aren’t loaded: you see a box with the image address instead. Real search results and share cards vary by app, device and country, and they change often, so treat the previews as a good guide rather than a promise.
The tags that matter
| Tag | What it’s for |
|---|---|
<title> | The blue link in search results and the browser tab. About 50 to 60 characters. |
meta name="description" | The summary under the link. About 70 to 155 characters. |
link rel="canonical" | The main address of the page, when it can be reached in several ways. |
og:title, og:description | The title and summary on share cards. Can be shorter and punchier than the search versions. |
og:image | The picture on share cards. A full https:// address, ideally 1200 × 630. |
og:image:width, og:image:height | Let apps lay out a large card before they’ve downloaded the image. |
og:url, og:type | The page’s main address, and what it is: usually website or article. |
twitter:card | summary_large_image for a big picture, or summary for a small square one. |
meta charset, meta name="viewport" | Not for previews, but every page needs them: the text encoding, and sensible scaling on phones. |
Titles and descriptions: characters or pixels?
Search engines cut titles by how wide they are on screen, not by counting characters. On desktop there’s room for about 580 pixels, which is roughly 55 to 60 characters of ordinary text. A title in capitals, or with lots of W and M, runs out sooner. This tool estimates the width with typical font measurements, so a title near the limit might fit or might not.
Descriptions are cut at about 155 to 160 characters on desktop, and fewer on phones. Put the words that matter first in both, so a cut doesn’t lose them. Search engines also rewrite titles and descriptions when they think other text from the page fits a search better. A good, accurate tag makes that less likely, but you can’t prevent it. To count characters in any text, try the character counter.
Open Graph in a nutshell
Open Graph is a set of <meta property="og:…"> tags that almost every app reads when someone shares a link: social networks, chat apps, email and note-taking tools. A minimal set looks like this:
<meta property="og:type" content="website">
<meta property="og:url" content="https://www.example.com/page/">
<meta property="og:title" content="A short, clear title">
<meta property="og:description" content="One or two sentences about the page.">
<meta property="og:image" content="https://www.example.com/share.png">
<meta property="og:image:width" content="1200">
<meta property="og:image:height" content="630">
<meta name="twitter:card" content="summary_large_image">The image is the part that goes wrong most often. Apps download it from their own servers, so it must be a full address that anyone can reach, not /images/share.png and not behind a login. If the address has spaces or odd characters, the URL encoder shows how it should be written.
Common mistakes
- Relative image addresses.
/share.pngworks in a browser, but not for an app fetching your page from somewhere else. name=instead ofproperty=on og: tags. Many apps accept either, but not all.- Two of the same tag, often one from a theme and one from a plugin. Apps don’t agree on which one wins.
- A leftover
noindexfrom a staging site, which asks search engines not to list the page at all. - Tags added by JavaScript. Most apps that build share cards don’t run JavaScript, so tags must be in the HTML your server sends. If you copied the HTML from DevTools, check the same tags are in View Source too.
- Forgetting to escape. A quote inside
content="…"ends the value early. Write it as", or use curly quotes. The corrected block always escapes for you.
Writing a page in Markdown? Convert it with the Markdown to HTML converter, then check its head here.
Questions people ask
Why can’t I just enter my URL?
How long should a title tag be?
How long should a meta description be?
What size should an og:image be?
I fixed my tags but the share card hasn’t changed. Why?
?v=2, to the link you share also makes most apps fetch it fresh.Do I need twitter: tags as well as Open Graph?
twitter:card to choose the card size. Add twitter:title or twitter:image only if you want something different there.