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: Frontend-specific. 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#

1. Copy this template into each project's review records; keep the shared repository template unchecked.
2. 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.
3. 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.
4. Apply the release gate below. These checklists guide review; they do not replace qualified specialist review when required.

Answer-ready structure and clarity#

• GEO-042 Test that extracted answer snippets still make sense without the original page title or navigation.

Machine readability and discovery#

• GEO-019 Relevant public pages are crawlable and render essential content in accessible HTML.

Frontend Checks#

Apply to browser-based, mobile-web, embedded, or other user-facing interfaces. Record N/A with reasons for headless services.

Reference basis: Google Search Central — AI features and your website; Google Search Central — Guide to optimizing for generative AI features; Google Search Central — JavaScript SEO basics.

• GEO-066 Put a direct, accurate answer near the relevant question while retaining context and meaningful caveats.
• GEO-067 Use descriptive headings, semantic HTML, tables, and lists that remain understandable without interactive widgets.
• GEO-068 Expose primary facts in rendered textual content; give charts, images, and media adequate text alternatives.
• GEO-069 Use stable public URLs and standard anchor links to canonical source pages.
• GEO-070 Verify initial HTML/rendered output shows the essential content to intended crawlers, including JavaScript-based pages.
• GEO-071 Match visible headings, answers, dates, and entities to supported structured data without invisible or invented claims.
• GEO-072 Present citations and source links where a reader can inspect supporting primary information.
• GEO-073 Avoid misleading summaries, unsupported numerical claims, or fabricated quotes in callouts and snippets.
• GEO-074 State geographic scope, eligibility, currency, date, and relevant version in comparative answer sections.
• GEO-075 Test mobile layout, accessibility, readability, and critical interactions so sources are usable by humans.
• GEO-076 Check translated or region-specific pages keep facts, named entities, and caveats consistent across languages.
• GEO-077 Confirm outdated or deleted content results in a clear correction/redirect or appropriate missing-page status.
• GEO-078 Make public contact, organization, product, and publication details consistent across page templates.

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.

• Google Search Central — AI features and your website
• Google Search Central — Guide to optimizing for generative AI features
• Google Search Central — JavaScript SEO basics
• Google Search Central — Structured data introduction
• OpenAPI Specification 3.2.1
• NIST — Generative AI Risk Management Profile

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 browser and client behavior 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 frontend 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.