Google’s August spam update and the entity playbook I’d run now

Google’s August spam update is on everyone’s radar. SEO Fight Club just streamed “Google August Spam Update and Mastering AI Search Visibility w/ Entity-Based SEO,” and it’s worth your time because it hits the only lever that compounds after updates: clean entity signals and provenance. I’ll translate that into what to harden this week and what to build next quarter. 🎯

If you want the source, here’s the video: Google August Spam Update and Mastering AI Search Visibility w/ Entity-Based SEO - SEO Fight Club. The frame is sensible: reduce spam risk, strengthen entities, and measure AI visibility — not just blue links.

What this spam update likely targets (and how I’d interpret it)

I don’t speculate beyond patterns Google has penalized for years. When SEOs report a “spam update,” I assume pressure on:

• Scaled, indistinct pages that read like interchangeable templates. 🧪
• Parasite/hosted pages that borrow trust but add no value. 🧹
• Repurposed expired domains and inorganic link patterns. 🔗

Could there be collateral damage? Yes — especially sites with ambiguous ownership, weak bylines, or mismatched topical footprints. The fix isn’t a “trick.” It’s clarity: who you are, what you cover, how each page earns its keep.

Entity-based SEO is how you harden and grow

If AI answers and classic SERPs are both adjudicating on entities, then your job is to make your entity graph unambiguous. Here’s the stack I’d run, in order.

1. 01
   Inventory the entity surface

   Map people, org, product/service, location, and core topics to specific URLs.

2. 02
   Consolidate and canonize

   Merge duplicative topics, set canonicals, and choose one bio/home for each entity.

3. 03
   Declare with schema

   Add Organization, Person, Product/Service, LocalBusiness, and Article schema with sameAs links.

4. 04
   Prove authorship and provenance

   Real bylines, author bios, profile links, and change logs on significant pages.

5. 05
   Connect the graph

   Internal links that state relationships (who does what, where, and for whom) in plain language.

6. 06
   Align off-page signals

   Update social, business listings, and links so names, addresses, and topics actually match.

Why this order? Because Google can’t trust what it can’t disambiguate, and AI systems are even more brittle with fuzzy entities. Clean structure beats clever tactics.

If you need help sizing the gap, run your site through the AI Visibility Checker to see how often you appear in AI answers, then spot markup gaps with the Schema Opportunity Analyzer. For deeper instrumentation work, my notes here align with that direction: Relevance engineering in AI search: my playbook after Mike King’s chat with Sean.

Quick triage: what to check this week

Here’s how I’d spend 2–4 focused hours before making bigger moves:

• Crawl + segment: identify thin/near-duplicate clusters; deindex or consolidate the junk. 🚨
• Authors: add missing bylines and bios; link bios to external profiles with consistent names.
• Parasite clean-up: audit third‑party hosted pages using your brand; prune anything not delivering value.
• Links: no knee‑jerk disavows; instead, spot obvious inorganic patterns tied to recent pushes and pause them.
• Local entities: ensure NAP, categories, and services align across GMB and top citations if you’re location-bound. 🛰️

Measuring AI search visibility, not just rankings

If traffic moved, don’t stare only at average position. Track:

• Share of mentions and answer inclusion in AI overviews and assistants (brand + non‑brand).
• Coverage across your entity set: which products/locations/authors show up, where, and how often.
• Answer quality: when you are cited, is the snippet on-message and up-to-date? 📈

This is where the AI Visibility Checker earns its keep. Use it to baseline, then re-run after each structural change.

Schema, provenance, and page-level clarity

• Add Organization and Person schema with sameAs to official profiles. Keep names and spellings identical.
• Articles: headline matches title tag, one primary H1, clear author, and date with a short update note for edits.
• Services/Products: unique value prop, specs, and how-to/use context. Don’t just list features — show outcomes.
• Local pages: service-in-city pages need distinct proof (case studies, photos, staff, directions) or they’re liabilities.

What not to do

• Don’t carpet-bomb disavow files. If you can’t tie links to a tactic you controlled, wait and watch.
• Don’t spin up more pages to “replace losses.” Consolidate, strengthen, then expand deliberately.
• Don’t outsource your entity to marketplaces/directories; keep canonical bios and descriptions on your domain.

Conclusion

Spam updates raise the cost of ambiguity. Entity work lowers it. If you do nothing else this quarter, stabilize your entity graph, retire thin clusters, and prove who wrote what and why it matters. That combination is boring in the best way: it survives updates and compounds in AI surfaces because machines can quote, attribute, and connect it without guessing.

Takeaway: treat every update as a governance test. Clean entities, clean markup, clean relationships — that’s the operating system for durable SEO, local relevance, and AI visibility.