# Sample report | RankX

**What does a client report look like?** A walkthrough of the AI Visibility Audit you'd receive, a decision on page 1, then scores, evidence, fixes and the fix list we work from, shown on a fictional business, **Example Ledger Co.** Every number on this page is example data. Illustrative example: not a real client and not real results.

Download the sample as a PDF: /sample/example-ai-visibility-audit.pdf (Example data, fictional business).

## Page 1, the decision, before the detail

**Verdict:** Worth pursuing. The site is crawlable and AI crawlers aren't blocked, but no page answers the questions customers ask, and the business details can't be confirmed from a structured source.

Three moves:

1. Publish an answer-ready FAQ page, starting with "How much does a bookkeeper cost in [Local area]?"
2. Add Organization and LocalBusiness JSON-LD with the current street address
3. Make the business details on public listings match the website footer

What would need to be true:

- Customers ask questions like these before they call (not measured here, prompt measurement is Coming)
- Someone can publish and keep the new pages current
- Someone can make the fixes, our Sprint or your own team, with your sign-off on every change

## One document, three readers

The owner reads the first page, the decision, the scope box, the short fix list. Whoever does the work gets the detail and an editable tracker. And the evidence is logged for anyone who wants to check the working.

- Prepared for: Example Ledger Co. (fictional), https://example-ledger.example
- Report: AI Visibility Audit
- Baseline run: 12 September 2026 · Recheck: 2 October 2026 · Method rankx-rules-v2

## Scope, printed on the cover

- **Measured:** site crawl and page checks (crawl & indexing, on-page, content quality, links & architecture); structured data & sharing checks; security & trust checks; AI search readiness (AI crawler access and readiness heuristics).
- **Not measured:** PageSpeed performance (the performance module didn't run in this example); search visibility & authority (needs market data outside this example's scope); first-party analytics (no GA4 / Search Console access in this example); prompt measurement across ChatGPT, Gemini and Perplexity (Coming, as part of the Retainer).

Areas without data are marked **Not assessed**, never estimated, never a fake 100.

## Score summary

Overall: **61 / 100** across the seven assessed areas (example data). The score summarizes the checks, it doesn't predict inquiries, and it isn't how we report progress. Progress is the fixes we verify.

| Area | What it captures | Score / 100 |
|---|---|---|
| Crawl and indexing | Can crawlers reach and index the site | 70 |
| On-page | Titles, headings and page-level signals | 64 |
| Content quality | Whether pages answer the questions clearly | 55 |
| Links and architecture | Internal linking and site structure | 61 |
| Structured data and sharing | JSON-LD and sharing metadata | 55 |
| AI search readiness | AI crawler access and readiness heuristics (llms.txt noted as optional) | 52 |
| Performance | Page speed signals, needs the performance module | Not assessed |
| Security and trust | HTTPS and baseline trust checks | 72 |
| Search visibility and authority | Market and authority data | Not assessed |

Illustrative overall score: the weighted mean of the assessed areas, using the published method weights (see /methodology/), renormalized over the seven areas assessed here. "Not assessed" areas contribute no number.

## The fixes we promised, rechecked

From the second report onward, a targeted recheck sits near the top: each fix we promised, rechecked under the same inputs. A fix counts only once it's verified. Example data: baseline 12 Sep, recheck 2 Oct.

**2 verified fixed · 2 still open · 1 not rechecked.** 2 new issues found on the recheck.

| Promised fix | Status | Evidence |
|---|---|---|
| Add JSON-LD structured data to key pages | Verified fixed | Organization + LocalBusiness found on home and services; validates cleanly |
| Make business details identical across public listings | Verified fixed | Current street address on the footer and both listings we control |
| Publish an answer-ready FAQ page | Still open | /faq → 404 |
| Build one answer-ready page per service area | Still open | No new service-area pages found |
| Set up AI-referral tracking in analytics | Not rechecked | No analytics access in this example |

New since the last check: two pages now share the same title tag (Low); one public listing still shows the old phone number (Medium).

## Findings, every finding carries its evidence

- **AI crawler access:** AI crawlers can read the site. There's no llms.txt; it's optional (a community proposal, not a search engine requirement), so it's noted, not prioritized.
- **Structured data:** no machine-readable business details; no JSON-LD on home or services pages.
- **Answer-ready content:** no page answers "How much does a bookkeeper cost in [Local area]?"
- **Profiles:** business details disagree across listings; two public listings still show the old address.

## Fix list, ordered by impact × effort

| Fix | Why it matters | Impact | Effort | Suggested owner | At recheck |
|---|---|---|---|---|---|
| Add JSON-LD structured data | Organization, LocalBusiness, FAQPage markup | High | Low | Developer | Verified fixed |
| Publish an answer-ready FAQ page | Including the cost question | High | Medium | Content | Still open |
| Make business details identical across listings | Current address everywhere | Medium | Low | Marketing | Verified fixed |
| Set up AI-referral tracking | So changes show in the client's own numbers | Medium | Medium | Marketing | Not rechecked |
| One answer-ready page per service area | Pages that answer common customer questions | Medium | High | Content | Still open |
| Fix the two pages sharing the same title tag | Found on the recheck crawl | Low | Low | Developer | New |
| Correct the old phone number on one listing | Found on the recheck profile check | Medium | Low | Marketing | New |
| Optional: add /llms.txt | A community proposal, not a search engine requirement | Low | Low | Developer | Optional |

## Next step: the fix list we work from

Every finding becomes a step in a plain-language fix list like this one. In a Sprint, we make the fixes ourselves, and nothing is published without your sign-off. Illustrative example, fictional site, fictional fix list. It covers robots.txt (keep AI crawlers allowed), homepage JSON-LD, an answer-ready /faq with FAQPage markup, making listings match the footer, and, optional, low priority, an llms.txt. Done when: JSON-LD validates, /faq is live and in nav, listings show the current address.

Book a Sprint and we make the top fixes ourselves, then re-audit to verify them. Or share this fix list with your own team.

Get started: /snapshot/ · The audit: /services/ai-visibility-audit/ · Method: /methodology/