Individual skill

gsc-seo-optimizer

Analyze Google Search Console exports or authorized API data to prioritize page improvements. Use for traffic changes, page/query opportunities, indexing evidence, and deciding when to leave recently edited or weakly supported pages alone.

plugins/all-skills/skills/gsc-seo-optimizer/SKILL.md

Read pinned source

Source commit 82ce2112b080810c6b72939201d6a53876116e12

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: No
Repository scan complete: No
Skill scan complete: No
Observed behavior: Not checked yet
Last checked: Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 3,733
Repository last updated: Nov 6, 2026
License: MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

claude Repository topic
claude-code Repository topic
subagents Repository topic
commands Repository topic
claude-code-commands Repository topic
cli-tool Repository topic
mcp Repository topic
mcp-server Repository topic
mcp-tools Repository topic
claude-skills Repository topic
marketing Derived category
data Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

LICENSEasset · 1,079 bytes
SKILL.mdcore · 7,564 bytes
references/data-access.mddoc · 5,360 bytes
references/data-quality.mddoc · 4,853 bytes
references/report-template.mddoc · 1,159 bytes
references/roi-rubric.mddoc · 1,670 bytes
scripts/gsc_fetch.pyruns · 9,868 bytes
scripts/import_gsc.pyruns · 11,292 bytes
scripts/requirements-api.txtdoc · 53 bytes
tests/fixtures/Filters.csvasset · 75 bytes
tests/fixtures/Pages.csvasset · 123 bytes
tests/fixtures/Queries.csvasset · 95 bytes
tests/test_gsc.pyruns · 9,263 bytes

Read excerpt


# GSC SEO Optimizer

Turn the user's own search evidence into a small, justified optimization batch. Default to read-only diagnosis. Execute changes only within the user's explicit authorization; existing approval for a concrete batch remains valid. An analysis request never authorizes publishing or spending.

## Establish scope and data route

Confirm the exact GSC property (domain property or URL prefix), target market, Web/other search type, and requested period. Verify the property returned by a connector matches the requested site before using any numbers. Do not choose the first accessible property. Infer from the user's site and supplied context when unambiguous; ask if multiple properties or markets remain plausible.

For ranking analysis use the user's target market, not a universal US default. Global performance totals may be useful separately; label them and never mix scopes in comparisons. If no market can be established, label aggregate findings and defer market-specific ranking claims.

Use the least-friction route already available:

1. **Supplied exports:** CSV or ZIP can be analyzed without credentials. Read [references/data-access.md](references/data-access.md) for the bundled local importer and export requirements.
2. **Existing Google API access:** prefer it for reproducible filtering and comparison. The same reference documents the bundled read-only fetcher, authentication, and URL Inspection.