Sample audit
What an audit report looks like
This page shows the structure of the report you get. Fields we fill from real runs are marked "Observed field" and left as slots. Recommendations here are example text. Nothing on this page was measured, and it names no client.
01 / Report details
Who and what the audit covers
| Field | In a real audit | In this sample |
|---|---|---|
| Business | Business name, as on the site | [EXAMPLE BUSINESS] |
| Site | The address you send us | example.com (a domain reserved for examples) |
| Business type and area | From the request form | [BUSINESS TYPE], [AREA] |
| Audit | Free or paid | Free |
| Size | Questions and platforms in the run | [AUDIT SIZE] |
| Run dates | Dates each question was run | [RUN DATES] |
| Prepared by | Named person | [AUTHOR NAME] |
02 / Question log
What was asked, where and when
Each question is run more than once, because AI answers change between runs. Every run gets its own row. The answer is recorded as it appeared, with a screenshot in the paid audit.
| # | Question | Platform | Run date | Business named? | Named instead | Cited sources |
|---|---|---|---|---|---|---|
| Q1 | Example: who can fix my website in [AREA]?Recommendation question | [PLATFORM] | [RUN DATE] | [YES / NO] | [NAMES AS SHOWN] | [URLS AS SHOWN] |
| Q2 | Example: what does a technical SEO audit include?Information question | [PLATFORM] | [RUN DATE] | [YES / NO] | [NAMES AS SHOWN] | [URLS AS SHOWN] |
| Q3 | Example: [CUSTOMER QUESTION FROM INTAKE]From the intake form | [PLATFORM] | [RUN DATE] | [YES / NO] | [NAMES AS SHOWN] | [URLS AS SHOWN] |
Observed field Every bracketed cell above is filled from a recorded run. The questions are Example text.
03 / Recorded answer
One recorded answer, in full
- Question
- Q1, run 1
- Platform and date
- [PLATFORM], [RUN DATE]
- Answer as shown
- [ANSWER TEXT, COPIED AS SHOWN]
- Sources the answer cited
- [CITED URLS, IN ORDER]
- Screenshot
- [SCREENSHOT, paid audit only]
04 / Technical check
What the technical check looks at
The paid audit adds this check. Each line gets a result and the pages it affects.
| Area | How we check | Result |
|---|---|---|
| Crawling | Fetch robots.txt and the key pages; note anything blocked or failing. | [RESULT AND PAGES] |
| Indexing | Check noindex tags, canonical tags and whether key pages are indexed. | [RESULT AND PAGES] |
| Structure | Map internal links and find duplicate or orphan pages. | [RESULT AND PAGES] |
| Speed | Run a lab test on mobile for the key pages. | [RESULT AND PAGES] |
| Structured data | Read the JSON-LD and compare it with the visible text. | [RESULT AND PAGES] |
| AI crawler access | Read robots.txt rules for the named AI search crawlers and check the host does not block them. | [RESULT AND PAGES] |
05 / Findings
How a finding is written
Each finding keeps what we saw apart from what we suggest.
What we saw
Observed field
[OBSERVATION, WITH THE RUN OR PAGE IT CAME FROM]
Pages affected: [URLS]
What we suggest
Example text
Example: state the area you serve in the first paragraph of the services page, so a page can answer "who does this in [AREA]?" directly.
Why: an answer is easier to quote when the page says it plainly. This is a reasonable choice, not a proven effect.
06 / Roadmap
The fix list, in order
| Priority | Meaning | Example item |
|---|---|---|
| P0 | Do now | Example: remove a noindex tag left on a page that should be found. |
| P1 | Do next | Example: add a short, direct answer at the top of the services page. |
| P2 | Later | Example: add FAQ markup that matches questions already on the page. |
What we track for the re-check
- For each question: how many runs named the business, out of the runs made.
- Which sources were cited, and whether any of them are your pages.
- Whether the technical issues on the list are fixed.
These are the measures. Their values come from the real runs; this sample has none.
07 / Limits
What the report cannot tell you
- AI answers change between runs, and can differ by account, location and time. The log shows what came back on the dates listed.
- A recorded answer is a snapshot. It does not predict the next one.
- The audit shows where things stand and what to fix. It does not promise a mention or a ranking.
- We only use what is public. We do not need access to your site.
08 / Next
Get your own audit
The free audit uses this format at a smaller size. The paid audit adds the technical check, screenshots and page-by-page findings.