ref-sp-web-seo-ailisted

# AI Search Visibility ## Purpose Give honest guidance on being found and cited by AI answer surfaces: what is mechanically true and checkable, what it does to your measurements, and — the part most sources get wrong — how much of the prevailing "GEO" advice is actually unvalidated guesswork that should not be shipped as a recommendation. ## Verify before you assert — this file rots fastest **Content below was verified 2026-07-12** and this is the fastest-moving material in the repo. Every dated claim has a row in `./references/sources.md` giving its source, its verified date, and what would invalidate it. Re-verification is cheap — one request tells you whether anything moved: ```sh curl -s https://developers.google.com/search/updates/search_docs_updates.rss ``` Scan it for the documents in that table, re-fetch only those, and update the claim and its row. Proof this is not theoretical: the first draft of this skill was superseded **within the same working session** — Search Console shipped a Generative AI performance report and Google published an AI optimization guide, neither of which existed in the docs the draft was built from. ## When to use this skill - Asked how to "rank in ChatGPT", "show up in AI Overviews", or "get cited by AI". - Asked about GEO (Generative Engine Optimization) or AEO (Answer Engine Optimization). - Deciding whether to allow or block AI crawlers in `robots.txt`, or **whether to opt out of AI training** — three separate decisions that mo