Changelog
One entry per milestone shipped. Nothing is announced here before it runs in production, a changelog that promises is the fastest way to collect complaints.
Latest entry:
-
Keyword research and AI intent
A single reference where the tracking facet, which spends, sits next to the semantic facet, which does not: clustering by meaning, winnability estimates, search volumes.
New "AI intent" view: share of citations captured across three providers, with its denominator shown next to it.
Mots-clés Visibilité IA
-
Daily rank tracking and backlink profiles
Daily rank capture at full depth, with SERP features, and competitors extracted from captures already paid for rather than from a second call.
The backlinks module requires explicit activation by an administrator: an inactive project spends nothing. Profile, lost and gained domains, on-demand gap analysis.
Positions Backlinks
-
Rendered accessibility audit, and conformance report
The accessibility audit runs against the rendered page, not the initial HTML; the distinction that decides everything on a modern application.
Contrast cards with a suggested fix, screenshots of failing elements, and an exportable conformance report in the format public-sector and US buyers ask for.
Accessibilité
-
Sovereign log analysis and Search Console cross-referencing
Server log upload up to two gigabytes, a streaming parser covering thirteen formats, and a human-versus-crawler traffic split.
No IP address is stored or sent to a model. Uploaded files are deleted after processing.
Three sources now meet on the same URL (crawl, logs, Search Console) with a diagnosis when they disagree, and orphan page detection.
Logs Search Console
-
Per-crawl "GEO readiness" report
Every crawl now produces an answer-engine readiness report: an AI crawler access matrix read against RFC 9309,
llms.txtvalidation, and opt-in active reachability checks.The score is versioned: changing the scale does not rewrite history, it opens a new comparable series.
Visibilité IA
What is missing from this page, and why
A module whose code is written but whose rollout is not done has no entry here. That covers billing and security signals: their build is closed, their operation is not. Listing them would date a promise rather than a delivery.
Start with a measurement, not a promise
Run an audit on your own site and read what the engine finds. If you would rather be walked through it, book a demo: we run it on your site, with your own URLs on screen.
Access opens in waves: we email you when yours is ready.