TL;DR Summary:
Search Console Shift: The biggest change is Google’s wider rollout of the Generative AI Performance Report, giving site owners new visibility into how pages appear in AI Overviews and AI Mode.Volatility Without Update: Ranking swings reported early in August were not tied to any confirmed Google core or spam update, so they may be noise rather than a real algorithm change.Technical Checks Matter: Misconfigured Cloudflare or CDN bot protections can block Googlebot, while hreflang URLs marked not indexed may still surface in search under the right conditions.Action This Week: Check Search Console for the new AI report, review bot-blocking rules, verify hreflang behavior, and avoid overreacting to unconfirmed volatility reports.FSAS SEO Trends This Week: What Changed and What to Do About It August 16 2026
Google confirmed no new core or spam algorithm update this week. The last confirmed ranking change remains the June 2026 spam update, which ran June 24 to 26. The most significant development instead is the wider rollout of the Generative AI Performance Report inside Google Search Console, which went live for most users around August 13 and gives site owners their first real data on how pages appear in AI Overviews and AI Mode.
Unconfirmed ranking volatility repeats for the third time this summer
Barry Schwartz at Search Engine Roundtable reported heightened ranking volatility between August 1 and August 3, based on third-party tracking tools. Google’s Search Status Dashboard showed no confirmed ranking, indexing, crawling, or serving incident between August 1 and August 6. Schwartz reported another volatility wave on August 5 and 6. Google has not confirmed any update tied to these swings. Schwartz noted that these movements “matter less and less for publishers because Google is sending less and less traffic to publishers,” a point some large publishers are citing while considering blocking Google Search entirely.
Search Console’s Generative AI Performance Report reaches general availability
As of August 13, the Generative AI Performance Report appears as an expandable tab under the main Performance report in Search Console for most accounts, though Google has not issued an official announcement confirming full rollout. This report shows how individual pages surface inside AI Overviews and AI Mode, data that was previously unavailable or limited to a small test group. If you don’t see the tab yet, check back within the next few days rather than assuming your site is excluded.
Gary Illyes explains why hreflang alternates show as “not indexed”
On or around August 10, Gary Illyes clarified a recurring Search Console confusion: when Google canonicalizes a URL, other URLs in that duplicate cluster can become “alternate names.” Google may still show these alternate URLs in search results when a query calls for them, with the “site:” search operator as the clearest example. This means a hreflang URL marked “not indexed” in Search Console isn’t necessarily broken or wasted — it can still appear in results under specific query conditions.
Googlebot’s declared location doesn’t reflect where it actually crawls from
Reported August 14, Google has long stated its crawlers originate from Mountain View, California, but this is only a self-declared location. Google operates data centers worldwide, and a crawler that declares itself as Mountain View may actually be crawling from a different physical location entirely. Site owners using IP-based geolocation or firewall rules tied to Google’s stated California origin should treat that data as unreliable for verification purposes.
Cloudflare and CDN bot-protection settings can block Googlebot outright
A widely shared warning on August 13 pointed out that Cloudflare and similar CDN tools often include settings designed to block AI bots and rogue crawlers. If rankings drop suddenly with no corresponding Google update, the likely cause is a misconfigured rule that blocks Googlebot along with the bots it was meant to stop. This is a config check, not an algorithm problem, and it’s one site owners can verify and fix directly without waiting on Google.
AI Overviews begin showing AI-generated images, with early results called “not good”
On August 14, Search Engine Roundtable flagged that Google has started placing AI-generated images directly inside AI Overviews rather than sourced photos or illustrations. Early observations from the report describe the results as “not good,” though no broader quality data or percentage figures were available yet. This is a new surface worth monitoring, particularly for sites in visually driven niches where AI Overviews already reduce click-through to the original source.
What to do this week
Log into Search Console and check whether the Generative AI Performance tab has appeared under your main Performance report; if it has, pull data on which pages already surface in AI Overviews and AI Mode. While you’re in there, tools like ClickRank can complement that Search Console data by checking whether AI model crawlers can even access the pages you expect to surface in AI Overviews and AI Mode in the first place.
Open your Cloudflare or CDN dashboard and review bot-management and firewall rules for any setting that could be blocking Googlebot’s declared user-agent or IP ranges, especially if you’ve noticed unexplained ranking or traffic drops since early August.
Review any hreflang pages currently marked “not indexed” in Search Console and confirm whether they still appear for relevant “site:” searches before assuming they need fixing.
Hold off on reacting to ranking swings reported between August 1 and 6 as if they were a confirmed update — check Google’s Search Status Dashboard directly before making changes based on third-party volatility tools alone.
