Free Online Meta Tag Analyzer
Inspect title, description, canonical, robots, and social tags on a page.
Automated checks
Core meta tags
| Tag | Value | Length |
|---|
Open Graph tags
| Property | Value |
|---|
No Open Graph tags were found on this page.
Twitter tags
| Name | Value |
|---|
No Twitter card tags were found on this page.
Redirect chain
| From | Status | Location |
|---|
Response headers
| Header | Value |
|---|
The page is fetched by this site's server, parsed, and summarized. Some sites block automated requests or return a JavaScript shell with little metadata; in that case the report reflects what a simple crawler sees. Private and local addresses are rejected.
About the Meta Tag Analyzer
Meta tags are small declarations in a page's head that tell search engines and social platforms what the page is about. They do not appear in the visible layout, which makes them easy to forget and hard to proofread. This analyzer fetches a URL, extracts the important tags, and presents them in a single report. It also runs a set of practical checks so you can see whether a title is missing, a description is too short, a page has duplicate first-level headings, or images lack alternative text.
What the report covers
- Title and description: the exact text plus its character length, which is a useful proxy for how much of it may be truncated in search results.
- Canonical and robots: whether a preferred URL is declared and whether indexing is blocked by a noindex directive.
- Viewport and charset: foundational mobile and encoding declarations that are easy to overlook in templates.
- Open Graph and Twitter: the tags that control link previews on Facebook, X, LinkedIn, and messaging apps.
- Structure: heading counts, image totals, missing alt attributes, word count, and estimated reading time.
- Transport: HTTP status, redirect chain, and a selection of response headers.
The character targets used by the checks are guidelines rather than rules. Google often rewrites titles and descriptions based on the query, and social platforms crop previews differently on each device. A title under thirty characters can still be perfectly effective for a brand page, while a long description can be trimmed automatically. Treat a warning as a prompt to review the text, not as a hard failure. The checks are most useful when comparing many pages from the same site: patterns such as consistently missing descriptions or multiple H1 elements usually point to a template issue rather than a one-off mistake.
The fetch happens on the server so that cross-origin restrictions do not hide the page source. That also means the result depends on the server's request headers and timeout. A site behind a bot challenge may return a block page with a valid 200 status, and a single-page application may return an empty shell whose metadata is injected later by JavaScript. The analyzer reports what was present in the HTML it received and notes when a response is not HTML at all. For a complete audit, combine this view with a rendered browser preview and a crawl of the whole site.
Open Graph and Twitter tables are shown separately because the two vocabularies can disagree. A page might declare a beautiful Open Graph image but forget the Twitter equivalent, leaving one platform to guess. When values are missing, the social preview tool on this site can help you build the correct tags. Reports can be copied or downloaded as JSON for a ticket, a spreadsheet, or a before-and-after comparison.
How to use this tool
- Enter the public URL of the page you want to inspect.
- Click Analyze meta tags and wait for the server to fetch and parse the document.
- Review the summary, automated checks, tag tables, and redirect chain.
- Copy the report or download it as JSON to share with your team.
Frequently asked questions
Why does the analyzer show different tags than my browser?
The server receives the initial HTML response. Tags added later by JavaScript, A/B testing scripts, or a tag manager will not appear. Bot protection pages can also replace the real document with a challenge.
Are the character limits official?
No. Search engines measure available space in pixels and may rewrite snippets. The 30–60 and 70–160 ranges are widely used planning targets that keep most of the text visible on common devices.
Can I analyze a private or local URL?
No. The endpoint rejects localhost, private IP ranges, and non-standard ports to prevent abuse. Use a publicly reachable address, or test a staging site that is protected by authentication in your own environment.