<title> · name=description
Page title & description
Describe the specific page. Google creates title links and snippets automatically and may use different page text; supplying these fields is not control over every result.
Small tags. A clearer first impression.
One workspace for search & social.
Build SEO, Open Graph and X tags from your page details. Preview the result, catch missing information, then copy clean HTML or a Next.js Metadata object—without an account.
Changes update your previews and code automatically. Nothing is saved after a reload.
The title, summary and preferred URL.
Include your brand only if needed. Character counts are editing aids, not Google limits.
Write a useful summary, not a list of keywords. Google may use different page text.
Used for rel=canonical and og:url. Include https:// and remove fragments; no page is fetched.
Used for og:site_name. It is not automatically added to your page title.
A public http(s) image URL, not a file on your computer. It is never fetched here.
Used for Open Graph and, by default, the X card. Blank optional tags are omitted.
Leave blank to use the page title. X also uses this unless overridden below.
Enter the actual image dimensions, not a target.
Language_TERRITORY, not hreflang.
A different X image needs its own alt text; it cannot use the local shared-image mockup.
Index/follow are defaults, not a command to get indexed. Noindex removes search eligibility; it does not make a page private.
-1: no limit; 0: no text snippet; positive integer: maximum characters. This does not set your meta description length.
Google ignores meta keywords for web ranking. This field does not perform keyword research.
Form text, pasted HTML and local preview images are processed in this tab, with no AI call or URL crawl. Reloading clears them. Site-wide services are covered by our privacy policy.
See the first impression
example.com
example.com › your-page
Your page title goes here
Describe what is on the page and why it is useful. Google may choose different text from the page.
Mockups, not live Google or platform results. Layouts, image crops, caching and rewritten text vary. The URL is never fetched; descriptions are omitted from our X mockup, not from your tags.
Choose a JPG, PNG or WebP to try the crop. Nothing is uploaded. You still need a publicly hosted image URL for the exported tags.
Add a page title to enable copy and download. This is a head fragment, not a whole HTML page.
Fill in your page details or choose an example. We will flag invalid URLs, missing social details and restrictive indexing settings.
From page details to usable code
Enter a page-specific title and summary, then its preferred URL. Or import a pasted HTML head and review the detected fields. Examples are fictional starting points; replace their URLs and copy.
Reuse the title and description for social cards or override them. Add the public image URL, alt text and actual dimensions. Use a local image to explore the crop without uploading it.
Fix format errors, review warnings, then choose HTML or Next.js output. Merge the fields into your current setup. Finally check the served page, not just this mockup.
Google's title-link guidance and snippet documentation do not set fixed 60- or 160-character limits. Displayed text is shortened to fit the result layout, and the snippet can change with the query.
Counts help you edit, not rank. Modern browsers count visible character clusters here; older browsers fall back to Unicode code points. Extra text whitespace is collapsed in the output. Input caps keep the editor responsive and are not search-engine limits. For approximate pixel measurements and comparing drafts, use the SEO Title Checker.
State the useful task or distinction naturally. Do not add “best,” “free” or a fresh year unless the page supports it. Our title-writing guide offers examples; confirm your final wording against the page itself.
The Open Graph protocol lists og:title, og:type, og:image and og:url as its core properties. Image alt text should describe what is shown. Width and height should match the actual hosted file; entering 1200 × 630 does not resize anything.
A 1200 × 630 canvas is a common starting point for a wide share image, not a universal platform requirement. This generator models wide Facebook/LinkedIn cards, a 2:1 large-image X card and a compact square X card. Actual crops, text and layouts can differ. Our Open Graph Preview is another manual mockup, not proof that a social crawler can access your file.
Local image selection is only a crop test. Host the image yourself, use its public HTTPS URL, and verify that the image is accessible without login. This tool does not test image-server responses, file size on the server or platform caches.
A worked example
This fictional accessibility guide uses a page-specific title, a canonical URL and one share image. The same wording feeds the Open Graph and X tags until you choose an override. Select the Article example above to edit it.
The code is generated by the same engine as the editor. Special characters such as ampersands and quotes are escaped in HTML attributes. No publication date, review rating or author profile URL is invented. Replace all example values before publishing.
For the wider head-markup context, see our meta tags guide with examples. A product-page example uses website metadata here; it is not product structured data.
<!-- Page metadata -->
<title>How to Plan an Accessible Website</title>
<meta name="description" content="A practical guide to navigation, readable content, keyboard access and testing. Build accessibility into your next website from the start.">
<meta name="author" content="Alex Morgan">
<link rel="canonical" href="https://example.com/guides/accessible-websites">
<!-- Open Graph -->
<meta property="og:type" content="article">
<meta property="og:title" content="How to Plan an Accessible Website">
<meta property="og:description" content="A practical guide to navigation, readable content, keyboard access and testing. Build accessibility into your next website from the start.">
<meta property="og:url" content="https://example.com/guides/accessible-websites">
<meta property="og:site_name" content="North Studio">
<meta property="og:locale" content="en_US">
<meta property="og:image" content="https://example.com/social/accessibility.jpg">
<meta property="og:image:alt" content="A keyboard beside a website accessibility checklist">
<meta property="og:image:width" content="1200">
<meta property="og:image:height" content="630">
<!-- X / Twitter Card -->
<meta name="twitter:card" content="summary_large_image">
<meta name="twitter:title" content="How to Plan an Accessible Website">
<meta name="twitter:description" content="A practical guide to navigation, readable content, keyboard access and testing. Build accessibility into your next website from the start.">
<meta name="twitter:image" content="https://example.com/social/accessibility.jpg">
<meta name="twitter:image:alt" content="A keyboard beside a website accessibility checklist">Merge the HTML fragment inside the page's head. Replace existing title, description, canonical and social values rather than pasting a second block. Keep styles, scripts, verification tags and security settings that this tool does not generate.
Prefer the theme or SEO plugin's per-page title, description and social fields where available. Paste plain text into those fields, not escaped HTML. Avoid running two metadata providers that both output conflicting tags. Do not paste head markup into the visible post body.
Merge the Metadata output into your existing server page or layout export. Do not add a second export or combine it with generateMetadata. Next.js handles charset and viewport. Preserve language alternates and review parent settings, null overrides, file-based images and framework fallbacks in the final HTML.
Use the framework's supported head/metadata mechanism or your builder's SEO settings. HTML and Next.js output are different formats; a Next.js export is not generic React code. Confirm what your deployed server returns to crawlers after you save.
Check syntax and configuration
Use page source and your platform's inspection tools to confirm one intended title, description and canonical. Compare HTML robots tags with HTTP X-Robots-Tag headers; this generator cannot see either on your live site. Blocking a URL in robots.txt can prevent a crawler from discovering a noindex tag. Noindex is not a substitute for canonicalization or access control.
Measure real outcomes
Work through the pre-publish SEO checklist, then compare relevant page/query impressions, clicks and position using our Search Console guide. Account for device and query changes. Correct markup is a useful foundation, not evidence that a ranking or traffic increase has happened.
Enter your title, description and canonical page URL, then add a public social image URL. Choose the tag groups you need, review the checks and previews, and copy HTML or Next.js Metadata. Replace existing values rather than adding duplicate tags. The generator formats your text; it does not write or publish content for you.
This version does not crawl a URL or call an AI service. Use Import HTML to read supported tags from pasted page source locally, review what was found, then replace the editor fields. Relative URLs need to be made absolute. Unsupported tags are not retained, so keep other required settings in your original head.
Correct metadata helps describe a page and communicates indexing preferences, but it does not guarantee ranking, indexing or clicks. Google may rewrite titles and snippets and choose a different canonical. Google ignores meta keywords for web ranking. Evaluate real page and query results in Search Console after publishing.
Open Graph describes a share object using properties such as og:title, og:type, og:image and og:url. X cards use the twitter: prefix, including twitter:card. This tool can reuse the same text and image or provide X-specific overrides. Actual card layouts, image crops and cache refreshes are controlled by the receiving platform.
The generator is free without an account. Its form text, pasted HTML and optional local image preview are processed in your tab; no URL is fetched or file uploaded by the generator. Reloading clears the editor. Site-wide analytics and other services follow ByteVerse's privacy policy. Avoid pasting confidential material into public tools.
Measure title characters and approximate pixels, preview desktop/mobile snippets and compare three drafts.
Mock up social share cards from your title, description and image. This is not a live URL audit.
Build JSON-LD for articles, products, businesses and more; validate eligibility before publishing.
Build crawler directives with user-agent groups, allow/disallow rules and sitemap URLs.