Snippet Inputs
Audit the title and meta description with character counts and practical warning bands, while accounting for Google's ability to rewrite either field.
Meta Tags Checker
TL;DR: Meta Tag Checker checks analyze title, description, canonical, robots, and og tags. so you can confirm the current issue, understand when it matters, and move directly into the next fix without leaving the browser.
Audit your page metadata in seconds.
Updated
Loading tool interface...
Title and meta description extraction with character counts Meta robots and X-Robots-Tag inspection Canonical extraction and URL resolution Viewport and hreflang metadata reporting Open Graph and Twitter Card tag coverage Open Graph image response type and size check Optional competitor title and description length deltas
What does Meta Tag Checker do?
The Meta Tags Checker fetches a live URL through the PageChecks server and reads the metadata in the returned HTML. One report covers the document title, meta description, meta robots, `X-Robots-Tag`, canonical URL, viewport, hreflang, Open Graph, Twitter Card, and Open Graph image response. An optional competitor URL adds title-length and description-length deltas without changing the primary audit.
Write a distinct title for the page: The `<title>` element supplies a strong candidate for the search result title link. Use roughly 50 to 60 characters as an editing range, place the main topic early, and add a detail that separates the page from other results. The checker flags titles below 30 or above 60 characters. Character count is a warning, not a rendering guarantee: Google measures displayed width and can generate another title from the H1, visible text, or links when the supplied title is repetitive or mismatched.
Use the description to earn the click: A meta description is not a direct Google ranking factor, but it can become the result snippet for a relevant query. Draft around 140 to 155 characters so the main answer and benefit appear before likely truncation. PageChecks treats 120 to 160 characters as its broader acceptable band. Google may replace the description with a passage from the page when that passage answers the search more directly.
Keep the H1 and title aligned: The title can be concise while the H1 is more descriptive, but both should identify the same page topic. A title about a pricing calculator paired with an H1 about a general guide gives search engines competing labels. Do not repeat the same site-wide title or append so much boilerplate that the unique topic appears last.
Check canonical output after redirects: The report extracts the canonical and resolves relative values against the fetched page URL. An indexable page should normally point to one preferred absolute URL. Fix HTTP-to-HTTPS, host, path, trailing-slash, and query mismatches. A canonical that points to a redirect or an unrelated page needs a dedicated canonical check because the metadata report does not replace target-health analysis.
Read every robots signal: `index,follow` permits the default behavior, while `noindex` asks a compliant search engine not to retain the page in its index. The same restriction can arrive in a meta robots tag or an `X-Robots-Tag` response header. A permissive value does not cancel an applicable `noindex` elsewhere. Check production pages after launch because a staging noindex can survive a template or header deployment.
Return critical tags in the initial HTML: This checker analyzes the server response and may not see a title, canonical, or robots tag inserted only after client-side JavaScript executes. Server-render these signals when possible. That also keeps diagnostic tools, social crawlers, and search crawlers from receiving different metadata depending on script execution.
Set a mobile viewport explicitly: A standard responsive declaration is `<meta name="viewport" content="width=device-width, initial-scale=1">`. A missing viewport can make a responsive layout render at a desktop-width canvas on phones. The checker reports presence and value; visual responsive testing still belongs in a browser or mobile-friendly test.
Complete the Open Graph core: `og:title`, `og:description`, and `og:image` provide the primary social-card content. `og:url` should use the preferred share URL, usually the same URL chosen as canonical. PageChecks requests the Open Graph image and reports response details such as content type and file size. Use the separate image-dimension validator to verify width and height rather than assuming this metadata audit measures pixels.
Keep Twitter Card tags intentional: A `twitter:card` value such as `summary_large_image` sets the card format. Dedicated `twitter:title`, `twitter:description`, and `twitter:image` fields let you control the X preview separately from Open Graph. The report lists both tag families so a complete Open Graph setup does not hide a missing Twitter declaration.
Review hreflang as a cluster, not a single tag: The metadata report extracts alternate-language annotations from the page. Each `hreflang` needs a valid language or language-region code and an absolute destination. Full validation also requires reciprocal return tags, self-references, and compatible canonicals across the alternate pages, so use the cluster checker after the initial metadata scan.
Use competitor data narrowly: The optional comparison reports character-count differences for titles and descriptions. It does not prove that the competitor's copy caused its ranking, and it does not copy their canonical strategy. Use the delta to see whether your snippet is unusually short or long, then write metadata that matches your own content and search intent.
Retest the live response: CMS plugins, edge middleware, and template conditionals can alter metadata by route. Check a representative article, product, category, and paginated page instead of assuming the home-page template covers them. After a fix, rerun the public URL and confirm the returned HTML and headers contain the intended values.
When should you use Meta Tag Checker?
Meta Tag Checker is most useful when you need a direct answer on a live URL or draft before you change templates, ship content, or rerun a wider audit.
How to Use This Tool
- 1 Enter a public page URL. Add a competitor only when title and description length comparison will help the edit.
- 2 Review the title and description values, character counts, and warnings before changing either field.
- 3 Check robots, X-Robots-Tag, canonical, viewport, and hreflang values for indexing or rendering conflicts.
- 4 Inspect Open Graph and Twitter Card fields, then confirm the reported Open Graph image response is usable.
- 5 Fix the CMS template or response header that owns each issue instead of patching one generated page by hand.
- 6 Rerun the live URL and verify the initial HTML response contains the corrected values without relying on client-side injection.
What should you do next?
After fixing meta tags, validate social previews and simulate your Google snippet. Then move to the related checks below to confirm the fix on the live canonical page.
What You Get
Indexing Directives
Review meta robots, X-Robots-Tag, and canonical values together so an unexpected noindex or URL mismatch does not survive launch.
Social Metadata
Check Open Graph and Twitter Card fields separately, then verify that the declared Open Graph image returns a usable response.
Initial HTML Evidence
Inspect metadata from the server-returned document and identify critical tags that exist only after client-side JavaScript runs.
Focused Comparison
Compare title and description lengths with one competitor without implying that copied wording or character count determines rankings.
Frequently Asked Questions
Answers about Meta Tag Checker
Run the live URL through the Meta Tags Checker to inspect the metadata returned in its HTML. The report covers the title, meta description, canonical, robots directives, viewport, hreflang, Open Graph, and Twitter Card tags.
Use 50 to 60 characters for an SEO title and 140 to 155 characters for a meta description as practical drafting ranges. Google truncates by rendered width and can rewrite either field, so put the page topic and distinguishing detail first.
Yes, the report flags missing or risky canonical and robots signals. Check the resolved canonical URL and every robots value before launch, because one unintended `noindex` directive can remove an otherwise crawlable page from search.
Open Graph and Twitter tags control social previews, not organic rankings. A complete `og:title`, `og:description`, and reachable `og:image` can improve the appearance of shared links without changing Google's ranking signals directly.
Google can rewrite a title or description when the supplied text does not match the query or visible page content. Keep each tag specific to the page, avoid repeated boilerplate, and make the H1 and opening copy support the same intent.
The checker reads the HTML returned by the web server and may not see tags inserted only after client-side JavaScript runs. Put critical title, canonical, and robots tags in the initial HTML response so crawlers and diagnostic tools receive the same signals.
Treat the most restrictive applicable directive as the effective rule. A `noindex` value in either a meta robots tag or an `X-Robots-Tag` header can block indexing even when another directive says `index,follow`.
The optional competitor check compares title and description lengths for two live URLs. Use the character deltas as an editing reference, then write distinct metadata that matches your own page instead of copying the competitor's wording.