{{ summaryTitle }}
{{ summaryValue }}

{{ summaryLine }}

{{ badge.label }} {{ badge.value }}
Use search plus social for most public pages; narrow the package only when another system owns part of the head.
Write a concise title that identifies this page rather than only the brand.
Use a unique, natural summary. Publish checks flag very short, long, or duplicated copy.
Enter the final public address including the scheme and path. URL fragments are removed.
Use the concise brand label visitors already recognize.
Social titles stay page-specific; this choice affects the HTML title element.
Website is the general default; use a more specific type only when it matches the page.
Use a public HTTPS image sized for link previews, commonly around 1200 × 630 pixels.
Choose the compact card when the page does not have a suitable large preview image.
Choose noindex only when this exact page should stay out of search results.
Describe the preview image itself. Leave blank when no social image is emitted.
Enter the real account handle or leave the field blank.
Use an ll_CC-style value, or leave blank to omit the tag.
Use #RRGGBB, or keep the neutral blank default to omit theme-color.
Prefer an HTTP Referrer-Policy header when the server configuration is under your control.
{{ values.head_markup }}

The chart renderer is unavailable. Exact system counts remain available in the tag ledger and CSV export.

SystemTagContentReview noteCopy
{{ row.system }}{{ row.tag }}{{ row.content }}{{ row.note }}
LevelAreaEvidenceNext actionCopy
{{ row.level }}{{ row.area }}{{ row.evidence }}{{ row.action }}
Open Graph Tag Generator Generate Open Graph and X card tags for a public page with useful image hints, article fields, and crawler-focused review warnings.
Open Graph Tag Previewer Preview social share cards from pasted HTML or a public URL and check metadata fallbacks, image fit and canonical identity with advisory scores.
Hreflang Tag Generator Build reciprocal hreflang clusters from locale and URL rows with HTML, sitemap, or HTTP output plus self-reference and duplicate checks.
HTML Boilerplate Generator Build an HTML starter document with semantic body structure and escaped metadata, then review script loading choices and publication warnings.

A page can look correct in a browser and still produce a vague search result, the wrong shared-link image, or conflicting indexing signals. Much of that public summary begins in the document head, where short pieces of metadata identify the page, its preferred URL, its crawl policy, and the facts a social preview may use.

These tags influence other systems; they do not control them absolutely. Google may build a title link from the title element, visible headings, prominent page text, links, and other signals. A meta description is a candidate for the search snippet, not guaranteed display copy. Social services fetch their own preview data and may keep an older cached image or title after the page changes.

Title element
A concise page name used by browsers and considered by search engines.
Meta description
A page-specific summary that may be used in a search snippet or social preview.
Canonical URL
The preferred address among duplicate or parameterized versions of substantially the same page.
Robots policy
Indexing and crawling instructions for compliant search crawlers.

Search metadata and social metadata overlap but serve different consumers. Open Graph properties describe a shared object with a title, type, URL, and image. X card tags choose a card style and provide parallel title, description, image, and account fields. Keeping the page title, canonical URL, and preview content aligned reduces surprises when the same link appears in several places.

The most consequential mistake is often a contradiction rather than a missing optional tag. A canonical URL can point away from the page while internal links point back. A launch page can retain noindex from staging. A large-image card can name no image, or an image can require authentication that a crawler does not have. Generated markup should therefore be checked against the final public response, not only the draft text.

Length checks are editorial warnings, not search-engine limits. Result layouts vary by device and query, and search services may rewrite or truncate copy. A short, accurate, unique summary is more dependable than padding text to reach a particular character count.

How to Use This Tool:

Build the package from facts that match the final public page.

  1. Choose Head package. Use Search + social preview for a normal public page; choose a narrower package only when another template or service owns the omitted tags.
  2. Write the Page title and Search description, then enter the absolute Canonical URL. Use the final scheme, host, and path rather than a preview URL or tracking variant.
  3. Add social facts when social metadata is enabled. Choose the matching page type, provide a public HTTPS image, and use summary if no suitable large preview image exists.
  4. Review Robots policy and Publish checks. Treat noindex, plain HTTP, missing social images, malformed locale or color values, and length notes as reasons to verify before copying the head markup.

Interpreting Results:

A clear publish-check list means the entered values satisfy the generator’s format and editorial rules. It does not prove that the canonical target returns a successful response, the preview image is crawlable, the page is indexable elsewhere in the stack, or a platform will display the suggested title and description.

Resolve Warning rows before publication unless the choice is intentional. Read Review rows as prompts for judgment rather than failures. After deployment, fetch the live HTML, follow redirects, inspect the final head, and test the public URL with the relevant search or social preview tools.

Technical Details:

Meta-tag generation is a structured transformation followed by a rule-based review. Required text and URLs are normalized first, the selected package determines which tag families are emitted, and all inserted values are escaped for HTML text or double-quoted attributes.

Transformation Core

Package Generated groups Important behavior
Search + socialFoundation, Search, Open Graph, and X CardUses one page description and canonical URL across the applicable groups.
Search onlyFoundation and SearchEmits the title element, description, robots policy, canonical link, and valid optional browser metadata.
Social onlyOpen Graph and X CardEmits social titles without site-name branding in the title text.

The HTML title is either page title only, page title followed by site name, or site name followed by page title. A pipe separates the two parts. The canonical and image fields must be absolute HTTP or HTTPS URLs; URL fragments are removed. An optional X handle is normalized to one leading @ followed by up to 15 letters, digits, or underscores.

Search packages always include UTF-8 character encoding and the responsive viewport baseline. Valid optional theme color and referrer-policy values are emitted only for search packages. Social packages emit Open Graph title, description, type, and URL, plus image, site name, locale, and image alternative text when valid values are available. X card tags mirror the page-specific social content and selected card type.

Rule Core

The review bands below are editorial heuristics, not ranking factors or platform limits.

Check Ready Review Warning
Composed HTML title20 to 65 charactersFewer than 20 or 66 to 90More than 90
Description70 to 160 charactersFewer than 70 or 161 to 200More than 200

A title repetition note appears when the same word longer than three characters occurs more than twice. The description is flagged when it contains the full page title. Plain HTTP canonical or image URLs produce warnings; noindex always produces a warning because exclusion must be deliberate. A six-digit #RRGGBB pattern is required for theme color, while Open Graph locale is reviewed against a language code with an optional uppercase territory such as en_US.

A missing social image prevents image tags from being emitted and conflicts with a large-image card. Missing image alternative text is a review note when an image exists. These checks examine the entered values only; they do not download the image, follow the canonical URL, or inspect the deployed page.

Accuracy and Privacy Notes:

Generation and review happen in the browser. The output is syntactically escaped markup, not a live-site audit. Search and social services can ignore, rewrite, cache, or combine metadata with other page signals, so the final public response remains the source to verify after deployment.

References: