Changelog

2026-04-12 — Content depth pass

• Expanded educational and compliance pages so each carries roughly four hundred words of substantive text, with educational pages emphasizing the mechanics of AI visibility tracking (capture, parsers, schedules, variance, evidence storage).
• Clarified cross-links between hub pages, the /track/ pillar, engine guides, and the “how it works” explainer so readers can move from concept to implementation checklist without dead ends.

2026-04-12 — Visual and IA alignment

• Visual refresh for a lighter, editorial layout. Rankscale appears in primary outbound actions and on the imprint, not in the footer or about page body.
• Aligned on-page copy and meta with AI visibility tracker and AI visibility tracking phrases. Canonical host remains apex (non-www).
• Initial publication of the site structure, core pages, compliance pages, robots.txt, sitemap.xml, and cats.txt.

How we version reference material

Unlike software binaries, reference prose changes when industry language shifts or when we learn a clearer way to describe measurement mechanics—for example, when a major engine adds tool-use traces that parsers must capture. Material updates appear here when they would confuse returning readers who memorized an older definition. Typo fixes may skip the changelog if they do not change meaning.

Planned maintenance mindset

AI surfaces will keep evolving. Expect future entries that document new capture requirements (layout changes, new citation objects) and that adjust cross-links if paths change. The mechanical advice—append-only rows, versioned parsers, explicit surface labels—should remain stable even as product names churn.

How changelog entries relate to measurement

When we revise wording about capture or variance, teams already running programs should diff the updated page against their internal runbooks. If the site now recommends storing tool traces you previously ignored, you are not legally required to change anything—but your historical series may not be comparable to peers who adopted the practice. Treat major editorial updates like dependency upgrades: read release notes, schedule engineering time if needed, and backfill only when the business case is clear.

Archival policy

Older bullets may be compressed or removed when they no longer help readers distinguish current practice from obsolete UI screenshots. The canonical technical story always lives in the main guides; the changelog is an audit trail of meaningful edits to this repository, not a blog archive of every typo.

RSS or feeds

This static site does not ship an RSS feed by default. If one is added later, this changelog will note the URL and whether full article text or only titles are included, because feed mechanics affect how readers mirror content into internal knowledge bases.