Charleston SEO Recap: Google's Quiet Rewrites (Jul 20-26)

If your Friday felt strange and your Saturday felt worse, you were not imagining it. Google moved rankings hard on July 24, and as I write this on Sunday morning it has still logged absolutely nothing on its own status dashboard.

That is the shape of the entire week. Four real changes landed between July 20 and July 26, and Google announced almost none of them. One arrived as a weekend ranking shakeup nobody will confirm. One arrived as a single new line added to a documentation page. One arrived as a model swap buried in a developer blog post. One arrived as a requirement quietly deleted from a help doc. If you were waiting for a Google blog post to tell you what changed this week, you are still waiting.

Here are the four, ordered by how much they should actually cost you sleep.

First, Google shook the rankings on Friday and will not admit it

Barry Schwartz at Search Engine Roundtable called it Sunday morning: rumblings starting late Thursday July 23, kicking into high gear on Friday the 24th, and running straight through the weekend. His read is that Google kicked some of its ranking servers. The tracking tools agree. Mozcast, Semrush, AccuRanker, Sistrix, Algoroo, DataForSEO, AWR, and most of the rest of the board spiked around the 24th. The forum chatter matched, and it was ugly: site owners reporting traffic at a fraction of normal, one describing a global site cut to roughly a quarter of its usual numbers, another in Brazil reporting drops of 60 to 70 percent.

So I went and looked at the official record myself. The Google Search Status Dashboard lists every confirmed ranking update, and the newest entry under Ranking is still the June 2026 spam update, which started on June 24 and ran for two days and one hour. There is nothing at all logged for July. Not the July 18 and 19 movement I wrote about last week, not the July 11 blip before it, and not this one.

Two big unconfirmed swings in nine days, and the official history of Google Search says July was a quiet month.

Last week I told you not to react to weekend volatility, and I stand by that. One weekend of chop is noise. But something changes when it happens twice inside nine days, and it is not "start rewriting pages." It is "start writing it down." (I keep a stupidly simple text file per client with the date and one line about what moved. It has saved me from more bad decisions than any tool I pay for.)

At this point a lot of owners are thinking: "so I just sit here doing nothing while my phone stops ringing?" No. You do measurement instead of surgery. There is a real difference. Open Search Console, set the date range to the last 28 days, toggle the comparison to the previous 28, and look at two things: whether clicks dropped on your money pages specifically, and whether impressions dropped with them. If impressions held and clicks fell, that is usually the AI answer box eating your click, not a ranking loss. If both fell together on the same handful of pages, now you have something worth investigating. Anything less than a week of sustained decline is weather, not climate. Last week's recap has the longer version of that argument, and this week is the second data point for it.

Second, Google banned undisclosed incentivized reviews in your own markup

This is the one nobody is talking about and the one most likely to bite a Charleston service business.

On July 24, Google updated its review snippet structured data documentation. The page carries a "last updated 2026-07-24" stamp, and I read the change on Google's own developer site rather than taking anyone's word for it. There is a new guideline telling site owners not to include "fake or undisclosed incentivized reviews" on their page or in their structured data markup. Google spells out what it means by that: reviews that are not based on a genuine experience of the product or service, and reviews written in exchange for a benefit, such as money, a discount, a voucher, or a free product, where the incentive is not clearly and prominently disclosed.

Read that second half again, because that is the part that catches good people doing a normal thing. Google is not only talking about a competitor buying fake five-star reviews from a click farm. It is talking about "leave us a review and take $25 off your next service call." Plenty of honest Mount Pleasant and Summerville operators run some version of that. It is not automatically banned. It is banned when you feed those reviews into the star rating markup on your own website without disclosing that they were incentivized.

Two separate surfaces here, and people mix them up constantly. Your Google Business Profile reviews are governed by Google's review policies, which have prohibited review incentives for years. This new line is about the reviews and star ratings living on your own site, marked up in your own schema, that generate the little gold stars in the search result. That is your web developer's problem now, not just your front desk's.

So do this, in this order:

1. Ask whoever built your site whether it outputs Review or AggregateRating schema. Most WordPress review plugins and most "testimonials" widgets do it automatically.
2. If it does, find out where those reviews come from. Imported from Google? Typed in by hand? Collected through a form after a discount was offered?
3. If any of them came with an incentive attached, either disclose the incentive clearly on the page, or pull those specific reviews out of the markup.
4. Kill any testimonial on your site that nobody can trace to a real job. If your marketing person cannot name the customer and the invoice, it does not belong in structured data.

This one has teeth because rich result penalties are quiet. Google does not send a letter. Your stars simply stop showing, your listing shrinks, and your click rate drops while your ranking looks fine. That is the same slow bleed I described in the piece on why Angi outranks your Charleston contractor website: you do not lose the ranking, you lose the reason anyone clicks it.

Third, Google swapped a model inside Search and would not say exactly where

On July 21, Google announced Gemini 3.5 Flash-Lite and noted, almost in passing, that it is rolling out in Google Search. Robby Stein at Google said it follows instructions better and understands user intent better, so conversations flow more smoothly. The day after, Rajan Patel at Google was more specific and said it will be one of the models that Search queries get routed to, depending on the question, and that it is particularly good at understanding intent on conversational queries.

Nobody at Google has published a clean answer on whether that means AI Overviews, AI Mode, agentic search, or all three.

Here is my opinion, and you can absolutely disagree with it. A change in which model handles your customer's question is not an algorithm update in the way we have always used that phrase, and it will never appear on a status dashboard. But it can absolutely change which pages get pulled into an answer, because a different model reads the same page differently and decides differently about what is relevant. I am not claiming that is what moved rankings on July 24. I have no evidence for that and neither does anyone else. I am saying we now live in a world where the plumbing under Search can change on a Tuesday, get one sentence in a developer blog post, and never be logged anywhere the rest of us can check.

(This is also why I have gotten so boring about fundamentals. You cannot optimize for a model routing decision you cannot see. You can be the clearest, most complete, most obviously local answer to a Charleston question, and let whichever model shows up figure it out.)

Fourth, Google Ads quietly dropped its $50,000 gate on lead forms

Good news for once, and it is aimed squarely at businesses your size.

Lead form assets are the Google Ads feature that lets someone submit their name and number straight from the ad, without ever touching your website. Until this month, using them meant clearing a $50,000 lifetime spend bar or qualifying through a narrower reputation path. Search Engine Land spotted the documentation change on July 20, so I opened the Google Ads help page myself. The $50,000 requirement is gone. What is listed now is a good history of policy compliance, an account in an eligible vertical, a privacy policy, and reputable advertisers spending more than $1,000 per account, or more than $15,000 across accounts, subject to Advertiser verification.

For a West Ashley HVAC company spending two grand a month, that is the difference between a locked feature and an available one.

Two honest caveats before you get excited. Google announced nothing here, so it is possible this is a documentation cleanup that does not match what the interface actually lets you do. Go look in your own account before you build a plan around it. And second, form leads are colder than phone calls, always. If you turn these on and nobody calls the lead back within five minutes, you have bought yourself a list of strangers instead of a pipeline. That is not a Google problem, that is a front office problem, and it is the same one that decides whether the Local Services Ads move into Google Ads helps you or hurts you next month.

The backdrop nobody at Google will engage with

One more thing worth knowing, because it colors everything above. On July 17, Nick Fox at Google posted on LinkedIn that Google is sending "billions of clicks to websites every week" through AI features in Search alone, and that Search overall still sends billions of clicks daily. Liz Reid, the VP of Google Search, amplified it.

I believe the number is real in aggregate. I also think it is completely useless to you, because there is no way for a roofer on James Island to check it against their own numbers. Google's own AI performance reports in Search Console still do not break out clicks from AI features. So Google is asking us to accept a figure it will not let us audit, while independent studies keep finding click rates falling when an AI answer appears. That is not a conspiracy. It is just a bad measurement situation, and it means your own Search Console data and your own call log are the only numbers that mean anything right now. That is exactly what our Charleston SEO work is built around: your data, not the platform's press release.

What to prioritize this week

Ranked, because these are not equally urgent:

1. Audit your website's review markup. This is the only item with a real downside risk attached. Incentivized reviews inside your own structured data, undisclosed, now violate Google's stated guideline. Find out today whether your site outputs review schema and where those reviews came from.
2. Do not touch your rankings over the July 24 movement. Pull the 28 day Search Console comparison, note what actually moved, and wait for a full week of sustained decline before you change a page.
3. Check whether lead form assets are now available in your Google Ads account. Five minutes to look. If they are there and you can answer a lead in five minutes, test them on one campaign.
4. Start a one line volatility log. Date, what moved, what you did. Two unconfirmed updates in nine days means this is the new normal, and memory is a terrible substitute for notes.

The through-line of the week is simple and slightly grim: Google is making more changes and announcing fewer of them. The ranking swing was unconfirmed. The review rule was a documentation edit. The model swap got one sentence. The ads change got no announcement at all. Nobody is going to hand you a summary of what happened to your visibility, which is why I go read the actual dashboards and the actual docs every Sunday instead of waiting for one. That is how we work with our service business clients across the Lowcountry: keep the fundamentals boring and solid, keep your own records, and the weeks Google goes quiet stop being scary.