Google September 2026 Core Update? What Actually Changed for E-commerce Stores

Was there a Google September 2026 core update? Google's dashboard lists a spam update, not a core update. What changed, how to read Search Console for a store, and what to do and not do now.

If you have searched for the Google September 2026 core update because your store's organic traffic moved last month, the first thing to know is that, according to Google's own records, there was no September 2026 core update. Google's Search Status Dashboard, which is where Google announces every confirmed ranking update, lists a September 2026 spam update that began on 24 September, but no core update in September. The last confirmed core update was the May 2026 core update. This post explains what Google did confirm, why so many people believe a core update happened, how an online store should read its Search Console data right now, and what to do and not do while the spam update finishes.

We wrote this because we have seen the claim of a September core update, running roughly from 12 to 26 September, repeated in several places. We checked it against Google's dashboard and could not verify it, so we are not going to treat it as fact. Getting this right matters for a store owner: the response to a core update and the response to a spam update are different, and the wrong diagnosis leads to the wrong fix.

What Google actually confirmed in 2026

Google's Search Status Dashboard keeps a history of ranking incidents. When we checked it on 3 October 2026, it showed the following updates for this year, with the durations Google recorded:

• February 2026 Discover update: began 5 February, recorded duration of 21 days and 17 hours. This affected Discover, not regular search results.
• March 2026 spam update: began 24 March, finished in 19 hours and 30 minutes.
• March 2026 core update: began 27 March, finished in 12 days and 4 hours.
• May 2026 core update: began 21 May, finished in 11 days and 21 hours.
• June 2026 spam update: began 24 June, finished in 2 days and 1 hour.
• August 2026 spam update: began 18 August, finished in 2 days and 16 hours.
• September 2026 spam update: began 24 September at 9:15 am Pacific time. Google said it applies globally and to all languages and that the rollout may take up to two weeks. When we checked on 3 October, the dashboard had not marked it complete.

So 2026 has had two confirmed core updates, in March and May, and four confirmed spam updates. SEO trade press coverage in early September noted that Google had announced no September core update, and nothing on the dashboard has changed that since. If a core update is announced later this year, it will appear on the same dashboard, and the guidance below on reading your data will still apply.

Why people think there was a Google September 2026 core update

There are understandable reasons for the confusion. Rankings move every day, and third-party tools that track ranking volatility often show spikes that look like an update. Google also makes many smaller changes that it does not announce. Google's own documentation on core updates says that smaller, unannounced updates happen continuously between the big ones. A store can see a real change in traffic without any named update being responsible.

The September spam update adds to the noise. Google said it could take up to two weeks to roll out, which is longer than the earlier 2026 spam updates. Search Engine Roundtable reported that some site owners saw large drops on 30 September and that several volatility trackers spiked that day, and suggested it may have been a second wave of the spam update. That is an observation from the SEO community, not something Google has confirmed, but it is a reminder that a two-week rollout can produce effects on more than one day.

Finally, for Indian stores in particular, late September and October are a time of strong seasonal change. Search demand for festive categories rises ahead of Navratri and Diwali, and demand for other categories can fall as shoppers move to the marketplace sales. A drop or rise in that period can easily be seasonal rather than algorithmic.

What the September 2026 spam update targets

Google has not said whether the September 2026 spam update targets a specific policy or tactic. What we do know is how Google describes spam updates in general. Its documentation says they are notable improvements to its automated spam detection systems, including SpamBrain, which it describes as an AI-based spam-prevention system. Sites that violate Google's spam policies may rank lower or not appear in results at all.

Google's spam policies are public. Several of them are especially relevant to online stores, because they describe tactics that have been popular in e-commerce SEO:

• Scaled content abuse: generating many pages primarily to manipulate rankings rather than to help users. For a store, this looks like hundreds of near-empty collection pages or blog posts generated for every keyword combination, whether written by people or by AI.
• Doorway abuse: pages or sites created to rank for specific queries that funnel users elsewhere rather than being useful destinations in their own right, such as one thin page per city that all say the same thing.
• Keyword stuffing: filling a page with keywords or numbers in an attempt to manipulate rankings. Long lists of keywords in collection descriptions or footers are a common example.
• Hidden text and links: content placed to manipulate search engines and not easily visible to visitors, such as text hidden behind a tab of the same colour as the background.
• Link spam: links created primarily to manipulate rankings, including bought links and large-scale link exchanges.
• Site reputation abuse: hosting third-party content mainly to benefit from the host site's ranking signals. Some stores have rented out sections of their site for this.
• Thin affiliation and scraping: copied descriptions or republished content without original value added.
• Hacked content and user-generated spam: content placed on a site through a security hole, or spam posted through public features such as reviews or comment sections.

If your store does none of these, a spam update should not affect you directly, although Google acknowledges that any update can have side effects. If it does some of them, the September update is a good reason to stop.

Core update versus spam update: why the diagnosis matters

Google treats these as different kinds of change, and the right response differs.

A core update, according to Google's documentation, is a broad change to how its systems assess content overall. It does not target specific sites or tactics. Google's advice for a site that loses traffic in a core update is to assess whether its content is helpful, reliable and made for people, and to make lasting improvements rather than quick fixes. Google is explicit that a drop in a core update does not necessarily mean anything is wrong with a page; other content may simply have been judged more relevant.

A spam update is about policy violations. Google's advice for a site affected by a spam update is to review its spam policies and fix anything that violates them. Its documentation says changes may help a site improve if Google's automated systems learn over a period of months that the site complies. For link spam specifically, Google says that when its systems neutralise spammy links, any ranking benefit those links produced is lost and cannot be regained.

If you assume a core update when the cause was a spam signal, you may spend months rewriting good content while the actual problem, perhaps a set of bought links or a hidden block of keywords, stays in place. If you assume spam when the cause was a broad quality reassessment, you may tear out pages that were fine. Start with the dates, then the evidence.

How to read Search Console after a Google update

Google's documentation for core updates sets out a sensible method, and it works for any confirmed update. Here it is, adapted for an online store.

1. 1Wait until the update is complete. Check the Search Status Dashboard. Google advises waiting at least a week after an update finishes before analysing the data, so for the September spam update, look in mid-October at the earliest.
2. 2Compare like with like. In Search Console's Performance report, compare the week after the update with the week before it started. Use the same days of the week in both periods.
3. 3Check year-on-year too. Search Console keeps 16 months of data, so compare against the same weeks last year. For Indian stores, remember Diwali fell on a different date in 2025, so align by festival as well as by date.
4. 4Look at average position, not just clicks. Google's own example is the difference between a page moving from position 2 to 4, which is small, and one moving from 4 to 29, which is large. Small moves call for small responses.
5. 5Break the drop down by page type, query, country and device before drawing any conclusion.

Segmenting a Shopify store's Search Console data

Shopify stores have predictable URL patterns, which makes segmenting easy. In the Performance report, add a page filter with 'URL contains' and use these patterns one at a time:

• /collections/ for collection pages. These usually carry the broad category queries, such as 'gold earrings' or 'cotton kurtas for women', and are often a store's most valuable organic pages.
• /products/ for product pages, which tend to catch more specific queries and product names.
• /blogs/ for articles. If a store's losses are concentrated here, ask whether the content was written to help readers or to catch keywords.
• /pages/ for static pages such as size guides, store locators and about pages.

Then look at the pattern. If losses are spread evenly across every page type, the cause may be site-wide, which points towards seasonality, a technical problem or a broad quality assessment. If losses are concentrated in one group, such as a batch of auto-generated blog posts or a set of near-duplicate collection pages, that group is where to look first.

Also check the Queries tab. A store that loses impressions on brand queries has a different problem from one that loses impressions on generic category queries. Brand query losses usually point to demand, reputation or a technical issue rather than an algorithm update.

Cross-check with your Shopify analytics

Search Console tells you about impressions, clicks and positions in Google. It does not tell you whether those visitors bought anything. For that, compare it with Shopify's own analytics, which count online store sessions and the sessions that went on to add to cart, reach checkout and complete checkout.

Shopify's analytics can break sessions down by referrer and by landing page. If Search Console shows clicks to your collection pages falling by a fifth, but Shopify shows sessions from Google landing on collection pages holding steady, the gap may be in measurement rather than in traffic. If both fall together, the drop is real. If clicks hold steady but orders from those sessions fall, the problem is not search at all: it is what happens on the page after the visitor arrives.

That last case is more common than people expect in festive season. Traffic arrives, finds a collection that opens with sold-out or off-season products, and leaves. No algorithm update caused that, and no SEO fix will cure it. A short ShopifyQL query on the sessions dataset, grouped by landing page type and filtered to Google as the referrer, will show conversion rate by landing page type for the same weeks you are comparing in Search Console.

Keep both views side by side for the next month. The spam update will finish, the festive peak will pass, and you will have a clean record of what changed in search and what changed on your store, which is exactly what you need to make the next decision calmly.

Rule out the boring causes first

In our experience, many supposed algorithm hits on online stores turn out to have ordinary causes. Before you read anything into an update, check these:

• Manual actions. Search Console's Manual actions report shows whether a human reviewer at Google has taken action against the site. That is different from an algorithmic update and has its own process.
• Security issues. The Security issues report flags hacked content, which can cause sudden drops and is covered by Google's spam policies.
• Indexing. The Page indexing report shows whether important pages have dropped out of the index, for example because of an accidental noindex tag, a robots.txt change or a theme update.
• Site changes. Did anyone change the theme, URLs, collection handles, navigation or redirects in September? A renamed collection without a redirect loses its rankings regardless of any update.
• Stock and availability. Products that went out of stock or were archived lose visibility naturally. A collection that is mostly sold out is less useful to searchers.
• Tracking. If your concern comes from analytics rather than Search Console, check that tracking is still working. Changes to Shopify's Thank you and Order status pages in August broke some stores' conversion tracking, which can look like a traffic or sales drop.

What to do now

With the September spam update still rolling out when we wrote this, here is a sensible list of actions for an online store.

1. 1Write down the dates. Note 24 September as the start of the spam update and 30 September as a day of reported volatility, and add any changes you made to the store in the same period.
2. 2Audit against the spam policies honestly. Look for keyword-stuffed collection descriptions, hidden text, bought links, thin doorway pages and sections of the site hosting third-party content you do not control.
3. 3Fix genuine violations properly. Remove hidden text, rewrite stuffed descriptions for people, and stop any link buying. Expect recovery to take months, as Google says.
4. 4Strengthen your collection pages. Give your main collections a short, useful introduction, clear filters and a product order that puts in-stock, relevant products first. These are the pages that answer category searches.
5. 5Improve product pages where they are thin. Original descriptions, real photographs, sizing information, delivery and returns details, and genuine reviews make a page more useful to people and more defensible in any update.
6. 6Wait for the update to complete, then analyse with the method above.

What not to do

• Do not delete large parts of the site in a panic. Google's documentation calls removing content a last resort, and deleting pages that earned traffic for years is hard to undo.
• Do not rewrite everything at once. If you change hundreds of pages in a week, you will not know which change helped or hurt.
• Do not change URLs during the festive season. Redirects work, but a URL migration in October adds risk at exactly the wrong time.
• Do not buy a recovery service that promises to reverse an update quickly. Google says recovery from a spam update depends on its systems learning over months that a site complies.
• Do not mass-produce pages with AI to win back traffic. Generating many pages primarily for rankings is the definition of scaled content abuse in Google's policies.
• Do not assume a core update caused your drop. As of 3 October 2026, Google had confirmed no September core update.

Why collection pages carry most of the weight

For most online stores, collection pages are the ones that rank for the broad searches that bring new customers: the category, the material, the occasion. They are also the pages most often neglected. Many stores have collection pages with no introduction, a filter set nobody configured and products in whatever order they happened to be added.

Search engines want to send people to pages that satisfy the search. A collection page that opens with sold-out products, or with products that have nothing to do with the query, is a weaker answer than one that opens with relevant, available products. Google does not publish how it weighs any of this, so we will not claim that product order is a ranking factor. What we can say is that a collection page which serves the shopper better is a better page by Google's own description of what it is trying to reward, and it converts the traffic you do get.

That is the part of the problem our app SellRank works on. It ranks the products in a Shopify collection by real performance, such as views, add-to-carts, orders, revenue or conversion rate, can keep out-of-stock products off the first rows using conditions, and writes the result into Shopify's own manual sort. The page's HTML is complete when it loads, with no JavaScript layer reordering products, so crawlers see what shoppers see.

The longer view

Two confirmed core updates and four spam updates by the end of September is a busy year, and there may be more before it ends. The stores that come through these updates best tend to do the same unglamorous things: original product information, useful collection pages, clean technical foundations, honest links and patience. None of that depends on predicting the next update.

Keep a simple change log for your store. Every time you change a theme, a URL, a collection structure or a large batch of content, write the date and what changed. When the next update arrives, real or rumoured, you will be able to separate your own changes from Google's in minutes rather than days.

Get help reading your data

If your store's search traffic changed in September and you want a second pair of eyes on the data before you change anything, get in touch through our contact page. We will look at the dates, the page types and the technical basics with you, and tell you plainly whether the cause looks like Google, the season or something on the site. If your collection pages are the weak spot, SellRank's free plan lets you set a performance-based order on one collection and see the result on your own store.