Build a weekly SEO health report with Claude

The scenario

Your Monday SEO check is currently: open Search Console, scroll through the last 7 days; open GA4, scroll through landing pages; open PageSpeed Insights, plug in a URL; copy-paste into a Notion page; tag the team. It takes 45 minutes and you do it because nobody else will. You want one prompt that does it for you in under five minutes of chat.

The prompt

Use the gsc-pap MCP. Build my weekly SEO health report for https://example.com (GA4 property properties/302550400). Cover the last 7 days vs prior 7 days. Sections: (1) Headline numbers, clicks/impressions/avg-pos delta via compare_periods. (2) Quick wins this week via find_quick_wins, top 5. (3) Content decay alerts via find_content_decay, anything down >25% WoW. (4) Top 5 queries with biggest position shift via historical_position_trend. (5) GA4 conversions by source for the same window via ga4_conversions_by_source, focus on Organic Search. (6) Any CWV regressions on the top 5 organic pages via pagespeed_insights mobile. Format as a Notion-friendly markdown report with H2 sections and tables.

What happens

1. 1

   AI fans out the tool calls in parallel where possible

   Claude / Cursor recognise this is a multi-tool prompt and parallelise the GSC + GA4 + PSI calls, compare_periods + find_quick_wins + find_content_decay + ga4_conversions_by_source can all start at the same time. PSI calls are sequential because each one is slow, but cached after the first run.

2. 2

   AI assembles the report markdown

   Each section becomes an H2 with a summary sentence + a markdown table. The AI captures dates, delta percentages, and exact URLs / queries so the report is actionable without flipping back to a tool.

3. 3

   Save the prompt as a reusable command

   In Claude Code: `claude --resume "weekly seo report"`. In Cursor: save as a custom slash command. In Claude Desktop: pin the project. Next Monday it runs in under five minutes with zero edits.

Outcome

A 45-minute manual ritual becomes a 5-minute chat. The first run reveals 1-2 things you'd been missing weekly (a quietly-decaying page, a CWV regression on a top product page). After that it becomes the team's source-of-truth weekly digest, paste into Slack or Notion and move on.

Where to take it next

• ·Add a Q4 / monthly variant that uses 28 days vs prior 28, same prompt, different windows.
• ·Schedule via Claude Code's automation if it ships scheduled runs.
• ·Add a brand-monitoring section if you have specific brand queries to track.