Design tool
Meta Tag and Open Graph Preview Builder
Preview how a page looks in Google, Facebook, X and LinkedIn, then copy ready-made title, description, Open Graph and Twitter tags or a Next.js metadata object.
Free, no sign-up. Runs in your browser; nothing is uploaded.
Page details
Leave empty to use the page URL.
Best size is 1200 by 630 pixels. The image is loaded from the address you type, nothing is uploaded.
Hex value such as #2563eb.
Google search result
Title: 0/60 - Empty
Estimated width: 0px of about 580px
Description: 0/160 - Empty
Your meta description appears here. Write one or two sentences that tell people what they will find on the page.
Facebook share
X card (large image)
LinkedIn post
HTML for your <head>
<meta name="robots" content="index, follow"> <meta property="og:type" content="website"> <meta property="og:locale" content="en_US"> <meta name="twitter:card" content="summary_large_image">
How to use the meta tag and open graph preview builder
Write the tags once, check them everywhere
A page is shared and found in several places, and each one reads a slightly different set of tags. Fill in the form once and the previews show how the page will look in Google, Facebook, X and LinkedIn before you publish.
Start with the three that matter most
- Title. Put the main topic first and the brand last. Keep it under about 60 characters, because Google cuts titles by pixel width and wide letters such as W and M use up room faster than narrow ones.
- Description. Write one or two plain sentences that say what the visitor gets. Google may rewrite it, but a clear description gives it a good starting point. Stay near 120 to 160 characters.
- Image. A 1200 by 630 pixel image served over https works on every network. Use large, simple shapes and little text.
What the other fields do
- Canonical URL tells search engines which address is the main version when the same page is reachable in several ways, such as with tracking parameters.
- robots controls indexing and link following. The default, index and follow, is right for almost every public page.
- og:type is website for most pages and article for blog posts.
- Locale helps networks pick the right language, for example en_US or fr_FR.
- Theme colour tints the browser toolbar on supported mobile browsers.
- X handle credits your account in cards.
Using the output
Choose HTML tags and paste the block inside the <head> of your page. If you use the Next.js App Router, choose Next.js metadata and paste it into a layout.tsx or page.tsx file. Theme colour is exported separately as viewport, as current Next.js versions expect.
After you publish
Social networks cache previews, so a changed image may not show at once. Use each network's own debugger to refresh the cache, and re-check any page whose title or image you change.
Frequently asked questions
How long should a title and description be?
Aim for a title under about 60 characters (roughly 580 pixels wide) and a description of about 120 to 160 characters. Longer text is cut off with an ellipsis in search results. The counters and red warnings show when you cross these lines.
What size should the Open Graph image be?
Use 1200 by 630 pixels (a 1.91 to 1 ratio) served over https. Keep key text away from the edges, because Facebook, X and LinkedIn each crop slightly differently. Keep the file under about 5 MB.
What is the difference between summary and summary_large_image?
summary shows a small square thumbnail beside the title and text. summary_large_image shows a wide image above them and is the better choice for most articles and landing pages.
Does this tool fetch my page?
No. Nothing is requested except the image you type, which your browser loads to draw the preview. All tags are generated from what you enter.
When should I use noindex?
Use noindex for pages you do not want in search results, such as thank-you pages, internal search results or staging copies. Do not use it on pages you want to rank.
Are special characters escaped?
Yes. Ampersands, quotes and angle brackets in titles and descriptions are converted to HTML entities so the tags stay valid.