SEO / AEO for Builders — Resources

All URLs verified resolving as of 2026-06-17. Knowledge for lessons is drawn from here, not from memory.

Knowledge

Official / primary docs (start here)

• SEO Starter Guide: The Basics — Google Search Central Google’s own beginner doc on crawling, indexing, and what actually moves rankings. The canonical “first read” before any opinionated blog.
• In-depth guide to how Google Search works — Google Search Central The crawl → index → serve pipeline from the engine itself. Use for: Lesson 0001 (the two pipelines), anything about the classic pipeline mechanics.
• SEO for developers (Get started) — Google Search Central Developer-angled entry point: rendering, JS SEO, technical requirements. Reach for it when building tooling, not writing content.
• Understand the JavaScript SEO basics — Google Search Central The crawl → render → index phases and why rendering is a deferred queue (“Once Google’s resources allow, a headless Chrome renders the page and executes the JavaScript”). Use for: Lesson 0006 (the JS-rendering gap), anything about client-side rendering, SSR/SSG, or why a no-JS crawler misses content.
• Introduction to structured data markup — Google Search Central How JSON-LD/Microdata/RDFa drive rich results. Read before automating any schema generation.
• Getting Started — schema.org The authoritative vocabulary spec (types, properties, formats). The source of truth your structured-data tooling should validate against.
• About the Search Console API + API Reference — Google (reference) REST API for Search Analytics, Sitemaps, Sites, URL Inspection. Backbone for any SEO monitoring/automation you build. The “Web” search-type now includes AI-feature traffic.
• Search Quality Rater Guidelines (PDF) — Google Google’s full evaluator manual defining E-E-A-T and “quality.” Use to understand what Google considers good content at the policy level. A rater framework, not an algorithm score.
• Creating Helpful, Reliable, People-First Content — Google Search Central Google’s on-page E-E-A-T explainer: the definition, “trust is most important,” and the key debunk — “While E-E-A-T itself isn’t a specific ranking factor, using a mix of factors that can identify content with good E-E-A-T is useful.” Use for: Lesson 0008 (E-E-A-T), and any time a vendor sells an “E-E-A-T score.”
• IndexNow — getting started (Bing) · protocol docs Open protocol for instantly pushing URL changes to Bing/Yandex/Naver/Seznam. POST {host, key, keyLocation, urlList} (≤10,000 URLs/post); the ping is shared across all participants. Google does NOT participate (verified June 2026) — it sticks to sitemaps + its own crawl scheduling, with the Indexing API limited to JobPosting/livestream. Use when building a crawl-notification step into a publishing pipeline.
• The Sitemap protocol — sitemaps.org · Build and submit a sitemap — Google The authoritative sitemap spec: ≤50,000 URLs and ≤50 MB per file, <loc> required, <lastmod> optional (W3C date), all URLs single-host; past 50k use a sitemap index. Google’s doc covers formats + submission. Use for: Lesson 0007 (sitemaps + IndexNow), generating/validating sitemaps in a publish pipeline.

Recognized authorities (evidence-based)

• Beginner’s Guide to SEO — Ahrefs Clean 10-chapter primer, now with chapters on AI search. Best free structured curriculum for zero → competent.
• The Beginner’s Guide to SEO — Moz Long-standing, vendor-neutral conceptual foundation. Pair with Ahrefs for a second framing of the fundamentals.

AI Overviews / AEO / GEO

• AI features and your website — Google Search Central Google on-record: how AI Overviews / AI Mode pick content and how to control inclusion (nosnippet, noindex). Primary source that debunks most AEO myths.
• Optimizing your website for generative AI features on Google Search — Google Search Central Google’s explicit “AEO/GEO is still SEO” guidance (May 2026). Reach for it whenever a vendor claims you need llms.txt or special AI markup. (announcement)
• Introducing Search Generative AI performance reports in Search Console — Google (June 2026) Newest primary source: Google’s own reporting on how your content performs in AI experiences. Closest thing to a first-party AEO measurement feed (UI report — see Gaps re: API).
• GEO: Generative Engine Optimization — Aggarwal, Murahari, Rajpurohit, Kalyan, Narasimhan, Deshpande (arXiv:2311.09735, KDD 2024) THE canonical academic paper. Coined “GEO,” introduced GEO-bench, measured tactics (up to ~40% visibility lift). The rigorous baseline beneath the marketing-blog noise. (ACM venue)
• 7 Steps for Tracking Your ChatGPT Visibility With Ahrefs — Louise Linehan (Ahrefs) Concrete, builder-friendly walkthrough of AI share-of-voice, citation analysis, fan-out queries. Use when designing what metrics your own AEO tracker should compute.

Wisdom (Communities)

• r/TechSEO (~41k) Technical/engineering side: rendering, log analysis, headers, indexing, API quirks. Best fit for a builder debugging tooling.
• r/bigseo (~127k) Higher-signal practitioner discussion bridging technical and strategy. Ask here once past beginner level.
• r/SEO Largest general SEO town square. Good for algorithm-update tracking and quick sanity checks (expect noise with the signal).
• AEO/GEO niche subs + vendor Discords (Profound, Ahrefs) Newer AEO discussion is fragmented. Treat as trend-radar, NOT authority — validate every claim against the Google primary docs above.

Community preference: not yet stated. Propose joining r/TechSEO once the user is doing hands-on technical work.

Gaps

• No first-party AEO measurement API. No public API from OpenAI, Anthropic, Perplexity, or Google to query “how often / where is my brand cited in AI answers.” Google’s June 2026 gen-AI performance reports are a Search Console UI report, not (yet) in the API. Biggest tooling gap — and directly on the build mission. A self-built tracker must scrape the UI or wait.
• AEO trackers rely on proxy methods, not ground truth. Every commercial tool (Profound, Ahrefs Brand Radar, Peec, Otterly) runs a prompt library against the engines and parses responses — synthetic sampling, not the engines’ real query distribution. No audited “AI share of voice” standard exists; cross-tool numbers aren’t comparable. Building your own = reinventing the same proxy.
• AEO/GEO writing is overwhelmingly vendor content marketing. Outside the one GEO paper and Google’s docs, almost all 2024–2026 “AEO guide” material is vendor-incentivized. The paper + Google primary docs are the only fully neutral anchors.
• No stable spec for AI-crawler controls. llms.txt and AI-specific markup proposals exist but aren’t standardized and are called unnecessary by Google. No settled, engine-backed equivalent to robots.txt/sitemaps for governing generative-AI inclusion.