Meta Tag Checker
The Meta Tag Checker extracts supported search, indexing and social metadata from up to 10 fetched pages and groups each value by source.
What the Meta Tag Checker checks
Extract every supported title and meta description from the fetched source, report each value and measured text length, and flag missing, empty or multiple page-level declarations. Length guidance is an editing aid; the checker does not predict a query-dependent search snippet or truncate the live metadata.
Group supported robots directives and canonical declarations by source, then route specialist conflicts to their dedicated checkers without treating either signal as proof of search-engine selection.
Inventory supported Open Graph and Twitter Card properties found in the fetched page, identify missing core preview values and show editable text-based previews without fetching remote images.
Keep extracted values, duplicate positions and issue identities tied to the exact fetched response. A single-page result does not guess whether titles or descriptions repeat elsewhere on the site.
When to use this tool
Run the Meta Tag Checker before publishing a template or when search and social previews expose missing, duplicate or unexpected metadata.
Example
Example: inspect https://example.com/pricing to review its title, description, canonical, Open Graph and Twitter Card values.
Issues and fixes
When a supported title, description or social property is absent or empty, add one accurate page-specific value where that element is appropriate. Publish the template change and fetch the page again; a preview editor alone does not alter the live response.
When the source contains multiple title or canonical declarations, use the reported evidence positions to find the responsible component, plugin or template. Retain one intended value so consumers do not have to choose between competing declarations.
Use the Noindex Checker when indexing directives conflict and the Canonical Tag Checker when canonical values differ across HTML or HTTP sources. This inventory identifies the metadata; the specialist result supplies the evidence and bounded remediation for that signal.
What the result includes
The report groups supported metadata, identifies page-level issues and provides editable search and social text previews with corrected HTML.
Limitation: The Meta Tag Checker reads raw fetched source metadata for up to 10 public pages. It does not execute JavaScript, fetch social images, crawl the site for duplicate values or reproduce a search engine’s query-dependent snippet and canonical selection. Network, redirect, authentication, content-type and response-limit failures remain inconclusive fetch evidence. Length measurements and text previews are editing aids rather than guaranteed display boundaries. Duplicate warnings apply only to declarations found on one inspected response, while Open Graph and Twitter Card findings describe supported preview metadata rather than direct ranking signals.
Frequently asked questions
Does Google always use the supplied meta description?
No. The Meta Tag Checker reports the description supplied by the fetched page, while Google can generate a different snippet for a query. Treat the extracted value as page evidence, then write a concise description that accurately represents the page rather than expecting a fixed search-result display.
Are Open Graph and Twitter Card tags search-ranking signals?
This checker does not classify social metadata as a direct search-ranking signal. Open Graph and Twitter Card properties primarily control supported social previews. The report inventories those values separately from robots and canonical metadata so social presentation does not become an unsupported indexing claim.
Monitor URLs over time
Turn a one-off diagnostic into ongoing index monitoring and change alerts.