SEO Metadata Checker
Check a page's title, description, canonical, robots and Open Graph tags.
Related tools
- Redirect CheckerTrace redirects from http and https, with and without www, to the final URL and spot loops and extra hops.
- HTTP HeadersGrade a site's security headers and cookies, get the header lines to add, and build a Content-Security-Policy that the same check approves.
- Record BuildersBuild SPF, DMARC, BIMI, MTA-STS and TLS-RPT records, meta tags and robots.txt with live checks as you type.
- TLS CheckerInspect a site's TLS certificate, expiry, issuer and negotiated protocol, with a renewal calendar you can download and a full report.
About this tool
SEO Metadata fetches the home page of the domain over HTTPS and reads the tags a search result and a link preview are built from: the title, the meta description, the canonical link and the Open Graph title, description and image. It judges the title against 30–60 characters and the description against 70–160, reports a missing canonical or one that points at another host, and lists the Open Graph tags that are absent, each with the lines to paste into the page head. It reads the HTML exactly as it arrives, without executing JavaScript, so what you see is what a crawler sees on its first pass. It checks one page, not a site: there is no crawl, no robots.txt or sitemap analysis, no check of headings, images, links or structured data, and no page speed measurement.
XGM fetches the HTTPS home page from its server (up to 250 KB) and reads the title, meta description, canonical link, Open Graph and Twitter card tags, the robots meta tag, the viewport and the charset. No JavaScript is run, so this is what a crawler sees. The Full report tab scores the same page and adds recommendations.
How to use it
- Enter the domain whose home page you want to check, for example example.com.
- XGM fetches https://<domain>/ from its server and reads the title, description, canonical and Open Graph tags.
- Work through the findings; missing tags come with a snippet to paste into the page head.
- Open the Full report tab for a score and recommendations, or build the tags with Record Builders.
FAQ
My title and description are set by JavaScript and show as missing. What now?
XGM reads the delivered HTML without running scripts, which is the state a crawler indexes on its first pass; whether and when a crawler runs your JavaScript afterwards is not something you control. Metadata that decides how a page appears in results belongs in the server-rendered head. The same applies to a canonical link injected by a framework after hydration.
Are 30–60 and 70–160 characters hard limits?
No, they are display guidance. Search engines truncate by rendered pixel width, not by character count, and they frequently rewrite the snippet using text from the page anyway. A title or description outside the range is still valid and still indexed; the warning only means the visible part is likely to be padded out or cut off.
Can I check a single page or the whole site instead of the home page?
The input is a domain and the request goes to the root page over HTTPS only. Nothing is crawled, so pages behind the home page are not checked. Since metadata is normally produced per template, checking the home page tells you about that one template - product, article and category templates have to be reviewed in the page source or with the builder that writes the tags.
The canonical points to a different host and is flagged. Is that always wrong?
It is compared against the domain you checked, ignoring a leading www. Pointing elsewhere is correct for a syndicated copy that should credit the original, and wrong for an original page, where it hands the ranking signals to somebody else's URL. The classic accident is a staging or CDN host left in the tag after a migration.
Why are missing Open Graph tags only informational?
Open Graph is a convention the social and chat platforms read for link previews, not part of any search standard, so its absence does not affect indexing - a shared link falls back to the page title or to the bare URL. Its one hard requirement is that the image URL must be absolute; a relative path is ignored by the platforms that read it.