Free tools
Generate SEO titles, meta descriptions, canonical tags, robots directives, Open Graph, Twitter/X cards and hreflang — with approximate search and social previews. Everything runs in your browser.
Loading meta tag generator…
A meta tag generator builds the HTML head metadata that search engines and social platforms read. This Web6 tool creates titles, descriptions, canonical and robots tags, Open Graph, Twitter/X cards, and hreflang — then validates conflicts and shows approximate previews entirely in your browser.
The title tag names the page. Put the most useful description early and add the brand naturally. Character counts help, but pixel-width estimates better approximate display. There is no guaranteed truncation point, and Google may rewrite titles.
A meta description summarizes the page for potential snippets. Write clear, unique copy. Google may replace it with on-page text when another snippet better matches the query. Meta keywords are ignored by major modern search engines and are usually unnecessary.
Canonical tags suggest the preferred URL among duplicates; they are hints, not absolute directives. Robots meta controls indexing and link following for the current page, while robots.txt controls crawl access. Do not confuse the two.
Open Graph tags shape shared-link previews on many platforms. Twitter/X Card tags refine card type and handles; platforms may fall back to Open Graph. A common image size is 1200×630. Platforms cache previews and may crop images differently.
Hreflang connects language and region alternate URLs. Use absolute URLs, include self-references, keep reciprocal sets consistent, and align with canonicals. This tool validates codes and duplicates but does not crawl live reciprocal implementations.
Place tags in the document head. In Astro, pass strings into your layout or SEO component. In Next.js, prefer the Metadata API. On Shopify and WordPress, audit theme and plugin output first — stacking duplicate titles or canonicals creates conflicts.
Check for missing titles, duplicate tags, robots conflicts, invalid URLs, weak social images, and hreflang issues. Use approximate search and social previews here, then confirm with platform debuggers when needed. Previews are never exact guarantees.
Common issues include multiple titles or canonicals from themes and apps, tracking parameters on canonicals, missing image alt text, conflicting index/noindex directives, treating meta keywords as a ranking factor, and assuming Google will always show your exact title or description.
Clear titles and descriptions help users and systems understand a page. Metadata does not guarantee rankings, rich results, or AI citations. Accurate, visible page content still matters most.
FAQ
Answers about titles, descriptions, canonicals, robots, Open Graph, Twitter cards, hreflang, privacy, and previews.
A meta tag generator helps you create HTML head tags such as title, meta description, canonical, robots, Open Graph, Twitter/X cards, and hreflang, then preview and validate them before publishing.
Yes. The Web6 Meta Tag Generator is free, runs in your browser, and does not require an account.
No. Metadata is generated locally in your browser. Web6 servers do not receive your titles, descriptions, URLs, or social images. Templates are saved only in your browser when you choose Save locally.
The HTML <title> element defines the primary document title. It often appears as the clickable search result title and in browser tabs, though search engines may rewrite it.
There is no single fixed character limit. This tool estimates pixel width and character count as guidance. Keep titles descriptive and concise; truncation varies by device and query.
A meta description summarizes the page in the HTML head. It can influence the search snippet, but Google may choose other on-page text when it better matches the query.
Aim for a clear summary in a typical display range (often around 70–160 characters as soft guidance). Longer text may truncate. Exact display varies.
No. Google may rewrite title links based on the query, page content, and other signals. Treat your title as a strong suggestion, not a guarantee.
No. Google may generate a snippet from page content when it better matches the search. Meta descriptions remain useful when they accurately summarize the page.
A canonical link suggests the preferred URL when similar or duplicate pages exist. It helps consolidate signals but is a hint, not an absolute directive.
No. Canonical tags are hints. Search engines may choose a different canonical when signals conflict.
A robots meta tag gives crawlers page-level instructions such as index/noindex and follow/nofollow. It is different from robots.txt, which controls crawl access to URLs.
noindex asks crawlers not to show the page in search results. nofollow asks them not to follow links on that page. They can be combined but should be used intentionally.
Open Graph tags (og:*) describe how a page should appear when shared on platforms that read OG metadata, including title, description, image, and type.
Twitter/X Card tags control card style and content for shared links. Platforms may fall back to Open Graph when Twitter-specific tags are incomplete.
Open Graph is primarily for social sharing previews. It is not a substitute for title, description, and canonical SEO tags, though consistent messaging helps users and platforms.
A common general-purpose size is 1200 × 630 pixels (about 1.91:1). Platforms may crop differently, so keep important text in safe zones.
Hreflang annotations indicate language and regional alternate versions of a page so search engines can serve the appropriate URL to users.
Yes. Each language version should typically reference itself and the other versions. This tool does not verify reciprocal implementation on live pages.
Yes. Mark a row as x-default when you have a suitable default or language-selector landing page.
Yes. Paste HTML head content or upload an HTML/TXT file. The tool extracts title, description, canonical, robots, Open Graph, Twitter, and hreflang tags without executing scripts.
Yes. Compare up to four title and description variants with character counts and estimated pixel widths using transparent rule-based checks.
Yes, as an approximate search preview. It is not exact Google rendering and does not scrape live SERPs.
No. Previews are approximate. Search engines may rewrite titles, snippets, site names, and display URLs.
Yes. Approximate Facebook-style, LinkedIn-style, X/Twitter-style, WhatsApp-style, and generic cards are available. Platforms may cache or crop differently.
Platforms often cache link previews. Updating tags does not always refresh cached cards immediately. Use each platform’s debugger or wait for cache expiry.
Yes. Copy HTML groups, download HTML/TXT/JSON, export hreflang CSV, and download a validation report.
Yes. Generate tags and place them carefully in theme Liquid or SEO settings. Audit theme and app output first to avoid duplicate titles, canonicals, or Open Graph tags.
Yes. The install guide covers Astro layouts, Next.js Metadata API / next/head, React, Vue, Nuxt, Angular, WordPress, Webflow, and Wix patterns.
View page source, search for title/description/canonical/og/twitter/hreflang, review plugins and themes, then remove conflicts before adding new tags.
This tool creates metadata based on the information you enter. Search engines and social platforms may rewrite, truncate, cache, or ignore parts of the metadata. Generated previews are approximate and may differ from final appearance on Google, Facebook, LinkedIn, X, WhatsApp, and other platforms.