Charleston SEO Recap: The Data Broke (Oct 8-14)

Google finished the longest spam update it has ever logged on Thursday morning. That is the headline. The actual story of the week is that in the same seven days, almost every instrument you would use to measure what that update did to you stopped working.

Search Console fell more than 64 hours behind. The date picker in Search Console then broke outright. And two independent rank-tracking vendors published data showing that Google is now feeding deliberately wrong search results to the tools your rank report is built on.

So this is a week where the thing you most want to measure became the thing you cannot measure. Six changes, ordered by what they cost a Charleston business that answers a phone for a living.

First, the September spam update is actually finished

I read this off the Google Search Status Dashboard myself this morning rather than trusting anybody's write-up, because the number is the point.

September 2026 spam update: started 24 Sep 2026, duration 13 days, 16 hours. Barry Schwartz clocked the completion notice at 4:37am ET on Thursday October 8.

Now look at the rows underneath it on that same dashboard. August 2026 spam update: 2 days, 16 hours. June 2026 spam update: 2 days, 1 hour. March 2026 spam update: 19 hours, 30 minutes. This one ran more than five times as long as August's and roughly sixteen times as long as March's. It also ran longer than either core update Google shipped this year, which were 11 days 21 hours in May and 12 days 4 hours in March.

Ten days ago I wrote that the dashboard was still blank on that row and projected a finish around October 8. That is the one call I got right this month, and I want to be honest that it was arithmetic, not insight. Google told everybody up front it would take up to two weeks.

The second thing that happened on Thursday: Schwartz also reported a visible uptick in manual action penalties landing in Search Console, building over the previous few weeks and getting louder at the end of the rollout. Manual actions are not the algorithm. A human at Google looked at your site. If one is sitting in your Search Console right now, that is a completely different problem from a ranking dip and it has a completely different fix.

Here is my stance, and it is the same one I have held through three rollouts now: the update being over is not permission to start ripping things out. It is permission to start reading. Those are different activities and most people skip straight to the first one.

• Set Search Console to 28 days versus previous 28 days and read the Pages tab before the Queries tab • Check Security and Manual Actions first. Thirty seconds. Rule it out before you theorize • Your before-and-after comparison needs a clean window now, so anything you change this week pollutes the data you are about to read • Hold deploys and migrations through the end of the month if you can

Second, your rank report is partly fiction right now

This is the one I would actually plan around, and almost nobody outside the SEO industry is talking about it.

Since mid September, Google has been fighting scrapers harder than it has in years, and it is doing it three ways at once: very wide IP blocking aimed at residential proxy networks, a sharp increase in captchas, and the nasty one, injecting fabricated results into search pages it suspects are being scraped.

That third tactic is the problem. Derek Perkins at Nozzle described what comes back as "complete, normal-looking pages whose results have been swapped out. Nothing on the page gives it away."

The numbers Nozzle published: 8.0% of the search results pages it collected came back poisoned from September 13 onward, against 0.17% in the weeks before that. It peaked at 27.0% on September 29. Since October 1 it has been running roughly 5 to 11% a day. Separately, DemandSphere reported on October 7 that about 11% of its daily checks were coming back spurious. Two vendors, separate data sets, same mechanism, same rough scale.

Sistrix, DataForSEO, SE Ranking, Advanced Web Ranking and Morningscore have all posted about the collection problems. Google has not commented on any of it.

At this point a lot of people are thinking: "so you are telling me the rank report my agency sends me is made up." Not made up. Sampled, and roughly one in ten of those samples is currently a lie that looks exactly like the truth. Which is worse in one specific way: you cannot spot the bad rows. There is no error flag, no gap, no obviously weird number. A poisoned result page renders as a totally normal page 4 where you used to be page 2.

What I actually do about this, and what I would push any Charleston agency you work with to do: stop treating a tool number as the measurement. Nine days ago I logged the same block of Charleston queries by hand and found five of nine page one results had turned over in seven days. That manual check has its own flaw (it is a sample of one person, one location, one moment), but it has the virtue of being a thing I actually saw.

• Treat Search Console clicks and impressions as your primary ranking evidence this month, not third-party position data • If a rank report shows a sudden cliff on a few keywords and Search Console clicks did not move, assume the tool before you assume the drop • Check your own money terms manually, signed out, in an incognito window, once a week, and write the number down • Ask whoever runs your SEO whether they know this is happening. The answer tells you a lot

Third, Search Console went dark in the exact week you needed it

Sunday the 11th into Monday the 12th, the Search Console performance report fell more than 64 hours behind. That report normally refreshes within hours. Google confirmed the latency publicly and said "We're working to solve this soon and will update here when the issues are resolved. We apologize for the inconvenience." It was mostly caught up by late Monday.

Then on Tuesday the 13th the custom date picker broke, with the end date stuck displaying "Date can't be after 1969-12-31." (A Unix epoch date showing up in 2026, in the one free tool every site owner on earth uses to read their own traffic. I laughed, then I stopped laughing.)

Why this matters: a 64 hour lag in the first week of October looks exactly like a traffic collapse. Open the report, see a cliff at the right edge of the chart, and the natural conclusion for an owner who just watched a two week spam update finish is that the update ate them. A few people are going to make permanent changes to a site this week based on a chart that was simply not finished loading.

If your clicks line falls off a cliff in the most recent two or three days, that is almost always reporting lag, not reality.

Fourth, AI Overviews now answer questions that have no answer

Google is now generating AI Overviews for queries where Search finds no matching pages at all, and for queries it thinks are typos. The reporting on this landed Monday and Tuesday. On genuine keyboard mash, the Overview comes back with something like "It looks like your message might have been a typo or random keyboard input."

I ran into the local version of this myself and wrote it up this morning: a Charleston plumbing query with zero matching pages, where Google skipped the empty results page and wrote its own answer naming three local plumbers with call buttons.

Sit with what that means for a second. The old mental model of local SEO was that you compete for a slot by having the better page. In the no-results case there is no page to be better than. Google assembles an answer out of Business Profiles, Maps data and whatever third party chatter it trusts, and your website is not in the loop at all. Your profile is the document.

That is also the through-line with the other thing I published today, where a Meta AI page built out of Facebook group chatter took the number one organic result for "local seo charleston sc". Different platform, same shape: the thing being surfaced is not a web page anyone optimized.

Fifth, restaurants got four new dietary attributes

Tuesday, Google expanded the dietary attributes available on Business Profiles for restaurants. Gluten-free, dairy-free, halal and kosher now sit alongside the vegetarian and vegan tags that were already there. Lisa Landsman from Google announced it on LinkedIn, calling it "Great news for local restaurants" and framing it as removing friction for diners who currently have to plan around their restrictions.

You set them per menu item: Business Profile, Edit menu, pick the item, check the badges. When somebody searches "gluten free dinner near me" on Maps or in Search, the tagged dishes surface on your profile.

For a Charleston restaurant this is twenty minutes of work with an unusually clean payoff, and I would do it this week specifically because it is one of the only things on this list that is both measurable and entirely within your control. King Street, Sullivan's Island, Mount Pleasant, every one of these rooms has a celiac table in it on a Friday night. We tag menu items as part of profile work for our restaurant clients in the Lowcountry, and the pattern I keep seeing is that the attributes nobody fills in are the ones with the least competition attached to them.

Sixth, Google is making forum content land faster

On Friday Google detailed a UGC Fresh Data Program, which lets platforms like Reddit push fresh user-generated content into Search faster than normal crawling would allow.

Nothing for you to do here. I am flagging it because it is the supply side of the thing in section four. Google and the AI search products are leaning harder on forum and social chatter as source material at the same time as they are making web pages less visible. If the Charleston subreddit thread about plumbers gets indexed in minutes instead of days, that thread is a ranking surface whether or not you ever post in it.

What to prioritize this week

Ranked, and the first one takes under a minute.

1. Check Manual Actions in Search Console. If there is one, nothing else on this list matters until it is resolved.
2. Ignore the last three days of your clicks chart. The reporting lag this week was real and it looks identical to a traffic collapse.
3. Pull a clean 28 day versus previous 28 day comparison now that the update is complete, and read the Pages tab first. Write down where you are before you touch anything.
4. Stop making decisions off third-party rank data this month. Roughly one in ten of those results is currently fabricated by Google on purpose, and you cannot tell which.
5. Restaurants: tag your dietary attributes. Twenty minutes, Monday morning, done.

One more thing worth saying out loud. The industry spent this week arguing about an algorithm update while the far bigger story was that the measurement layer underneath all of us quietly fell apart. If you take one idea out of this recap, make it that one: knowing which of your numbers you can trust is now a real skill, and this month it is worth more than knowing what the update did.

This is the part of the job we spend most of our time on with service businesses in the Lowcountry, and weeks like this one are exactly why.