Snag List

Internal survey

Search-visibility findings for bricknbolt.com. Sign in with your work email to continue.

Only @bricknbolt.com addresses are accepted.

Access check, not a security control. This page is served as a public static file, so it deters casual sharing and nothing more. Keep anything confidential out of it.

Snag List

survey of bricknbolt.com
Re-measured 24 Sep 2026 · 6 templates
12,458 URLs enumerated · 157 checks
Search visibility survey

Two surfaces. Two different jobs.

Google decides whether these pages can be found. ChatGPT and AI Overviews decide whether they get quoted. The same site can be strong at one and invisible in the other — and the work that fixes each is not the same work.

SEO4/10Sound base, broken architecture
GEO3/10Entity conflicts, and a stale fact
AEO5/10Markup good, passages not shaped
9 pages, one query → 1 primary
01

SEO Optimize

Whether Google can find, crawl, understand and rank what already exists. Architecture first — no amount of content fixes nine pages fighting each other for one query.

Open the SEO snags
41 questions declared → 4 are headings
02

AEO / GEO Optimize

Whether ChatGPT, AI Overviews and Perplexity quote Brick&Bolt rather than a third-party listicle. Answer engines cite passages and entities, not pages — so this is different work.

Open the AEO/GEO snags
Health score 39/100
weighted by severity
Critical open 13
across 6 templates
High open 34
fix before content spend
Pages competing 166
in 44 clusters, 10 cities
Not yet measured —
needs access or licence
Section 01

SEO Optimize

What decides whether Google can find, crawl, understand and rank the pages Brick&Bolt already publishes. Architecture first — no amount of content fixes nine pages fighting each other for one query.

Section 02

AEO / GEO Optimize

What decides whether ChatGPT, Google AI Overviews and Perplexity quote Brick&Bolt rather than a third-party listicle. Answer engines cite passages and entities, not pages — so the work is different from Section 01.

Layout scaffold — extend via the skill file

Every row on this page is rendered from the SNAGS array in data.js. Adding a pointer means appending one object with section, group, ref, status, severity, title, why, evidence and fix — no markup changes, no build step.

Markup lives in shell.html; node build.mjs writes both index.html (GitHub Pages) and artifact.html from it, so the two entry points cannot drift apart.

Status values fail / warn / pass / unknown drive the pills, the filters and the tallies. unknown is deliberate: it marks what has not been measured yet rather than quietly omitting it.

Evidence. Measured from production URLs on 24 Sep 2026 with a headless rendering browser, computed styles and full sitemap enumeration — not copied from a third-party tool. Scores use the seo-aeo-geo audit rubric.
bnb-seo-aeo-geo · v0.4