Before / after
Rescan after a deploy and see which layers moved. If nothing moved, you will know.
Free 30-second scan. See how you show up when AI answers — no signup.
Home / Tools / Scan History & Trends
Every scan stored as a point on a timeline — so you can see whether deploying files, publishing content, or a technical fix changed AI readiness.
What it covers, how you run it, and who it is for — then the long-form detail.
Rescan after a deploy and see which layers moved. If nothing moved, you will know.
Content can rise while discovery files stay flat. The chart does not hide that.
A history view you can screenshot for a client or a board — real scores, not a mock.
Manual, or scheduled on a subscription so you are not relying on memory.
Tie a spike to “published comparison page” or “deployed llms.txt.”
If the layer did not move, pick a different lever.
Proof that last month’s work did something.
A trend line in the monthly deck without exporting CSV by hand.
A simple answer to “are we more AI-ready than last quarter?”
A single score is a mood. History is whether deploying llms.txt, publishing a comparison, or fixing crawl issues moved a layer. Each scan is a point on a timeline with category breakdowns, not one vanity number.
Deltas matter more than absolutes. Going from 41 to 58 after a content sprint is the story. Sitting at 91 because you never rescanned is not.
Overall score, per-layer scores, and enough context to annotate “shipped files on Tuesday.” Subscriptions add a cadence so you are not relying on someone remembering to click scan.
Opportunity scoring uses the latest scan. Citation tracking is the outcome metric when the score moves but answers do not (or vice versa). History is how you keep those honest.
If a layer did not move, pick a different lever next sprint. That is the whole point.
Free 30-second scan. See where you stand — then use Scan History as part of scan, fix, and prove. No signup.
Free scan