Back to Details

pp-google-search-console

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Google Search Console — Printing Press CLI

Google Search Console — Printing Press CLI

Prerequisites: Install the CLI

前提条件：安装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:
    bash
    npx -y @mvanhorn/printing-press install google-search-console --cli-only
  2. Verify: 
    google-search-console-pp-cli --version
  3. Ensure 
    $GOPATH/bin
    (or 
    $HOME/go/bin
    ) is on 
    $PATH
    .
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 install step did not put the binary on 
$PATH
. Do not proceed with skill commands until verification succeeds.
A single binary covering search analytics, URL inspection, sitemaps, and site management -- with the agent-native JSON and CSV outputs, --dry-run, exit codes, and offline search every other GSC tool half-implements. The transcendence layer (compare, quick-wins, cannibalization, historical, decaying, outliers, cliff, roll-up, coverage-drift, sitemap-watch, new-queries) runs entirely from the local SQLite store, so the workflows the API can't answer in one call are answered in one command.
本技能驱动
google-search-console-pp-cli
二进制文件。在调用本技能的任何命令前，你必须确认CLI已安装。如果未安装，请先执行以下步骤：
  1. 通过Printing Press安装器安装：
    bash
    npx -y @mvanhorn/printing-press install google-search-console --cli-only
  2. 验证安装：
    google-search-console-pp-cli --version
  3. 确保
    $GOPATH/bin
    （或
    $HOME/go/bin
    ）已添加到
    $PATH
    环境变量中。
如果
npx
安装失败（无Node环境、离线等），可以直接通过Go安装（要求Go 1.26.3或更高版本）：
bash
go install github.com/mvanhorn/printing-press-library/library/marketing/google-search-console/cmd/google-search-console-pp-cli@latest
如果安装后执行
--version
提示“command not found”，说明安装步骤未将二进制文件添加到
$PATH
中。请在验证成功前不要执行技能命令。
这是一个集成了搜索分析、URL检测、站点地图和站点管理的单一二进制工具，支持Agent原生的JSON和CSV输出、
--dry-run
、退出码，以及其他GSC工具仅部分实现的离线搜索功能。其核心增强层（对比、快速优化机会、关键词 cannibalization、历史数据、页面衰退、异常值、流量骤降、跨属性汇总、覆盖漂移、站点地图监控、新查询）完全基于本地SQLite存储运行，因此API无法通过单次调用完成的工作流，本工具可通过单个命令完成。

When to Use This CLI

何时使用本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.
当Agent需要在不往返Web界面的情况下，为Google Search Console属性解答SEO问题时，可使用本CLI。适用于以下场景：提取任意时间窗口的热门查询和页面；对比不同时段数据；发现索引或站点地图退化问题；挖掘第二页快速优化机会、衰退页面或关键词 cannibalization；当存在同步历史时，解答API 16个月窗口之外的历史数据相关问题。如果尚未运行同步操作，不适合用于一次性临时查询——请先执行
sync
命令。

Unique Capabilities

独特功能

These capabilities aren't available in any other tool for this API.
以下功能是其他同类型API工具所不具备的。

SEO opportunities from local corpus

基于本地语料库的SEO机会

  • 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-console-pp-cli outliers sc-domain:example.com --metric ctr --sigma 2 --top 50 --json
  • quick-wins
     —— 展示高曝光、低点击率的第二页查询结果，按优化潜力排序，基于同步到本地的语料库离线计算得出。
    当Agent需要为某个属性推荐顶级SEO优化机会，且无需从API重新获取数据时，可使用此命令。
    bash
    google-search-console-pp-cli quick-wins sc-domain:example.com --position 8-20 --min-imps 100 --json
  • cannibalization
     —— 找出多个页面竞争同一查询的情况，按总曝光量排序——这是GSC Web界面未提供的关键词 cannibalization 审计功能。
    当Agent调查某个查询排名低于预期的原因时使用，可展示该查询对应的竞争页面。
    bash
    google-search-console-pp-cli cannibalization sc-domain:example.com --min-imps 50 --top 25 --json
  • outliers
     —— 点击率偏离自身语料库中“点击率-排名”曲线的查询或页面。
    可直接作为标题标签和摘要改写的候选对象——高曝光量，但对应排名下的点击率偏低。
    bash
    google-search-console-pp-cli outliers sc-domain:example.com --metric ctr --sigma 2 --top 50 --json

Time-series analysis

时间序列分析

  • compare
     — Period-over-period delta on clicks, impressions, CTR, and position for any dimension -- week-over-week, month-over-month, or arbitrary windows.
    First-line investigation when a property's traffic shifts -- the agent gets the deltas without spelunking two raw queries.
    bash
    google-search-console-pp-cli compare sc-domain:example.com --period 28d --vs prev-period --dim query --top 50 --agent --select rows.keys,rows.delta_clicks,rows.delta_position
  • cliff
     — Find the day clicks or impressions cratered, with signature hints matching same-day sitemap regressions or indexing drops.
    The first command an agent should run when a human says 'traffic dropped' -- points at the day and likely cause.
    bash
    google-search-console-pp-cli cliff sc-domain:example.com --metric clicks --threshold -25% --window 7d
  • historical
     — Search analytics for date ranges older than the API's 16-month rolling window -- answer 'is this March-2024 normal?' from cached history.
    Forecasting and seasonality questions; a one-shot agent can answer 'compared to two years ago' without breaking out a backup file.
    bash
    google-search-console-pp-cli historical sc-domain:example.com --start 2023-01-01 --end 2023-12-31 --dim query --top 100
  • compare
     —— 对比任意维度下的点击量、曝光量、点击率和排名的时段差异，支持周环比、月环比或任意时间窗口。
    当某个属性流量发生变化时，可作为首要调查工具——Agent无需查看两次原始查询结果即可获取差异数据。
    bash
    google-search-console-pp-cli compare sc-domain:example.com --period 28d --vs prev-period --dim query --top 50 --agent --select rows.keys,rows.delta_clicks,rows.delta_position
  • cliff
     —— 找出点击量或曝光量骤降的日期，并提供当日站点地图退化或索引下降等相关线索。
    当用户反馈“流量下降”时，Agent应首先运行此命令——可指出具体日期和可能原因。
    bash
    google-search-console-pp-cli cliff sc-domain:example.com --metric clicks --threshold -25% --window 7d
  • historical
     —— 查询API 16个月滚动窗口之外的搜索分析数据——可从缓存历史中回答“2024年3月的数据是否正常？”这类问题。
    适用于预测和季节性问题；一次性Agent无需调取备份文件即可回答“与两年前相比情况如何？”
    bash
    google-search-console-pp-cli historical sc-domain:example.com --start 2023-01-01 --end 2023-12-31 --dim query --top 100

Cross-property analysis

跨属性分析

  • roll-up
     — Aggregate top queries or pages across every verified property in one command -- the API forces N round-trips.
    Agency workflows where the agent surfaces top performers across a portfolio without writing per-site loops.
    bash
    google-search-console-pp-cli roll-up --metric clicks --group-by query --top 50 --last 28d --json
  • roll-up
     —— 通过单个命令汇总所有已验证属性的热门查询或页面——而API需要N次往返调用才能完成。
    适用于代理机构工作流，Agent无需编写逐站点循环即可展示整个组合中的顶级表现者。
    bash
    google-search-console-pp-cli roll-up --metric clicks --group-by query --top 50 --last 28d --json

Indexing diagnostics

索引诊断

  • coverage-drift
     — URLs whose inspection state flipped (indexed → not indexed, robots changed, canonical changed) within a window.
    Catches indexing regressions an agent would otherwise miss because the API hides them once the state has flipped back.
    bash
    google-search-console-pp-cli coverage-drift sc-domain:example.com --field indexingState --days 30 --json
  • sitemap-watch
     — Diff sitemap state between snapshots -- surface new errors, new warnings, content-count drops, and stale lastDownloaded times.
    Friday automation that catches sitemap regressions before the next Monday traffic dip -- runs from local data, no extra API spend.
    bash
    google-search-console-pp-cli sitemap-watch sc-domain:example.com --since 7d --json
  • coverage-drift
     —— 在指定时间窗口内检查状态发生变化的URL（如从已索引变为未索引、robots规则变更、规范URL变更）。
    可捕捉Agent可能遗漏的索引退化问题，因为一旦状态恢复，API会隐藏这些变化记录。
    bash
    google-search-console-pp-cli coverage-drift sc-domain:example.com --field indexingState --days 30 --json
  • sitemap-watch
     —— 对比站点地图快照之间的状态差异，展示新错误、新警告、内容数量下降和过期的lastDownloaded时间。
    可作为周五自动化任务，在周一流量下降前捕捉站点地图退化问题——基于本地数据运行，无需额外API调用开销。
    bash
    google-search-console-pp-cli sitemap-watch sc-domain:example.com --since 7d --json

Content workflows

内容工作流

  • decaying
     — Pages with monotonic click decline over a rolling window, ranked by total impressions × negative slope -- the content-refresh queue.
    Content marketers' Thursday refresh queue -- the agent picks update candidates with concrete supporting numbers.
    bash
    google-search-console-pp-cli decaying sc-domain:example.com --window 90d --min-imps 500 --top 50 --json
  • new-queries
     — Queries that started showing up with impressions in the last N days but didn't exist in the corpus before -- emerging demand.
    Content-ideas surface for marketers; the agent gets emerging-search trends scoped to this site rather than generic Trends data.
    bash
    google-search-console-pp-cli new-queries sc-domain:example.com --since 28d --min-imps 50 --top 100 --json
  • decaying
     —— 在滚动窗口内点击量持续下降的页面，按总曝光量×负斜率排序——即内容更新优先级队列。
    内容营销人员的周四更新队列——Agent可挑选有具体数据支撑的更新候选页面。
    bash
    google-search-console-pp-cli decaying sc-domain:example.com --window 90d --min-imps 500 --top 50 --json
  • new-queries
     —— 过去N天内首次出现曝光量的查询，且之前未出现在语料库中——即新兴需求。
    为营销人员提供内容创意；Agent可获取针对本网站的新兴搜索趋势，而非通用趋势数据。
    bash
    google-search-console-pp-cli new-queries sc-domain:example.com --since 28d --min-imps 50 --top 100 --json

Command Reference

命令参考

url-inspection — Inspect a URL's index status in Google Search
  • google-search-console-pp-cli url-inspection
    — Returns Google's view of a single URL: index status, last crawl time, canonical URL (Google-selected vs...
webmasters — Manage webmasters
  • google-search-console-pp-cli webmasters add-site
    — Adds a site to the set of the user's sites in Search Console. The site must still be verified separately (via DNS,...
  • google-search-console-pp-cli webmasters delete-site
    — Removes a site from the set of the user's Search Console sites. Does not delete data Google has collected.
  • google-search-console-pp-cli webmasters delete-sitemap
    — Deletes a sitemap from the Sitemaps report. Does not stop Google from crawling the sitemap if it's still...
  • google-search-console-pp-cli webmasters get-site
    — Retrieves information about a specific verified site, including the user's permission level.
  • google-search-console-pp-cli webmasters get-sitemap
    — Retrieves information about a specific sitemap, including warnings, errors, last submitted/downloaded times, and...
  • google-search-console-pp-cli webmasters list-sitemaps
    — Lists the sitemaps submitted for this site, or included in the sitemap index file (if 
    sitemapIndex
    is provided in...
  • google-search-console-pp-cli webmasters list-sites
    — Returns every site (domain property or URL-prefix property) the authenticated user has access to in Search Console,...
  • google-search-console-pp-cli webmasters query-search-analytics
    — Returns clicks, impressions, CTR, and average position grouped by the dimensions you specify (query, page, country,...
  • google-search-console-pp-cli webmasters submit-sitemap
    — Submits a sitemap for a site. The sitemap URL must be an absolute URL on the same site as 
    siteUrl
    . Submission is...
url-inspection —— 检查URL在Google搜索中的索引状态
  • google-search-console-pp-cli url-inspection
    —— 返回Google对单个URL的视图：索引状态、最后抓取时间、规范URL（Google选择的与……
webmasters —— 管理网站管理员权限
  • google-search-console-pp-cli webmasters add-site
    —— 将站点添加到用户的Search Console站点集合中。站点仍需单独验证（通过DNS……
  • google-search-console-pp-cli webmasters delete-site
    —— 从用户的Search Console站点集合中移除站点。不会删除Google收集的数据。
  • google-search-console-pp-cli webmasters delete-sitemap
    —— 从站点地图报告中删除站点地图。如果站点地图仍可访问，不会阻止Google抓取它……
  • google-search-console-pp-cli webmasters get-site
    —— 获取特定已验证站点的信息，包括用户的权限级别。
  • google-search-console-pp-cli webmasters get-sitemap
    —— 获取特定站点地图的信息，包括警告、错误、最后提交/下载时间，以及……
  • google-search-console-pp-cli webmasters list-sitemaps
    —— 列出为该站点提交的站点地图，或站点地图索引文件中包含的站点地图（如果提供了
    sitemapIndex
    参数……
  • google-search-console-pp-cli webmasters list-sites
    —— 返回已认证用户在Search Console中有权访问的所有站点（域名属性或URL前缀属性）……
  • google-search-console-pp-cli webmasters query-search-analytics
    —— 返回按指定维度（查询、页面、国家……）分组的点击量、曝光量、点击率和平均排名……
  • google-search-console-pp-cli webmasters submit-sitemap
    —— 为站点提交站点地图。站点地图URL必须是与
    siteUrl
    同站点的绝对URL。提交操作……

Finding the right command

查找合适的命令

When you know what you want to do but not which command does it, ask the CLI directly:
bash
google-search-console-pp-cli which "<capability in your own words>"
which
resolves a natural-language capability query to the best matching command from this CLI's curated feature index. Exit code 
0
means at least one match; exit code 
2
means no confident match — fall back to 
--help
or use a narrower query.
当你知道要做什么但不知道对应命令时，可直接询问CLI：
bash
google-search-console-pp-cli which "<用你自己的语言描述功能>"
which
命令会将自然语言的功能查询解析为与CLI精选功能索引最匹配的命令。退出码
0
表示至少有一个匹配项；退出码
2
表示没有明确匹配项——请改用
--help
或更精准的查询。

Recipes

使用示例

Top queries with low CTR -- title-tag rewrite candidates

低点击率的热门查询——标题标签改写候选

bash
google-search-console-pp-cli outliers sc-domain:example.com --metric ctr --sigma 2 --top 50 --agent --select rows.keys,rows.position,rows.ctr,rows.expected_ctr
Pairs --agent (compact NDJSON) with --select to narrow the response so the agent doesn't have to wade through full ApiDataRow objects. Outputs only the dimensions and the CTR delta vs the bucket mean for the position.
bash
google-search-console-pp-cli outliers sc-domain:example.com --metric ctr --sigma 2 --top 50 --agent --select rows.keys,rows.position,rows.ctr,rows.expected_ctr
将
--agent
（紧凑NDJSON格式）与
--select
结合使用，可缩小响应范围，避免Agent处理完整的ApiDataRow对象。仅输出维度数据以及该排名下的点击率与分组均值的差异。

Why did traffic drop yesterday?

昨日流量为何下降？

bash
google-search-console-pp-cli cliff sc-domain:example.com --metric clicks --threshold -20% --window 14d --json
Returns the days clicks dropped more than 20% versus the prior day, plus same-day signals from sitemaps (new errors) and url_inspections (indexing-state flips). Single command answers the most common SEO post-mortem question.
bash
google-search-console-pp-cli cliff sc-domain:example.com --metric clicks --threshold -20% --window 14d --json
返回点击量较前一日下降超过20%的日期，以及当日站点地图（新错误）和URL检测（索引状态变化）的相关信号。单个命令即可回答最常见的SEO事后分析问题。

Cross-property weekly summary

跨属性每周汇总

bash
google-search-console-pp-cli roll-up --metric clicks --group-by query --last 7d --top 25 --csv > weekly.csv
Aggregates top 25 queries by clicks across every verified property, last 7 days. CSV pipes straight into a spreadsheet or data tool.
bash
google-search-console-pp-cli roll-up --metric clicks --group-by query --last 7d --top 25 --csv > weekly.csv
汇总所有已验证属性过去7天内点击量排名前25的查询结果。CSV格式可直接导入电子表格或数据分析工具。

Bulk URL inspection from a file

从文件批量检测URL

bash
google-search-console-pp-cli url-inspection inspect-batch --file urls.txt --site sc-domain:example.com --max-per-day 2000 --json
Streams NDJSON one inspection per line. Respects the per-property daily quota. Pipe to 
jq 'select(.indexStatusResult.coverageState != "Submitted and indexed")'
to surface only problems.
bash
google-search-console-pp-cli url-inspection inspect-batch --file urls.txt --site sc-domain:example.com --max-per-day 2000 --json
以NDJSON格式逐行输出检测结果。遵守每个属性的每日配额限制。可通过管道传递给
jq 'select(.indexStatusResult.coverageState != "Submitted and indexed")'
仅筛选出有问题的结果。

Cannibalization audit before publishing a new page

发布新页面之前的Cannibalization审计

bash
google-search-console-pp-cli cannibalization sc-domain:example.com --min-imps 50 --top 20 --json
Surfaces existing queries where multiple pages on the site already compete. Run before publishing a new piece on the same topic -- pick the strongest existing page or consolidate.
bash
google-search-console-pp-cli cannibalization sc-domain:example.com --min-imps 50 --top 20 --json
展示网站内已有多个页面竞争同一查询的情况。在发布同一主题的新页面之前运行此命令——选择现有表现最佳的页面或进行内容整合。

Auth Setup

身份验证设置

Google Search Console uses OAuth 2.0. The CLI reads a pre-fetched access token from the GSC_ACCESS_TOKEN environment variable. Generate one from the Google OAuth Playground (https://developers.google.com/oauthplayground/) using scope https://www.googleapis.com/auth/webmasters.readonly for read-only operations or https://www.googleapis.com/auth/webmasters for full read-write (sitemap submit/delete, sites add/delete). Tokens expire after one hour; refresh from the same Playground UI. There is no 
auth login
flow in this CLI by design -- pre-fetched tokens keep the install path simple and match the google-ads house pattern.
Run 
google-search-console-pp-cli doctor
to verify setup.
Google Search Console使用OAuth 2.0。CLI从
GSC_ACCESS_TOKEN
环境变量中读取预获取的访问令牌。可通过Google OAuth Playground（https://developers.google.com/oauthplayground/）生成令牌，只读操作使用范围`https://www.googleapis.com/auth/webmasters.readonly`，全读写操作（提交/删除站点地图、添加/删除站点）使用范围`https://www.googleapis.com/auth/webmasters`。令牌1小时后过期，可从同一Playground界面刷新。本CLI设计上不包含`auth login`流程——预获取令牌可简化安装路径，与google-ads的通用模式一致。
执行
google-search-console-pp-cli doctor
验证设置是否正确。

Agent Mode

Agent模式

Add 
--agent
to any command. Expands to: 
--json --compact --no-input --no-color --yes
.
  • Pipeable — JSON on stdout, errors on stderr
  • Filterable — 
    --select
    keeps a subset of fields. Dotted paths descend into nested structures; arrays traverse element-wise. Critical for keeping context small on verbose APIs:
    bash
    google-search-console-pp-cli url-inspection --inspection-url https://example.com/resource --agent --select id,name,status
  • Previewable — 
    --dry-run
    shows the request without sending
  • Non-interactive — never prompts, every input is a flag
  • Explicit retries — use 
    --idempotent
    only when an already-existing create should count as success, and 
    --ignore-missing
    only when a missing delete target should count as success
在任何命令后添加
--agent
参数，等效于：
--json --compact --no-input --no-color --yes
。
  • 可管道传输 —— 标准输出为JSON，错误输出到标准错误流
  • 可过滤 —— 
    --select
    参数可保留字段子集。点路径可深入嵌套结构；数组可遍历元素。对于复杂API，这是保持上下文精简的关键：
    bash
    google-search-console-pp-cli url-inspection --inspection-url https://example.com/resource --agent --select id,name,status
  • 可预览 —— 
    --dry-run
    参数可显示请求内容但不发送
  • 非交互式 —— 从不提示用户，所有输入均通过标志参数提供
  • 显式重试 —— 仅当已存在的创建操作应视为成功时使用
    --idempotent
    ；仅当删除目标不存在应视为成功时使用
    --ignore-missing

Agent Feedback

Agent反馈

When you (or the agent) notice something off about this CLI, record it:
google-search-console-pp-cli feedback "the --since flag is inclusive but docs say exclusive"
google-search-console-pp-cli feedback --stdin < notes.txt
google-search-console-pp-cli feedback list --json --limit 10
Entries are stored locally at 
~/.google-search-console-pp-cli/feedback.jsonl
. They are never POSTed unless 
GOOGLE_SEARCH_CONSOLE_FEEDBACK_ENDPOINT
is set AND either 
--send
is passed or 
GOOGLE_SEARCH_CONSOLE_FEEDBACK_AUTO_SEND=true
. Default behavior is local-only.
Write what surprised you, not a bug report. Short, specific, one line: that is the part that compounds.
当你（或Agent）发现本CLI存在问题时，可记录反馈：
google-search-console-pp-cli feedback "the --since flag is inclusive but docs say exclusive"
google-search-console-pp-cli feedback --stdin < notes.txt
google-search-console-pp-cli feedback list --json --limit 10
反馈条目存储在本地
~/.google-search-console-pp-cli/feedback.jsonl
文件中。除非设置了
GOOGLE_SEARCH_CONSOLE_FEEDBACK_ENDPOINT
且传递了
--send
参数，或
GOOGLE_SEARCH_CONSOLE_FEEDBACK_AUTO_SEND=true
，否则反馈不会被POST发送。默认行为仅存储在本地。
请写下让你感到意外的内容，而非正式的错误报告。简短、具体、一句话即可：这样的反馈价值更高。

Output Delivery

输出交付

Every command accepts 
--deliver <sink>
. The output goes to the named sink in addition to (or instead of) stdout, so agents can route command results without hand-piping. Three sinks are supported:
SinkEffect
stdout
Default; write to stdout only
file:<path>
Atomically write output to 
<path>
(tmp + rename)
webhook:<url>
POST the output body to the URL (
application/json
or 
application/x-ndjson
when 
--compact
)
Unknown schemes are refused with a structured error naming the supported set. Webhook failures return non-zero and log the URL + HTTP status on stderr.
所有命令均支持
--deliver <sink>
参数。输出会发送到指定的接收端，同时（或替代）输出到标准输出，因此Agent无需手动管道即可路由命令结果。支持三种接收端：
接收端效果
stdout
默认值；仅输出到标准输出
file:<path>
原子性地将输出写入
<path>
（先写入临时文件再重命名）
webhook:<url>
将输出体POST到指定URL（
application/json
格式，若使用
--compact
则为
application/x-ndjson
格式）
不支持的协议会返回结构化错误，并列出支持的接收端类型。Webhook失败时返回非零退出码，并在标准错误流中记录URL和HTTP状态码。

Named Profiles

命名配置文件

A profile is a saved set of flag values, reused across invocations. Use it when a scheduled agent calls the same command every run with the same configuration - HeyGen's "Beacon" pattern.
google-search-console-pp-cli profile save briefing --json
google-search-console-pp-cli --profile briefing url-inspection --inspection-url https://example.com/resource
google-search-console-pp-cli profile list --json
google-search-console-pp-cli profile show briefing
google-search-console-pp-cli profile delete briefing --yes
Explicit flags always win over profile values; profile values win over defaults. 
agent-context
lists all available profiles under 
available_profiles
so introspecting agents discover them at runtime.
配置文件是一组保存的标志值，可在多次调用中复用。适用于定时Agent每次运行相同命令且配置相同的场景——即HeyGen的“Beacon”模式。
google-search-console-pp-cli profile save briefing --json
google-search-console-pp-cli --profile briefing url-inspection --inspection-url https://example.com/resource
google-search-console-pp-cli profile list --json
google-search-console-pp-cli profile show briefing
google-search-console-pp-cli profile delete briefing --yes
显式标志参数始终优先于配置文件值；配置文件值优先于默认值。
agent-context
会在
available_profiles
下列出所有可用配置文件，因此自省Agent可在运行时发现它们。

Exit Codes

退出码

CodeMeaning
0Success
2Usage error (wrong arguments)
3Resource not found
4Authentication required
5API error (upstream issue)
7Rate limited (wait and retry)
10Config error
代码含义
0成功
2使用错误（参数错误）
3资源未找到
4需要身份验证
5API错误（上游问题）
7速率限制（请等待并重试）
10配置错误

Argument Parsing

参数解析

Parse 
$ARGUMENTS
:
  1. Empty, 
    help
    , or 
    --help
     → show 
    google-search-console-pp-cli --help
    output
  2. Starts with 
    install
     → ends with 
    mcp
    → MCP installation; otherwise → see Prerequisites above
  3. Anything else → Direct Use (execute as CLI command with 
    --agent
    )
解析
$ARGUMENTS
的规则：
  1. 为空、
    help
    或
    --help
     → 显示
    google-search-console-pp-cli --help
    输出
  2. 以
    install
    开头     → 若结尾为
    mcp
    → 安装MCP；否则 → 参考上方前提条件中的安装步骤
  3. 其他情况 → 直接使用（添加
    --agent
    参数执行CLI命令）

MCP Server Installation

MCP服务器安装

Install the MCP binary from this CLI's published public-library entry or pre-built release, then register it:
bash
claude mcp add google-search-console-pp-mcp -- google-search-console-pp-mcp
Verify: 
claude mcp list
从本CLI的公开库条目或预构建版本安装MCP二进制文件，然后注册：
bash
claude mcp add google-search-console-pp-mcp -- google-search-console-pp-mcp
验证安装：
claude mcp list

Direct Use

直接使用

  1. Check if installed: 
    which google-search-console-pp-cli
    If not found, offer to install (see Prerequisites at the top of this skill).
  2. Match the user query to the best command from the Unique Capabilities and Command Reference above.
  3. Execute with the 
    --agent
    flag:
    bash
    google-search-console-pp-cli <command> [subcommand] [args] --agent
  4. If ambiguous, drill into subcommand help: 
    google-search-console-pp-cli <command> --help
    .
  1. 检查是否已安装：
    which google-search-console-pp-cli
    若未找到，提供安装选项（参见顶部前提条件中的安装步骤）。
  2. 将用户查询与上方“独特功能”和“命令参考”中的最佳命令匹配。
  3. 添加
    --agent
    参数执行命令：
    bash
    google-search-console-pp-cli <command> [subcommand] [args] --agent
  4. 若存在歧义，查看子命令帮助：
    google-search-console-pp-cli <command> --help
    。