After Google's August Spam Update, Noindex the Repeated URL Pattern First (2026)

Google's Search Status Dashboard lists an August 2026 spam update that began on August 18 and ran for 2 days and 16 hours. The dashboard shows no recent crawling or indexing incident alongside it. 1 Search Engine Land reported that the rollout finished on August 21 and applied globally to all languages; Google described it as a normal spam update. 2

Two fresh r/SEO posts describe site owners dealing with large or repetitive page families around the same period. On August 20, a nutrition-app developer said the site had published about 4,500 food pages across five languages from one repeated template, then reported a month-long period with zero impressions and clicks. The developer said the pages were still returning HTTP 200, remained crawlable, had a noindex directive, and had been removed from the sitemap. 3

On August 19, another developer reported a fall from about 900 daily impressions and 50 clicks to about 100 impressions and almost no clicks. The post raised repetitive pages such as pdf to mp3 and txt to mp3, along with a sitemap containing public user-generated pages, as possible concerns. 4 These posts are practitioner reports. They support checking a matching URL family on your own site, while causation remains unproven for either site.

The one action: noindex the repeated URL pattern and remove it from the sitemap

Use this action when your site recently exposed a large URL family built from one repeated template and each page adds little distinct value for users. Possible examples include app database pages, automatically generated language variants, or pages that change only a file type or keyword while offering nearly the same experience. Google defines scaled content abuse as many pages created mainly to manipulate Search, with large amounts of unoriginal content that provide little or no user value. Google advises site owners to exclude such content from Search. 5

Apply the exclusion to the matching family, rather than to every page that lost traffic. noindex removes a page from Google Search after Googlebot crawls the page and sees the directive. Removing the same URLs from the sitemap keeps the sitemap focused on pages you consider important; sitemap removal by itself is not the deindexing signal. 6 7

Define the exact URL family. Use your URL inventory and Search Console's Performance report to identify the shared path, parameter, or generation rule. Sample several URLs from the family. Continue only when the pages use the repeated template and provide little distinct search value. Keep valuable pages outside the pattern.
Add one noindex directive to every matching page. For HTML pages, place this in the <head>:

   &lt;meta name=&quot;robots&quot; content=&quot;noindex&quot;&gt;

If the route is served through a response layer, return this header instead:

   X-Robots-Tag: noindex

Google documents the meta tag and the X-Robots-Tag response header as equivalent ways to supply noindex. If users still need the pages, keep them available with an HTTP 200 response while Google processes the directive. 6

Keep the URLs crawlable. Check robots.txt and remove any Disallow rule that covers the same family. Google cannot read a noindex directive on a URL that robots.txt blocks from crawling, and Google does not support noindex as a robots.txt rule. 6
Remove the same URLs from the XML sitemap. Delete the matching entries from the sitemap files you submit or reference. Leave the sitemap entries for valuable pages. Google uses a sitemap to discover pages and to understand which pages you consider important, so this cleanup keeps the excluded family out of that preferred list. 7
Verify one representative URL in Search Console. Open URL Inspection for a URL from the family and check the HTML or response that Google received. Confirm that the noindex directive is visible. Then monitor the Page indexing report for the corresponding noindex exclusion. Google documents both reports for testing the directive and monitoring pages from which Googlebot extracted it. 6

What to expect after the change

A representative URL has passed the check when all four conditions hold:

The URL still responds with HTTP 200 when the page remains useful to visitors.
The URL is reachable for Googlebot and is absent from any XML sitemap.
URL Inspection shows the noindex directive in the response Google received.
The Page indexing report moves the URL into a noindex exclusion state after Google recrawls it.

If the URL remains indexed, inspect the response again and check whether Google has recrawled the page since the change. Google says that a revisit can take months, depending on the page's importance, so the directive is a containment step that needs time to appear in Search Console. 6

Use this step only for a repeated, low-added-value URL pattern that matches the evidence on your site. A traffic drop alone does not identify that pattern, and the two Reddit reports do not establish a universal cause for August losses. The action gives Google a clear exclusion signal for the selected family; it does not promise instant recovery for unrelated pages.