Meta Tag Analyzer
Inspect HTML metadata values, duplicates and robots conflicts
Inspect parsed HTML head fields, duplicates and common robots conflicts. There is no SEO score; title/description lengths are descriptive counts. Missing robots meta is not an error, and intentional noindex can be appropriate. Scripts, live pages and social previews are not evaluated. Input limit: 1 MiB.
This tool processes input in the page, does not request embedded addresses, and does not save input drafts. Site analytics records actions and summary information only.
The full guide also includes pitfalls, worked examples, snippets, FAQs, and related tools for checking results or troubleshooting.
About this tool
Inspect the supplied HTMLβs parsed head for title, description, canonical and optional common Open Graph/Twitter fields. The report shows actual values and duplicate declarations, checks common social URL/card shapes, and inspects general and Google-scoped robots instructions, including common index/noindex and follow/nofollow conflicts. Missing robots meta is not an error; explicit noindex may be intentional. Title and description character counts are descriptive because Google has no fixed character limit. No SEO score or ranking prediction is provided. The browser parser may repair malformed HTML, so this is not complete markup validation. Scripts, HTTP headers, live pages, image accessibility, full app/player cards and search indexing are not evaluated. Input limit: 1 MiB. Input is not saved as a draft; site analytics records actions and counts without the HTML.
Failure Clinic (Common Pitfalls)
Adding a robots tag only to improve a score
Cause: There is no score here. Missing robots meta is not an error and adds no restriction through that tag.
Fix: Add indexing directives when the page needs them; check both HTML and HTTP header rules.
Expanding a concise Chinese title to hit an English character target
Cause: Google has no fixed title or description character limit; displayed text depends on context and device width.
Fix: Use clear, specific text suited to the page. Character counts are observations, not search-ranking grades.
Scenario Recipes
Inspect generated head markup before publishing
Goal: See actual metadata values and conflicting declarations in a saved HTML response.
- Paste the HTML response or a head fragment. The parser may repair malformed HTML, so this is not a markup validator.
- Review duplicate title/description/canonical fields and general or Google-scoped robots instructions.
- Enable common social-field checks when needed. Verify HTTP headers, JavaScript-rendered changes and remote previews separately.
Result: A field report with observations and warnings, without a synthetic SEO score.
Production Snippets
A later noindex is not canceled by an earlier index
html
<meta name="robots" content="index,follow">
<meta name="ROBOTS" content="NOINDEX">
<!-- Google treats name/content case-insensitively and applies
the more restrictive applicable instruction: noindex.
Whether noindex is appropriate depends on this pageβs purpose. -->Frequently Asked Questions
Why is there no SEO score?
Presence and length checks cannot establish content quality, ranking or click-through rate. The report lists observations and concrete conflicts instead of assigning an unsupported grade.
Is a missing robots meta tag an error?
No. Its absence adds no restriction through that tag. HTTP headers and other indexing factors may still matter and are outside this source-only analysis.
How are duplicate robots instructions handled?
Names and content are read case-insensitively. The report highlights common restrictive/permissive conflicts and notes that Google applies the more restrictive applicable rule. It does not evaluate every possible directive.
Are title and description lengths hard SEO limits?
No. Google has no fixed character limits for them. Counts help editing, but display depends on the content and device width.
Can I paste only a head fragment?
Yes. The browser HTML parser creates a document from the supplied fragment. Its repairs may move or ignore malformed markup, so inspect the original response when placement is in doubt.
Does it confirm social preview or live indexing?
No. It checks common fields and URL shapes without fetching images or pages. Remote previews, app/player requirements, rendered JavaScript and indexing need separate verification.
Keep browsing