Skip to content
Technical SEO and Search Console

Prompt to Assess Damage from a Google Spam Update

After a Google update, you need to know which pages to fix first. This prompt ranks them by real impression loss, not by misleading percentages on small pages.

Works with
Claude
Input
A Search Console CSV comparing the period after the update to the period before it
Output
A table of the 10 hardest-hit pages, with impressions, clicks and position
Time
About 10 minutes

Full prompt to copy

I'm giving you a CSV file from GSC comparing August 18, 2026 to today against the previous period. I was hit by the August spam update and I need to know which pages to fix first.

Do the following:
• Rank every page by impression loss (biggest drops first)
• Flag every page that lost 30%+ of its impressions or clicks
• For the 10 pages with the biggest drop, list the URL, impressions lost, clicks lost, and change in average position
• Format it as a table I can work through row by row

What does the prompt do?

  • Ranks every page by impression loss
  • Flags pages that lost 30% or more of their impressions or clicks
  • Shows impressions, clicks and position change for the top 10 pages
  • Returns a table you can work through row by row

How do you use it?

  1. In Search Console: Performance, set the range from the update date and compare to the previous period of the same length
  2. Pages tab, export to CSV
  3. Upload to Claude with the prompt and update the relevant update date in it
Field tip: This prompt was written for the August 2026 update. For a different update, swap in the date and name, and it works the same way.
The full guideGoogle's August 2026 Spam Update: How to Check If You Were Hit and What to DoStep by step: how to prepare the input, what to do with the output, and when it won't work.

Want us to do this for you?

Our team runs these processes on client sites every week, as part of organic SEO services. We'll start with a review of your site.

Get a free site review

Last updated: October 14, 2026 · Written by the DigiAssets team

Skip to content