wowprompt

Ranking drop check after a Google core update

Compares search traffic before and after a known update date, separates real update losses from seasonality, tracking errors and technical faults, and names the pages and query types that lost. Use it when traffic falls in the week of a confirmed search update and the team wants facts before rewriting anything.

A before-and-after table of clicks by page group, a list of other causes ruled in or out, the most affected pages and queries, and a recovery plan in order
The output this prompt produced, unedited.

The prompt

Fill in these first

  • Site and topic: [e.g. a personal finance blog with 600 articles]
  • Update name and rollout dates: [as announced, e.g. a core update from 2026-03-12 to 2026-03-28]
  • Clicks and impressions by page, before and after: [paste two equal periods of Search Console data, e.g. 28 days before the rollout and 28 days after it finished]
  • Same periods last year, if available: [paste, or none]
  • Query data for the biggest losers: [paste top queries per page, before and after]
  • Changes made on the site in the same weeks: [e.g. new theme, URL changes, content pruned, none]
  • Analytics or tracking changes: [e.g. consent banner added, none]

Task

Decide how much of the drop is caused by the update and where it hit, then plan a response.

Output format

  1. Verdict in three sentences: update-related, mixed, or other cause, with the numbers behind it.
  2. Other causes checked: seasonality, tracking, site changes, indexing, a single lost feature such as a rich result; each marked ruled out, possible or likely.
  3. | Page group | Clicks before | Clicks after | Change | Average position change |
  4. The ten pages that lost most, each with the queries lost and the type of page now ranking instead, if given.
  5. Recovery plan in order: what to improve on the losing pages, what to leave alone, and when to judge results.

Rules

  • Compare equal-length periods and wait until the rollout has finished before calling a verdict.
  • Never recommend mass deletion or rewriting every page; act on the evidence for specific pages.
  • Say clearly that recovery often shows only after a later update.
  • Use only the numbers pasted.
core updateranking dropgoogle algorithm updatetraffic loss analysisseo recoverysearch console comparison

How to run this

Copy the prompt and paste it into Gemini, then set the aspect ratio to 3:4. No reference photo is needed for this one.

The prompt is written in Markdown with each part under its own heading, which is what the copy action hands over. Change one section at a time, keeping the rest intact, so you can tell which change did the work.

Related prompts

All productivity