What is page-deep-dive?

A complete report for one web address, covering Google indexing, search performance, page content, loading experience, and search terms.

Use it to inspect a page’s indexing status, review clicks and rankings, check Core Web Vitals, assess page health, and see which searches bring visitors.

It combines the main checks needed to understand why a particular page may be underperforming in Google Search.

How FlorianBruniaux/google-search-console-mcp configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to FlorianBruniaux/google-search-console-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/FlorianBruniaux/google-search-console-mcp/main/.claude/skills/page-deep-dive/SKILL.md

Clone the repo

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

Made for: Claude Code.

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/florianbruniaux/google-search-console-mcp/page-deep-dive/github.svg)](https://agentmods.dev/skills/florianbruniaux/google-search-console-mcp/page-deep-dive)

Your own site

<a href="https://agentmods.dev/skills/florianbruniaux/google-search-console-mcp/page-deep-dive"><img src="https://agentmods.dev/badge/skills/florianbruniaux/google-search-console-mcp/page-deep-dive/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/florianbruniaux/google-search-console-mcp/page-deep-dive"><img src="https://agentmods.dev/badge/skills/florianbruniaux/google-search-console-mcp/page-deep-dive.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 469 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.00101	$0.00469
Opus 5	$0.00051	$0.00234
Sonnet 5	$0.00020	$0.00094
Haiku 4.5	$0.00010	$0.00047

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

Security

Grade A, and why

page-deep-dive 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 11d 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.

.claude/skills/page-deep-dive/SKILL.md · 45 lines

What it actually says

Page Deep Dive

Complete analysis of a single page: indexing, performance, Core Web Vitals, and content signals in one pass.

Input

Requires a specific page_url from the user before starting.

Steps

Call list_properties to confirm the site_url.
Call inspect_url with the target URL to get its indexing status, canonical URL, robots.txt compliance, and last crawl date.
Call page_analysis on the same URL for on-page content signals and quality assessment.
Call page_health_score to get a composite health score with a breakdown by category.
Call crux_page_vitals to get real-user Core Web Vitals (LCP, INP, CLS) for that URL from the Chrome User Experience Report.
Call get_search_by_page_query to get all queries driving traffic to that page, sorted by clicks over the last 28 days.

Output format

Indexing status: indexed / not indexed / issues, with the specific reason if not indexed.

Performance snapshot: clicks, impressions, avg CTR, avg position over 28 days.

Top queries driving traffic: Query | Clicks | Impressions | CTR | Position

Core Web Vitals: LCP | INP | CLS | Overall status (Good / Needs improvement / Poor)

Health score: numeric score plus a breakdown by category.

Action list sorted by priority:

Critical: indexing or crawl issues to fix immediately
High: Core Web Vitals failing thresholds
Medium: content or on-page optimization opportunities from page_analysis
Low: internal linking or schema enhancements

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.

11d ago First seen · 45 lines · 101 tokens per session scan A cbec6a33f1e1

Subscribe to this mod's changes

page-deep-dive is a skill published in the GitHub repository FlorianBruniaux/google-search-console-mcp (10 stars, last pushed 10d ago), licensed MIT. It adds 101 tokens to every session and 469 once invoked, about $0.0005 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-08-31.

Debugging Research fastmcp google-analytics google-search-console indexing-api mcp

traffic-diagnosis

Systematically diagnose why traffic changed — spike, drop, or shift in mix. Follow these steps in order. Each step narrows the hypothesis.

surendranb/google-analytics-mcp · 34 tokens

triaging-incidents

Creating, triaging, updating, and analyzing ServiceNow incidents. Assess severity, check affected CIs, find related incidents, and recommend assignments. Use when the user mentions incidents, INC numbers, outages, service disruptions, ticket creation, triage, priority, severity, ITSM operations, SLA breaches…

jschuller/mcp-server-servicenow · 82 tokens

ips-cleanup

Audit and clean up an IP-Symcon system — recurring errors, red logs, instances in error state, dead objects. Triggers: "Fehler-Audit", "rote Logs", "tote Instanzen entfernen", "IPS-Health-Check".

Schimmilab/ipsymcon-mcp-server · 56 tokens

gsccli

Use when the user wants to query Google Search Console search analytics (clicks/impressions/CTR/position by query/page/country/device), inspect URL indexing status, manage sitemaps, or send Indexing API notifications via the gsccli shell command. Triggers on GSC, Search Console, sitemap, indexing API, mobile…

nalyk/gsccli · 102 tokens

analytics-and-monitoring

Work with the GA4 analytics and Sentry error-monitoring integrations in this project. Use when adding events, capturing errors, configuring user identity, managing consent, or troubleshooting the integration.

kws-projects/react-boilerplate · 0 tokens

web-analytics

Analyze web traffic, SEO performance, and search engine trends using Google Search Console, Google Analytics 4, and Bing Webmaster Tools. Use when the user asks to analyze traffic, check SEO, or find keyword opportunities.

SeoToolkit/web-analytics-agent-skill · 47 tokens

google-search-console-mcp: Skill for Claude Code