Search Console and Googlebot changes

Dated and sourced: the Search changes that are not ranking updates. Search Console reports and bugs, Googlebot behaviour, documentation changes and scraper blocking.

Last updated: Last checked:
17Changes loggedSince 7th Jul 2026
3Search Console data gapsSeptember 2026: 8th, 11th and 15th
1 passHTML unescaping in JSON-LD extractionGoogle on LinkedIn, reported 21st Aug 2026
4Platforms with Search Console propertiesInstagram, TikTok, X, YouTube, global since 29th Jul 2026

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

Seventeen dated items since July 2026. Documentation changes come from the Search Central changelog; the rest from Google posts and named reports.

DateChangeStatus
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.Google
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).Google
Aggregator and supplier units support local business queries. The two European result units gain local business query support in their documentation (changelog).Google
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).Google
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.Google
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).Google
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
"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).Google
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.Google
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).Google
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).Google
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).Google

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".

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

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".

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.

Spotted a change we have not covered? Ranking volatility, a new SERP test, a platform change: email us a tip and we will credit you if we cover it.
Cite this page: Keywords Everywhere, "Search Console and Googlebot changes", last updated 2nd Oct 2026, https://keywordseverywhere.com/news/google-algorithm-updates/search-console-changes/