14 — GEO and AEO Checklist#

Improve how clearly and reliably a project can be understood, sourced, and answered by search answer systems and generative AI. GEO = Generative Engine Optimization; AEO = Answer Engine Optimization. Neither guarantees citation or inclusion.

Scope: Shared / cross-cutting. This file is one part of the 14_GEO_and_AEO.md checklist. Apply the domain-wide release gate across all applicable scope files; each checklist ID remains unique.

Review details#

Project / product:
Release / version / environment:
Scope and applicable jurisdictions / markets:
Reviewer / owner:
Review date:
Decision: Pending / Approved / Approved with documented exceptions / Blocked

How to use#

Copy this template into each project's review records; keep the shared repository template unchecked.
Check [x] only after verifying the item with evidence. For any inapplicable item, record N/A and the reason in the project's own review notes or issue tracker using its checklist ID; do not mark it as passed.
Record evidence links or artifact references by checklist ID. Open an issue for every failed item, assign an owner and due date, and retest after remediation.
Apply the release gate below. These checklists guide review; they do not replace qualified specialist review when required.

Audience, answer intent, and coverage#

GEO-001 High-value user questions, follow-ups, and conversational queries are inventoried.
GEO-002 Questions are mapped to authoritative, relevant pages with a clear intended answer.
GEO-003 Content distinguishes definitions, instructions, comparisons, FAQs, and decision criteria.
GEO-004 Answers reflect audience knowledge level and include scope, caveats, and applicability.
GEO-005 Important topics have sufficient depth and context beyond isolated keyword phrases.
GEO-037 Include legitimate comparison and follow-up questions without making redundant doorway pages.
GEO-038 Evaluate whether visitors can independently verify critical claims from the cited primary evidence.
GEO-039 Identify authoritative, public canonical pages for each product, concept, service, or policy.

Answer-ready structure and clarity#

GEO-006 Priority pages state a concise, accurate answer close to the related question or heading.
GEO-007 Headings, short paragraphs, numbered steps, and tables organize information where useful.
GEO-008 Terms, entity names, units, dates, and product/version details are explicit and unambiguous.
GEO-009 Key claims include methodology, assumptions, limitations, and dates where relevant.
GEO-010 FAQs address genuine user needs and avoid repetitive or fabricated question-answer blocks.
GEO-011 Structured examples or comparisons are accurate and consistent with the surrounding narrative.
GEO-040 State prerequisites, limitations, and conditions near short answers where omission would mislead.
GEO-041 Ensure charts, figures, and videos have textual context sufficient to convey important facts.

Authority, provenance, and factual reliability#

GEO-012 Claims that could affect decisions are backed by trustworthy, attributable sources.
GEO-013 First-party data, original research, real examples, or demonstrated expertise are identified when available.
GEO-014 Authors, organizations, editorial responsibility, and update history are stated accurately.
GEO-015 Statistics and time-sensitive facts are dated, checked, and scheduled for refresh.
GEO-016 Citations and outbound links lead to the actual source and do not imply endorsements.
GEO-017 Product names, specifications, organization facts, and public profiles are consistent across owned channels.
GEO-043 Maintain a provenance record for changing datasets, prices, statistics, and public statements.
GEO-044 Set a review schedule and visible update date for pages with material time-sensitive facts.

Machine readability and discovery#

GEO-020 Canonical URLs, sitemap entries, internal links, and index directives are consistent with the SEO checklist.
GEO-021 Schema.org markup is used only where appropriate, valid, and supported by visible page content.
GEO-022 Important assets, downloads, and data tables have descriptive text or accessible alternatives.
GEO-047 Use provider-published crawler guidance to distinguish search crawling from model-training controls where relevant.
GEO-048 Check structured data is consistent with page text and avoid fabricated organization/entity identifiers.

Trustworthy answer experience#

GEO-026 Direct answers avoid exaggerated certainty, misleading superlatives, and unsupported comparisons.
GEO-027 Policies, pricing, availability, support details, and product limitations are easy to locate and current.
GEO-028 Where appropriate, content identifies geographic, regulatory, language, or version differences.
GEO-029 Answer snippets preserve context and do not omit material safety, cost, or eligibility caveats.
GEO-030 Public contact, entity, and brand information is consistent and can be verified independently.
GEO-049 Make sources and important qualifications accessible from short answer sections and summaries.
GEO-050 Test quotations and paraphrases for faithful context rather than optimizing only for answer length.
GEO-051 Provide explicit correction paths when publicly shared answers or data are found to be wrong.

Measurement and iteration#

GEO-031 Baseline questions and evaluation criteria are documented before optimization.
GEO-032 Sampled answers are checked across relevant answer/search systems without assuming all results are stable.
GEO-033 Observed mentions, citations, factual accuracy, referral traffic, and conversions are tracked separately.
GEO-036 Changes are reviewed for measurable user benefit and aligned with SEO, accessibility, privacy, and legal constraints.
GEO-052 Keep a dated, reproducible sample of prompts/questions and any observed citations for trend analysis.
GEO-053 Separate ranking, crawl/index diagnostics, referral logs, answer sampling, and conversions in reports.

Release gate#

All applicable high-priority checks above pass, or an authorized decision-maker has explicitly accepted and documented each residual risk.
Failed items have tracked remediation, owners, and deadlines; material blockers remain blocked until resolved.
Evidence links and the reviewer, review date, and final decision are recorded.

Domain-specific approval rule: Do not approve deceptive, fabricated, or unsubstantiated content. Verify essential public facts and make evidence available; AI answer visibility cannot be promised.

Trusted references and scope#

The checks above are adapted into practical verification questions from these authoritative publications (not copied as standards text). Verify current versions and the project's scope before sign-off.

GEO/AEO techniques are not separate eligibility requirements for Google AI Overviews or AI Mode. Google documents ordinary Search eligibility, helpful content, and no required AI-specific markup. Other providers differ; inclusion and citations are not guaranteed.

Source review date: 2026-11-12.

Suggested testing tools#

Choose tools appropriate to the project's stack and risks; automation supports evidence but does not approve the checklist.

Test focus: machine-readable answers, structured data, citation links, and content consistency (not rankings); include shared/cross-team controls where applicable.
Cross-stack: Schema.org Validator + lychee.
Python: Beautiful Soup + pytest; for pytest-based suites, run python -m pytest -q.
TypeScript: Playwright + schema-dts + Vitest; for Vitest-based suites, run npx vitest run (or npx playwright test for E2E).
JavaScript: Playwright + Ajv + Jest; for Jest-based suites, run npx jest --ci (or npx playwright test for E2E).
Evidence: Save tool versions, configuration, test environment, fixtures, results, and links in project-specific review records using the existing checklist IDs. Expert review remains necessary where relevant.

Suggested AI skills for verification#

These are optional agent review aids, not automated passes or release approval. Each linked repository had at least 1,000 GitHub stars when checked on 2026-11-12; counts are per repository, not per skill, and do not indicate security or correctness.

ai-seo — Review answer-engine discoverability and source quality (coreyhaines31/marketingskills, 59,899 repo stars).
schema — Check machine-readable content structure (coreyhaines31/marketingskills, 59,899 repo stars).
seo-audit — Identify crawl and citation-link issues (coreyhaines31/marketingskills, 59,899 repo stars).

How to check: In a project-specific copy, have the agent audit the shared / cross-cutting scope and map findings to this file's existing checklist IDs, with code/configuration references, reproducible test results, failed or inapplicable cases, and uncertainties. Independently verify findings; keep shared template boxes unchecked and retain human approval requirements.

Before use: Read the skill's SKILL.md, referenced scripts, license, and requested tool permissions. Only execute vetted skills with appropriate access in a controlled environment.

Important warning: reference only#

⚠️ Reference only — not a definitive or exhaustive checklist. This template is a starting point for review, not the ultimate authority or a guarantee of project safety, quality, regulatory compliance, accessibility, security, or launch readiness.

Use project-specific judgment and independent verification. Requirements and risks evolve and differ by project, technology, and jurisdiction. Adapt the checks, consult current authoritative sources, perform relevant tests, and obtain qualified specialist review or approval when appropriate. Checking every box does not replace these steps.