seo-optimizing

seo-optimizing is a skill for Claude Code from naveedharri/benai-skills. It costs 132 tokens per session (6,030 once invoked), scanned A, original, MIT.

A skill for improving website search visibility using Google Search Console, Google's service for measuring how pages appear in search results. It examines search impressions, clicks, click rate, and ranking position.

In plain words
What is it for?
Use it to find promising search terms, investigate falling pages, improve low-click results, and detect pages competing for the same search term.
Why use it?
It helps replace guesswork with real search data when deciding which pages or search terms need attention.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: mentions Claude Code.

Part of the all-skills plugin — 99 skills shipped together

Good fit Use it to find promising search terms, investigate falling pages, improve low-click results, and detect pages competing for the same search term.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/naveedharri/benai-skills/seo-optimizing
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 naveedharri/benai-skills --skill seo-optimizing
Clone the repo
git clone --depth 1 https://github.com/naveedharri/benai-skills

Made for: Claude Code.

Or install all-skills, the plugin that ships this one along with the rest of its 99 skills.

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.

agentmods badge for seo-optimizing

README.md
[![agentmods](https://agentmods.dev/badge/skills/naveedharri/benai-skills/seo-optimizing/github.svg)](https://agentmods.dev/skills/naveedharri/benai-skills/seo-optimizing)
Your own site
<a href="https://agentmods.dev/skills/naveedharri/benai-skills/seo-optimizing"><img src="https://agentmods.dev/badge/skills/naveedharri/benai-skills/seo-optimizing/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.

agentmods 80×15 button for seo-optimizing

Your own site · 80×15
<a href="https://agentmods.dev/skills/naveedharri/benai-skills/seo-optimizing"><img src="https://agentmods.dev/badge/skills/naveedharri/benai-skills/seo-optimizing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 132 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 6,030 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 12 findings, up to high

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • high Privilege Escalation · line 17
    Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
    Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
  • high Privilege Escalation · line 18
    Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
    Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
  • high Privilege Escalation · line 19
    Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
    Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
  • high Privilege Escalation · line 23
    Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
    Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
  • high Privilege Escalation · line 77
    Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
    Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
  • medium Data Exfiltration · line 79
    Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
    Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
  • medium Data Exfiltration · line 208
    Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
    Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
  • medium Data Exfiltration · line 223
    Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
    Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
  • medium Data Exfiltration · line 238
    Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
    Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
  • medium Data Exfiltration · line 253
    Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
    Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
  • medium Data Exfiltration · line 268
    Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
    Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
  • medium Data Exfiltration · line 283
    Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
    Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
How audits are shown
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00132 $0.06030
Opus 5 $0.00066 $0.03015
Sonnet 5 $0.00026 $0.01206
Haiku 4.5 $0.00013 $0.00603

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

Security

Grade A, and why

seo-optimizing scanned grade A with 1 finding 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 5d 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

curl -s -X POST \
plugins/all-skills/skills/seo-optimizing/SKILL.md · 574 lines

How it starts

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

SEO Optimizing Skill

You are an expert SEO strategist who uses Google Search Console (GSC) data to find high-impact optimization opportunities and execute them. You analyze real search performance data — clicks, impressions, CTR, and average position — to make decisions backed by evidence, not guesswork.


On Skill Load — Immediate Actions

Run these checks automatically before asking questions:

# 1. Check for .env file with GSC credentials
if [ -f .env ]; then
  source .env
  echo "GSC_SERVICE_ACCOUNT_JSON: ${GSC_SERVICE_ACCOUNT_JSON:-NOT SET}"
  echo "GSC_SITE_URL: ${GSC_SITE_URL:-NOT SET}"
else
  echo "No .env file found"
fi

# 2. Check for existing seo-audit results
ls -la seo-audit-*.md seo-audit-*.json audit-results* 2>/dev/null || echo "No existing audit data found"

# 3. Check for previously saved GSC data
ls -la gsc-*.json seo-baseline-*.json 2>/dev/null || echo "No existing GSC data found"

Then determine the path:

  • If .env has GSC credentials → Proceed to Phase 1 (API path)
  • If no credentials → Ask: "I can connect to GSC three ways: (1) Service account API key, (2) I'll open GSC in the browser and extract the data for you automatically, or (3) you can export CSVs manually. Which do you prefer?"
  • If user chooses API → Guide setup and proceed to Phase 1
  • If user chooses Browser → Proceed to Phase 1 (Browser path)
  • If user chooses CSV → Guide them through export and skip to Phase 2

Workflow

Phase 1: Connect → Phase 2: Pull Data → Phase 3: Analyze → Phase 4: Prioritize → Phase 5: Optimize → Phase 6: Track

Phase 1: Connect

Goal: Establish authenticated access to Google Search Console API or set up CSV import.

API Path (Primary)
  1. Check .env for required variables:
# Required in .env:
GSC_SERVICE_ACCOUNT_JSON=/path/to/service-account.json
GSC_SITE_URL=https://example.com    # or sc-domain:example.com for domain property
  1. If missing, guide the user through setup:
    • Create a Google Cloud project (or use existing)
    • Enable the Search Console API
    • Create a service account and download JSON key
    • Add service account email as a reader in GSC property settings
    • Create .env with the paths

Read the full file on GitHub · 574 lines

Files

What ships with it

7 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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.

  1. 5d ago First seen · 574 lines · 132 tokens per session scan A cfa6f8b4e01f

Subscribe to this mod's changes

seo-optimizing is a skill published in the GitHub repository naveedharri/benai-skills (61 stars, last pushed 7d ago), licensed MIT. It adds 132 tokens to every session and 6,030 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-05.

Related

Other skills, from other repositories

project

A single starting point for setting up an AI-assisted project in Claude Cowork. It asks questions about the work, reviews available add-ons, and creates project instructions, custom agents, and connected workflows.

modu-ai/moai-cowork · 475 tokens

cs-channel-message

A channel-message writing tool for search ads, advertising, customer relationship messages, and app notifications. It uses the NCM sequence—Need, Channel, Moment, Message, and CTA—to adapt wording to where and when customers see it.

modu-ai/moai-cowork · 470 tokens

design-sync-upload

An uploader for design-system files such as DESIGN.md, tokens, logos, fonts, and images into Claude Design. It can either use an authenticated connection or prepare a folder and guide for manual upload.

modu-ai/moai-cowork · 211 tokens

design-tokens-transformer

A converter for design tokens, which are named values for colors, fonts, spacing, borders, shadows, and motion. It translates one shared token source into CSS variables and Tailwind or shadcn-style theme files, and can convert them back for checking.

modu-ai/moai-cowork · 255 tokens

doc-html-slide

A renderer that turns presentation content into a single HTML slide deck that opens directly in a browser. It creates a 16:9 slide sequence with navigation, fullscreen viewing, printing to PDF, and speaker-note controls.

modu-ai/moai-cowork · 469 tokens

finance-investor-relations

An investor-relations tool for preparing pitch decks and three-year financial models for fundraising. An IR, or investor-relations, deck explains a company to potential investors, while the model covers sales, profit, cash flow, and valuation.

modu-ai/moai-cowork · 180 tokens