Meta Tag Analyzer
Read Any Live Page

What A Meta Tag Analyzer Tells You

View-source shows you the tags. It does not tell you which one is missing, which is too long, or which one contradicts another.

The Denwix report opens with its findings. A title cut at 620 pixels, no canonical, two H1 tags: those are jobs, and they belong at the top.

Under the findings sit the tags themselves, grouped. The head block first, then Open Graph, then the Twitter card, then anything else the page carries.

Point it at any public page, including a competitor. That is how most people use a meta tag checker, and reading what a site publishes breaks no rule.

Why A Server Has To Fetch It

Your browser may not read another site on your behalf. The same-origin rule blocks it, and that rule also stops any page you visit from reading your webmail.

So the address travels to this server, which fetches the page once and returns only the parts this report draws. No markup reaches your browser.

The footer on the tool says so in plain words, because the difference matters. Every other tool on this site sends nothing anywhere.

The Twelve Things It Checks

Title and description come first, measured in pixels rather than characters, since a result cuts by width.

Then the structural tags: canonical, robots, viewport, charset and the language attribute. Each of those changes how software treats a page rather than how it reads.

After that the social block, the H1 count, the hreflang links and the images with no alt text. Twelve checks, and each one names a fix rather than a score.

What It Cannot See

Tags a script inserts once the page has loaded. This fetch reads the HTML as served, which is also what most crawlers and every social scraper read. If your tags appear only after a script runs, that is worth knowing.

Canonical Tags Are Where Sites Break

One page can answer on six addresses. With and without www, with and without a slash, http and https, plus whatever tracking parameters a campaign adds.

A canonical tag settles which one counts. Google says the same in its guidance on consolidating duplicate URLs.

The analyser flags a missing canonical, and it prints the one it finds so you can see whether it points where you expected.

How the Analyzer Gets Its Figures

The server sends back values, and your browser measures the two that need measuring. Title and description widths come from the same text metrics a results page would use.

So the pixel numbers here match the ones on the snippet preview, because both pages call the same code.

Everything else is a count or a yes and no. How many H1 tags, how many hreflang links, how many images arrived without alt text.

The report gives no single grade. A number out of a hundred hides which finding mattered, and hiding that is the opposite of useful.

Pages to Analyse Before Any Others

Start with your three most valuable pages. The home page, the page that earns the most traffic, and the page you most want people to reach.

Then run one page from each template. A product page, an article, a category listing. A fault in one of those usually repeats across hundreds.

Finally, run the same three on a competitor who outranks you. Their title lengths and descriptions tell you more than a checklist does.

Reading Somebody Else's Head Block

Competitor research is the honest half of this. How long are their titles, do they write their own descriptions, what does their card look like. The meta element reference covers what each tag means.