Skip to content
SiteMonk Learn
Esc
↑ ↓ navigate ↵ open ⌘J preview
On this page
  1. Ask what the percentage actually counts
  2. Read two example reports
  3. Decide what evidence justifies the next fee
  4. Optional brief for a specialist

How to review an AI visibility improvement report

Ask for comparable questions, original answers and business relevance before accepting an AI visibility claim.

A provider says AI recommendations increased after its work. Before renewing, ask to see the questions, original answers and the website changes. You can review that evidence without running a research project yourself.

Ask what the percentage actually counts

Ask the provider Why it matters
Were the same customer questions used before and after? Easier questions can make a later score look better
Did questions include the company name? Prompting your name is different from being discovered
Which product, location, language and dates were checked? Different conditions can produce different answers
Can I inspect all original answers and sources? A few favorable screenshots do not show the whole check
Were mentions, recommendations and website citations counted separately? A name or a citation is not automatically a recommendation
How were errors and absent AI answers handled? No answer is not a valid answer that omitted you

For North American local services, use the actual city and state or province, such as Columbus, Ohio or Mississauga, Ontario. Review each language and product separately. A tool using a developer interface may not reproduce the app a customer uses; ask which was checked.

Read two example reports

Harbor Lane Roofing is fictional. These are illustrative observations, not measured results.

Report A: “Recommendations doubled.” The first check found two recommendations in 12 answers, the later check four in 24. Both describe about 17%; the count grew because more answers were checked. Ask for the counts together with the percentages.

Report B: The same questions received two recommendations in 12 answers, then four in 12. That describes a change in those checks. It still does not establish that the page edits caused it: AI answers vary, and other business or product changes may have occurred.

Ask what the company actually changed and whether the new answers cite or reflect the updated information. A recommendation chart alone cannot establish that the new page was read. Google’s AI guidance explains eligibility, not a promise of selection.

Decide what evidence justifies the next fee

A confirmed source error can justify repair. More favorable answers may justify further observation if costs are proportionate. Ask whether suitable inquiries support continued spending. If evidence is incomplete, record the result as undetermined.

Optional brief for a specialist

For a larger repeated check, agree the customer questions, definitions, products, local conditions, budget and stopping date before work starts. Include repeated checks before any change to observe variation. Keep some unchanged questions as a rough comparison, while recording changes that may affect them too.

Save every planned attempt, valid answer, absent AI Overview, error and timeout. Show valid-answer counts; exclude no-answer attempts from answer-based percentages while still reporting them. Keep name checks separate. Compare later rounds under the agreed conditions and preserve the original records. This is repeated observation, not proof of cause, and there is no universal question count or checking schedule.

Start smaller with the quick AI check . For help judging a proposal, see SiteMonk’s technical advisory .

Official sources checked on October 27, 2026. Examples are illustrative, not client results.