SAMPLE REPORT — fictional business — illustrative, not a client result

Sample AI Revenue Readiness Report™

Harbor & Pine Bistro

Restaurant · 60 seats · reservations by phone · harborandpine.example

An AI assistant asked for 'a good seafood place near the harbor that takes reservations' could not confirm Harbor & Pine's cuisine, hours or how to book, so it was likely to recommend competitors with clearer data.

Before

31/100

After Get Found (illustrative)

79/100

AI Visibility

28→82

Business Understanding

45→85

Structured Data

10→90

Agent Discovery

5→80

Transaction Readiness

40→70

Payment Readiness

55→60

Download the sample report (PDF)
Harbor & Pine Bistro is a fictional business created to show what our report contains. Every score, finding and result on this page is illustrative — it is not a client result.

Findings & exact fixes

1. No structured business data

critical

What AI sees: AI systems cannot reliably confirm cuisine, address, hours, price range or that the restaurant takes reservations.

Exact fix: Add Restaurant JSON-LD to every page with address, geo, openingHours, servesCuisine, priceRange, acceptsReservations and menu URL.

{"@context":"https://schema.org","@type":"Restaurant","name":"Harbor & Pine Bistro","servesCuisine":["Seafood","Italian"],"priceRange":"$$","acceptsReservations":true,"openingHours":"Tu-Su 17:00-22:00","menu":"https://harborandpine.example/menu"}

2. AI crawlers are blocked

critical

What AI sees: robots.txt disallows all bots except Googlebot, so GPTBot, ClaudeBot and PerplexityBot cannot read the site at all.

Exact fix: Rewrite robots.txt to allow AI search and assistant crawlers and link the sitemap.

User-agent: GPTBot
Allow: /
User-agent: ClaudeBot
Allow: /
User-agent: PerplexityBot
Allow: /
Sitemap: https://harborandpine.example/sitemap.xml

3. Menu is an image-only PDF

high

What AI sees: Dishes, dietary options and prices are invisible to AI because they exist only as pixels in a PDF.

Exact fix: Publish an HTML menu page with Menu, MenuSection and MenuItem markup including prices and dietary labels.

4. No llms.txt

high

What AI sees: There is no plain-language summary an AI model can read in one request.

Exact fix: Publish /llms.txt with the restaurant's summary, hours, booking link, menu link and policies.

# Harbor & Pine Bistro
> Seafood & Italian bistro on the harbor. Tue–Sun 5–10pm. Reservations online.
- [Menu](https://harborandpine.example/menu)
- [Book a table](https://harborandpine.example/reserve)

5. Booking only by phone

high

What AI sees: No machine-readable way to check availability or request a table, so an agent cannot complete the booking.

Exact fix: Connect the existing reservation platform and expose it with a ReserveAction in the schema. Whether an AI agent can complete the booking depends on that platform's integrations.

6. Hours conflict across sources

medium

What AI sees: Website says closed Mondays; business listing says open, so AI systems treat the hours as unreliable.

Exact fix: Align hours on the website, schema and business listings, and add holiday hours.

7. Policies are hard to find

medium

What AI sees: Deposit, cancellation and allergy policies are buried in a footer image.

Exact fix: Publish a plain-text policies page and reference it in the schema and llms.txt.

What the owner receives with Get Found — $2,997 setup + $297/month

  • AI Revenue Readiness Audit
  • AEO/GEO audit + remediation
  • Machine-readable business identity
  • Structured services & product information
  • Pricing & policy clarity
  • Schema.org implementation
  • FAQ optimization & direct-answer content
  • Sitemap, robots & crawler remediation
  • AgenticReady Manifest
  • Before-and-after scoring + QA
  • Monthly monitoring & readiness report
  • Join Group Calls — 4+ hours a month virtually for consultancy on AI and the moves you should be making

Score improvements are measured, not promised as rankings. See AI visibility vs. AI transactions.