Most Google Search changes are not ranking updates. They are Search Console report changes and data gaps, crawler parsing rules, documentation edits, changes to who can fetch results.
None of them gets a dashboard entry, and our algorithm updates tracker is for ranking. This page is where the rest goes, newest first, each with a source we have read.
How to read the status column. A status of Google means Google published or confirmed the item.
A status of Reported means a named observer or tool vendor saw it, and Google has not commented.
A Search Console data gap is a reporting problem, not a change to your site. Google has restored every gap on this page so far.
Every change, newest first
Thirty-seven dated items since July 2026. Documentation changes come from the Search Central changelog; the rest from Google posts and named reports.
| Date | Change | Status |
|---|---|---|
| Ahrefs: "between 5% and 20%" of results affected, "depending on the data provider". An Ahrefs product update, credited to no named author, says it has "witnessed an increase in the “poisoning” of search results by Google, where different results are shown to suspected SERP data providers". It calls this "an industry-wide issue", says its filters "detect and reject the abnormal results and request accurate replacements", and says it is "cleaning up any past results that may have been affected". No method, sample, start date, country or device is given. | Reported | |
| The "Control what you share with Google Search" page gains the robots meta tag and the Search generative AI control as listed methods. The Search Central changelog entry for 21st Oct says the page was updated "to include existing options such as the robots meta tag, data-nosnippet, X-Robots-Tag, and the Search generative AI control, along with minor clarifications that the page applies to Google Search". Against a 15th Oct archived copy, two method blocks are new. One covers the robots meta tag, data-nosnippet and X-Robots-Tag. The other, marked "Applicable: site-wide", says "You can manage your site's inclusion in generative AI features on Google Search, including AI Overviews and AI Mode, by using the Search generative AI control in Search Console". The title now ends "with Google Search", and the block heading became "How to block content from Google Search". No control is new: the generative AI control reached every property on 31st Aug 2026. Search Engine Roundtable notes that "Google specifically added these two sections". | ||
| The URL structure page is edited with no changelog entry. The page is stamped "Last updated 2026-10-21", up from 10th Dec 2025. Against a 15th Oct archived copy, one sentence changed, in the hyphens section. It now explains that the "_" separator is "commonly used for denoting concepts that should be kept together", and ends "whereas hyphens clearly signal a word boundary". The 21st Oct changelog lists only the entry above. Barry Schwartz writes that "The overall meaning of the section really did not change". It is the second documentation edit this month with no changelog entry, after the people-first content page on 5th Oct. | ||
| Nozzle updates its study: 8.4% of judged SERPs poisoned, 3 to 7% a day since 14th Oct. Nozzle's page, updated 19th Oct with data through 18th Oct, now counts 27.0 million judged SERPs since 13th Sep. Of those, 8.4% came back poisoned, against 0.17% before, with a peak of 28.6% on 29th Sep. From 8th to 13th Oct the daily share was 8 to 11%. It fell to about 3% on 14th Oct, then rose to 6.6% on 17th Oct and 7.0% on 18th Oct. Nozzle now says 68.9% of poisoned SERPs had their usual sites back within three days, and 92.7% within two weeks; the 10th Oct version said 77.9%. A tracked site misses the top 10 on 60.2% of poisoned SERPs, against 2.7% before. Nozzle calls it "too early to call it over". | Reported by Nozzle | |
| AccuRanker: a quarter of its sample swapped on 25th Sep, under 1% by 17th Oct after its checks. AccuRanker's post by Peter Emil Tybirk dates the onset to "Late on September 24". On a fixed sample of tracked keywords, its "sandwich check" found 30.2% of desktop and 25.7% of mobile page-1 results swapped on 25th Sep, against 0.26% and 0.38% before. Its own filtering brought that "below 2%" within two days and to 0.58% and 0.47% by 17th Oct. It says "Google tightened its detection again on October 15, mostly on mobile", and sees smaller rounds of the same pattern "From late January 2026". The later shares count what passed AccuRanker's checks, so they are not comparable with Nozzle's 8.4%. It says "Google has made no statement". Semrush told Search Engine Roundtable it has seen the issue "since late summer" with "limited" impact, and gives no figure. | Reported | |
| Indexing API quota page rewritten; the approval and quota request form removed. The changelog says the page was updated "to reflect the current quota limits and process" and to "remove an outdated form". The default limits are unchanged: 200 publish requests a day, 180 metadata requests a minute, 380 requests a minute. The quickstart and using-the-API pages lost their "Request approval and quota" steps the same day. The quickstart also dropped its advice to prefer the API over sitemaps for short-lived pages. Both pages still say the API is only for pages with JobPosting or BroadcastEvent markup. Search Engine Roundtable read the change as the end of the default quota; the live page still states it. | ||
| SE Ranking: "roughly 2% of tracked results" still affected. SE Ranking said on X that Google "has recently been returning incomplete or unreliable results to rank trackers across the industry". After its fixes "roughly 2% of tracked results" are still affected, "and that share continues to shrink". Its status page opened the incident on 23rd Sep and says data is "corrected for all affected dates". The 2% counts results still wrong after its fixes, so it is not comparable with Nozzle's 8.0% or DemandSphere's 11%. | Reported | |
| Performance report custom date picker broken, fixed within two hours. Barry Schwartz reports the custom date range's end date stuck at 1969, with the message "Date can't be after 1969-12-31". The preset ranges worked. His post, timed 7:16 am ET, was updated at 9:10 am to say it was fixed. | Reported | |
| Performance report more than 64 hours behind. Barry Schwartz reports the Search performance report "over 64 hours delayed" on the morning of 11th Oct, after lagging "over the past few days, post-spam update". He says the last delay this long was in December 2025. Google had not commented, and the data anomalies page listed nothing when we read it that evening. | Reported | |
| Nozzle measures "poisoned" results pages served to rank trackers. Nozzle's study covers 27.5 million SERPs collected to 9th Oct. Of the SERPs it could judge against each keyword's history, 8.0% came back "poisoned" since 13th Sep, against 0.17% before, with the first on 20th Sep. The page looks normal, but most of the keyword's usual sites are gone. Nozzle calls it Google's response to AI scraping, with rank trackers "caught in it". Barry Schwartz reports Derek Perkins of Nozzle describing wide IP blocking, more captchas and injected bad data. Google has not commented. | Reported by Nozzle | |
| UGC Fresh Data Program documented. The Search Central changelog logs a new page on the UGC Fresh Data Program. Approved forum and social platforms push fresh content and engagement counts to Search through a dedicated pipeline. Google says it is independent of the Indexing API and of organic crawling, and guarantees nothing. Our entry has the eligibility list. | ||
| DemandSphere puts "spurious" results at about 11% of its daily SERPs. Ray Grieselhuber of DemandSphere writes that Google has "started to introduce spurious results into their SERPs when they detect alleged bot traffic", affecting "~11% of our daily SERPs". He says not to take the figure as final. His 24th Sep post dates the heaviest blocking to "right around September 11th", the earliest vendor date we have. The method is not described, and Google has not commented. | Reported | |
| Sistrix calls divergent results "an industry-wide problem". A support page by Johannes Beus says that "Since September 2026" Google returns, for some queries, results that "differ significantly from the regular search results" and "contain different websites". Sistrix now publishes only results that pass extra checks, has switched off on-demand updates, and gives no share. It says "top 10 rankings and the Visibility Index remain reliable". | Reported | |
| Preferred source selection counts emailed. Search Console emails tell property owners how many people chose them as a preferred source, with data as of 5th Oct and a survey on future reporting. No console report exists. Our entry has the email text. | ||
| Performance report filter takes several countries at once. Google Search Central posted on LinkedIn: "If you operate in multiple countries, you can now view their combined Google Search traffic." The device filter changed in the same update. | ||
| Reduce-crawl-rate documentation gains Retry-After details. The crawling docs changelog says Google "restructured the emergency crawl rate reduction section" and added Retry-After header examples for 503 and 429 responses. Google says support for the header "is not new". | ||
| Search generative AI control page notes child-property overrides. The help page now says owners of a top-level domain property "will see a notification" when a child property overrides the parent setting. An undated edit, reported by Search Engine Roundtable. | ||
| People-first content page gains a main content section and a fake-author warning. The page now defines main content, lists four attributes raters judge, and calls fabricated author profiles "a form of deception". The changelog does not list the edit; the page's own stamp dates it. Our entry has the detail. | ||
| Review snippets fade from healthcare pages. Schema App's Andrea Badder reports a drop in Review Snippet visibility across its healthcare customers "since late May, with another drop occurring in early August". Markup changes did not restore them, and the pages stay eligible. Picked up by Search Engine Roundtable; Google has said nothing. | Reported | |
| Generative AI content guidance revised. Three new sentences say AI output can contain inaccuracies and must be fact-checked by hand before publishing (changelog). Our entry has the detail. | ||
| Multimodal search type in Search Console. A new web multimodal search type for image-based searches. Our entry has the detail and a correction on how totals add up. | ||
| VideoObject gains the creator property. The structured data documentation now documents the creator and author properties and lists the supported interaction types for interactionStatistic (changelog). | ||
| Aggregator and supplier units support local business queries. The two European result units gain local business query support in their documentation (changelog). | ||
| Search profile badge guide. A new guide on adding a Search profile badge to a website, "to help site owners point their audience to their Search profile" (changelog). | ||
| Crawl stats report missing a day. The Crawl Stats report lost 15th Sep for every property. Roundtable notes earlier gaps in October 2025 and August 2026, each restored (Search Engine Roundtable, 20th Sep). | Reported | |
| Google blocking more scrapers and rank trackers. Nozzle reported about an 80% drop in data it could pull from Google; Sistrix's status page said on 16th Sep that collection was "running at a reduced rate" after Google changed "the way search results are delivered" (Search Engine Roundtable, 18th Sep). | Reported by tool vendors | |
| Page indexing report missing June data. A block of June 2026 vanished from the report's chart for every property, spotted by Dan Lauer (Search Engine Roundtable). | Reported | |
| Indexing report "short blip". For about an hour Search Console showed indexed pages as "Crawled - currently not indexed". John Mueller confirmed a reporting bug the next day (Search Engine Roundtable, 9th Sep). | Google (confirmed as a bug) | |
| Regional differences documentation. A new page on search experiences available in certain countries, such as aggregator units, supplier units and carousels. Our entry covers the European changes behind it. | ||
| News tab missing indexed articles. Publishers saw articles in web results but not in the News tab, sometimes appearing much later; Roundtable reproduced it and got no answer from Google (Search Engine Roundtable). | Reported | |
| European Search Dataset Licensing Program page refreshed. The program overview, eligibility criteria and application details were updated (changelog). | ||
| Favicon documentation lists the supported formats. Google says the supported formats "haven't changed"; the page used to link to an external reference that "evolved over time and caused ambiguity" (changelog). | ||
| "Google's crawlers don't parse JSON." Gary Illyes on Bluesky: the crawlers download, and parsing happens in indexing; Merchant Center very likely uses the same parser (Search Engine Roundtable). | ||
| JSON-LD extraction applies one pass of HTML unescaping. Google on LinkedIn: "we changed our JSON-LD extraction and are now only applying a single pass of HTML unescaping", so double-escaped entities "will no longer be unrolled". Sites should use standard JSON escapes or Unicode escapes. Reported by Search Engine Roundtable on 21st Aug. | ||
| Custom button for preferred sources. The preferred sources documentation gains instructions for a custom, interactive button that brings users "right back to where they left off" (changelog). | ||
| Platform properties go global, with a social and video performance guide. Search Console properties for Instagram, TikTok, X and YouTube content became "globally available to everyone" (Search Central blog). | ||
| Platform properties introduced. A new Search Console property type showing how posts on the four platforms perform on Google Search and Discover, with Performance, Insights and Achievements reports, rolling out "gradually over the coming weeks" (Search Central blog). |
Search Console data gaps: what they are and what to do
Three in September 2026 alone. They are reporting problems, they affect every property at once, and Google has restored each one.
A data gap is a day missing from a Search Console report, or a wrong status shown for an hour. It appears for every property at the same time.
That is the test: if your report changed and nobody else's did, it is your site. If everyone's did, it is the report.
September 2026 had three. The indexing "short blip" of 8th Sep, confirmed by John Mueller as a reporting bug, came first.
Then June's data went missing from the page indexing report on 11th Sep, and Crawl Stats lost 15th Sep.
Google has restored every gap in this record. Do not change your site in response to one, and annotate the date if you report on the data.
The JSON-LD change: one pass of HTML unescaping
A parsing rule change that can silently break rich results on sites that double-escape entities.
In August 2026 Google said its JSON-LD extraction now applies "a single pass of HTML unescaping", to bring the parser "up to JSON and other standards".
The practical effect, in Google's words: double-escaped entities "will no longer be unrolled". A product name written as "Smith & Sons" inside JSON-LD used to be corrected; now it is read as written.
Gary Illyes pointed to RFC 8259 section 7 for proper escaping. Use standard JSON escapes, or a Unicode escape for the ampersand.
Illyes added on 25th Aug that Google's crawlers do not parse JSON at all. They download, and indexing parses, so the change lives in indexing and very likely applies to Merchant Center too.
Check with the Rich Results Test. A page that validated before August and fails now, with an entity in the message, is the signature.
Rank trackers and scrapers: what Google blocked in September
Tool vendors reported sharp drops in the data they could collect from Google from about 13th Sep 2026. Google has said nothing.
From about 13th Sep 2026, several tools that collect Google results reported being blocked more often. Derek Perkins of Nozzle told Search Engine Roundtable of an 80% drop in retrievable data, and the same at DataForSEO.
Sistrix's status page said on 16th Sep that Google "has made further changes to the way search results are delivered" and that its collection was "running at a reduced rate". Steve Paine of Sistrix said Google had been changing delivery "for about a year now, currently at a very high pace".
On 7th Oct a Sistrix support page called the divergent results "an industry-wide problem". Sistrix publishes only results that pass extra checks, has switched off on-demand updates, and gives no share.
On 10th Oct Nozzle published a study of 27.5 million SERPs. Since 13th Sep, 8.0% came back "poisoned": normal-looking pages missing most of the keyword's usual sites.
Nozzle's page, revised by 17th Oct, names the denominator: 17.8 million SERPs judged against each keyword's history. The 12th Oct copy gave only the 27.5 million.
Such pages were a quarter of all SERPs from 27th to 29th Sep. The peak was 28.6% on the 29th.
They ran at 8 to 11% a day from 8th to 13th Oct. On 14th Oct the share fell to about 3%.
It was 6.6% on 17th Oct and 7.0% on 18th Oct.
Nozzle's 19th Oct update carries data through 18th Oct. It puts the share since 13th Sep at 8.4% of 27.0 million judged SERPs.
Nozzle now says 68.9% of poisoned SERPs had the usual sites back within three days, and 92.7% within two weeks. The 10th Oct version said 77.9%.
Its advice stands: a one-day drop in late September is more likely this than a ranking change. On 19th Oct it called the pattern "too early to call it over".
Nozzle reads the pattern as a response to AI scraping, with rank trackers "caught in it".
DemandSphere reports the same pattern at a different scale. Its 7th Oct post puts spurious pages at about 11% of its daily SERPs, a figure it says "could change rapidly".
Ray Grieselhuber dates the heaviest blocking to "right around September 11th", two days before the reports above. He writes that Google's target is the AI labs, with rank trackers "caught in the crossfire".
The two vendors measure different keyword sets. DemandSphere does not say how it counts a spurious page, so 8% and 11% are two estimates, not a range.
SE Ranking gives a third figure of a different kind. On 16th Oct it said "roughly 2% of tracked results" were still affected after its fixes, "and that share continues to shrink".
That counts what its checks still miss, not what Google served. It sits beside the other two figures, not between them.
AccuRanker gives a fourth figure, from its own stored data. Its 19th Oct post dates the onset to late on 24th Sep.
On that first day, 30.2% of desktop and 25.7% of mobile page-1 results in a fixed sample were swapped. Its filtering brought that below 2% within two days and under 1% by 17th Oct.
It says Google "tightened its detection again on October 15, mostly on mobile".
AccuRanker also sees smaller rounds of the same pattern from late January 2026. From April to July they ran at 7 to 10 times the 2025 level.
Its later shares describe what passed its checks, so they do not compare with Nozzle's 8.4%.
Semrush told Search Engine Roundtable it has seen the issue "since late summer", with "limited" impact on the rankings its users track. It gives no figure.
Ahrefs gave a band rather than a share. Its 22nd Oct update says "between 5% and 20% of search results" are affected, "depending on the data provider".
The post names no sample, start date, country or device. It does not say which providers it counts, so the band is not a measurement of Ahrefs' own data.
Google has not commented. This matters for every rank-tracker figure on our statistics pages.
A measurement taken after 13th Sep may rest on a smaller or different sample than one taken before.
Search Console is unaffected. It is Google's own report, not a scrape.
Platform properties: Search Console for Instagram, TikTok, X and YouTube
Introduced 7th Jul 2026, global on 29th Jul. Search performance for posts you do not host.
A platform property is a Search Console property for an Instagram, TikTok, X or YouTube account rather than a website. It shows which search terms lead people to your posts on Google Search and Discover.
Google introduced them on 7th Jul 2026 after an earlier experiment, with Performance, Insights and Achievements reports. They became available to everyone worldwide on 29th Jul, with a guide to analysing social and video performance.
Setup is in Search Console's property selector: add a property, pick one of the four platforms and authorise the connection. Our Instagram tracker covers the launch from the creator's side.
Sources
- Google Search Central: Latest documentation updates (changelog)
- Google Search Central blog: See how content from social and video platforms performs on Google Search (7th July 2026)
- Google Search Central blog: Platform properties roll out globally, plus a new social and video performance guide (29th July 2026)
- Search Engine Roundtable: JSON-LD Extraction For Googlebot Now Does One Pass Of HTML Unescaping (21st August 2026; quotes Google's LinkedIn post)
- Search Engine Roundtable: Google Says Google's Crawlers Don't Parse JSON (25th August 2026)
- Search Engine Roundtable: Publishers Noticing Google News Tab Content Disappearing (3rd September 2026)
- Search Engine Roundtable: Google Confirmed Indexing Reporting Bug From Yesterday As Short Blip (9th September 2026)
- Search Engine Roundtable: Google Search Console Indexing Report Missing Old June Data (11th September 2026)
- Search Engine Roundtable: Google May Be More Successful In Blocking Scrapers & Tracking Tools (18th September 2026)
- Nozzle Research: Poisoned Google SERPs (10th October 2026, updated 19th October with data through 18th October)
- AccuRanker: How AccuRanker Handles Poisoned SERPs, by Peter Emil Tybirk (19th October 2026)
- Sistrix support: Google ranking data collection, by Johannes Beus (7th October 2026)
- SE Ranking on X (16th October 2026)
- SE Ranking status page: Google rankings, missing positions for some keywords (incident opened 23rd September 2026)
- DemandSphere: Spurious data in Google SERPs (7th October 2026)
- DemandSphere: Google's Summer of Love (24th September 2026)
- Ahrefs: An update on Google's poisoning of search results (22nd October 2026)
- PPC Land: Google returns wrong results on 11% of DemandSphere's daily rank checks (13th October 2026)
- Search Engine Roundtable: Third-Party Google Rank Tracking Struggling Now (12th October 2026; later updated with a Semrush statement)
- Search Engine Roundtable: Google Search Console Crawl Stats Missing A Day Of Data: September 15th (20th September 2026)
Frequently asked questions
Is a Search Console data gap a problem with my site?
No. A gap or wrong status that appears for every property at once is a reporting problem on Google's side.
Google has restored every gap in this record. Compare with another property before changing anything.
What changed in how Google reads JSON-LD?
Google now applies "a single pass of HTML unescaping" when extracting JSON-LD, so double-escaped entities "will no longer be unrolled". Use standard JSON escapes or Unicode escapes, and re-test pages with the Rich Results Test.
Why did my rank tracker lose data in September 2026?
Several tool vendors reported Google blocking their collection more often from about 13th Sep 2026. Nozzle reported about an 80% drop and Sistrix's status page confirmed a "reduced rate".
Nozzle's 10th Oct study covers 27.5 million SERPs, 17.8 million of them judged against each keyword's history. Since 13th Sep, 8.0% of the judged SERPs came back "poisoned", with the usual sites swapped out.
Its 19th Oct update, with data through 18th Oct, puts the share at 8.4% of 27.0 million judged SERPs. The daily share has run at 3 to 7% since 14th Oct.
DemandSphere put spurious pages at about 11% of its daily SERPs on 7th Oct. It dates the blocking to about 11th Sep.
Sistrix called the pattern "an industry-wide problem" on 7th Oct. SE Ranking said on 16th Oct that about 2% of its tracked results were still affected after its fixes.
AccuRanker said on 19th Oct that its checks had the share under 1% by 17th Oct. Semrush told Search Engine Roundtable its impact had been "limited".
Ahrefs said on 22nd Oct that between 5% and 20% of results were affected, depending on the data provider.
Google has not commented. Search Console data is unaffected.
What is a Search Console platform property?
A property for an Instagram, TikTok, X or YouTube account. It shows how the account's posts perform on Google Search and Discover.
Introduced on 7th Jul 2026 and available worldwide since 29th Jul 2026.
Where does Google announce documentation changes?
On the Search Central "Latest documentation updates" page, which also has an RSS feed. The HTML page can carry an entry a day before the feed does.
Compiled by Claude from primary sources, checked by Akash Mansukhani before publication. See how we source and correct this page.Keywords Everywhere, "Search Console and Googlebot changes", last updated 22nd Oct 2026, https://keywordseverywhere.com/news/google-algorithm-updates/search-console-changes/