The gates

Family A

Page-set integrity

The route registry and the built output match exactly. Every registered page is built; nothing is built that is not registered. Either direction fails.

• ✅page set integrity: 12 pages built, registry matches dist exactly

Family B

Phone and ZIP discipline

No forbidden ZIP in any HTML, JS, CSS, XML or text file in the build. Every tel: and sms: link carries the public number. A tracked number never reaches JSON-LD, and a Google-only number never reaches an indexable page or a crawler-readable string.

• ✅no tracked number configured; every tel/sms link carries the public number

Family C

Tracking and consent

Asserted in both directions. A practice with tracking carries exactly one tag-manager loader per page, with consent defaults and first-party capture ahead of it and the consent sentence verbatim. A practice without tracking carries zero Google tags anywhere. A chat widget, when enabled, is deferred to window load and placed after the loader; when disabled, no marker exists.

• ✅empty tracking config: zero Google tags in the build; first-party capture + consent text intact
• ✅chat widget disabled: zero widget markers in the build

Family D

Meta lint

One h1 per page, root-domain canonicals, no vercel.app address in the markup, titles within 60 characters and descriptions within 155.

• ✅meta lint: one h1, root-domain canonicals; title/description lengths checked

Family D2

Social cards

The card a messaging app renders is fetched from the destination page, so a texted link's credibility is decided here. og:title present; og:image an absolute URL that resolves to a file at least 1200px wide at about 1.91:1, measured from the bytes. Skipped on staging, where there is no shareable link — flipping the practice to production turns it on.

• ✅social cards: og:title + a ≥1200px, ~1.91:1 og:image on all 0 indexed page(s)

Family D3

Declared assets

Every hand-typed absolute asset URL in a practice's config — logo, images — resolves to a real file in the build. A rename that would ship a 404 with a green build fails here instead.

• ✅declared assets: 0 schema.org URL(s) resolve to real files in the build

Family E

Index discipline

Production: noindex pages excluded from the sitemap, the sitemap exactly the indexable set, and every noindex landing page still followable. Staging inverts it: every page noindex and nofollow, no sitemap, no llms.txt, a robots.txt that disallows everything, an X-Robots-Tag noindex header in vercel.json, and a registry that marks every page unindexable.

• ✅staging: no sitemap.xml in the build
• ✅staging: no llms.txt in the build
• ✅staging: robots.txt disallows all crawling
• ✅staging: X-Robots-Tag noindex header configured in vercel.json
• ✅staging: registry marks every page unindexable

Family F

Link graph

Every internal href resolves to a built page, a declared redirect, or a real file on disk. Every page has at least one inbound link. The pass line is guarded on both counts — it once printed zero dead links above nine recorded ones.

• ✅link graph: zero dead internal links, zero orphans (12 pages reachable)

Family N

Image invariants

Every raster image carries srcset, width, height and loading. No referenced raster over 300KB. No preload-as-image candidate over 200KB, because preloaded bytes sit in the LCP critical window.

• ✅image invariants: raster imgs fully attributed; no raster >300KB referenced; no preload candidate >200KB

Family G

Structured data

Every JSON-LD block parses. The Dentist node appears on the home page and nowhere else. Service pages carry Service with a name and provider; FAQ pages carry four to eight answer-first items; hubs carry an ItemList of the declared minimum; About and Contact carry their page types; every BreadcrumbList counts 1 to n.

• ✅structured data: Dentist home-only; Service/FAQPage/ItemList/About/Contact/Breadcrumb shapes valid

Family M

Entity graph

The home graph defines the practice, the doctor and the website. Every @id reference on every page resolves to a defined node; no @id carries two types; no self-authored AggregateRating, Review or Rating; a telephone only on the practice node, and only the public number.

• ✅entity graph: 13 @id references all resolve; no conflicting @ids; no rating self-markup; phone on #dentist only

Family I

Redirect integrity

Every legacy route in config is in vercel.json with the same target. No redirect shadows a built page; no target is missing from the build; no redirect exists in vercel.json without a source of truth in config.

• ✅redirect integrity: 0 legacy routes map to built pages, no shadowing

Family J

Taxonomy bans

The word warranty appears nowhere in any practice's site. The practice's own banned phrases appear nowhere. No Webflow CDN reference survives in any file. Compliance-signed copy that legitimately contains a banned word is exempted verbatim, page by page — and an exemption that no longer matches the built page is itself a failure, so a stale exemption cannot keep masking the ban.

• ✅taxonomy bans hold: zero "warranty" site-wide; practice bans (9 phrases — list elided — see the note below) clear; no Webflow CDN refs

Family P

Persona tiers

Every persona switch is checked against the built output in both directions. The motion kit on every page or on none. A specimen says so on every page and is noindex on every page. Every declared font face resolves and is preloaded. View-transition names unique per page. No CDN script, canvas, three.js, gsap or WebGL anywhere. Section modules render only where switched on.

• ✅persona tiers hold: motion "editorial", specimen on (line + noindex on every page), 3 self-hosted face(s) resolved, view-transition names unique per page, no CDN/canvas/WebGL

Family S

Style hygiene

Source-side and repo-level, run before any practice is audited. Within a single .astro file, the same class selector defined twice at the same media scope with conflicting declarations fails — the cascade would otherwise resolve it silently, which is how a page-level style once restyled the flagship hero. Redefinition under a different media query passes. Reported to the console, not to the per-practice file.

Runs against source; prints to the console, not to the report.