Split evidence (URL) from note (prose) on the AI visibility scoreboard
What was done
Schema split
- Added a new optional
note?: stringfield to the Item type ingetting-found-by-ai.astro. evidenceis now URL-only; the template still guards withisUrl(...)so future malformed values can’t reach<a href>.noterenders as an inline italic, muted, 80ch-wrapping<span class="evidence-note">on its own row inside.item-meta(flex-basis: 100%).- Both fields can coexist on the same item — see the two isitagentready items below.
items.json migrations (9 items)
Moved prose from evidence → note:
id-linkinggoogle-business-profileschema-validationai-crawler-monitoringmonthly-retestmcp-server-considerlearn-keystone-wat
Added a working evidence URL and moved prose to note:
isitagentready-baseline→evidence: https://isitagentready.com/baileyengineers.comisitagentready-monthly→evidence: https://isitagentready.com/baileyengineers.com
(Note: isitagentready.com serves 404 to bot User-Agents on that path, but the SPA hydrates the report client-side in a browser — Ryan confirmed it works.)
Why
Ryan flagged that the two isitagentready items 404’d when clicking “Evidence →”. Root cause: 9 items in items.json had descriptive prose in their evidence field instead of URLs. The template was wrapping all of them in <a href={i.evidence}>, so clicking produced malformed relative URLs that 404’d against the site root.
The fix is structural — separating “where to go for proof” (URL) from “what’s worth saying about this item” (prose) — so an editor can’t accidentally produce another broken anchor by typing prose into evidence, and items that have both a URL and useful context (like the two isitagentready items) can show both.
Files affected
src/pages/dev-iq/ai-iq/getting-found-by-ai.astro(Item type, frontmatter helper, template render,.evidence-notestyles)src/content/seo-plan/items.json(9 items migrated)