Data Intelligence
The Half of the System Most Websites Never Get.
Search Console tells you one story. Server logs tell you another. Change history tells you when you did something. Separately they are trivia. Joined together and dated, they are evidence.
Why one source is never enough
Search Console will tell you impressions fell. It will not tell you that a template change shipped nine days earlier, that it touched forty pages, or that the AI crawlers stopped arriving at the same time. Analytics will tell you humans left. It will not tell you whether a bot ever showed up to read the page in the first place.
Every one of those sources is partial on purpose. They were each built to answer a narrow question. The useful information lives in the overlap.
Knowing traffic dropped is ordinary. Knowing traffic dropped eleven days after a specific change, on the specific pages that change touched, is a different kind of information. That join is the whole point of the warehouse.
What gets collected
Search performance
- Google Search Console data
- Query trends over time
- Page-level performance
- Query-to-page relationships
Server and crawler activity
- Server request logs
- Good AI crawler activity
- Human request activity
- Which pages get read by what
Work and change history
- SEO events with dates
- What changed and where
- Specialist or employee activity where recorded
- Cross-site comparisons where applicable
Log ingestion depends on server access. Some hosting does not expose request logs at all, and we confirm what is available rather than promising it upfront.
Why AI-bot activity matters now
For most of the history of the web, the only crawler worth thinking about was a search engine's. That is no longer true. AI systems read pages to answer questions, and whether they arrive, what they read, and how often is a measurable signal that does not appear in any traditional analytics tool.
Separating good AI crawler traffic from noise, and tracking it per page over time, is one of the clearest differences between watching a site and understanding it.
This is an area where honest reporting matters more than a confident dashboard. Crawler behavior is observable. What any given AI system does with what it read is not. We report the first and do not pretend to the second.
What an SEO event is, and why it is dated
An SEO event is a recorded change: a page rewritten, a schema type added, a redirect fixed, a section restructured, a batch of internal links repointed. It carries what was done, where, and when.
The date is the load-bearing part. Without it, performance data and work history are two separate stories that can never be checked against each other. With it, you can ask the only question that actually matters after doing work: did that do anything?
See the glossary for the terms used across the system, or proof entries for recorded observations from live properties.
Want to see real data rather than a description of it?
The walkthrough uses live properties. Not a mock dashboard.