GEO Audit Checklist: How to Assess AI Search Visibility Without Guesswork

#What a GEO audit should answer

A GEO audit should show whether priority content can be accessed, whether it is useful and verifiable enough to serve as a source, how the brand currently appears in generated answers, and whether that visibility produces qualified business activity. It should not promise future citations or compress every finding into a mysterious “AI ranking score.”

The audit has seven parts:

1. Goals and prompt baseline.
2. Search eligibility and crawler access.
3. Content usefulness and extractability.
4. Evidence, authorship, and entity accuracy.
5. Structured data and machine-readable surfaces.
6. Citation and competitor patterns.
7. Analytics, conversion, and experiment design.

Use this checklist for Google AI Overviews and AI Mode, ChatGPT Search, and Perplexity. Record platform-specific evidence rather than assuming one engine's behavior applies to the others.

#Before the audit: define the scope

Do not begin by scanning every page. Begin with the decisions the content is expected to influence.

• [ ] Identify 3–5 business-critical services, products, or categories.
• [ ] Define the countries and languages that matter.
• [ ] Select 3–5 direct competitors for each category.
• [ ] Identify the primary conversion: audit request, demo, qualified lead, purchase, or another event.
• [ ] Choose the owned pages that should support each category.
• [ ] Agree on a review window and who will validate technical, editorial, and business findings.

#Build a prompt cohort

Create 20–50 prompts that reflect real research behavior. Use the same wording for every baseline and follow-up run.

For each observation, record platform, model or mode where available, language, location context, date, session state, answer, linked sources, brand mention, competitors, and factual errors.

#Part 1: Google Search eligibility

Google states that its generative AI features use the core Search index and quality systems. Start with ordinary Search requirements.

• [ ] Priority URLs return 200 and are not blocked by robots.txt.
• [ ] Pages are not marked noindex and are eligible to show a snippet.
• [ ] Canonicals point to the intended indexable URL.
• [ ] Pages appear in the XML sitemap with accurate modification dates.
• [ ] Main content is visible in rendered HTML.
• [ ] Internal links connect hubs, supporting articles, and commercial pages.
• [ ] Google Search Console shows the expected indexed canonical.
• [ ] The Search generative AI control is not excluding the property when inclusion is desired.
• [ ] The dedicated Generative AI performance report is reviewed if the property has access.

Google's AI optimization guide says there is no special AI markup, required text length, or chunking formula.

#Part 2: AI search crawler access

Crawler names have different purposes. Audit the actual documented search crawler rather than allowing every bot under an “AI” heading.

#ChatGPT Search

• [ ] OAI-SearchBot is not blocked when ChatGPT Search inclusion is desired.
• [ ] WAF, CDN, and bot management rules allow OpenAI's published searchbot IP ranges.
• [ ] The policy for GPTBot is documented separately because it relates to potential model training.
• [ ] The team understands that ChatGPT-User may be used for user-initiated visits and is not the automatic Search crawler.

Source: OpenAI crawler documentation.

#Perplexity

• [ ] PerplexityBot is not blocked when Perplexity search inclusion is desired.
• [ ] Published Perplexity IP ranges are not rejected by infrastructure.
• [ ] Server logs are checked for successful crawler responses and unexpected 403, 429, or 5xx patterns.

Source: Perplexity crawler documentation.

#Policy check

• [ ] Search inclusion, model training, and user-initiated fetching are treated as separate decisions.
• [ ] Legal, privacy, and content teams approve the policy.
• [ ] robots.txt and edge security implement the same decision.
• [ ] Changes are dated and documented.

Crawler access supports discovery. It does not guarantee selection or citation.

#Part 3: Content usefulness and extractability

Review the priority pages as a skeptical buyer and as an editor.

• [ ] The page directly answers its primary question near the beginning.
• [ ] The content adds first-hand experience, original data, a method, a template, or a decision framework.
• [ ] Important terms are defined in plain language.
• [ ] Headings reflect reader tasks rather than keyword variations.
• [ ] Tables are used for genuine comparisons.
• [ ] Processes use ordered steps.
• [ ] Each key paragraph can be understood without an unexplained pronoun or missing qualifier.
• [ ] The page covers limitations and cases where the recommendation does not apply.
• [ ] The content has a visible publication or update date in metadata.
• [ ] The next step is appropriate for the reader's buying stage.

Do not optimize for an invented token window. Google explicitly says it can understand multiple topics on a page and does not require publishers to divide content into tiny AI-oriented chunks.

#Part 4: Evidence and claim review

Create a claim ledger for every priority page.

• [ ] Every statistic links to an original or authoritative source.
• [ ] The source actually supports the wording used on the page.
• [ ] Dates, products, crawler names, and standards are current.
• [ ] Case results include baseline, period, scope, and material changes.
• [ ] Correlation is not described as causation.
• [ ] Superlatives such as “best,” “leading,” or “top 1%” have evidence or are removed.
• [ ] Guarantees concern deliverables under the provider's control, not third-party search outcomes.
• [ ] Authors are real people or an accurately identified organization.

#Part 5: Entity and structured data review

Structured data should reflect visible facts. It can help systems understand page entities and qualify pages for supported Search features, but Google says there is no special schema required for generative AI search.

• [ ] Organization name, legal identity, URL, logo, and contact facts are consistent.
• [ ] Service names and descriptions agree across navigation, landing pages, articles, and public profiles.
• [ ] Author markup matches the visible author.
• [ ] Article or TechArticle data uses accurate datePublished and dateModified values.
• [ ] Breadcrumb markup matches visible navigation.
• [ ] Structured data validates and does not describe hidden content.
• [ ] Only supported, relevant Schema.org types and properties are used.
• [ ] Non-versioned URLs such as https://schema.org/Organization are used.
• [ ] “Schema 3.0” or other invented AI schema layers are removed.

Schema.org's public release history lists version 30.0 as the current release at the time of this audit template. Publishers generally use the ordinary non-versioned vocabulary URLs.

#Part 6: llms.txt review

Treat llms.txt as an optional navigational file for agents that choose to use the proposal—not as a ranking factor.

• [ ] The file describes the business accurately.
• [ ] Links resolve to canonical public pages.
• [ ] Claims match visible website content.
• [ ] Stale services, prices, authors, and results are removed.
• [ ] The file is not presented as a Google visibility factor.
• [ ] Deployment is not counted as a citation result.

Google says Search ignores llms.txt. The specification calls itself a proposal. A valid file may still be useful for documentation or agent workflows that deliberately request it.

#Part 7: Citation and competitor analysis

Run the agreed prompt cohort and create a source map.

• [ ] Record owned citations separately from unlinked brand mentions.
• [ ] Record third-party pages that mention the brand.
• [ ] Identify recurring competitor sources.
• [ ] Classify each cited source: official documentation, publisher, directory, review, forum, social, academic, or other.
• [ ] Note whether the cited passage directly supports the generated claim.
• [ ] Record factual inaccuracies and outdated descriptions.
• [ ] Identify questions for which no current source gives a strong answer.
• [ ] Prioritize gaps by buyer importance, not by citation count alone.

Do not copy a competitor's format blindly. Determine what uncertainty its page resolves and whether you can contribute stronger evidence.

#Part 8: Measurement and conversion

• [ ] Google Generative AI impressions are exported where Search Console provides the report.
• [ ] AI referral sources and UTM parameters are preserved in analytics.
• [ ] ChatGPT referrals using utm_source=chatgpt.com are monitored.
• [ ] Landing page, engagement, conversion, and qualified lead data are connected.
• [ ] Brand mention rate and owned citation rate are separate metrics.
• [ ] Sentiment and factual accuracy use a documented classification rubric.
• [ ] The same prompt cohort is rerun on a fixed cadence.
• [ ] Reports state platform, market, sample size, and limitations.

Use the AI visibility measurement guide for formulas and a reporting template.

#How to prioritize findings

Classify each finding by evidence, impact, and control.

An audit score can help organize work, but it is not an AI-platform score and should never be presented as a prediction of citations.

#Recommended audit deliverables

A useful audit should produce:

1. A documented scope, prompt cohort, competitors, markets, and date.
2. A technical eligibility report with reproducible evidence.
3. A page-level claim ledger.
4. A source and citation map.
5. An entity inconsistency list.
6. A prioritized 30/60/90-day backlog with owners.
7. A measurement specification and baseline export.
8. A list of assumptions that still require testing.

#Bottom line

A GEO audit is a disciplined evidence review, not a magic score. Fix eligibility first, unsupported claims second, and source quality third. Then measure whether visibility, referrals, and qualified business outcomes change under a repeatable protocol.

For the strategic context behind this checklist, read the complete GEO guide. AppWebSeo can also run the technical, editorial, and measurement review as one scoped diagnostic.

#Primary sources

• Google: Optimizing for generative AI features
• Google Search Console: Generative AI performance report
• Google: Search generative AI control
• OpenAI: Overview of OpenAI crawlers
• OpenAI: Publishers and Developers FAQ
• Perplexity: Crawler documentation
• Google: Structured data guidelines
• Schema.org: Releases
• The `llms.txt` proposal