# The SEO/GEO Optimization Checklist (2026) > A standalone checklist for optimizing any piece of content for traditional SEO, Generative Engine Optimization (GEO), and Answer Engine Optimization (AEO). > > Print this and tape it next to your monitor. Run every article through it before publishing. --- ## Section 1: Structure for AI Extraction (GEO) The single most important shift in 2026 SEO. AI models cite content by extracting discrete claims. If your key points are buried in long narrative paragraphs, they won't get extracted. If each section opens with a clear, self-contained sentence stating a fact or claim, AI models will find it, quote it, and link back to you. - [ ] Every major section (H2) opens with a clear, self-contained claim sentence - [ ] Paragraphs are 2-3 sentences max (not dense walls of text) - [ ] A direct-answer paragraph appears within the first 200 words for the primary keyword - [ ] Lists are formatted as proper HTML lists (not numbered paragraphs) - [ ] Comparisons are formatted as tables when appropriate - [ ] Definitions follow the "X is Y because Z" sentence pattern - [ ] No critical claim is buried more than 2 paragraphs from its supporting heading **Test:** Read just the first sentence of each H2 section. Does each one stand alone as a quotable claim? If yes, you pass. --- ## Section 2: Optimize for Featured Snippets (AEO) Featured snippets and "People Also Ask" boxes are the precursors to AI Overviews. Content that appears in these is more likely to get cited by AI models. - [ ] FAQ sections are formatted as explicit Q&A (question as H3, answer as paragraph) - [ ] "How-to" sections use numbered steps with clear action verbs at the start of each step - [ ] Question-format headings ("What is X?" "How do I Y?") appear at least 3 times in the article - [ ] Each FAQ answer is 40-60 words (the optimal length for a paragraph snippet) - [ ] List-format snippets (when used) have 5-8 items each - [ ] Definition snippets (when used) start with the term being defined **Test:** Could a search engine extract any single answer from your article and display it as a featured snippet without losing meaning? If yes, you pass. --- ## Section 3: Authority Signals AI models prefer to cite content that demonstrates expertise and credibility. Random opinions don't get cited; sourced claims do. - [ ] Every section includes at least one specific data point, statistic, or example - [ ] Claims are sourced (linked to original research, studies, or reports — not just other blog posts) - [ ] An author bio with credentials relevant to the topic appears at the end - [ ] Schema markup includes Author and Organization types - [ ] Internal links point to other relevant content on the same site (3-5 links minimum) - [ ] External links cite authoritative sources (.gov, .edu, peer-reviewed journals, primary sources) **Test:** Could a fact-checker verify every claim in your article using only the linked sources? If yes, you pass. --- ## Section 4: Technical SEO Baseline The foundation. Skip this and nothing else matters. - [ ] Schema markup added (Article + any applicable: FAQPage, HowTo, Product, Review) - [ ] Page loads in under 3 seconds (test on PageSpeed Insights) - [ ] Heading hierarchy is clean (H1 > H2 > H3, no skipped levels, only one H1) - [ ] All images have descriptive alt text - [ ] Meta title is 50-60 characters and includes the primary keyword - [ ] Meta description is 140-160 characters and reads as compelling preview text - [ ] URL slug is short, descriptive, and includes the primary keyword - [ ] Canonical URL is set to prevent duplicate content issues - [ ] Mobile-responsive (test on real phone, not just dev tools) **Test:** Run the page through PageSpeed Insights and a schema validator (search.google.com/test/rich-results). Both must pass. --- ## Section 5: AI Discoverability The 2026 additions. These signals tell AI models how to crawl and represent your site. - [ ] Site has an `llms.txt` file at the root (use the llms-txt-template from the Vault) - [ ] Site has a clean `robots.txt` that allows AI crawlers (GPTBot, ClaudeBot, PerplexityBot, etc.) unless intentionally blocking - [ ] XML sitemap is current and submitted to Google Search Console - [ ] Page is indexable (no `noindex` tag, no canonical pointing elsewhere) - [ ] Page is linked from at least one other indexed page on your site - [ ] Open Graph tags are set (og:title, og:description, og:image) - [ ] Twitter Card tags are set (for X/Twitter previews) **Test:** Search for your exact page URL in ChatGPT search and Perplexity within 7 days of publishing. The URL should appear in results. If not, indexing or discoverability is the issue. --- ## Section 6: Pre-Publish Quality Check The non-technical, "is this actually good" review. - [ ] Reading level is 8th grade or lower (test in Hemingway Editor) - [ ] No banned phrases from brand-kit.md appear in the copy - [ ] All required brand-kit phrases appear ("60-day guarantee," etc.) - [ ] Article matches the search intent of the target keyword (informational vs. commercial vs. transactional) - [ ] The first paragraph hooks a real human (not just an algorithm) - [ ] At least one specific, surprising, or counterintuitive insight is included - [ ] Headlines and subheadings would make sense to someone reading the article in 30 seconds **Test:** Show the first three paragraphs to someone outside your industry. Can they explain what the article is about and why they should keep reading? If yes, you pass. --- ## Section 7: Post-Publish Actions (Within 24 Hours) Publishing isn't the end. These actions accelerate indexing and citation. - [ ] URL submitted to Google Search Console for indexing (don't wait for natural crawl) - [ ] URL submitted to Bing Webmaster Tools for indexing - [ ] Page shared on at least one social platform (signals freshness to crawlers) - [ ] Internal links from existing pages updated to point to new article (boost crawlability) - [ ] If targeting a high-priority keyword, consider one quality backlink from a relevant site - [ ] Page added to the geo-citation-tracker watchlist for AI citation monitoring --- ## Section 8: 30-Day Follow-Up Track these metrics 30 days after publishing. - [ ] Has the page been indexed by Google? - [ ] What's the current ranking for the target keyword? - [ ] Has any traffic arrived from organic search? - [ ] Has the page been cited by any AI model (ChatGPT, Perplexity, Gemini, Claude)? - [ ] Has the page been linked to by any external site? - [ ] Has the page been added to any AI-generated answer in Google's AI Overviews? If the page hasn't been indexed in 30 days, there's a technical issue. If it's indexed but not ranking, the SERP analysis was wrong about ranking difficulty. If it's not getting AI citations after 60 days, the content needs more authority signals. --- ## The Three Common Failure Modes ### Failure Mode 1: Wrote for Google, Not AI Symptoms: Article ranks well but traffic is declining as AI Overviews take over the SERP. Fix: Restructure the content for AI extraction. Run the content-chunker skill from Pillar 8. Add citable claim sentences at the start of every section. ### Failure Mode 2: Wrote for AI, Not Humans Symptoms: Article ranks and gets cited but bounce rate is high and time-on-page is low. Fix: Add narrative, examples, and personality. AI extraction friendliness and human readability are not in conflict — they require different attention to different parts of the article. The first sentence of each section is for AI; the rest of the section is for humans. ### Failure Mode 3: Wrote for Everyone Generically Symptoms: Article is technically optimized but feels like every other AI-generated article on the topic. Fix: Add specific brand voice, real case studies, original POV, and surprising insights that AI models can't generate from public sources. The unique angle is what gets shared and linked to. --- ## Notes - This checklist is current as of mid-2026. The GEO and AEO disciplines are evolving fast. Re-evaluate the checklist quarterly. - Not every section applies to every article. A short news post doesn't need the full checklist; a cornerstone evergreen guide does. Use judgment. - For agencies producing client content, run this checklist as your QA gate. Articles don't get published until they pass. Quality > velocity.