AEO content checklist for 2026: 47 checks to make every page citation-ready
A practical 47-item AEO checklist organized by stage: pre-publication structure, on-page formatting, schema markup, E-E-A-T signals, post-publication validation, and ongoing maintenance. Apply it to every new article and to your top 20 existing pages — the difference between cited and ignored content usually comes down to whether these checks were done systematically or skipped.
This is a 47-item AEO checklist organized by workflow stage: 12 pre-publication checks (planning and structure), 9 on-page formatting checks, 11 schema markup checks, 8 E-E-A-T and author signal checks, 5 post-publication validation checks, and 7 ongoing maintenance checks. Apply it to every new article you publish and work through your top 20 existing pages systematically. Most pages that fail to get cited by AI engines fail not because the writer didn't know what to do, but because they didn't run through a structured checklist before publishing — small omissions compound into invisibility.
A checklist isn't optional in 2026. AI engines (ChatGPT, Perplexity, Google AI Overviews, Gemini) evaluate dozens of structural signals when deciding which pages to cite. Missing one or two signals weakens citation eligibility. Missing five or six often makes a page invisible to AI synthesis entirely, even if the content is genuinely high-quality.
This checklist synthesizes the practices covered in our foundational AEO guide, schema markup guide, FAQ schema implementation guide, and our engine-specific deep dives for ChatGPT, Perplexity, and Google AI Overviews. The 47 items below cover every meaningful structural decision that affects whether AI engines cite the page.
Stage 1: pre-publication checklist (12 items)
Run these checks during the planning and writing phase, before you publish.
Topic and query selection:
- Page targets a specific question users actually ask, not a keyword stuffed into a question shape
- Target query has measurable AI engine query volume (ran in ChatGPT/Perplexity/Google to verify it produces an answer with citations)
- Target query is winnable — you can plausibly become a top citation source within 3-6 months given your domain authority and topical density
Content depth and originality:
- Article will be 2,000+ words (research validates 293% growth advantage over articles under 1,000 words)
- Article includes original perspective, data, examples, or analysis — not summarizing what's already widely available
- At least 2-3 specific named sources cited (studies, tools, named experts) for major claims
- At least one quantitative claim with specific numbers and attribution
Structural planning:
- Direct answer to primary question identified before writing first paragraph (50-80 words)
- H2 hierarchy mirrors the questions readers actually ask, not keyword variations
- FAQ section planned with 5-7 buyer/reader questions identified
- Internal links to 2-3 related existing articles planned where natural
- Article fits into existing topic cluster on your site (not topical sprawl into new niches)
Stage 2: on-page formatting checklist (9 items)
Run these during the writing and editing phase.
Opening structure:
- First sentence directly answers the article's primary question
- First 50-80 words contain a complete answer that could be cited as a self-contained unit
- No preamble like "In this guide we'll explore..." or "There are several factors..." — direct answer first
Mid-content structure:
- Each H2 section opens with a topic-sentence answer to the question implied by the heading
- Comparison content includes at least one structured table where direct comparison applies
- Specific factual claims appear with attribution rather than as vague statements ("studies show" replaced with "Stanford 2025 research showed")
- No keyword stuffing — keywords appear only as natural language requires
FAQ section:
- FAQ section present with 5-7 question-answer pairs at end of article
- Each FAQ answer is 30-70 words and starts with a direct answer
Stage 3: schema markup checklist (11 items)
Run these during the technical implementation phase, before publishing.
Article schema:
- BlogPosting or Article schema present in
<head>as JSON-LD - Required fields present:
headline,description,datePublished,dateModified,image,author -
authorfield is full Person sub-schema, not just a string - Person sub-schema includes
name,urllinking to bio page,sameAsarray with social profile URLs -
publisherfield is Organization sub-schema withname,url,logo
FAQPage schema:
- FAQPage schema present matching the visible FAQ section
- Each Q&A pair in JSON-LD also appears verbatim (or nearly so) in visible HTML
-
namefield in each Question is plain text without HTML markup - Only one FAQPage block per URL (not multiple)
Specialty schemas (where applicable):
- HowTo schema added if article is genuinely a step-by-step tutorial (not all how-to articles qualify; Google has tightened HowTo eligibility)
- Review schema with proper Person reviewer + Product/SoftwareApplication entity if article is a product review
Stage 4: E-E-A-T and author signal checklist (8 items)
Run these checks for every article. Without these, schema and content optimization both underperform.
Author identity:
- Article has a real named author (not "Editorial Team" or "Admin" or generic byline)
- Author has a bio page on your site (
/authors/[slug]) with substantive content demonstrating relevant expertise - Bio page includes credentials, years of experience in the topic, prior work samples
- Bio page links to verified professional profiles (LinkedIn essential for B2B; Twitter/X for tech; relevant industry profiles for niche topics)
Visible author signals on the article:
- Visible byline with author name near article header
- Author photo visible near byline (small headshot, real photo not stock)
- 1-2 sentence "About this author" near top of article (or pull-quote style)
Experience markers in body content:
- At least one first-person experience marker in body ("after testing for 3 weeks," "in our research," "we ran X queries")
Stage 5: post-publication validation checklist (5 items)
Run these immediately after publishing the page.
- Validate JSON-LD with Google's Rich Results Test (
search.google.com/test/rich-results) — zero errors required - Validate JSON-LD with Schema.org Validator (
validator.schema.org) — green checkmarks across all entities - Manually cross-check schema content against visible page content — substance must match
- Submit URL via Google Search Console URL Inspection → Request Indexing
- Add the page URL to your AEO citation tracking spreadsheet for weekly manual citation checks
Stage 6: ongoing maintenance checklist (7 items)
Run quarterly on your top 20 pages, or when you notice a page losing rankings.
Content freshness:
-
dateModifiedupdated whenever you make material changes (not just typo fixes) - Specific factual claims (prices, statistics, named tools) verified as still accurate
- References to "current year" or "as of [date]" still relevant
Technical health:
- Page still loads under 2.5s on mobile (Core Web Vitals check)
- All internal links still resolve (no 404s from cascading deletions)
- Schema still validates with Google's Rich Results Test (CMS updates can break schema)
Citation tracking:
- Manual AI citation rate checked weekly across major engines for queries this page targets
How to apply this checklist at scale
If you have 50+ existing pages, running 47 checks per page is 47 × 50 = 2,350 checks. Done sequentially that's weeks of work. Make it tractable:
Priority by traffic potential. Start with your top 20 pages by historical traffic. Apply the full checklist to each. The other 30 pages get attention only if they're rescuable; otherwise consider deletion.
Batch by check type, not by page. Instead of going page-by-page, batch by checklist stage:
- Day 1: run Stage 4 (author signals) across all 20 pages — usually similar fixes per page, faster batch
- Day 2: run Stage 3 (schema) across all 20 pages
- Day 3: run Stage 2 (formatting) across all 20 pages
- And so on
This is 5-10x faster than going page-by-page because context-switching cost dominates per-check time.
Use templates and tools where they save time. Author bio pages, schema markup blocks, FAQ structures — all benefit from templates. The compounding work (real expertise demonstration, original research, named expert quotes) is what you protect for direct attention.
Re-run quarterly on top performers. Pages that drove 80% of historical traffic deserve quarterly maintenance. Pages that drove 20% might not be worth ongoing attention; they're maintenance debt with low ROI.
What to skip if you have to choose
If you can only do 10 of the 47 items, do these (highest impact):
- Direct answer in first 50-80 words (Stage 2)
- Article schema with full Person author sub-schema (Stage 3)
- Real named author with bio page (Stage 4)
- FAQPage schema mirroring visible FAQ section (Stage 3)
- 5-7 visible FAQ pairs at end of article (Stage 2)
- 2,000+ word count with original perspective (Stage 1)
- At least one quantitative claim with named source (Stage 2)
datePublishedanddateModifiedcorrect in schema (Stage 3)- Validate JSON-LD with Google's Rich Results Test (Stage 5)
- Internal link to 2-3 related articles in your topic cluster (Stage 1)
These ten cover roughly 75% of the citation rate impact of the full 47. Sites time-constrained should prioritize getting these consistently right across all pages before tackling the long tail of remaining items.
Common reasons pages fail the checklist silently
The checks that matter most but are easiest to skip:
- Anonymous authorship. Easy to skip when you don't have established authors. Becomes a hard filter for AI citation eligibility, especially in YMYL topics.
- Schema typos.
"@type": "FaqPage"instead of"FAQPage". The schema is silently ignored — no error message, just zero AI citation impact. - Stale content with current dates. Article shows "Updated 2026" but mentions discontinued products. AI engines fact-check claims against current data and downweight pages with mismatches.
- Hidden FAQs. Q&A pairs in schema that don't appear in visible HTML. Violates Google guidelines explicitly; AI engines filter silently.
- Topical sprawl. Site covers 10 topics shallowly instead of 1-2 topics deeply. AI engines treat broad/shallow sites as content farms regardless of individual page quality.
- Keyword stuffing. Counterintuitively decreases citation rate. The original GEO research paper (2023) measured this directly.
- Generic intro paragraphs. Opening with "In this guide we'll explore..." rather than direct answer. Engines extract from opening; weak opening = weak extraction signal.
How long this checklist takes per article
Realistic time estimates (assumes you have author bio pages and CMS templates already set up):
- Stage 1 (planning): 30-60 minutes if topic chosen well; 2+ hours if topic-fit research needed first
- Stage 2 (writing/formatting): Built into article writing time; doesn't add separate hours if checklist is mental during writing
- Stage 3 (schema): 15-30 minutes per article using templates; 1-2 hours if writing JSON-LD by hand or using a free FAQ schema generator
- Stage 4 (E-E-A-T): 5-10 minutes per article if author bio infrastructure exists; major one-time investment if you need to build bios from scratch
- Stage 5 (validation): 10-15 minutes per article (run validators, request indexing, add to tracking sheet)
- Stage 6 (maintenance): 30-45 minutes per article quarterly
Total for new article publishing with full checklist: about 60-90 minutes of checklist-specific work on top of writing time. The ROI: significantly higher citation eligibility versus pages skipping the discipline.
What this checklist doesn't cover
Limits worth knowing:
It assumes content quality. The checklist optimizes the structural layer around content. Genuinely poor content with perfect checklist compliance still won't get cited. Substance > structure when forced to choose.
It doesn't address backlink building. External authority signals matter for both SEO and AEO foundations. The checklist focuses on on-page work; off-page work (link earning through original research, outreach, partnerships) is a separate discipline.
It doesn't cover distribution. Publishing alone isn't enough. The X thread + LinkedIn post + outreach work that drives initial traffic to a page is critical for accumulating signals AI engines weight. Distribution is separate from this checklist.
It assumes legitimate use. This is an optimization checklist for genuine content. Trying to game it through fake authorship, AI-generated content with false attribution, or schema spam will get caught and penalized. The checklist works because it aligns with what AI engines actually want; trying to satisfy it without substance defeats the purpose.
FAQ
How many of these 47 checks are absolutely required for AEO citation eligibility?
Should I run this checklist before or after writing the article?
Can I skip the schema checklist if my CMS adds schema automatically?
How often should I re-run the checklist on existing pages?
What's the biggest mistake people make using AEO checklists?
Closing
A 47-item checklist sounds heavy. In practice, after running it on 10-15 articles it becomes habituated — most items become automatic decisions during writing rather than separate verification steps. The compounding benefit: pages built with checklist discipline from the start outperform pages retrofitted with the same items added later, because the structural decisions integrate with content decisions when made together.
If you're starting today: don't try to apply all 47 items to all your existing pages immediately. Pick 3 priorities — your highest-traffic pages — and apply the full checklist to each. Use them as templates for your writing process going forward. The first batch reveals which items are easy and which require infrastructure investment (usually author bios). Tackle infrastructure once; apply the rest as a normal part of publishing.
The work is bounded but real. The result, when done consistently, is the difference between content that gets cited by AI engines and content that gets ignored — even when both pieces are equally substantive in their underlying ideas.