MetadataViewerFree Website Meta Tag Checker
Inspect the meta tags a public page actually sends: title, description, canonical, robots, hreflang, Open Graph and Twitter Card—plus redirects, conflicts and previews.
What this checker reads
The report starts with the page’s final URL and redirect chain, then inventories the tags inside the returned
<head>. It calls out missing or duplicate titles, descriptions and canonicals; noindex
directives; and direct conflicts such as canonical disagreeing with og:url.
| Group | Fields | What the report highlights |
|---|---|---|
| Search | Title, description, canonical, robots | Missing, duplicate and conflicting declarations |
| Technical | Charset, viewport, hreflang | Declared values and resolved alternate URLs |
| Social | Open Graph and Twitter Card | Declared title, description, URL and image |
| Fetch | Status, final URL, redirects | What the checker requested at each hop |
Server HTML versus JavaScript-injected tags
This tool does not run the target page’s JavaScript. That is intentional: the result represents the raw HTML available to a plain HTTP client, and the report labels that source explicitly. If your tags only appear after hydration or a tag manager runs, they will not appear here. Compare the result with a rendered-browser inspector when diagnosing a JavaScript SEO implementation.
Facts instead of an SEO score
Search engines can rewrite titles and descriptions, and different pages have different jobs. Character ranges are shown as editing notes, not pass/fail laws. The useful signals are concrete: which values exist, whether they repeat, where a canonical points and whether social URLs agree with it.
Website tags are not file metadata
HTML meta tags describe a web page. EXIF, PDF properties, MP4 atoms and Office document fields live inside files. To inspect those locally without uploading, use the image metadata viewer, PDF metadata viewer or video metadata viewer.
Limits
- Only public HTTP and HTTPS pages on standard web ports can be checked.
- The fetch is capped at five redirects, ten seconds and 1 MiB of HTML.
- The report covers one URL, not every page or template on a site.
- A preview approximates declared tags; it cannot guarantee how Google or a social network will render them.
Frequently asked questions
What does this meta tag checker inspect?
It reads the server-delivered HTML head and reports title, meta description, canonical, robots, viewport, charset, hreflang alternates, Open Graph and Twitter Card tags. It also shows redirects, direct conflicts and search/social previews.
Does the checker execute JavaScript on the target page?
No. It deliberately inspects the raw HTML returned by the server. Tags injected later by JavaScript are not included, which makes the distinction visible instead of silently mixing two different sources.
Why is there no SEO score?
A single score hides context and turns editing ranges into fake rules. The checker reports facts and specific conflicts—such as duplicate canonicals or canonical versus og:url—so you can decide what matters for the page.
Are my URLs private?
The URL must be sent to the MetadataViewer.org Worker so it can fetch the public page. The application does not log submitted URLs, but the target website receives a normal HTTP request. Do not enter private, signed or credential-bearing URLs.