Tools Central

HTML Head Auditor

Check the SEO, social, mobile, and multilingual metadata of a pasted HTML code.

100% local analysis: no site is called and no pasted code is executed.

1. Paste the head to check

A complete HTML document or a head fragment is suitable. The parser remains inert.

Optional, it allows comparing canonical, og:url, and hreflang self-reference. No requests are sent.
Limit: 1,000,000 characters, 1,000 tags, and 200 diagnostics.

3. Diagnostics

Tags scanned : 14

No issues detected by local rulesCheck the published HTML and its rendering in official tools.

Language alternatives

en
https://example.com/en/guide
fr
https://example.com/fr/guide

Social metadata

og:image
https://example.com/images/guide.jpg
og:title
Practical Guide to Auditing an HTML Head
og:type
article
og:url
https://example.com/en/guide
twitter:card
summary_large_image

4. Interpreting the audit correctly

Signals, not guarantees

A canonical remains a signal and a search engine may rephrase the title or excerpt according to the query.

Responsive

width=device-width allows the browser to adapt the layout width to the device.

hreflang

Each variant must use an absolute URL and include the current URL in its group.

Local processing

The parser reads bounded text. It does not insert HTML into the page, load any resources, or execute any scripts.

Back to SEO tools

Similar Tools

robots.txt Generator and ValidatorGenerate, analyze, and download a robots.txt file, then simulate access to a URL for a specific bot.
XML Sitemap Generator and ValidatorCreate a URL sitemap or an index, validate the XML, dates, limits, and scope, then download the file locally.
Hreflang Generator and CheckerCreate HTML, HTTP, or sitemap annotations, then locally check self-references, canonicals, and backlinks between multilingual pages.
Structured Data ExtractorExtract JSON-LD, Microdata, and RDFa from HTML locally, explore entities and relationships, then export a bounded JSON report.
Google Snippet PreviewTest a title, meta description, and URL on desktop and mobile with an estimated width in pixels.
PDF Fields → JSONExport the list of fields from a PDF form (AcroForm) to JSON format.

Audit essential tags of an HTML head

The head contains signals that help browsers, search engines, and social platforms understand a page. This auditor locally examines title, description, canonical, robots, viewport, encoding, hreflang, Open Graph, Twitter, and JSON-LD without crawling the site or executing the pasted code.

When to use this auditor

  • Review a template before publicationQuickly spot a missing, empty, or duplicated tag before integrating a new page template into the deployment chain.
  • Compare the actual rendered HTMLCopy the head from the development tools to check the metadata after server-side rendering or client-side hydration.
  • Document an SEO recipeDownload the JSON report to retain values, language alternatives, and diagnostics associated with a given version.

Verification method

Enter the exact public URL, then paste the rendered HTML document or just its head. This URL is used for local comparisons with canonical, og:url, and hreflang variants; it is never opened by the tool.

First address structural errors like multiple titles, a relative canonical, or an invalid hreflang. Then examine noindex, missing metadata, and informational inconsistencies based on the page's intent.

After correction, check the HTTP response and the published HTML. An X-Robots-Tag directive, a redirect, JavaScript rendering, or a canonical sent by header may not necessarily appear in the pasted code.

Checks performed

  • Search and indexingPresence and uniqueness of title, description, and canonical, validity of the canonical, conflicting robots directives, noindex, and meta refresh.
  • Document and mobileUTF-8 declaration, viewport containing width=device-width, presence of a base tag, and number of JSON-LD blocks.
  • International and social sharingHreflang codes and URLs, self-reference, basic Open Graph properties, consistency between og:url and canonical, and Twitter card type.

What the report does not promise

  • A canonical URL is a grouping signal, not an obligation imposed on the engine. Its consistency with redirects, internal links, and sitemaps remains important.
  • Length alone does not determine the displayed title or description. Engines may generate or rephrase a result based on content and query; thus, the tool displays counts without arbitrary thresholds.
  • Social previews and rich results also depend on resource accessibility, platform caching, visible content, and rules external to this parser.

Limits and privacy

The source is limited to 1,000,000 characters, 1,000 tags, and 200 diagnostics. These limits reduce the risk of blocking with a deliberately excessive document.

The parser processes a text string without an active DOM. It does not insert HTML, load images or scripts, execute any handlers, or send any data to a remote service.

Frequently asked questions

Is a meta description absolutely necessary?
It is not necessary for indexing, but a specific description can help the engine compose a useful snippet. Its absence is therefore a warning, not proof of blocking.
Why is a different canonical just information?
A page may intentionally designate another representative URL. The report highlights the difference without assuming it is a business error.
Can the tool directly analyze a URL?
No. It does not crawl any site. This constraint makes processing predictable and confidential; copy the rendered HTML to accurately audit the desired version.

Also audit the HTTP response

The best head does not compensate for an inaccessible page, a chain of redirects, a server error, or a noindex X-Robots-Tag. Use this report as a checkpoint, then verify the response actually served.