What Meta Tag Analyzer does
Meta Tag Analyzer asks the PagesTools server to fetch a public URL and parse its returned HTML. It records the requested and final URL, HTTP status, standard metadata, selected link and language signals, social-card maps, and the page's first three heading levels.
The report describes source HTML seen by a server-side request. It does not execute the page's JavaScript, confirm how every crawler renders the page, validate social-card images, or predict whether a search engine will use a title or description. Redirects and content negotiation can also make the server's version differ from a browser session.
How to use Meta Tag Analyzer
- Enter the full public URL of the page you want to inspect.
- Select Analyze metadata and wait for the bounded server fetch.
- Review the final URL, status, standard tags, social tags, and H1–H3 arrays.
- Compare the findings with the page template and a browser-rendered inspection before publishing changes.
Important details
Canonical URLs are resolved against the final page
A relative canonical reference is resolved using the fetched page's final URL. Presence does not prove that the canonical is correct, indexable, reciprocal, or accepted by a search engine.
Social metadata is grouped by prefix
Open Graph properties beginning with og: and Twitter metadata beginning with twitter: are returned as bounded key-value maps. The analyzer does not download or validate the referenced media assets.
Headings are an inventory, not an outline score
Up to bounded H1, H2, and H3 text values are listed so you can inspect structure. Whether that structure is meaningful still requires reading the page in context.
Practical uses
- Audit metadata after a template, CMS, or migration change.
- Compare canonical and social-card values across landing pages.
- Collect title, description, and heading evidence for an editorial review.
Privacy and limitations
The URL is sent to PagesTools and fetched by its server. The destination can log that request, and any URL query string is part of it; avoid private or tokenized links. The JSON response uses no-store cache headers.
The tool analyzes one bounded public HTML response without JavaScript rendering. It does not verify indexing, crawler behavior, structured data, remote images, content quality, or how search and social platforms will rewrite or display tags.