AHD · Audit

Run the linter against any URL.

Paste a hostname. This page fetches https://<host>/, runs AHD's source linter against the HTML it finds, and returns the findings. Unlike /verify, the site does not need to publish its own manifest. The answer comes from the linter running over the page's own HTML right now.

What this catches

Every source-level AHD rule: the 34 HTML/CSS rules (slop taxonomy, typography, layout, accessibility, em-dash-in-prose) plus the 3 SVG rules when the page carries inline SVG. No vision critic (requires a browser) and no mobile audit (renders at 375px in Playwright); both are available via the ahd CLI.

What it doesn't catch

Rendered-pixel tells (Corporate Memphis on a hero image, iridescent 3D blobs, mesh gradients without counterforce, layout dead-space) need a multimodal critic over a rendered screenshot, which is not available in this route. Run ahd critique-url <url> locally for that. Mobile layout tells (horizontal overflow at 375px, tap targets below 32px, body font below 14px) are similar; run ahd audit-mobile <url>. Install AHD to run either one.

Against a site that doesn't know about AHD

Real AI-generated landing pages fire ten to forty rules against this linter. That is the point. The findings are a checklist of named failure modes the generator reached for, each grounded in the taxonomy. A page that fires zero rules is either extremely disciplined or extremely thin; the linter does not promise the design is good, only that it avoids these specific failure modes.

Adjacent: /verify for asserted provenance, the taxonomy, methodology.