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.
curl -O https://raw.githubusercontent.com/FlorianBruniaux/google-search-console-mcp/main/.claude/skills/internal-linking-audit/SKILL.mdgit clone --depth 1 https://github.com/FlorianBruniaux/google-search-console-mcpWrote 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.
[](https://agentmods.dev/skills/florianbruniaux/google-search-console-mcp/internal-linking-audit)<a href="https://agentmods.dev/skills/florianbruniaux/google-search-console-mcp/internal-linking-audit"><img src="https://agentmods.dev/badge/skills/florianbruniaux/google-search-console-mcp/internal-linking-audit/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.
<a href="https://agentmods.dev/skills/florianbruniaux/google-search-console-mcp/internal-linking-audit"><img src="https://agentmods.dev/badge/skills/florianbruniaux/google-search-console-mcp/internal-linking-audit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00137 | $0.00663 |
| Opus 5 | $0.00068 | $0.00331 |
| Sonnet 5 | $0.00027 | $0.00133 |
| Haiku 4.5 | $0.00014 | $0.00066 |
Grade A, and why
internal-linking-audit 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.
How it starts
The opening of the file, as written. The whole thing — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Internal Linking Audit
A link in the body of a page carries materially more weight than the same link in the footer or the main nav. This audit measures that placement instead of assuming it.
Input
A page URL. If the user gave a site rather than a page, ask which page, or run the
audit on the pages that matter most from get_search_analytics.
Steps
- Call
internal_links_auditon the target URL. No auth needed, no quota consumed. - Read
footer_only_targetsfirst. These are internal pages linked from nav, footer or aside and from the body of no page. This is the highest-value finding. - Check
body_linksagainstdemoted_links. A page whose internal links are almost all structural has no editorial linking at all. - Read
generic_anchorsandempty_anchors. The anchor is a ranking signal for the target page, so "en savoir plus" wastes it. - Read
nofollow_internal. An internal link marked nofollow throws away the weight it would otherwise pass, and it is almost always unintentional.
Cross-reference before recommending
Do not recommend adding links blind. Pull seo_striking_distance for the site first.
A page sitting at position 11 to 20 with no body link pointing at it is where an
internal link pays off fastest. A page already at position 3 does not need one.
Same rule in reverse: before calling a page orphaned, confirm with
get_search_analytics that it actually has impressions worth rescuing.
Output format
Verdict: healthy or issues_found, with the counts behind it.
Placement: body links vs nav/footer/aside links, and what that ratio says.
Targets linked only from footer or nav: Path | Zones | Current anchor
For each one, say where a body link should go instead, naming the source page.
Anchor problems: URL | Current anchor | Suggested anchor
Priority list:
- Critical: a page with search impressions and no body link anywhere
- High: an important target that lives only in the footer
- Medium: generic or empty anchors on pages that matter
- Low: internal nofollow, self-links
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 · 63 lines · 137 tokens per session scan A b1fbf8bb0172
internal-linking-audit is a skill published in the GitHub repository FlorianBruniaux/google-search-console-mcp (10 stars, last pushed 10d ago), licensed MIT. It adds 137 tokens to every session and 663 once invoked, about $0.0007 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.
Other skills, from other repositories
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…
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.
seo-mcp-reports
Generate professional, visually stunning SEO reports using SEO-MCP tools. Use when generating HTML/PDF SEO reports with charts, metric cards, gradient headers, and agency-quality styling. Covers weekly, monthly, quarterly, technical audit, competitive analysis, and client-friendly agency report formats. Requires…
seo
Use and read this skill immediately if the user request is in any way related to SEO or a site's organic search or AI search presence. That includes site audits, rankings, keyword research, competitors, backlinks, click or traffic changes, indexing problems, crawling, redirects, sitemaps, metadata, structured data…
bot-traffic-detection
Identify and exclude bot, scraper, and spam sessions from GA4 data.
featured-snippet-optimizer
Use when you want to win a featured snippet for a keyword you already rank for. The agent checks the current snippet format, analyzes your content, and rewrites the relevant section to match what Google wants.