What is seo-weekly-report?

An SEO reporting workflow for Google Search Console, a Google service that shows how a site appears in search results.

It is for producing site summaries, comparing search performance, prioritizing SEO actions, and checking warnings or limitations in the results.

It combines current and previous 28-day performance with traffic drops, content opportunities, competing pages, and follow-up tasks in one weekly report.

seo-weekly-report — Skill for Claude Code by shutovdef-dotcom

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add shutovdef-dotcom/google-search-console-mcp --skill seo-weekly-report

Clone the repo

git clone --depth 1 https://github.com/shutovdef-dotcom/google-search-console-mcp

Made for: Claude Code.

Or install mcp-search-console, the plugin that ships this one along with the rest of its 4 skills, 1 MCP server.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/shutovdef-dotcom/google-search-console-mcp/seo-weekly-report/github.svg)](https://agentmods.dev/skills/shutovdef-dotcom/google-search-console-mcp/seo-weekly-report)

Your own site

<a href="https://agentmods.dev/skills/shutovdef-dotcom/google-search-console-mcp/seo-weekly-report"><img src="https://agentmods.dev/badge/skills/shutovdef-dotcom/google-search-console-mcp/seo-weekly-report/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/shutovdef-dotcom/google-search-console-mcp/seo-weekly-report"><img src="https://agentmods.dev/badge/skills/shutovdef-dotcom/google-search-console-mcp/seo-weekly-report.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 30 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 596 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00030	$0.00596
Opus 5	$0.00015	$0.00298
Sonnet 5	$0.00006	$0.00119
Haiku 4.5	$0.00003	$0.00060

Measured 10d ago against content hash e4b3b58699e6, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

seo-weekly-report scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 10d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/seo-weekly-report/SKILL.md · 40 lines

How it starts

The opening of the file, as written. The whole thing — 40 lines — stays where its author put it; the contents beside it link to each section on GitHub.

SEO Weekly Report

Generate a weekly SEO performance report for a Google Search Console property.

Steps

Call list_properties to confirm the exact site_url to use.
Prefer gsc_run_weekly_seo_ops_report for the report. It returns stable JSON with:
- schema_version="weekly_seo_ops_report.v1"
- performance_snapshot for current and previous 28-day periods
- top_actions combined from traffic-drop, content-opportunity, cannibalization, and manual follow-up sections
- traffic_drop_queue, content_action_queue, cannibalization_decision_queue, and manual_operator_checklist
- section-level warnings, limitations, provenance, and error
Use default dates unless the user provides explicit ranges. Defaults are the last 28 days ending today and the immediately preceding 28 days.
If gsc_run_weekly_seo_ops_report returns a section-level error, keep the successful sections and clearly label the failed section instead of discarding the whole report.
If the aggregator is unavailable, fall back to the older manual workflow:
- Call get_performance_overview with days=28.
- Call compare_search_periods comparing the last 28 days against the prior 28-day period, using dimensions=query and limit=20.
- Call get_search_analytics with dimensions=query and row_limit=100 or higher if available.
- Call gsc_get_manual_operator_checklist with focus=weekly.
- Sort returned query rows client-side by clicks descending and keep the top 10 queries.
Summarize the aggregator or fallback results in a structured report with:
- Overall performance snapshot (totals + period-over-period change)
- Prioritized operator actions with source section and confidence
- Traffic drop, content opportunity, and cannibalization queue summaries
- Manual Search Console follow-up checklist: UI paths, evidence to collect, and safe next actions
- Clear warnings, limitations, and partial-failure notes

Output format

Read the full file on GitHub · 40 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

10d ago First seen · 40 lines · 30 tokens per session scan A e4b3b58699e6

Subscribe to this mod's changes

seo-weekly-report is a skill published in the GitHub repository shutovdef-dotcom/google-search-console-mcp (0 stars, last pushed 2mo ago), licensed MIT. It adds 30 tokens to every session and 596 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-01.

Analytics and metrics Marketing and SEO

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens