Meta tags are the part of a page nobody sees and everybody judges it by. The title decides what appears in search results. The description writes the sentence underneath it. The Open Graph tags decide what the link looks like when someone shares it on Facebook, LinkedIn or WhatsApp. Get them wrong and the page can be perfectly good while presenting itself badly everywhere it appears.
This checker fetches a page and reports what it actually serves, which is not always what the content management system claims. Enter an address and it returns the tags along with an assessment of each.
What it checks
Title and description come with length feedback. Titles are flagged as short below 30 characters and long above 60. Descriptions are flagged below 70 and above 160. These are working thresholds rather than hard rules - Google measures pixel width, not characters, and rewrites descriptions when it judges a different snippet more relevant - but staying inside them keeps you out of trouble.
Canonical URL is the tag that tells search engines which address is the authoritative one for the content. Missing canonicals are how the same page ends up indexed under several URLs, splitting its ranking signals between them.
Viewport is checked because its absence means the page is not mobile-ready, and mobile-first indexing makes that a serious problem rather than a cosmetic one.
Open Graph and Twitter Card tags are listed in full. These are the most commonly neglected group, because nothing on the page looks wrong when they are missing - the damage only appears when someone shares the link and gets a bare URL with no image.
Headings are counted, with the H1 highlighted. One H1 is the expectation; several is a structural signal that the page has more than one main topic.
Images and links are summarised - how many images lack alt text, and how many links are internal versus external.
The one tool here that uses the server
Every other utility on this site runs entirely in your browser. This one cannot, because browsers block a page from fetching arbitrary other sites. The request is made by our server instead.
That means two things worth stating plainly. The URL you enter is sent to our server so the fetch can be made. And the request is refused for addresses on private and internal networks - localhost, 192.168.x.x, 10.x.x.x and similar - because an open fetcher that could reach internal addresses would be a way to probe networks that are not publicly reachable.
What it cannot see
The fetch reads the HTML the server returns. If your tags are inserted by JavaScript after the page loads, they will not appear here - and that is worth knowing rather than working around, because it tells you those tags are invisible to any crawler that does not execute JavaScript. Some do, some do not, and relying on it is a risk.
Pages behind a login, behind aggressive bot protection, or serving different content to unfamiliar user agents may also return something other than what a visitor sees.