<head *>

Full head report

One URL, every check headlint runs, graded against a rubric published on this page. Each item shows what it scored and which standard it was checked against — the deduction ledger at the end shows all the arithmetic. The record writes itself down the page as each check finishes.

What this record covers

Eight graded checks, 100 points in total — each item's maximum shown below. An error costs 4, a warning 2, a note nothing. Rubric version 1, published 2026-08-20.

  1. Indexability<meta name="robots">Google's robots.txt matching rules and robots directives20 max verified 2026-08-19
  2. Meta tags<title>Google search-appearance documentation, measured in pixels20 max verified 2026-07-06
  3. Redirects & canonical<301 → 200>HTTP redirect semantics and canonical consolidation12 max
  4. Social previews<meta property="og:image">each platform's own published card documentation12 max verified 2026-07-06
  5. Favicons<link rel="icon">browser, Apple and web-manifest icon requirements10 max verified 2026-08-19
  6. Structured data<script type="application/ld+json">Google's per-type rich-result requirements10 max verified 2026-08-19
  7. Head order<head>capo.js element weights, transcribed from source8 max verified 2026-08-19
  8. hreflang<link hreflang="…">Google's hreflang reciprocity rules and ISO 639-18 max verified 2026-08-19

The SERP snippet and each platform's resolved fields appear as exhibits — evidence attached to the item that grades them, worth no points of their own.

FAQ

Why does the grade appear at the bottom?

Because the record is written as the checks finish, and a grade printed before the last check would be a guess. Each item lands as soon as it resolves, and the grade is the sum of what you can already read above it.

Is the grade an SEO score?

No. It is the sum of deductions from findings in this page's <head>, each checked against documentation we cite and date. Nobody outside headlint uses this number, and it predicts nothing about rankings.

Why did a check not complete?

Each check gets its own time budget. Pages with many icons or many hreflang alternates need several extra fetches, and a slow origin can outlast that budget. An unfinished check costs no points and links to its own tool, where it can run alone with the whole budget to itself.

How many requests does this make to my site?

Your page is fetched once and shared by every check. Beyond that, only checks that genuinely need more files make more requests — icons and the manifest, hreflang alternates, social images, and each redirect hop — and each of those is individually capped. Nothing is crawled and nothing is stored.