Scope
Homepage, robots.txt, sitemap.xml, llms.txt, one controlled missing URL, and up to five same-origin sitemap samples.
Example only
What a useful public audit looks like.
This is a fictional, redacted illustration. It shows the standard of evidence and the handoff structure, not a client result or a ranking promise.
Run a public audit for your siteExample: a small service website
Public evidence
robots.txt returned an HTML fallback; sitemap was available; the homepage had no canonical; no common analytics script was detected.
Not publicly knowable
Index coverage, search queries, clicks, conversions, page templates, historical redirects, and content approvals.
How one finding is delivered
P0 · robots.txt returns HTML
Evidence: E1 public HTTP response, high confidence. The path returned text/html and an app shell rather than crawler rules.
Owner: Developer. Action: serve a text/plain robots file and prevent SPA fallback.
Verification
Open /robots.txt on a public connection. Confirm a 200 response, text/plain content type, a User-agent directive, and the correct sitemap declaration.
This makes the task testable before it is marked done.
The resulting plan
- 0-15 days: repair public crawl entry points and agree on the preferred domain.
- 15-30 days: correct page metadata, canonical rules, and analytics measurement.
- 30-60 days: publish service, FAQ, about, and proof pages that answer real buyer questions.
- 60-90 days: review authorized GSC and analytics evidence before expanding work.
The important distinction
A public report can show what is observable. It should never pretend that search traffic, conversions, or index coverage have been verified without the owner's authorized data.