Meta Tag Checker
The Meta Tag Checker reads the page metadata on up to 10 URLs and reports each title tag, meta description, robots directive, canonical URL, Open Graph tag and Twitter Card with its source. Page metadata tells search engines and social platforms how to interpret and preview a page.
What page metadata does
Page metadata describes a page to the systems that display it, so a search engine can build a result entry and a social platform can build a link preview from values the publisher supplies.
Each element covers a different surface: the title tag names the page, the meta description summarizes it, robots and canonical values describe how it should be treated in search, and Open Graph and Twitter Card values describe how it should be presented when shared.
A supplied value is a proposal rather than a guaranteed display. A search engine can replace a title or description with text from the page when the supplied value does not match the query well.
Where page metadata lives in the source
Search, indexing and social values appear together in the document head, and each one controls a different surface.
Search and indexing metadata
<title>Blue Widget Pricing</title><meta name="description" content="Blue widget pricing per unit, in bulk and on subscription."><link rel="canonical" href="https://example.com/pricing"><meta name="robots" content="index, follow">Social preview metadata
<meta property="og:title" content="Blue Widget Pricing"><meta property="og:image" content="https://example.com/blue-widget.jpg"><meta name="twitter:card" content="summary_large_image">Title tag and meta description
The title tag names the page and appears as the clickable line in a search result, and the meta description supplies the summary text a search engine can use below it.
Writing a title tag
A title that identifies the page and its subject without repeating boilerplate distinguishes the page from every other page in the result list. A duplicate title across several pages removes the distinction a search engine uses to tell them apart.
Writing a meta description
The meta description does not influence ranking as a direct signal, and it can still change what a searcher reads before clicking. A description that accurately summarizes the page earns a more predictable result entry than an empty or generic value.
Avoiding template defaults
Both values are page-level. A template that emits the same description on every URL leaves each page competing with the same summary text.
How length affects search and social previews
Titles and descriptions are truncated by rendered width rather than by a fixed character count, so a value that fits in one result can be cut in another.
Truncation is measured in pixels
Search results truncate at a measured pixel width, which means character capacity moves with the letters used. A title built from wide characters reaches the cut sooner than one built from narrow characters at the same length.
Social previews truncate sooner
Social platforms apply their own truncation and layout to Open Graph and Twitter Card values, with less room than a search result in most card layouts. A title that fits in search can still be cut in a social preview.
Measuring before publishing
The Meta Tag Checker measures each extracted text value and renders a text preview, so a length problem is visible before publishing rather than after the page appears in results.
Open Graph and Twitter Card metadata
Open Graph and Twitter Card elements control how a shared link is presented on social platforms, and they are not direct search-ranking signals.
Core Open Graph values
The core Open Graph set covers the title, description, URL, and image of a shared page. A platform that finds no Open Graph values falls back to values it derives from the page, which makes the preview unpredictable. The image is the value most likely to be dropped, because a link preview expects a landscape asset roughly 1200 by 630 pixels; a square logo or a missing og:image leaves the platform to choose a fallback image.
Twitter Card values
Twitter Card properties describe the same preview for platforms that read them. A page without them depends on a fallback that may show a wrong title or a missing image.
Metadata added by client-side script
Metadata injected by client-side JavaScript is not seen in the raw fetched response, and this checker does not execute JavaScript. A tag that appears in the browser inspector can therefore be missing from what a crawler reads, which is why a value that looks correct on the page can be absent from search results and social previews. Render or view the page source, or inspect the server response, to confirm which metadata is actually served.
Metadata that overlaps other checkers
Robots directives and canonical URLs are metadata, and each one also has a dedicated checker that supplies deeper evidence for that signal.
Inventory here, decide there
The Meta Tag Checker inventories the robots and canonical values it finds so a missing declaration is visible in one pass across several pages. The Noindex Checker reads every applicable directive with its crawler scope, and the Canonical Tag Checker reports declared and resolved targets with their sources.
Scope of a duplicate warning
Use the inventory to find which pages carry a value and the specialist tool to decide whether the value is correct. A duplicate warning from this checker applies to declarations found on the inspected response, and it does not report whether the same value repeats elsewhere on the site.
Metadata elements and the surface each one controls
| Element | Controls | Where it appears | Dedicated checker |
|---|---|---|---|
| Title tag | The page name in a result entry | Search results and browser tabs | This tool |
| Meta description | The summary text under a result | Search results | This tool |
| Robots directive | Whether a crawler may index or follow | Search engines | Noindex Checker |
| Canonical URL | The preferred address for the content | Search engines | Canonical Tag Checker |
| Open Graph values | Title, description and image in a shared link | Social platforms | This tool |
| Twitter Card values | The shared link preview layout | Platforms that read the card properties | This tool |
Using the Meta Tag Checker
What the Meta Tag Checker checks and reports
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 the Meta Tag Checker
Run the Meta Tag Checker before publishing a template or when search and social previews expose missing, duplicate or unexpected metadata.
How to use the Meta Tag Checker
Example: inspect https://example.com/pricing to review its title, description, canonical, Open Graph and Twitter Card values.
Common Meta Tag Checker 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.
Understanding your Meta Tag Checker results
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.
How long should a title tag and meta description be?
Google renders a title in a result entry at roughly 580 pixels, which is about 60 characters for average-width text, and a meta description at roughly 920 pixels, which is about 155 characters. Both cut earlier when a value is built from wide letters, so treat the character count as a diagnostic and the preview as the decision. Aim for a title that carries the page subject within the first few words and a description that states the page value in one sentence.
Should the title tag match the H1?
A title and an H1 that describe the same subject are consistent, and they do not need identical wording. The title carries the query match in a result entry, and the H1 names the page for a reader. Repeating one string verbatim in both places wastes the chance to cover a related phrasing.
Do the meta keywords still matter?
Search engines do not use a meta keywords element as a ranking signal. The Meta Tag Checker inventories supported search, indexing and social metadata, so a keywords element is not reported as a value that affects a result.
Monitor URLs over time
Metadata breaks when a template or plugin release overwrites a value. Monitor your key pages and catch a missing title, description or preview image before it reaches search or social.