Site audit
Visibility & authority
Resources
Consultants spend more time demonstrating their work than doing it. Your servers’ logs and the citations inside AI answers are two kinds of evidence a client never argues with, because both come out of their own site.
Access opens in waves: we email you when yours is ready.
One team, many projects, each with its own history and crawl campaigns. No licence per machine, no local file to pass around.
A curated executive PDF for the board and an exhaustive Excel workbook for the technical team, both generated from the database rather than assembled by hand.
What the crawl finds, what the logs confirm, what Search Console measures: three sources on the same URL, and a diagnosis when they disagree.
Strict per-team isolation across all business data, verified by tests on every release.
How it starts
Nothing to install and nothing to hand around: the project lives in the team, and its history starts at the first crawl.
One URL, one crawl campaign, and tracking begins.
The three sources meet on the same URL, and the gaps between them become readable.
An executive PDF for the board, an Excel workbook for the technical team, both generated from the database.
What you show a client cannot be one more dashboard: every module returns a dated measurement, comparable to the previous run.
The parser streams your server logs at a measured throughput, separates human traffic from crawlers, and surfaces the pages engines never request. No IP address is stored, and none is sent to a model.
Multi-threaded crawling with real JavaScript rendering: your pages are explored the way an engine sees them, not the way the initial HTML describes them. PageSpeed, scheduled crawls, and diffs between two runs.
Daily capture at full depth, SERP features, and competitors extracted from your existing readings. Desktop or Mobile, chosen per project.
Link profile, spam score, lost and gained domains, and a comparison against your competitors’ profiles to isolate the domains that cite them but not you.
Answer engines cite sources. We check which of their crawlers can actually read your site, validate your llms.txt, and capture your share of citations from real answers, with the denominator shown next to it.
The question your clients will ask first this year: are we cited when someone asks an AI? The page says what can be measured, and what is still folklore.
Read 02Real-browser crawling, status codes, canonicals: the material for an audit your client can run again after your fixes.
Read 03What you show before and after a rewrite: how a page covers its target keyword, and the E-E-A-T signals counted with their denominator.
Read 04A desktop crawler produces a file on one machine. What a shared reference changes, in ten lines.
Read 05The cornerstone guide on visibility inside answer engines, the one you can quote in a meeting without adding anything to it.
ReadRun an audit on a site you already look after: a single pass will tell you what your current reports leave out.
Access opens in waves: we email you when yours is ready.