Charleston SEO Recap: Gemini 4 Lands Mid-Update (Nov 9-15)
Google dropped Gemini 4 Hydrogen into Search on day three of the November core update, lost three days of AI impressions, and published a new traffic doc.
Google is six days into a core update it says will take about two weeks. On day three, it replaced the model that runs Search.
Both of those things are true at the same time, and the second one makes the first one almost impossible to read cleanly. If your calls are down in Mount Pleasant this week, there is now no honest way to tell whether it was the ranking update, the new model, or the fact that it rained Thursday. That is the week. Here is what actually happened, ranked by what it costs a business that lives off the phone ringing.
First, Gemini 4 Hydrogen is now running Search for everybody
Thursday, November 12, Robby Stein, VP of Product for Google Search, published the announcement on Google's own blog. Gemini 4 Hydrogen is in Search, and in his words, "Hydrogen is now available globally in Google Search for all users." Not a test, not a Labs opt-in, not AI Pro subscribers. Everyone, in every supported language, two days after a core update started.
The part that matters for a Charleston service business is buried in the middle. Google says Hydrogen's reasoning "supercharges our query fan-out technique," running "simultaneous queries across all the relevant subtopics," which connects searchers to "a broader range of helpful links than before."
Read that as a prediction about your traffic. Query fan-out means one typed question becomes a dozen invisible searches behind the scenes, and the answer gets assembled from whatever those dozen searches find. A broader range of links is Google telling you it intends to pull from more sites per answer, which cuts both ways: more chances to be included, smaller share of the click when you are.
I published a measurement last Tuesday on what the word "best" does to Charleston roofing results, where adding one modifier dropped local roofers from 7 of 9 results to 2 and handed the space to Yelp, Houzz and Expertise.com. Fan-out is the same dynamic with the engine turned up. The more subtopics Google splits your query into, the more of those subtopics get answered by a national directory page that covers all of them at once.
At this point a lot of people are thinking: "so AI is eating search, same story as last year." Not quite, and here is the odd part. The same week Google shipped its biggest model upgrade into Search, Glenn Gabe caught it testing the removal of the AI Mode tab from the search bar entirely, along with the Ask anything box inside AI Overviews. His post on Friday was blunt about how strange that is: "Are they really testing removing AI Mode." So Google is simultaneously making the AI answer better and quietly testing whether anybody needs the separate AI destination at all. (My read, and I will own it if I am wrong: AI Mode as a tab is dead within a year because the model is being absorbed into regular Search, which is exactly what Hydrogen just did.)
Second, the core update is still running, and nobody can tell you what it did
As of tonight, the November 2026 core update sits on Google's Search Status Dashboard with a start date of November 10 and no duration listed. Completed updates show their full runtime. This one does not, which means it is still going.
For context on the ladder it is climbing: March core update ran 12 days and 4 hours, May ran 11 days and 21 hours, and September's spam update ran 13 days and 16 hours. Two weeks from November 10 lands around November 24, three days before Black Friday.
Last Tuesday I wrote the day one version of this and the advice has not changed: do not touch the site, write down your baseline on paper, wait. What has changed is that the baseline comparison got messier, because Hydrogen shipped on November 12 and it is not part of the core update. When you sit down on November 25 to compare the week after against the week before, you will be measuring two changes with one ruler.
So add one line to whatever you wrote down: November 12, new model. If something moved on that date rather than on the 10th, it is probably a presentation change in how answers are assembled, not a ranking change in how your pages are judged.
Third, Search Console lost three days of AI impressions, and it had nothing to do with any of this
Google confirmed a bug in Search Console's data anomalies list, and the wording is verbatim: "A logging error caused a decrease in impressions on the Generative AI performance report in Search for data from November 9 - November 11, 2026."
Look at those dates. The core update started on the 10th, in the middle of the broken window. Every owner who opened Search Console this week, saw AI impressions fall off on November 9, and concluded the core update hammered them was looking at a logging error.
It affects data logging only. Nothing happened to your actual performance. But if you already emailed somebody about a drop on those three days, go un-email them, and if an agency has already pitched you a recovery retainer using that chart, I would ask them which dates the anomaly covers before you sign anything.
Fourth, Google finally documented how to find its own traffic in your logs
The same day Hydrogen shipped, Google Search Central published a new page called "Identify Google Search traffic in your web analytics or server logs." It is dry and it is the most practically useful thing published this week.
It spells out the Referer values Google Search actually sends: https://www.google.com/ or a local domain for web, and android-app://com.google.android.googlequicksearchbox/https/www.google.com for the Android app. It explains when that header comes through blank (private browsing, anti-fingerprinting, opening a result in a new tab in some browsers, jumping from a native search widget into a browser). And it gives four reasons your analytics will never match Search Console:
• Browser privacy settings, extensions, ad blockers or consent choices block the analytics script entirely • Client-side redirects overwrite the Referer with your own URL • Search Console counts a click when somebody selects the link, analytics counts a session only after the page finishes loading • Search Console reports organic clicks only, and never includes Google Ads clicks
That third one is why a slow page quietly loses you numbers that Search Console still counts. The gap between the two reports is partly your load time.
Here is the absence worth noticing: the doc lists no separate Referer value for AI Overviews or AI Mode. A visit sent by an AI answer arrives looking exactly like a plain organic visit. Anybody selling you a dashboard that claims to isolate your Google AI traffic by referrer is working from inference, not from a signal Google sends.
This is the same measurement discipline behind the piece I ran last week on the Search Console click spike that turned out to be bots, where clicks ran 2x to 6.5x normal at the start of November and almost none of them were people. Same lesson in a different hat. Know what the number is actually counting before you react to it. That is most of what digital marketing for a Charleston service business really is, under the reporting polish.
Fifth, Google Ads will now show you what it did not charge you for
Also on Thursday, Keerat Sharma, VP and GM of Ads Privacy and Safety, announced the Invalid Traffic Overview card, rolling out globally from the week of November 12. It shows two numbers: what Google filtered out before billing you, and the credits it issued after billing you.
Google's own line in the post: "So far in 2026, we've reduced advertiser exposure to invalid leads by an average of 30% through continuous system upgrades."
If you run Google Ads for a plumbing or HVAC company anywhere between West Ashley and Summerville, open it when it lands in your account. Not because the number is a scorecard (Google grading its own homework is still Google grading its own homework), but because it is the first time the invalid-click conversation has a figure attached that both sides can look at. Every service-business owner I talk to is convinced competitors click their ads. Now there is a line item for it.
Sixth, your Maps ranking moves twice as much as your Search ranking, daily
Friday, Synup published findings from a tracking project across 25,000 local searches each on Google Search and Google Maps, covering 250 business categories in the 100 largest US cities, between October 24 and November 11.
The headline number: Maps results changed 68% from one day to the next, on average. Search results changed 32%. Maps sat in a tight 65 to 70% band the whole time while Search swung more, peaking at 38% on November 6.
By category, Maps volatility ran from 44% for hospitals to 90% for fast food. On the Search side it ran from 18% for welding supply to 43% for digital marketing agencies. (Yes, my own category is near the top of the churn. I noticed.)
Niladri Sarkar, Synup's CMO, framed it the right way: "A ranking report tells you where one business stands. It doesn't tell you whether the whole market moved underneath it."
For a Charleston roofer or dentist, this is the most useful thing on this page. If you check your Maps position from your phone on James Island every morning and panic when it moves, stop. Two thirds of local map results change daily as a matter of course. A single position dropping on a single day is not a signal. Four weeks of a declining trend line is.
What to prioritize this week
Ranked. Do them in this order.
- Add "Nov 12, new model" to whatever baseline you wrote down last week, so your November 25 comparison knows there were two events, not one
- If you saw AI impressions drop in Search Console around November 9 to 11, ignore it. It was a logging error and Google has said so
- Still change nothing on the site until the core update finishes, somewhere around November 24
- Stop reacting to single-day Maps movement. Check it weekly, not daily, and only act on a trend
- If you run Google Ads, look for the new Invalid Traffic card on the Overview page and see what your real number is
The through-line this week is that Google made your measurement harder in four separate ways in six days, then published a help doc about measurement. I do not think that is cynical. I think it is a company that genuinely cannot tell you what its own search results will look like in March, shipping transparency about the plumbing because it cannot ship certainty about the outcome.
This is how we work with service businesses across the Lowcountry: fewer dashboards, a short list of things that actually move a phone call, and somebody reading Google's fine print on a Saturday night so you do not have to.