Captures were made on the dates below, sometimes after first detection. Hashes apply to decompressed files. Compared text is a normalized extraction; the source capture retains the received bytes.
Shortened excerpt · normalized text, not verbatim.
Deploying a Content Delivery Network (CDN) to distribute your site's assets across fast, globally…
Moving to a CDN without overwhelming your origin (or blocking Googlebot)
Captures were made on the dates below, sometimes after first detection. Hashes apply to decompressed files. Compared text is a normalized extraction; the source capture retains the received bytes.
Keep a comparison baseline. To analyze a change associated with the rollout, wait for its official completion and at least one full week of data.
Rollout ongoingOfficial start · 2026-11-10Last confirmed status · 2026-11-12 · 02:16 UTC
Who is affected
Sites monitoring their visibility in Google Search. Google announces a global rollout across all languages. The announcement does not establish that any particular site will be affected.
What changes
A broad update to ranking systems is ongoing at the time of this reading. It does not announce a new technical requirement for all sites. Coincident dates alone do not establish the cause of a traffic change.
What to do
Record changes made to the site and keep baseline data. After the recommended waiting period, compare pages and queries before and after, separating search types and other possible causes. Avoid a rushed redesign based on this announcement alone.
When
Completion must be confirmed by Google. Then wait at least one full week before analyzing Search Console data. The announced rollout duration is not a guaranteed completion date.
Verify and assess for TSEP
Check dates in Google’s dashboard, then pages, queries and search types in Search Console. No TSEP control alone establishes an algorithmic effect.
For review: does this case call for clearer guidance on attribution limits? The announcement alone does not justify adding a normative rule.
Protocol version considered : 0.3.0-draft.9 · TSEP review decision pending
Shortened excerpt · normalized text, not verbatim.
Incident began at 2026-11-10 10:06 (all times are US/Pacific). Released the November 2026 core update, which applies globally…
UPDATE: November 2026 core update
Captures were made on the dates below, sometimes after first detection. Hashes apply to decompressed files. Compared text is a normalized extraction; the source capture retains the received bytes.
Shortened excerpt · normalized text, not verbatim.
Today, we're announcing our plans to support a shared AI training control in robots.txt. This will help…
Supporting a shared AI training control for websites
Captures were made on the dates below, sometimes after first detection. Hashes apply to decompressed files. Compared text is a normalized extraction; the source capture retains the received bytes.
Updated common crawlers page to mention future AI training control support
Captures were made on the dates below, sometimes after first detection. Hashes apply to decompressed files. Compared text is a normalized extraction; the source capture retains the received bytes.
Your content, your choice: clearer preferences for training and grounding
Captures were made on the dates below, sometimes after first detection. Hashes apply to decompressed files. Compared text is a normalized extraction; the source capture retains the received bytes.
Making it easier for websites to express AI training preferences
Captures were made on the dates below, sometimes after first detection. Hashes apply to decompressed files. Compared text is a normalized extraction; the source capture retains the received bytes.
How Anthropic honors website preferences for AI training
Captures were made on the dates below, sometimes after first detection. Hashes apply to decompressed files. Compared text is a normalized extraction; the source capture retains the received bytes.
Captures were made on the dates below, sometimes after first detection. Hashes apply to decompressed files. Compared text is a normalized extraction; the source capture retains the received bytes.
Shortened excerpt · normalized text, not verbatim.
What: Updated the user-generated spam prevention guide with guidance on blocking indexing of link-shared content and monitoring abuse…
Updated guidance on preventing user-generated spam
Captures were made on the dates below, sometimes after first detection. Hashes apply to decompressed files. Compared text is a normalized extraction; the source capture retains the received bytes.
Shortened excerpt · normalized text, not verbatim.
What: Updated the URL structure best practices to clarify word separation guidelines using hyphens versus underscores.…
Updated guidance on crawlable URL structures
Captures were made on the dates below, sometimes after first detection. Hashes apply to decompressed files. Compared text is a normalized extraction; the source capture retains the received bytes.
Shortened excerpt · normalized text, not verbatim.
What: Updated the how Google interprets the robots.txt specification to add recommendation for percent-encoding in rule paths.…
Updated guidance on robots.txt specifications
Captures were made on the dates below, sometimes after first detection. Hashes apply to decompressed files. Compared text is a normalized extraction; the source capture retains the received bytes.
Shortened excerpt · normalized text, not verbatim.
What: Updated the control what you share with Google Search documentation to include existing…
Updated the control what you share with Google Search documentation
Captures were made on the dates below, sometimes after first detection. Hashes apply to decompressed files. Compared text is a normalized extraction; the source capture retains the received bytes.
Experimental soft navigation metrics now available in CrUX
Captures were made on the dates below, sometimes after first detection. Hashes apply to decompressed files. Compared text is a normalized extraction; the source capture retains the received bytes.
Introducing Topics Portfolio (Beta) in AI Performance
Captures were made on the dates below, sometimes after first detection. Hashes apply to decompressed files. Compared text is a normalized extraction; the source capture retains the received bytes.
An event counts once when any of its official reports enters the collection. Each provider is counted separately. Later backfills preserve the month-end score.
IETF
training signal text · Nightly
Last successful read ·
RSL
content licensing specification · Nightly
Last successful read ·
Schema.org
releases · Nightly
Last successful read ·
Outside the default selection3 sources
Baidu
search resource platform · Nightly
Last successful read ·
6 archived publications Sep 2026 – Nov 2026Official source
Naver
Search & Tech · Nightly
Last successful read ·
18 archived publications Jul 2026 – Nov 2026Official source
Yandex
webmaster news · Nightly
Last successful read ·
5 archived publications Aug 2026 – Oct 2026Official source
Available archives vary by source. Changes to undated documentation pages are reviewed before they may appear in the feed.
Primary sources feed the editorial selection. Baidu, Naver and Yandex remain available by filter and in search.
The method
Facts. With context.
Collect
Critical sources are checked hourly; all sources are checked nightly. One record keeps the original title, published date and sources for each event. Undated documentation changes are held for review. The French and English RSS feeds support WebSub to notify compatible subscribers after publication.
Classify
A yellow square marks a change that may affect a TSEP check, access rule, diagnosis or deadline. Recurring publications and events remain background information. A yellow triangle identifies background news; a dashed circle means classification is pending. Translations are editorial.
Review for TSEP
Each month, the review connects announcements to relevant TSEP controls. For each item reviewed, the team decides whether the protocol already covers it, a change needs consideration, or monitoring should continue or close.
Impact explains practical consequences after human review in the displayed language. View adds a distinct editorial position: it is public only after personal approval, with the author’s name and reviewed language. AI-assisted proposals remain in the private workspace.
