Note on candidate corpus / Caveat Among this batch of 18 candidate posts, only 8 posts actually fall under the theme of "AI / ML / Knowledge Graph / AI Overviews" (2007 auto-generated / 2015 Knowledge Graph events / 2017 user-generated spam / 2021 page titles / 2023 google-search-and-ai-content / 2023 definitely-not-ai-generated-post / 2025 succeeding-in-ai-search / 2025 ai-powered-configuration). The remaining 10 posts (2005 sitemap generator v1.3 / 2005 OAI-PMH / 2005 sitemap v1.4 / 2008 retire OAI-PMH / 2009 sitemap generator / 2009 caffeine sandbox / 2012 crawl errors / 2017 Vietnamese announcement / 2018 German announcement / 2026 SCL Shanghai) are unrelated to the AI theme. This wiki does not elaborate on them, and only records them in the source list to preserve evidence of ingest completeness. Updated 2026-05-18: The official original texts for the 5 major milestones — RankBrain (2015) / BERT (2019) / MUM (2021) / HCU (2022) / AI Overviews (2024) — have been retrieved from blog.google (The Keyword); see Google Search's 5 Major AI Algorithm Milestones (RankBrain/BERT/MUM/HCU/AIO). These announcements are not on the Google Search Central blog, but on the main blog.google site, so the original GSC scraper did not capture them — they have now been independently archived at
sources/reference/google-the-keyword/blog/. The skeleton content for Part 2 / Part 3 can now be verified/expanded using the official original texts in Google Search's 5 Major AI Algorithm Milestones (RankBrain/BERT/MUM/HCU/AIO).
Part 1 — Google's Official Stance on AI-Generated Content (the "how, not who" framework)
1.1 Core proposition: Quality takes priority over "who/what wrote it"
Source:2023/02 Google Search's guidance about AI-generated content(Danny Sullivan + Chris Nelson)
"Our focus on the quality of content, rather than how content is produced, is a useful guide that has helped us deliver reliable, high quality results to users for years."
Historical analogy (Google's original words):
"About 10 years ago, there were understandable concerns about a rise in mass-produced yet human-generated content. No one would have thought it reasonable for us to declare a ban on all human-generated content in response. Instead, it made more sense to improve our systems to reward quality content."
Logic: During the 2011 Panda era, Google did not ban "human-written but mass-produced low-quality content"; instead, it upgraded its systems to identify quality. Facing the LLM era, Google reiterates the same path — it does not ban AI content, but evaluates quality.
1.2 Boundary: scaled content abuse
"Using automation—including AI—to generate content with the primary purpose of manipulating ranking in search results is a violation of our spam policies."
What is judged is intent, not the tool:
- ✅ AI-generated weather, sports, transcriptions → long-term compliant
- ✅ AI-assisted creative expression → compliant
- ❌ Mass-produced AI content with the primary purpose of "gaming rankings" → violates spam policy
Enforcement systems:SpamBrain (mentioned in the 2022 webspam report; this wiki cites it from the embedded link in the 2023/02 post).
1.3 Official advice for creators (distilled from the FAQ)
Source:2023/02 FAQ section (8 questions and 8 answers).
| Question | Google's stance (condensed from original wording) |
|---|---|
| Is AI content a violation? | No — unless it is used to manipulate rankings |
| Why not just ban AI content outright? | Automation has long had legitimate uses in publishing |
| How do you prevent low-quality AI content from flooding results? | We address it with existing helpful content / original news / spam systems; this is not a new problem |
| Will AI content receive preferential treatment? | "Using AI doesn't give content any special gains. It's just content." |
| Should I use AI to write? | Using AI to help you produce genuinely useful original content = okay; treating AI as a cheap tool to game rankings = don't |
| Do I need to credit an author? | You should credit an author when readers would ask "Who wrote this?" |
| Do I need to disclose AI involvement? | You should disclose it when readers would ask "How was this created?" |
| Can AI be listed as an author? | "probably not the best way" — it is more appropriate to disclose along the "how it was created" dimension, rather than treating AI as an author |
1.4 The Who / How / Why three-question framework
Google added a new framework in its Creating helpful, reliable, people-first content help page:Who who wrote it,How how it was written (including whether AI tools were used),Why why it was written (for people or for search engines).
"Evaluating your content in this way, whether you're using AI-generated content or not, will help you stay on course."
This means Who/How/Why is a universal quality yardstick, not an "AI-specific audit".
1.5 Early "pre-history of AI stance" — auto-generated links / content
Source:2007/08 Quality websites: avoid auto-generated links(Jianfei Zhu)+ 2017/01 Protect your site from user-generated spam(Anouar Bendahou)
The 2007 post was Google's first systematic statement of opposition to "auto-generated" content — at the time, this referred to spamware automatically generating guestbook links, a form of "pre-LLM automation". Original wording:
"Google will not give credit for auto-generated links. When we detect that a site has unnaturally generated their own backlinks, the site's ranking can be negatively affected and can be removed from our index."
The 2017 post extended this to automated spam in forums / comments: 8 defensive measures including CAPTCHAs, rate limiting, nofollow, and Akismet.
Continuity of the thematic thread:
2007 auto-generated links → 2017 automated spam in user-generated areas → 2022 helpful content update → 2023 generative AI scaled abuse
Google repeatedly emphasizes:"automation" itself has never been the problem; "using automation to manipulate rankings" is. Policy in the LLM era is simply an extension of this 15+ year-old line, not a new rule.
Part 2 — History of machine learning signal introduction: RankBrain → BERT → MUM → and beyond
2.1 ML anchors identifiable in this batch of corpus
Note: Among this batch of 18 candidate posts, there are no official launch blog posts for RankBrain (2015-10) / BERT (2019-10) / MUM (2021-05) / Helpful Content Update (2022-08). The only traces of ML that can be found are the following two secondhand citations:
2021/08 Update to how we generate page titles(Danny Sullivan) — Google rewrites titles using systems that go "beyond the HTML title tag" (in practice, language understanding models after BERT). Original wording:
"We are making use of text that humans can visually see when they arrive at a web page. We consider the main visual title or headline shown on a page, content that site owners often place within
<H1>tags... Other text contained in the page might be considered, as might be text within links that point at pages."Key data:HTML
<title>tags still account for 80%+ of final displayed titles — even when ML takes over rewriting decisions, explicit semantics remain the primary signal.2023/02 google-search-and-ai-content mentions SpamBrain — Google's ML anti-spam system, deployed in 2018 and disclosed in the 2022 public webspam report. Google's stance:
"Our spam-fighting efforts—including our SpamBrain system—will continue, however spam is produced."
2.2 Skeleton timeline of ML introduction (official original texts to be supplemented in the next round of ingest)
| Year | System | Nature | Source present in this batch? |
|---|---|---|---|
| 2009 | Caffeine index infrastructure preview | Index architecture, not ranking ML | ✅ (2009/08 sandbox preview) |
| 2012 | Knowledge Graph launch | Entity graph | ❌ (this batch only has the 2015 events derivative post) |
| 2015 | RankBrain | First deep learning ranking signal | ❌ |
| 2018 | SpamBrain | ML anti-spam | Only cited in 2023 |
| 2019 | BERT | Bidirectional transformer for query understanding | ❌ |
| 2021 | MUM | Multitask unified model, multimodal/multilingual | ❌ |
| 2021 | Title rewriting ML system | Title generation based on visible page text | ✅(2021/08) |
| 2022 | Helpful Content System | Site-level helpfulness signal | Only cited in 2023 |
| 2024 | AI Overviews | Generative answers | Only cited in 2025 |
| 2025 | AI Mode | Complex multi-turn generative search | ✅ (cited 2025/05) |
TODO for the next round of ingest:
- Retrieve official original texts from the GSC blog for the
rankbrain/bert/mum/helpful-content-update/ai-overviewskeywords - Retrieve the 2015/10 official RankBrain announcement (first published by Bloomberg, Google later added a blog post)
- Retrieve the 2019/10 post "Understanding searches better than ever before" (BERT launch)
- Retrieve search blog writeups around MUM from Google I/O 2021
Part 3 — Evolution from Knowledge Graph to AI Overviews
3.1 The only Knowledge Graph anchors in this batch
Source:2015/01 Upcoming Events In The Knowledge Graph(Justin Boyan)
This post itself does not explain what the Knowledge Graph is — it assumes readers already know. It discusses writing schema.org Event / MusicGroup / ComedyEvent markup on official websites in order to appear in search results in the form of entity cards.
Key mechanisms:
- Direct markup: Embedding schema.org markup on the official website
- Delegated markup(
delegation markup): When "my event is not on the official website", useMusicGroupJSON-LD to point to third parties (Bandsintown / Songkick / Ticketmaster) - Venue entities:
Eventmarkup lets venues enter the Knowledge Graph - Infrastructure leverage: Large sites such as Ticketmaster are already marked up; venues that use their ticketing do not need to do anything to be covered
Significance: After its 2012 launch, the Knowledge Graph gradually expanded from "encyclopedic entities" to "events / products / organizations / businesses" — this path directly fed into later AI Overviews: the "fact blocks" that AI Overviews cites when generating answers come largely from entities extracted from the Knowledge Graph + structured data.
3.2 Evolution logic (reverse-inferred from 2025/05 succeeding-in-ai-search)
The 2025/05 post explicitly places structured data among the 7 items for "AI search success":
"Structured data is useful for sharing information about your content in a machine-readable way that our systems consider and makes pages eligible for certain search features and rich results. If you're using structured data, be sure to follow our guidelines, such as making sure that all the content in your markup is also visible on your web page."
This formally connects the Knowledge Graph / structured data path that began in 2012 into the AI Overviews era — the markup remains unchanged, while the consumption side expands from "knowledge cards" to "fact anchors for AI-generated answers".
3.3 Official description of AI Overviews (2025/05)
"With AI Overviews and AI Mode, people are using Search more often, asking new and more complex questions, and are more satisfied with their results. AI Overviews display links in a range of ways, and show a wider range of sources on the results page so it's easy for people to click out and explore content on the web."
Google's defense that "AI Overviews does not steal traffic":
"When people click to a website from search results pages with AI Overviews, these clicks are higher quality, where users are more likely to spend more time on the site.... Our AI results may give people more context about a topic overall, and display more relevant supporting links."
(Note: This is Google's own claim; the SEO community has produced large amounts of counter-evidence data, but this wiki only faithfully records Google's original words.)
Part 4 — Succeeding in AI Search guide (2025+)
Source:2025/05 Top ways to ensure your content performs well in Google's AI experiences on Search(John Mueller)
4.1 Checklist of 7 Recommendations (Full Distillation)
| # | Recommendation | Key Execution Points |
|---|---|---|
| 1 | Focus on unique, valuable content for people | Non-commoditized content; capture "longer, more specific, follow-up" AI Mode queries; apply the creating helpful, reliable, people-first content yardstick |
| 2 | Provide a great page experience | Cross-device compatibility, low latency, easily identifiable main content |
| 3 | Ensure we can access your content | Satisfy technical requirements for Google Search; Googlebot is not blocked;200 status; content is indexable —"Meeting the technical requirements covers you for search generally, including AI formats." |
| 4 | Manage visibility with preview controls | nosnippet / data-nosnippet / max-snippet / noindex control exposure within AI formats;The stricter the rules → the less AI display(Using noindex on a site is equivalent to opting out of being cited by AI Overviews) |
| 5 | Make sure structured data matches the visible content | Markup content must be visible on the page; follow sd-policies; pass the Rich Results Test |
| 6 | Go beyond text for multimodal success | High-quality image/video; keep Merchant Center / Business Profile information fresh — integrate with AI Mode multimodal search |
| 7 | Understand the full value of your visits | Don't only look at clicks; look at session duration, conversions, sign-ups, inquiries — Google claims traffic from AI Overviews is "higher quality" |
4.2 The Unchanging Underlying Ethos
"The underpinnings of what Google has long advised carries across to these new experiences. Focus on your visitors and provide them with unique, satisfying content."
Google did not provide a "new AI SEO formula" in 2025; what it offered is "old methods remain valid in new formats" — this counter-message urges creators not to chase tactics, but to keep producing helpful content.
4.3 The Rhetoric of "Search Has Always Been Evolving"
"The only thing predictable in Search is that it always evolves because people's needs are always evolving. The classic 'ten blue links' format changed to handle the needs of those seeking visual, video, news, and other types of content. Desktop displays evolved to mobile-friendly ones. Search evolved to handle voice queries, or 'multimodal' queries..."
Framing AI Overviews as the latest segment on the natural evolution curve of "ten blue links → mobile → voice → multimodal → AI", rather than "Google being forced by OpenAI to revolutionize itself" — this is a qualitative framing, not a quantitative claim.
Part 5 — AI-Powered Configuration of Search Console / Crawler
Source:2025/12 Streamline your Search Console analysis with the new AI-powered configuration(Nati Yosephian)
5.1 Functional Positioning
The Search Console Performance Report added AI-powered configuration(experimental, rolling out in grayscale): describe the data you want to see in natural language, and AI will configure filters / comparisons / metrics for you in one click.
"Powered by AI, this feature lets you describe the analysis you want to see in natural language. Your inputs are then transformed into the appropriate filters and settings, instantly configuring the report for you."
5.2 Three Things AI Can Do
- Applying filters — query / page / country / device / search appearance / date range
- Configuring comparisons — Complex custom date comparisons
- Selecting metrics — Select from among Clicks / Impressions / Average CTR / Average Position (4 metrics)
5.3 Example Natural Language Queries
- "Show me queries on phone searches that contain the word 'sports' in the last 6 months."
- "Compare traffic for my pages that contain '/blog' in this quarter to the same quarter last year"
- "Show me the Average CTR and Average Position of my queries in Spain in the last 28 days."
- "Show clicks for pages that include the word 'google'."
5.4 Stated Boundaries
| Dimension | Limitations |
|---|---|
| Scope | Only the Performance report for Search results;Discover / News are not supported |
| Accuracy | "AI can sometimes misinterpret requests. Always review the suggested filters." |
| Things it will not do | It will not sort tables or export data —it only configures, it does not execute |
5.5 Pattern Assessment
This is a sample of AI integration into Google's internal tools,not a change to ranking signals — it affects SEO practitioners' workflows (data query efficiency), not search results themselves. This wiki records it to fully capture the 2025 product line of "AI penetrating every layer of GSC".
5.6 AI Integration on the Crawler Dimension (Sources Temporarily Missing)
This batch of corpus does not cover official announcements for dedicated crawlers such as Google-Extended / GoogleOther for "AI training / Gemini crawling" (these are usually found on the crawlers overview page and in separate blog posts). The next round of ingest will supplement googleother / google-extended / vertex keywords.
Part 6 — Multimodal Search (Image / Lens / Multisearch)
This batch of corpus does not include standalone release blog posts for Image / Lens / Multisearch, but 2025/05 succeeding-in-ai-search categorizes multimodal search under AI Mode:
"Through the power of our AI, people can perform multimodal searches where they snap a photo or upload an image, ask a question about it and get a rich, comprehensive response with links to dive deeper."
Corresponding recommendations for webmasters:
- Provide high-quality Google Images (local reference material) content
- Provide high-quality Video (local reference material) content
- Keep Merchant Center product information fresh
- Keep Business Profile information fresh
Interpretation: Google has merged multimodal from standalone products (Google Lens / Multisearch) into the unified entry point of AI Mode — this is not "launching another new feature", but rather "AI Mode = the unified front end for text + image + video + voice".
Sources to capture in the next round of ingest:
- Official Google Lens blog history
- Original Multisearch release post (2022/04)
- "AI Mode multimodal search" (2025/04 release on blog.google)
Part 7 — Google's Core Belief: Quality Takes Priority Over "Whether It Was Written by AI"
Layering the official original statements from five time points — 2007 / 2017 / 2021 / 2023 / 2025 — Google's stance is consistent throughout:
| Year | Source | One-sentence stance |
|---|---|---|
| 2007 | quality-websites-avoid-auto-generated | "Google will not give credit for auto-generated links." (Opposing manipulative automation, not automation itself) |
| 2017 | protect-your-site-from-user-generated | Provided webmasters with 8 anti-spam tools (technical defense ≠ value judgment) |
| 2021 | update-to-generating-page-titles | "HTML title tags still account for 80%+ of final display" — while ML takes over, explicit signals remain the primary signals |
| 2023/02 | google-search-and-ai-content | "It's just content. Using AI doesn't give content any special gains." |
| 2023/12 | definitely-not-ai-generated-post | Gary Illyes made a self-deprecating remark in a year-end summary: "all this text (that we definitely didn't generate with AI)" —Google internally holds a relaxed, non-anxious attitude toward "AI writing" |
| 2025/05 | succeeding-in-ai-search | "The underpinnings of what Google has long advised carries across to these new experiences." |
7.1 Three Compressed Original Quotes
- "Our focus on the quality of content, rather than how content is produced, is a useful guide." — 2023/02
- "It's just content." — 2023/02 FAQ
- "The underpinnings of what Google has long advised carries across to these new experiences." — 2025/05
7.2 Strategy Behind the Stance
Google's choice to not act as a classifier judging AI content is based on product considerations:
- Enforceability: It is impossible to reliably determine whether a piece of text "was written by AI" — any detector will produce false positives/false negatives
- Incentive alignment: Rather than punishing tools, it is better to reward outcomes (helpful content), so that AI tools in turn serve quality
- Historical consistency: The 2011 Panda update did not ban people from writing spam content, and 2023 does not ban AI-written content,the logic is isomorphic
7.3 Actionable Takeaways for Webmasters
| Scenario | Action |
|---|---|
| Use AI to help write drafts, with human editing and polishing | OK, no disclosure required (unless readers would ask "How was this created") |
| Use AI to mass-generate keyword pages | scaled content abuse,Will be penalized |
| AI-written but supplemented with real experience / cases / data | OK, satisfies the "Experience" dimension in E-E-A-T |
| List AI as the author | Not recommended — disclose based on "how it was created", not based on "who wrote it" |
| Add disclosure to all AI content | Not necessary; disclose only when "readers would ask How" |
| Opt out of being cited by AI Overviews | Use noindex or nosnippet/max-snippet, but this also opts out of search visibility |
Appendix A: Actual Classification of the 18 Candidate Items in This Batch
| Document | AI/ML related? | Assigned to Part |
|---|---|---|
| 2005/09 announcing-sitemap-generator-version | ❌ sitemap encoding | — |
| 2005/09 using-oai-pmh-with-google-sitemaps | ❌ OAI-PMH protocol | — |
| 2005/12 new-version-of-sitemap-generator | ❌ GZip bugfix | — |
| 2007/08 quality-websites-avoid-auto-generated | ✅ Early stance on auto-generated content | Part 1.5 / Part 7 |
| 2008/04 retiring-support-for-oai-pmh-in | ❌ OAI-PMH decommissioning | — |
| 2009/01 new-google-sitemap-generator-for-your | ❌ sitemap tools | — |
| 2009/08 help-test-some-next-generation | ⚠️ Caffeine indexing infrastructure preview (not AI/ML ranking) | Timeline skeleton only, Part 2.2 |
| 2012/03 crawl-errors-next-generation | ❌ Webmaster Tools error reporting optimization | — |
| 2015/01 upcoming-events-in-knowledge-graph | ✅ Knowledge Graph entity expansion path | Part 3.1 |
| 2017/01 protect-your-site-from-user-generated | ✅ Automated spam defense (pre-LLM) | Part 1.5 / Part 7 |
| 2017/12 nhac-nho-ve-lien-ket-tai-tro | ❌ Vietnamese announcement stub | — |
| 2018/07 ein-meilenstein-fur-die-sicherheit-in | ❌ German announcement stub | — |
| 2021/08 update-to-generating-page-titles | ✅ ML title rewriting + HTML title 80% anchor | Part 2.1 / Part 7 |
| 2023/02 google-search-and-ai-content | ✅✅✅ Core stance original text | Full Part 1 / Part 7 |
| 2023/12 definitely-not-ai-generated-post | ✅ Self-deprecating AI remark in year-end summary | Part 7 |
| 2025/05 succeeding-in-ai-search | ✅✅✅ 7 SEO rules for the AI era | Full Part 4 / Part 3.3 / Part 6 |
| 2025/12 ai-powered-configuration | ✅ Search Console AI assistant | Part 5 |
| 2026/04 scl-shanghai-2026 | ❌ Event announcement | — |
Hit rate: 8 out of 18 items hit (44%), of which 3 (2023/02 / 2025/05 / 2025/12) are core original texts.
Appendix B: Next Round Ingest TODO (Fill in official original texts from RankBrain → AI Overviews)
developers.google.com/search/blogFull crawl, filter by keywords:rankbrain/bert/mum/helpful-content/ai-overviews/ai-mode/google-extended/googleotherknowledge-graph(first released 2012)multisearch/lens
- Crawl the
webspam-reportseries (SpamBrain public scorecards) - Crawl
google-search-and-ai-contentcompanion posts before/after (look backward for original posts published in helpful content system 2022/08 / 2022/12; look forward for the original 2024/05 AI Overviews release post) - Merge and upgrade with this wiki — do not create a second AI-themed wiki; directly append Part 8 / Part 9 to this document——Do not create a second AI-themed wiki; append Part 8 / Part 9 directly to this file.
Sources and Related Materials
- https://developers.google.com/search/blog/2005/09/announcing-sitemap-generator-version?hl=en
- https://developers.google.com/search/blog/2005/09/using-oai-pmh-with-google-sitemaps?hl=en
- https://developers.google.com/search/blog/2005/12/new-version-of-sitemap-generator?hl=en
- https://developers.google.com/search/blog/2007/08/quality-websites-avoid-auto-generated?hl=en
- https://developers.google.com/search/blog/2008/04/retiring-support-for-oai-pmh-in?hl=en
- https://developers.google.com/search/blog/2009/01/new-google-sitemap-generator-for-your?hl=en
- https://developers.google.com/search/blog/2009/08/help-test-some-next-generation?hl=en
- https://developers.google.com/search/blog/2012/03/crawl-errors-next-generation?hl=en
- https://developers.google.com/search/blog/2015/01/upcoming-events-in-knowledge-graph?hl=en
- https://developers.google.com/search/blog/2017/01/protect-your-site-from-user-generated?hl=en
- https://developers.google.com/search/blog/2017/12/nhac-nho-ve-lien-ket-tai-tro?hl=en
- https://developers.google.com/search/blog/2018/07/ein-meilenstein-fur-die-sicherheit-in?hl=en
- https://developers.google.com/search/blog/2021/08/update-to-generating-page-titles?hl=en
- https://developers.google.com/search/blog/2023/02/google-search-and-ai-content?hl=en
- https://developers.google.com/search/blog/2023/12/definitely-not-ai-generated-post?hl=en
- https://developers.google.com/search/blog/2025/05/succeeding-in-ai-search?hl=en
- https://developers.google.com/search/blog/2025/12/ai-powered-configuration?hl=en
- https://developers.google.com/search/blog/2026/04/scl-shanghai-2026?hl=en
- GSC Blog: Evolution of Quality Policies and E-E-A-T (Webmaster Guidelines → Search Essentials)
- GSC Blog: Evolution of Core Updates and Algorithm Iterations (2010–2026)
- Google SEO Office Hours Highlights (2022.11–2024.08) + Summary of 3 Major FAQ Topics
- GSC Blog 2021–2026: The Era of Helpful Content / Page Experience / AI Overviews