Pp Google Search Console
Run Google Search Console audits, period comparisons, and quick-win reports from the terminal with an offline SQLite cache instead of clicking through the GSC UI.
Overview
pp-google-search-console is an agent skill most often used in Launch (also Grow) that runs Google Search Console analyses via the Printing Press CLI with cached period compares and audit-style commands.
Install
npx skills add https://github.com/mvanhorn/printing-press-library --skill pp-google-search-consoleWhat is this skill?
- Drives the `google-search-console-pp-cli` binary with install-via-`npx` Printing Press flow when the CLI is missing
- Offline SQLite cache powers period-over-period compare and faster repeat audits
- Trigger-driven commands: quick wins, cannibalization audit, decaying pages, traffic-drop analysis
- Property-scoped workflows for `sc-domain:` and URL-prefix properties
- Requires verifying CLI install before any command—explicit prerequisite gate in SKILL.md
- Offline SQLite cache for period compare and repeat audits
Adoption & trust: 1 installs on skills.sh; 1.5k GitHub stars; 1/3 security scanners passed (skills.sh audits); trending (+100% hot-view momentum).
What problem does it solve?
You need GSC insights—quick wins, cannibalization, or a traffic drop explanation—but repeating exports and UI clicks does not fit an agent or terminal-first workflow.
Who is it for?
Solo builders who already verify a site in GSC and want Claude or Cursor to run repeatable SEO diagnostics from natural-language trigger phrases.
Skip if: Teams without GSC property access, without willingness to install `google-search-console-pp-cli`, or who only need one-off manual checks in the browser.
When should I use this skill?
User asks for Search Console performance, quick wins, cannibalization, period compare, decaying pages, traffic-drop analysis, or uses trigger phrases like `use google-search-console` / `run gsc`.
What do I get? / Deliverables
You get scripted GSC performance and diagnostic outputs from the CLI (with cache-backed compares) ready to paste into plans, tickets, or follow-on content/SEO skills.
- CLI-backed GSC performance and diagnostic reports
- Cached query results for period-over-period comparison
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Search Console is the canonical launch-phase surface for organic search diagnostics; the skill’s commands map directly to visibility and indexing work after you have a live property. SEO subphase covers performance queries, decaying pages, cannibalization, and traffic-drop forensics—the exact trigger phrases baked into the skill description.
Where it fits
Pull GSC performance and quick-win candidates before rewriting titles and meta for key URLs.
Compare two 28-day windows to explain an organic traffic dip before changing content or pricing pages.
Audit which queries and pages are losing impressions when tuning AI-search and traditional SERP snippets.
How it compares
CLI skill package for GSC workflows—not an MCP server and not a generic web-scraping substitute for authenticated Search Console API data.
Common Questions / FAQ
Who is pp-google-search-console for?
Indie and solo builders who ship web products and want agent-driven Google Search Console commands (performance, quick wins, cannibalization, period compare) via the Printing Press CLI.
When should I use pp-google-search-console?
At launch when tuning SEO and indexing; during grow when monitoring decay or traffic drops; whenever you say phrases like `search console performance for example.com`, `compare last 28 days to prior period in GSC`, or `run gsc`.
Is pp-google-search-console safe to install?
Review the Security Audits panel on this Prism page and the skill’s allowed-tools (`Read Bash`) before granting shell access; do not assume pass/fail counts from this FAQ.
SKILL.md
READMESKILL.md - Pp Google Search Console
<!-- GENERATED FILE — DO NOT EDIT. This file is a verbatim mirror of library/marketing/google-search-console/SKILL.md, regenerated post-merge by tools/generate-skills/. Hand-edits here are silently overwritten on the next regen. Edit the library/ source instead. See the repository agent guide, section "Generated artifacts: registry.json, cli-skills/". --> # Google Search Console — Printing Press CLI ## Prerequisites: Install the CLI This skill drives the `google-search-console-pp-cli` binary. **You must verify the CLI is installed before invoking any command from this skill.** If it is missing, install it first: 1. Install via the Printing Press installer. It defaults binaries to `$HOME/.local/bin` on macOS/Linux and `%LOCALAPPDATA%\Programs\PrintingPress\bin` on Windows: ```bash npx -y @mvanhorn/printing-press-library install google-search-console --cli-only ``` 2. Verify: `google-search-console-pp-cli --version` 3. Ensure the reported install directory is on `$PATH` for the agent/runtime that will invoke this skill. If the `npx` install fails (no Node, offline, etc.), fall back to a direct Go install (requires Go 1.26.3 or newer): ```bash go install github.com/mvanhorn/printing-press-library/library/marketing/google-search-console/cmd/google-search-console-pp-cli@latest ``` If `--version` reports "command not found" after install, the runtime cannot see the binary directory on `$PATH`. Do not proceed with skill commands until verification succeeds. ## When to Use This CLI Reach for this CLI when an agent needs to answer SEO questions for a Google Search Console property without round-tripping to the web UI. It is the right choice for: pulling top queries and pages for any window; comparing periods; finding indexing or sitemap regressions; surfacing page-2 quick wins, decaying pages, or keyword cannibalization; and answering questions about data older than the API's 16-month window once a sync history exists. It is not the right choice for one-off ad-hoc lookups when a sync hasn't run -- start with `sync` first. ## Unique Capabilities These capabilities aren't available in any other tool for this API. ### SEO opportunities from local corpus - **`quick-wins`** — Surface page-2 queries with high impressions and low CTR -- page-2-to-page-1 candidates ranked by upside, computed offline from your synced corpus. _Reach for this when an agent needs to recommend the top SEO opportunities for a property without re-fetching from the API._ ```bash google-search-console-pp-cli quick-wins sc-domain:example.com --position 8-20 --min-imps 100 --json ``` - **`cannibalization`** — Find queries where multiple pages compete, ranked by combined impressions -- the keyword-cannibalization audit the GSC web UI doesn't offer. _Use when an agent investigates why a query ranks worse than expected -- surfaces the competing pages on its own URL._ ```bash google-search-console-pp-cli cannibalization sc-domain:example.com --min-imps 50 --top 25 --json ``` - **`outliers`** — Queries or pages with click-through rates that deviate from the observed CTR-by-position curve in your own corpus. _Title-tag and snippet-rewrite candidates an agent can act on directly -- high impressions, low CTR for their position._ ```bash google-search-