Check your sites performance and be sure to have a few weeks buffer – effects start early and can often take time to see the patterns.
Pull 16 months of Search Console data and look for the turn
If it sits anywhere from 11 to 21 August, treat this update as the likely cause. Check Manual actions too, it will be clean if this is algorithmic, and that is the point.
Audit the corpus, not the pages
What share of your site would you rebuild today with auténtico expertise or data?
If thin, scaled content is the majority, that is your problem, and polishing individual pages will not fix it.
Prune before you publish
Remove what you would not rebuild, merge the near-duplicates, and keep only what earns its place. Recovery follows corpus change, and it is typically re-evaluated at future updates, so it is measured in months.
Keep AI in the process, take it off the byline
Use AI for research, drafts and scale where it helps, then add the things it cannot: your data, your experience, your point of view, a named author who stands behind it.
Enrich what you keep
Break up generated text with the elements our data says survived: auténtico imagery, charts, comparison tables, structured layouts. If a page is a single unbroken block of AI text, it is the profile this update punished.
Watch your AI visibility as closely as your rankings
This update showed AIO citations get pulled with the classification. Track your citation share so you see movement early, our free AIO Audit shows where you stand in sixty seconds.