Check the metadata crawlers receive—not only what DevTools shows.

Inspect core SEO tags in both the initial HTML and rendered browser page. Find missing, conflicting or JavaScript-injected fields before they cause inconsistent indexing and snippets.

Report includesEvidence based

Metadata with context and evidence

Title and description

Presence, exact text and measured character length.

Canonical URL

The declared canonical in raw and rendered HTML.

Robots directives

Noindex and related page-level instructions.

Headings

Primary H1 content and heading counts for page structure.

Results describe the submitted URL and separate measured evidence from anything still unverified.

What the check covers

Useful answers, with the limits made clear.

Raw tag presence

Confirm that essential fields exist before JavaScript runs.

Rendered consistency

Detect fields changed or injected by the client application.

Length guidance

Show measured lengths as guidance, without treating arbitrary limits as ranking rules.

Indexing controls

Surface canonical and noindex signals that can change indexing behavior.

Why this matters

Presence and consistency matter more than a magic character count

Search engines can rewrite titles and descriptions, and there is no universal character limit that guarantees display. Useful checks should show the actual values and lengths, then explain whether they are missing, unusually short or likely to truncate.

For JavaScript sites, the location of a tag matters too. Comparing raw and rendered HTML reveals whether crawlers must execute JavaScript before receiving essential page metadata.

Questions answered

Meta Tag Checker FAQ

What title length is best?+

There is no fixed ranking limit. Concise, descriptive titles are usually easier to display and understand. The report measures length and focuses first on relevance, uniqueness and presence.

Does Google always use the meta description?+

No. Google may generate a different snippet based on the query. A strong description still provides useful context and can influence how the page is presented.

Should there be exactly one H1?+

One clear primary H1 is a practical convention, but multiple H1 elements are not automatically a penalty. The report shows the evidence so you can judge the structure.

Why compare raw and rendered tags?+

JavaScript can add or change tags after the first response. The comparison identifies crawlers that may receive incomplete or conflicting metadata.

Continue checking

Related free tools

View all tools →