RevealTheme logo

Meta Tags Analyzer

Fetch any public URL on our server and list every <meta> and <link> tag found in its raw HTML <head> — title, description, Open Graph, Twitter Card, viewport, robots, canonical, and more.

How to use this tool

  1. 1

    Paste the full URL of the page you want to inspect (include https://) into the input field.

  2. 2

    Submit the form — our server fetches the page, following up to 5 redirects, and reports the final URL and HTTP status.

  3. 3

    Review the parsed <title>, the list of <meta> tags (each shown by its name, property, http-equiv, or charset plus its content), and the <link> tags (rel and href).

  4. 4

    Compare the results against the SEO and social tags you expect; if a tag is missing here, it is missing from the raw HTML the page served.

What does a meta tag analyzer actually read from a page?

Meta tags live in the <head> of an HTML document and tell browsers, search engines, and social platforms what a page is about. This tool requests the URL you give it from our server, then parses the returned HTML with cheerio — a fast, static parser that reads markup but does not run JavaScript. It collects every <meta> tag inside <head> (exposing each tag's name, property, http-equiv, or charset attribute alongside its content), every <link> tag (rel and href), and the document <title>. That covers the SEO-relevant tags people care about: title and meta description (the search snippet), viewport (mobile rendering), robots (indexing rules), link rel=canonical (duplicate-content control), Open Graph og:* tags (Facebook, LinkedIn, Slack, Discord previews), and Twitter Card twitter:* tags. The important caveat: because nothing executes JavaScript, tags injected client-side after load — via React Helmet on a SPA, Next.js client-side navigation, or a tag-manager script — will not appear unless the server already rendered them into the initial HTML. What you see here is exactly what a basic crawler receives on first request, which is also roughly what social scrapers and many search bots read.

Common use cases

  • Verify your SEO setup after deploying — confirm title, meta description, canonical, robots, and og:image are present in the server-rendered HTML.

  • Catch a page that renders its meta tags only client-side: if og:image is missing here but visible in your browser's devtools, social scrapers will not see it.

  • Reverse-engineer how a competitor structures their title, description, and Open Graph tags across key pages.

  • Audit a client site before a redesign by cataloguing every meta and link tag so the migration preserves SEO signals.

  • Check for an accidentally-shipped robots noindex tag on a production page.

  • Trace a redirect chain — the tool reports the final resolved URL and status after following up to 5 hops.

Frequently asked questions

Why are tags missing that I can see in my browser's inspector?▼
This tool reads only the raw HTML the server returns; it does not execute JavaScript. If your meta tags are injected client-side (React Helmet on a single-page app, a tag manager, or client-side navigation), they appear in your browser's live DOM but not in the initial response — so they are absent here, and many social scrapers and basic crawlers will miss them too. Render the tags server-side to fix that.
Does this run in my browser or on your server?▼
On our server. The page is fetched server-side because most sites block cross-origin browser requests (CORS), which would make a purely client-side fetch fail. You submit a URL; our backend retrieves and parses it.
Does it follow redirects?▼
Yes, up to 5 hops, re-validating each hop to block requests to private or internal addresses. The result shows the final resolved URL and the HTTP status code returned by that final page.
Which meta tags should I check for first?▼
For search: <title>, meta description, meta viewport, link rel=canonical, and meta robots. For social previews: og:title, og:description, og:image, twitter:card, and twitter:image. If those are present and correct in the output, your core setup is sound.
Why doesn't Facebook show my image even though og:image is listed here?▼
Common causes beyond a missing tag: the image is smaller than Facebook's recommended 1200x630, the og:image URL is relative or unreachable, or Facebook cached an older scrape. Use Facebook's Sharing Debugger to force a re-fetch. This tool only confirms the tag exists in the HTML; it does not download or validate the image itself.
Do I still need a meta keywords tag?▼
No. Google confirmed back in 2009 that it ignores the keywords meta tag for ranking. If the tool lists one, it is harmless but does nothing for SEO.
Can it analyze a page behind a login or a local address?▼
No. It can only reach publicly accessible URLs, and it deliberately blocks private, loopback, and internal hosts (and any redirect that points to one) to prevent server-side request forgery. Pages requiring authentication will return whatever the server shows to an anonymous visitor.

Related tools

Heading Hierarchy Analyzer

Audit H1-H6 structure for SEO and accessibility issues.

Schema Markup Validator

Extract and validate JSON-LD schema from any page.

Open Graph Inspector

Preview how a URL appears on Facebook, Twitter, and LinkedIn.

Sitemap Inspector

Analyze any XML sitemap — URL count, lastmod, structure.

robots.txt Inspector

Parse robots.txt and flag common mistakes.

Page Word Count

Count visible words on any URL.

Subscribe for updates

We do not sell your email. We do not spam.

© 2026 RevealTheme. All rights reserved.