Agent Skills · ZIP download

SEO Growth & Recovery Kit

Compare reporting periods and review redirects or migrations when organic search traffic changes.

$39One-time purchase · USD

You’ll review the offer on Whop before paying.

Cover of SEO Growth & Recovery Kit

What’s included

In the download

  • 14 task Skills and a shared router in one ZIP.
  • A playbook for baselines, reporting windows, traffic anomalies, refreshes and migration checks.
  • A public URL input example and an evidence log CSV for tracking findings and follow-up.

What you can produce

Capture a baseline, a comparison by reporting window and redirect checks that can guide follow-up.

What’s included
Use cases and outputs

How to use it

  1. Set a fair comparison

    Choose equal, complete windows that do not overlap. Match the source, property, filters and timezone, then record any missing rows.

  2. Trace changes back to pages

    Compare impressions, clicks and conversions separately. Open affected landing pages and redirect samples in Chrome to look for a reproducible explanation.

  3. Build a recovery queue

    For each suspected issue, record the evidence, owner, pass condition and recheck date. Repeat the page sample after the approved change.

Before you buy

Pick this edition if

  • SEO leads investigating a change in organic visibility, traffic or conversions after a release.
  • Migration teams reviewing redirect maps, affected landing pages and a recovery queue.

What you’ll need

  • Node.js 22 or later, Chrome, the affected URLs and a timeline of relevant content, release or migration changes.
  • Compatible baseline and follow-up exports, or a verified Google Search Console property with authorized access.

Account comparisons use supplied exports or a supported read-only Google path with verified scope. Differences between periods are observations. Attributing a change to a release needs corroborating evidence.

Questions

Which data should I have before investigating a drop?

Bring comparable periods from the same property, affected page URLs and a dated change timeline. Keep any known data gaps with the comparison.

Can I start before an analytics account is available?

Start with public landing pages, redirects and your release records. Add compatible exports or the authorized report when you have access.