GEO Audit Checklist: Be Visible to AI Answers

GEO Audit Checklist: How Visible Is Your Website to AI Answer Engines?

This checklist helps you assess how well generative AI answer engines (ChatGPT, Perplexity, Google AI Overviews, Gemini) find, understand and cite your website. Work through it section by section, ticking off every item you can verify; the open items become your priority list. GEO complements classic SEO rather than replacing it.

Progress: 0 / 30 done

1. Answer-First: Content & Structure

Every core page answers a concrete question directly in the opening paragraph (40-60 words).

Headings (H2/H3) are phrased as real questions or clear statements, not keyword fragments.

Key statements sit in short, self-contained paragraphs that can be quoted standalone.

Lists, tables and definitions summarise complex points in a scannable form.

Technical terms are briefly defined on first use (no unexplained jargon).

An FAQ section covers the real follow-up questions your audience asks.

2. Structured Data & Schema

Relevant Schema.org types (Organization, Article, FAQPage, Product) are implemented as JSON-LD.

The markup is validated with the Rich Results Test or Schema validator (no errors).

Schema values match the visible page content (no misleading or hidden data).

Author, publish date and last-updated date are marked up in a structured way.

Title, meta description and OpenGraph fields are unique and descriptive per page.

A maintained XML sitemap lists all relevant pages with current lastmod dates.

3. Entity Clarity & Authority (E-E-A-T)

Your organisation is clearly identifiable as an entity with consistent name, purpose and location.

Content names a real author with a short bio, credentials and a profile page.

Evidence of experience is visible: case examples, first-hand figures, references.

Name, address and contact details are consistent across site, imprint and external profiles.

The brand is mentioned or linked by independent, credible third-party sources.

A current legal notice and a privacy policy (aligned with revFADP/nFADP) are linked.

4. Technical Access for AI Crawlers

robots.txt intentionally allows (or blocks) AI crawlers such as GPTBot, PerplexityBot, Google-Extended, ClaudeBot.

The decision to allow or exclude AI crawlers is made deliberately and documented.

Core content is available as server-rendered text (not only loaded via JavaScript).

An optional llms.txt points to your key content; note its adoption is not yet widely supported.

Pages load fast, are mobile-friendly and return correct HTTP status codes.

Canonical tags and clean redirects prevent duplicate or orphaned URLs.

5. Freshness, Sourcing & Evidence

Important pages show a visible last-reviewed or last-updated date.

Figures, dates and claims are linked to a verifiable primary source.

Outdated content is reviewed on a schedule and updated or clearly marked as historical.

Legal, health or financial statements point to professionals and current legal positions.

Any legal framework cited is accurate (Switzerland: revFADP/nFADP, FDPIC; EU: EU AI Act, GDPR).

You spot-check whether and how AI answer engines cite your content.

Frequently asked questions

What is GEO and how does it differ from SEO?

GEO (Generative Engine Optimization) optimises content to be understood and cited by AI answer engines such as ChatGPT, Perplexity or Google AI Overviews. SEO targets classic search rankings; GEO aims to be part of the generated answer. Both rest on the same foundations, so GEO complements your SEO rather than replacing it.

Should I allow or block AI crawlers in robots.txt?

It depends on your goal: to be visible in AI answers, the relevant crawlers need access. If you do not want your content used as training or answer material, you can exclude them. Make the choice deliberately, document it, and note that robots.txt directives cannot always be enforced.

Does my website need an llms.txt file?

llms.txt is a proposed standard that bundles a site's most important content for AI systems. It is optional and not yet widely supported, but it does no harm and fits a complete GEO setup. Prioritise clean structure, schema and accessibility first; llms.txt is an add-on, not a substitute for those.

Does this checklist replace a legal review of my website?

No. This checklist offers practical guidance on AI visibility, not legal advice, and ticking the items does not guarantee compliance. For data protection, legal notice and AI-relevant duties (Switzerland: revFADP/nFADP, FDPIC; EU: EU AI Act), have your website reviewed by qualified professionals.