Being Cited Is the New Ranking #1  Full Document Contents/Tweets/Being Cited Is the New Ranking #1.md, Being Cited Is the New Ranking #1, Joey Kudish. ## Document Notes --- tags: [SEO, AI, marketing] author: Joey Kudish source: Twitter reference: [https://twitter.com/jkudish/status/2026679436649943536/?rw_tt_thread=True] date created: 2026-02-27 12:00 --- # 🏷️ Title: Being Cited is the New Ranking #1 ## 🧭 Table of Contents - [[#📝 Summary]] - [[#📖 Main Content]] - [[#🗒️ Notes]] - [[#📚 References]] - [[#🗣️ Paraphrase]] - [[#📰 Newsletter]] - [[#✅ Action Items]] - [[#🧪 Hypotheses]] - [[#📊 Methodology]] - [[#❓ Questions]] - [[#🔮 Future Research]] - [[#💡 Implications]] - [[#🧠 Learning Styles Assessment]] - [[#📊 Accessibility Assessment]] - [[#🌍 DEIB Assessment]] - [[#✅ Logical Validity]] - [[#🛡️ DARVO Analysis]] - [[#🎯 Conclusion]] ### 🔗 References - Include links cited in or relevant to the article. ## 📝 Summary - What happened: The author argues that traditional SEO is no longer enough; you must optimize for AI assistants (Answer Engine Optimization, AEO) so they cite your site. - Why it matters: 58% of Google searches end in zero clicks and AI Overviews often answer questions without sending traffic, so visibility depends on being cited, not just ranked. - Key stakeholders: Site owners, marketers, SEO professionals, product and content teams. - Risks and tradeoffs: Staying SEO-only risks being invisible to AI tools; over-focusing on AEO may skew content toward short answers and citation-friendly structure. - Bottom line: “Doing well on the internet is no longer about ranking, it's now about being cited.” ## 📖 Main Content - Core argument: There is a growing gap between pages that rank highly in Google and pages AI assistants cite. The author introduces Answer Engine Optimization (AEO) to bridge that gap by aligning content with how AI systems evaluate and extract answers. - Definitions and context: - AEO (Answer Engine Optimization): Practices designed so AI assistants (ChatGPT, Gemini, Perplexity, Claude, Google AI Overviews) can discover, trust, and quote your content. - Zero-click searches: According to the author, “58% of Google searches now end in zero clicks,” meaning users get answers directly from the SERP or AI Overviews. - Citation overlap: “There's only a 45% overlap between brands Google ranks highly and brands AI assistants recommend,” underscoring that SEO and AEO lists differ. - Three-layer model of what AI “sees”: 1. **Technical foundation** ([crawler access and structure](https://read.readwise.io/read/01kjcxxmk46m94p2z0je28wth3?endLexposition=00000_00000_00007_00000_00003-001t&startLexposition=00000_00000_00000&emphasizeText=AEO+stands+for+Answer+Engine+Optimization.+It%27s+how+you+get+cited+by+AI+assistants+instead+of+ranked+by+Google.)): ensure AI crawlers aren’t blocked, use `/llms.txt` to give guidance, and add schema markup for structured data. 2. **Content structure**: “AI citation models favor content that leads with a direct answer in 40-60 words, then explains. Not a long buildup to the point.” Pages that cite authoritative sources are cited “40% more often.” 3. **Owning terminology**: The author calls this “dictionary definition heists”—finding niche terms that lack clear definitions and publishing the best, cleanly structured definition so AI treats your page as the canonical source. - Key insight: “AI needs to extract a clean answer from your page. If your content buries the point, AI moves on.” - Measurement approach: - Built an AEO analytics tool that queries Gemini, ChatGPT, and Perplexity to see whether they mention or cite target sites. - Used Librarium, a multi-provider research CLI, to query 10 providers at once and look for patterns across assistants rather than relying on one. - Employed a three-agent “Counselors” review (SEO specialist, content strategist, AI indexing expert) to critique pages; disagreements (e.g., FAQ phrasing) surfaced actionable improvements. - Platform-specific findings: - **ChatGPT**: “87.4% of AI referral traffic comes through Bing.” Branded domains get cited “11% more often,” and content “updated within the last 30 days gets cited 3.2x more.” - **Perplexity**: Strong preference for FAQ schema and question-shaped content; it favors pages that “answer questions directly.” - **Google AI Overviews**: Emphasizes E-E-A-T and topical authority clusters—depth in a focused area beats shallow coverage of many topics. - **Claude**: Uses Brave Search and “favors high factual density. The more verifiable claims per paragraph, the better.” - Practical heuristic: CRASP (Clarity, Relevance, Authority, Structure, Precision) as a pre-publish checklist for AEO. - Recommended starting point: “Start with one page. Add a direct-answer lead in the first paragraph. Cite the data you're referencing. Structure it so AI can extract a clean quote. Check whether AI assistants mention it in two to four weeks.” ### 🗒️ Notes - “Your SEO is fine yet most AIs have no idea you exist.” Problem framing: AI visibility is decoupling from SEO health. - AEO (Answer Engine Optimization) is explicitly contrasted with being “ranked by Google”; the new goal is being cited by AI assistants. - “58% of Google searches now end in zero clicks. AI Overviews answers the question before anyone clicks through.” Suggests much of search demand is now satisfied upstream. - “There's only a 45% overlap between brands Google ranks highly and brands AI assistants recommend. Those are two different lists.” Implication: winning SEO does not guarantee AI presence. - Layer 1 – Technical foundation: - Many sites “block AI crawlers without realizing it.” - `/llms.txt` is introduced as a configuration file to tell AI assistants “how to understand your site.” - Schema markup provides structured context that AI can interpret. - Layer 2 – Content structure: - AI citation models prefer content that “leads with a direct answer in 40-60 words, then explains.” - “The answer first, then the context.” This is the inverse of many blog-style posts that delay the key takeaway. - Princeton GEO study: pages “citing authoritative sources get cited by AI 40% more often.” Attributing data builds trust with models. - If you “don't cite where the data came from, AI has less reason to trust you as a source.” - Layer 3 – Owning terminology: - “Dictionary definition heists”: find niche terms with weak existing definitions. - “Write the best definition. Structure it so AI can extract it cleanly. Become the source of record.” - Described as “a longer game, but it compounds.” - Research stack: - Built an AEO analytics tool to query Gemini, ChatGPT, Perplexity directly; checks whether assistants “mention or cite my (my clients) sites.” - For research, used “Librarium, a multi-provider research CLI” to query 10 providers, looking for cross-provider patterns. - Used “Counselors” (three AI agents) to review content from: - SEO perspective - Content strategy perspective - AI indexing perspective Disagreements were particularly insightful, e.g., FAQ questions not being phrased like user queries. - Platform tactics: - **ChatGPT/Bing**: - “87.4% of AI referral traffic comes through Bing.” - “Branded domains get cited 11% more often than generic ones.” - “Content updated within the last 30 days gets cited 3.2x more than stale pages.” - **Perplexity**: - “FAQ schema consistently drives higher citation rates.” - Prefers content that directly matches how people phrase questions. - **Google AI Overviews**: - “E-E-A-T signals dominate.” - “Topical authority clusters (writing deeply about one area instead of broadly about many) carry more weight than single-page optimizations.” - **Claude/Brave**: - “Favors high factual density. The more verifiable claims per paragraph, the better.” - CRASP checklist: - Clarity: Is the answer explicitly stated? - Relevance: Does the content match likely user questions? - Authority: Are sources cited and expertise signaled? - Structure: Is the page or > [!note]+ Document Notes > tags: [SEO, AI, marketing] > author: Joey Kudish > source: Twitter > reference: [https://twitter.com/jkudish/status/2026679436649943536/?rw_tt_thread=True] > date created: 2026-02-27 12:00 > > # 🏷️ Title: Being Cited is the New Ranking #1 > <!-- deep-read:sections start --> ## 🧭 Table of Contents - [📝 Summary](#-summary) - [📖 Main Content](#-main-content) - [🗒️ Notes](#️-notes) - [📚 References](#-references) - [🗣️ Paraphrase](#️-paraphrase) - [📰 Newsletter](#-newsletter) - [✅ Action Items](#-action-items) - [🧪 Hypotheses](#-hypotheses) - [📊 Methodology](#-methodology) - [❓ Questions](#-questions) - [🔮 Future Research](#-future-research) - [💡 Implications](#-implications) - [🧠 Learning Styles Assessment](#-learning-styles-assessment) - [📊 Accessibility Assessment](#-accessibility-assessment) - [🌍 DEIB Assessment](#-deib-assessment) - [✅ Logical Validity](#-logical-validity) - [🛡️ DARVO Analysis](#-darvo-analysis) - [🎯 Conclusion](#-conclusion) ### 🔗 References - Include links cited in or relevant to the article. ## 📝 Summary - What happened: The author argues that traditional SEO is no longer enough; you must optimize for AI assistants (Answer Engine Optimization, AEO) so they cite your site. - Why it matters: 58% of Google searches end in zero clicks and AI Overviews often answer questions without sending traffic, so visibility depends on being cited, not just ranked. - Key stakeholders: Site owners, marketers, SEO professionals, product and content teams. - Risks and tradeoffs: Staying SEO-only risks being invisible to AI tools; over-focusing on AEO may skew content toward short answers and citation-friendly structure. - Bottom line: “Doing well on the internet is no longer about ranking, it's now about being cited.” ## 📖 Main Content - Core argument: There is a growing gap between pages that rank highly in Google and pages AI assistants cite. The author introduces Answer Engine Optimization (AEO) to bridge that gap by aligning content with how AI systems evaluate and extract answers. - Definitions and context: - AEO (Answer Engine Optimization): Practices designed so AI assistants (ChatGPT, Gemini, Perplexity, Claude, Google AI Overviews) can discover, trust, and quote your content. - Zero-click searches: According to the author, “58% of Google searches now end in zero clicks,” meaning users get answers directly from the SERP or AI Overviews. - Citation overlap: “There's only a 45% overlap between brands Google ranks highly and brands AI assistants recommend,” underscoring that SEO and AEO lists differ. - Three-layer model of what AI “sees”: 1. **Technical foundation** ([crawler access and structure](https://read.readwise.io/read/01kjcxxmk46m94p2z0je28wth3?endLexposition=00000_00000_00007_00000_00003-001t&startLexposition=00000_00000_00000&emphasizeText=AEO+stands+for+Answer+Engine+Optimization.+It%27s+how+you+get+cited+by+AI+assistants+instead+of+ranked+by+Google.)): ensure AI crawlers aren’t blocked, use `/llms.txt` to give guidance, and add schema markup for structured data. 2. **Content structure**: “AI citation models favor content that leads with a direct answer in 40-60 words, then explains. Not a long buildup to the point.” Pages that cite authoritative sources are cited “40% more often.” 3. **Owning terminology**: The author calls this “dictionary definition heists”—finding niche terms that lack clear definitions and publishing the best, cleanly structured definition so AI treats your page as the canonical source. - Key insight: “AI needs to extract a clean answer from your page. If your content buries the point, AI moves on.” - Measurement approach: - Built an AEO analytics tool that queries Gemini, ChatGPT, and Perplexity to see whether they mention or cite target sites. - Used Librarium, a multi-provider research CLI, to query 10 providers at once and look for patterns across assistants rather than relying on one. - Employed a three-agent “Counselors” review (SEO specialist, content strategist, AI indexing expert) to critique pages; disagreements (e.g., FAQ phrasing) surfaced actionable improvements. - Platform-specific findings: - **ChatGPT**: “87.4% of AI referral traffic comes through Bing.” Branded domains get cited “11% more often,” and content “updated within the last 30 days gets cited 3.2x more.” - **Perplexity**: Strong preference for FAQ schema and question-shaped content; it favors pages that “answer questions directly.” - **Google AI Overviews**: Emphasizes E-E-A-T and topical authority clusters—depth in a focused area beats shallow coverage of many topics. - **Claude**: Uses Brave Search and “favors high factual density. The more verifiable claims per paragraph, the better.” - Practical heuristic: CRASP (Clarity, Relevance, Authority, Structure, Precision) as a pre-publish checklist for AEO. - Recommended starting point: “Start with one page. Add a direct-answer lead in the first paragraph. Cite the data you're referencing. Structure it so AI can extract a clean quote. Check whether AI assistants mention it in two to four weeks.” ### 🗒️ Notes - “Your SEO is fine yet most AIs have no idea you exist.” Problem framing: AI visibility is decoupling from SEO health. - AEO (Answer Engine Optimization) is explicitly contrasted with being “ranked by Google”; the new goal is being cited by AI assistants. - “58% of Google searches now end in zero clicks. AI Overviews answers the question before anyone clicks through.” Suggests much of search demand is now satisfied upstream. - “There's only a 45% overlap between brands Google ranks highly and brands AI assistants recommend. Those are two different lists.” Implication: winning SEO does not guarantee AI presence. - Layer 1 – Technical foundation: - Many sites “block AI crawlers without realizing it.” - `/llms.txt` is introduced as a configuration file to tell AI assistants “how to understand your site.” - Schema markup provides structured context that AI can interpret. - Layer 2 – Content structure: - AI citation models prefer content that “leads with a direct answer in 40-60 words, then explains.” - “The answer first, then the context.” This is the inverse of many blog-style posts that delay the key takeaway. - Princeton GEO study: pages “citing authoritative sources get cited by AI 40% more often.” Attributing data builds trust with models. - If you “don't cite where the data came from, AI has less reason to trust you as a source.” - Layer 3 – Owning terminology: - “Dictionary definition heists”: find niche terms with weak existing definitions. - “Write the best definition. Structure it so AI can extract it cleanly. Become the source of record.” - Described as “a longer game, but it compounds.” - Research stack: - Built an AEO analytics tool to query Gemini, ChatGPT, Perplexity directly; checks whether assistants “mention or cite my (my clients) sites.” - For research, used “Librarium, a multi-provider research CLI” to query 10 providers, looking for cross-provider patterns. - Used “Counselors” (three AI agents) to review content from: - SEO perspective - Content strategy perspective - AI indexing perspective Disagreements were particularly insightful, e.g., FAQ questions not being phrased like user queries. - Platform tactics: - **ChatGPT/Bing**: - “87.4% of AI referral traffic comes through Bing.” - “Branded domains get cited 11% more often than generic ones.” - “Content updated within the last 30 days gets cited 3.2x more than stale pages.” - **Perplexity**: - “FAQ schema consistently drives higher citation rates.” - Prefers content that directly matches how people phrase questions. - **Google AI Overviews**: - “E-E-A-T signals dominate.” - “Topical authority clusters (writing deeply about one area instead of broadly about many) carry more weight than single-page optimizations.” - **Claude/Brave**: - “Favors high factual density. The more verifiable claims per paragraph, the better.” - CRASP checklist: - Clarity: Is the answer explicitly stated? - Relevance: Does the content match likely user questions? - Authority: Are sources cited and expertise signaled? - Structure: Is the page organized for easy extraction (direct answer, headings, FAQ)? - Precision: Are claims specific, quantifiable, and verifiable? - Closing thesis and recommendation: - “Being great at SEO and invisible to AI are not mutually exclusive. They're increasingly common together.” - You can start small: revise a single page with a direct-answer opening, citations, and extractable structure, then watch whether AI assistants start citing it within a few weeks. - Final line: “Doing well on the internet is no longer about ranking, it's now about being cited. Are your sites cited?” ## 📚 References - Joey Kudish, “Being Cited is the New Ranking #1” (Twitter thread): https://twitter.com/jkudish/status/2026679436649943536 - Princeton GEO study on AI citation and authoritative sources (referenced but not linked). - Librarium (multi-provider research CLI, open-sourced; tool referenced in the article). - Bing, Perplexity, Google AI Overviews, Brave Search documentation for crawling and citation behaviors. - Schema.org (for structured data and FAQ schema). - Emerging `/llms.txt` proposals and implementations. ## 🗣️ Paraphrase - Paragraph A paraphrase: The landscape of online visibility is shifting from ranking in search results to being cited by AI assistants. Because a majority of searches now end without clicks and AI Overviews often answer questions directly, websites can appear successful in traditional SEO metrics while remaining unseen by AI. To address this, Answer Engine Optimization focuses on making content accessible, trustworthy, and easy for AI models to quote. - Paragraph B paraphrase: The author outlines three key layers of AEO—technical access, answer-first content structure with strong citations, and owning niche terminology—then validates them with experiments across multiple AI systems. Different assistants favor different signals, from FAQ schema to topical authority and factual density. A practical CRASP checklist and a simple starting plan (optimize one page, then test AI citations) translate these insights into concrete next steps. ## 📰 Newsletter In this issue, we’re zooming in on a critical shift for WordPress site owners and builders: being cited by AI assistants is fast becoming as important as ranking in Google. Joey Kudish frames this as Answer Engine Optimization (AEO). With “58% of Google searches now end[ing] in zero clicks,” and AI Overviews answering questions before anyone visits your site, we can’t afford to think about SEO in isolation anymore. What does this mean in practice for WordPress folks? - Lead with answers: Open key pages with a crisp 40–60 word answer, then elaborate below. This helps AI systems extract a clean quote. - Cite your sources: Posts that link to authoritative data tend to be cited more often by AI. Treat your content like a well-documented developer handbook. - Own your glossary: Define your niche WordPress terms (e.g., “block theme onboarding,” “site editor playbook”) in clear, structured entries. You want AI tools to treat your docs as the canonical reference. - Tune for platforms: - Bing/ChatGPT: keep content fresh and hosted on a strong, branded domain. - Perplexity: lean into FAQ blocks and question-shaped headings. - Google AI Overviews: build topical authority—write deeply and consistently about the same WordPress problem areas. If you’re maintaining docs, developer portals, or plugin landing pages, try this experiment: pick one high-value page, apply AEO structure, and track if AI assistants start mentioning it within a month. Helpful starting points: - WordPress.org Developer Resources: https://developer.wordpress.org - Schema.org FAQ: https://schema.org/FAQPage - Site health & crawl tools from major hosts or plugins (e.g., Yoast SEO, Rank Math, All in One SEO). TL;DR: In the age of AI-assisted search, WordPress excellence isn’t just about building fast, accessible sites—it’s about making them the go-to citations for the questions your users actually ask. ## ✅ Action Items #### DevRel - Audit key developer docs and tutorials for answer-first structure and clear, cited data on WordPress features and APIs. - Create workshops on AEO for plugin/theme developers, including examples of good FAQ schema and `/llms.txt` guidance. - Add AEO-focused examples and templates to SDKs, starter themes, and developer quickstarts. - Run a content campaign demonstrating how optimized WordPress docs get cited by AI tools, with measurable traffic and referral metrics. - Survey developer communities about how they discover WordPress resources via AI assistants; adjust DevRel strategy accordingly. - Align internal DevRel and product teams on shared KPIs around AI citations, not just search rankings. #### OSPO - Define policies on AI crawling and `/llms.txt` for open-source projects, clarifying what is allowed and how. - Ensure license metadata is correctly surfaced so AI systems can understand open-source usage terms. - Integrate security advisories and SBOM metadata in ways that AI can parse and cite accurately. - Maintain an inventory of core open-source assets (repos, docs, sites) with clear ownership for AEO and schema markup. - Offer guidance hours for maintainers on AI-safe content, licensing, and governance implications. - Support upstream projects whose docs are critical dependencies, ensuring they remain high-quality AI reference points. - Report to leadership on how AI citation patterns affect strategic open-source initiatives. #### Community - Host maintainer clinics on structuring READMEs and docs for AI citation (answer-first, FAQs, clear definitions). - Provide contributor-friendly templates for FAQs and terminology glossaries. - Share best practices with sponsors about funding documentation and AEO improvements as first-class outcomes. - Coordinate cross-project drills where teams test how AI assistants describe and recommend their projects, then remediate gaps. #### WordPress - Core: Prioritize documentation and dev notes that clearly explain new features in answer-first formats. - Core Performance: Publish measurable performance claims with cited benchmarks for AI tools to quote. - Core AI: Define guidelines for responsible AI usage, including how WordPress wants to be crawled and cited. - **Core Program Team:** Add AEO and AI documentation visibility to release checklists and cross-team planning. - Mobile: Document mobile app capabilities and edge cases succinctly, with FAQs tailored to common user questions. - Playground: Provide structured, question-led docs so AI tools can recommend Playground for experimentation scenarios. - Community: Ship meetup and WordCamp kits explaining AEO basics for local organizers and speakers. - Training: Design lesson plans on AEO, AI search, and content structure for WordPress educators. - Marketing: Shift narratives from “rank higher” to “become the canonical answer”; track citations by AI in reporting. - Support: Turn common tickets into structured FAQs that AI can parse and re-use. - Design: Encourage content patterns (cards, callouts) that surface short, quotable answers. - Documentation: Audit HelpHub and DevHub for answer density, citation quality, and FAQ schema coverage. - Photos: Clarify licensing, captions, and attributions in ways that AI can interpret. - TV: Provide captions and transcripts optimized with clear headings and definitions for AI ingestion. - Polyglots: Localize glossaries and key definitions for non-English AI assistants. - Accessibility: Ensure AEO-friendly structures (headings, FAQs) also meet accessibility best practices. - Meta: Implement and document `/llms.txt` and structured data for .org properties. - CLI: Improve command help text and man pages so AI can correctly describe and recommend WP-CLI commands. - Hosting: Collaborate on default setups that don’t inadvertently block AI crawlers. - Tide: Document scoring logic in precise, citable terms AI can reuse. - Openverse: Offer clear, structured definitions around licensing and attribution for AI that recommends media. - Themes: Provide structured guidance and definitions for block themes and style variations. - Plugins: Encourage plugin authors to adopt FAQ schema and answer-first readmes. #### The WPOCC - Programs: Offer fellowships focused on documentation excellence and AEO improvements. - Projects: Run documentation sprints dedicated to restructuring existing content for AI citation. - Funding experiments: Sponsor measurable AEO experiments for critical WordPress ecosystem sites and report on outcomes. ### FAIR - Technical independence: Document clear, machine-readable licensing and provenance for WordPress content used by AI. - Policies and covenants: Publish transparent guidelines on AI usage, funding, and independence for community-run sites. - Productized governance artifacts: Template `/llms.txt`, governance charters, and operator agreements for shared infrastructure. ## 🧪 Hypotheses - H1: Pages that open with a 40–60 word direct answer will be cited by AI assistants more often than similar pages with delayed or buried answers. - H2: Adding authoritative citations to existing content increases AI citation frequency by at least 40%. - H3: Implementing FAQ schema for user-shaped questions improves Perplexity citation rates compared to non-FAQ pages on the same domain. - H4: Sites with focused topical authority clusters receive more AI citations in that niche than generalist sites of similar overall traffic. - H5: Recently updated content (≤30 days) is at least 3x more likely to be cited by ChatGPT/Bing than older pages. ### 📊 Methodology - For H1–H2: Randomly select matched pairs of pages; treat one set with answer-first rewrites and added citations, keep the other as control. Track mentions and links from Gemini, ChatGPT (via Bing), Perplexity, and Claude over 4–8 weeks. - For H3: Implement FAQ schema on half of a site’s high-traffic Q&A pages, leaving the rest unchanged. Log Perplexity answer sources for relevant queries; compare citation lift. - For H4: Compare AI citation counts across sites with concentrated content in one niche vs. broadly scoped blogs, controlling for domain authority. - For H5: Use an AEO analytics tool to monitor AI citations for pages before and after updates, segmenting by age since last update. ### ❓ Questions - How stable are AI citation patterns over time as models and training data change? - To what extent can smaller, niche sites outrank large publishers in AI citations by owning definitions and topical authority? - How do different AI providers weigh structured data (schema) versus unstructured but well-written content? - What ethical and legal frameworks should govern the use of `/llms.txt` and AI crawler permissions? - Can open standards emerge for reporting and auditing AI citation attribution? ### 🔮 Future Research - Longitudinal studies of how AI assistants’ citation sources evolve with new model releases. - Comparative analysis of how non-English content is cited across AI platforms. - Experiments on multi-modal AEO (text + code + diagrams) for technical documentation. - Investigation into feedback loops where AI citations drive traffic that further influences traditional SEO rankings. - Exploration of standardized metrics for “AI visibility” akin to domain authority. ### 💡 Implications - Practice: Content teams must write for both humans and AI—answers first, with verifiable, structured data. - Policy: Organizations need clear policies on AI crawling, licensing, and acceptable usage of their content. - Security: Mis-citations or hallucinated attributions in AI answers could mislead users about authoritative sources. - Education: Training for marketers, developers, and writers should now include AEO fundamentals. - Funding: Documentation and knowledge-base work becomes more strategically valuable and fundable as a primary visibility channel. ### 🧠 Learning Styles Assessment - Reading level estimate: Approximately 9th–11th grade (Flesch-Kincaid style; mix of short, punchy lines with some technical terms). #### 👀 Visual learners - Present: Conceptual layering (three AEO layers) lends itself to diagrams; CRASP as a mnemonic. - Improve: Add simple diagrams of “search vs AI citation,” flowcharts of crawling and extraction, and examples of good vs. bad page structures. #### 🔊 Aural learners - Present: None explicitly (text-only). - Improve: Provide a short audio summary or podcast-style discussion of AEO and platform-specific tactics. #### 🗣️ Verbal learners - Present: Clear definitions (AEO, dictionary definition heists, CRASP); concrete phrases and examples. - Improve: Add more analogies (e.g., “front-loading your thesis statement”) and a mini-glossary at the end. #### 🧩 Kinesthetic learners - Present: Suggested experiment (optimize one page, then check AI citations). - Improve: Include step-by-step checklists and interactive labs (e.g., “run this query in three AI assistants and compare”). #### 🧠 Logical learners - Present: Data points (58% zero-click, 45% overlap, 3.2x lift), structured checklists (CRASP), platform comparisons. - Improve: Provide tables summing up platform preferences and decision trees for choosing AEO tactics. #### 🧑‍🤝‍🧑 Social learners - Present: References to collaborative tools (Counselors agents) and client experiments. - Improve: Encourage peer review of content for AEO, community experiments, and shared reporting. #### 🧘‍♀️ Solitary learners - Present: Standalone framework and tactics that can be applied in solo content work. - Improve: Add reflection prompts (e.g., “Which of your pages is most at risk of being invisible to AI?”). #### 🌿 Naturalistic learners - Present: Limited direct relevance. - Improve: Use ecosystem analogies (e.g., “AI citation as a new food chain for information”) and discuss energy/compute implications of redundant crawling. ### 📊 Accessibility Assessment #### Screen reader semantics - Present: Conceptual structure conducive to headings and landmarks. - Improve: Ensure actual implementations use proper headings, landmarks, and descriptive alt text for examples. #### Keyboard navigation - Present: Not specifically addressed. - Improve: Provide guidance that examples and templates follow good keyboard navigation practices. #### Contrast and readability - Present: Text-only; color not discussed. - Improve: Recommend high-contrast design when implementing examples on real sites. #### Text resizing and reflow - Present: No explicit guidance. - Improve: Encourage responsive layouts and testing at 200% zoom for example pages. #### Media and captions - Present: No media in the original text. - Improve: For any future talks or videos on AEO, ensure captions and transcripts are provided. #### Forms and interactions - Present: N/A in the article. - Improve: When implementing FAQ or feedback forms, follow accessible form patterns. #### Standards reference - Map future implementation guidance to WCAG 2.2 AA, especially around structure, headings, and readable content. ### 🌍 DEIB Assessment #### Cultural breadth - Present: Focused on AI and SEO, primarily from an English-language, Western search ecosystem. - Improve: Discuss AI citation behavior in non-English markets and on region-specific search engines. #### Inclusive language - Present: Generally neutral, professional language, limited jargon. - Improve: Add short definitions for acronyms (SERP, E-E-A-T, etc.) and avoid assuming prior SEO knowledge. #### Neurodiversity support - Present: Clear structure, lists, and concise statements support some neurodivergent readers. - Improve: Break long paragraphs into smaller chunks, add summaries per section, and keep formatting highly consistent. #### Representation - Present: No people or identities depicted directly. - Improve: When creating examples or case studies, include diverse industries and organization types. #### Psychological safety - Present: Non-accusatory, focused on opportunity rather than blame. - Improve: Emphasize experimentation and learning; avoid framing current SEO practices as failures. ### ✅ Logical Validity #### Strong reasoning - Inductive reasoning: Uses quantitative claims (e.g., “58% of Google searches now end in zero clicks”) to support the idea that ranking is insufficient. - Causal reasoning: Links answer-first structure and authoritative citations to higher AI citation rates, referencing the Princeton GEO study and platform behaviors. - Comparative reasoning: Shows that only “45% overlap” exists between top SEO rankings and AI recommendations, justifying the need for a new optimization lens. #### Fallacies - Potential overgeneralization: Some precise numbers (e.g., 87.4% of AI referral traffic) might be drawn from limited samples. Clarifying scope, sample size, and methodology would strengthen the claims. - Survivorship bias risk: Highlighting successful AEO examples without equally detailed non-success stories could skew perception of effectiveness. #### Tone of voice - Tone: Analytical, pragmatic, and mildly urgent. Uses short, punchy sentences and quantifiable data to motivate action (“Doing well on the internet is no longer about ranking, it's now about being cited.”). ### 🛡️ DARVO Analysis - Deny: The text does not deny problems; it foregrounds a new problem (AI invisibility) even when SEO is fine. - Attack: No attacks on individuals or groups; critique is directed at outdated assumptions about SEO. - Reverse victim/offender: No evidence of trying to recast the author or site owners as victims of unfair criticism. Instead, the piece frames them as actors who can adapt. - Overall: The article does not employ DARVO tactics; it is solution-focused rather than defensive. ## 🎯 Conclusion - Bottom line: The web’s discovery layer is shifting from ranking in search engines to being cited by AI assistants. Traditional SEO can no longer guarantee visibility as zero-click searches and AI Overviews grow. - Practical next steps: Start with one important page—ensure AI crawlers can access it, lead with a clear 40–60 word answer, cite authoritative sources, add helpful schema (especially FAQs), and monitor whether AI tools begin to mention or link to it over the next few weeks. Expand the approach across your content once you see traction. ## 🧱 Refactor Appendix (append after 🎯 Conclusion) ### 📚 Literature Split Pad - Purpose: Stage Konik CEE units that become per-source Literature notes. - Split level: **H3**. - Include verbatim quotes under 25 words and a [view highlight] link. ### [H1] AEO reframes SEO for AI citations > [!quote] [Being Cited is the New Ranking #1](https://twitter.com/jkudish/status/2026679436649943536/?rw_tt_thread=True) by [[Joey Kudish]] via [[Twitter]]. Published 2026-02-25. > “Doing well on the internet is no longer about ranking, it's now about being cited.” Two lines: context and use. Cite data if relevant. [view highlight](https://twitter.com/jkudish/status/2026679436649943536/?rw_tt_thread=True#H1) #xref #articleseed ID:rw_[MISSING] ### [H2] AI assistants need clean extractable answers > [!quote] [Being Cited is the New Ranking #1](https://twitter.com/jkudish/status/2026679436649943536/?rw_tt_thread=True) > “AI needs to extract a clean answer from your page. If your content buries the point, AI moves on.” Two lines: context and use. [view highlight](https://twitter.com/jkudish/status/2026679436649943536/?rw_tt_thread=True#H2) #xref ID:rw_[MISSING] --- ### 🔖 Atomic Split Pad (Zettel Candidates) - Purpose: Promote reusable claims into Atomic notes. - Split level: **H4**. - Each item: one idea, present tense, specific, testable. #### [Z1] AI citations depend on answer-first structure - Scope/condition in one line. - Pointer to page/time or dataset. - Links: [[Answer-Engine-Optimization]] [[Content-Structure]] #### [Z2] Topical authority boosts AI citation rates - Scope/condition in one line. - Pointer to page/time or dataset. - Links: [[Topical-Authority]] [[AI-Search]] --- ### ✏️ Fleeting Queue (Extract by Selection) - Purpose: Capture quick actions or sparks for Fleeting notes. - Extraction: **Select one line** → “Refactor: Extract selection to new note (content only).” - Keep each line short and self-contained. - [F1] Identify one high-value page to AEO-optimize first — context/https://twitter.com/jkudish/status/2026679436649943536/?rw_tt_thread=True #fleeting #inbox - [F2] Draft 40–60 word answer-first intros for top FAQs — context/https://twitter.com/jkudish/status/2026679436649943536/?rw_tt_thread=True #fleeting #inbox - [F3] Research and implement `/llms.txt` and FAQ schema on key docs — context/https://twitter.com/jkudish/status/2026679436649943536/?rw_tt_thread=True #fleeting #inbox --- <!-- deep-read:sections end --> ## Highlights - AEO stands for Answer Engine Optimization. It's how you get cited by AI assistants instead of ranked by Google. And here's the number that reframed everything for me: ***58% of Google searches now end in zero clicks.*** AI Overviews answers the question before anyone clicks through. ([View Highlight](https://read.readwise.io/read/01kjfzayrjyh2gfcpk3r3cfw0x)) - Tags: 👻 ai highlighted