AGENT SKILL
pm-google-search-console
Google Search Console connector knowledge and safe action guide.
- License 许可
- AGPL-3.0
- 最近更新
- 2026-09-21
- Stars
- ★ 7
- Forks
- 0
01 前言 Front Matter
- name
- pm-google-search-console
- description
- Google Search Console connector knowledge and safe action guide.
03 SKILL.md 正文
pm-google-search-console
Purpose
Reads Google Search Console sites, sitemaps, and Search Analytics performance reports (by date, query, page, country, and device) through the Search Console v3 REST API; submits/removes sites and sitemaps through explicit write actions.
Icon
- id: googlesearchconsole
- asset: icons/googlesearchconsole.svg
- source: upstream_registry
- review_status: upstream_seeded
- review_url: https://developers.google.com/search/news
Capabilities
- check=true catalog=true read=true write=true query=false
- Integration type: api
Authentication
- Use pm credentials add with --from-env or --value-stdin for secret fields.
Configuration
- base_url
- data_state
- end_date
- feedpath
- inspection_url
- max_pages
- mobile_test_url
- mode
- page_size
- search_type
- site_url
- site_urls
- start_date
- access_token (secret) (required)
ETL Streams
- sites:
- primary key: site_url
- fields: permission_level(string), site_url(string)
- site_details:
- primary key: site_url
- fields: permission_level(string), site_url(string)
- sitemaps:
- primary key: site_url, path
- fields: errors(string), is_pending(boolean), is_sitemaps_index(boolean), last_downloaded(string), last_submitted(string), path(string), site_url(string), type(string), warnings(string)
- sitemap_details:
- primary key: site_url, path
- fields: errors(string), is_pending(boolean), is_sitemaps_index(boolean), last_downloaded(string), last_submitted(string), path(string), site_url(string), type(string), warnings(string)
- search_analytics_by_date:
- primary key: site_url, search_type, date
- cursor: date
- fields: clicks(number), ctr(number), date(string), impressions(number), position(number), search_type(string), site_url(string)
- search_analytics_by_country:
- primary key: site_url, search_type, date, country
- cursor: date
- fields: clicks(number), country(string), ctr(number), date(string), impressions(number), position(number), search_type(string), site_url(string)
- search_analytics_by_device:
- primary key: site_url, search_type, date, device
- cursor: date
- fields: clicks(number), ctr(number), date(string), device(string), impressions(number), position(number), search_type(string), site_url(string)
- search_analytics_by_page:
- primary key: site_url, search_type, date, page
- cursor: date
- fields: clicks(number), ctr(number), date(string), impressions(number), page(string), position(number), search_type(string), site_url(string)
- search_analytics_by_query:
- primary key: site_url, search_type, date, query
- cursor: date
- fields: clicks(number), ctr(number), date(string), impressions(number), position(number), query(string), search_type(string), site_url(string)
Sync Modes
- ETL sync modes: full_refresh_append, full_refresh_overwrite, full_refresh_overwrite_deduped
Reverse ETL Actions
- add_site:
- endpoint: PUT /webmasters/v3/sites/{{ record.site_url | urlencode }}
- required fields: site_url
- risk: adds a site property to the authenticated Search Console account
- delete_site:
- endpoint: DELETE /webmasters/v3/sites/{{ record.site_url | urlencode }}
- required fields: site_url
- risk: removes a site property from the authenticated Search Console account
- submit_sitemap:
- endpoint: PUT /webmasters/v3/sites/{{ record.site_url | urlencode }}/sitemaps/{{ record.feedpath | urlencode }}
- required fields: site_url, feedpath
- risk: submits a sitemap URL for a Search Console site property
- delete_sitemap:
- endpoint: DELETE /webmasters/v3/sites/{{ record.site_url | urlencode }}/sitemaps/{{ record.feedpath | urlencode }}
- required fields: site_url, feedpath
- risk: deletes a sitemap from a Search Console site property
Security
- read risk: external Google Search Console API read of site/sitemap metadata and search analytics performance data
- write risk: adds or removes Search Console site properties and submits or deletes sitemap resources
- approval: reverse ETL writes require plan preview and approval token
- Never pass secret values in chat, shell arguments, logs, docs, or JSON output.
Command Surface
- Inspect, read, and safely plan typed Google Search Console operations.
- Usage: pm google-search-console <command> [flags]
- Source CLI: Google Search Console API (Official REST discovery documents for Search Console v3 and searchconsole v1)
- Global flags:
- --credential (string): Credential name to use for the Google Search Console request.
- --connection (string): Alias for --credential.
- --config (string_array): Connector config override as key=value.
- --json (boolean): Emit machine-readable JSON output.
- --limit (integer): Maximum PM ETL records to emit; does not control Search Console rowLimit.
- --max-bytes (integer): Maximum direct-read response bytes; typed operations are capped at 16 MiB and each Google Search Console operation declares a lower limit.
- --plan (string): Execute an approved reverse-ETL plan by id.
- --preview (boolean): Preview a reverse-ETL write command without making a network mutation.
- --approval-token-stdin (boolean): Read the approval token as one bounded line from standard input.
- --confirm (string): Typed confirmation challenge for destructive reverse-ETL writes.
- Sites
- sites list - List verified Search Console site properties as ETL records. [intent=etl availability=implemented stream=sites]
- sites get - Read one verified Search Console site property as an ETL record. [intent=etl availability=implemented stream=site_details]
- sites add - Plan adding a Search Console site property through reverse ETL. [intent=reverse_etl availability=implemented write=add_site]; approval: Use reverse ETL plan -> preview -> approval -> execute. No raw HTTP body is accepted; the record must match writes.json.; risk: medium: adds a site property to the authenticated Search Console account; requires reverse ETL plan and approval; flags: --site-url (non-empty)
- sites delete - Plan deleting a Search Console site property through destructive reverse ETL. [intent=reverse_etl availability=implemented write=delete_site]; approval: Use reverse ETL plan -> preview -> approval -> typed destructive confirmation -> execute. Missing provider records are idempotent for HTTP 404.; risk: high: removes a site property from the authenticated Search Console account; requires reverse ETL plan, approval, and destructive confirmation; flags: --site-url (non-empty)
- Sitemaps
- sitemaps list - List sitemap entries for configured Search Console site properties. [intent=etl availability=implemented stream=sitemaps]
- sitemaps get - Read one sitemap entry for a Search Console site property. [intent=etl availability=implemented stream=sitemap_details]
- sitemaps submit - Plan submitting a sitemap URL for a Search Console site property. [intent=reverse_etl availability=implemented write=submit_sitemap]; approval: Use reverse ETL plan -> preview -> approval -> execute. No raw HTTP body is accepted; the record must match writes.json.; risk: medium: submits a sitemap URL for a Search Console site property; requires reverse ETL plan and approval; flags: --site-url (non-empty), --feedpath (non-empty)
- sitemaps delete - Plan deleting a sitemap URL from a Search Console site property through destructive reverse ETL. [intent=reverse_etl availability=implemented write=delete_sitemap]; approval: Use reverse ETL plan -> preview -> approval -> typed destructive confirmation -> execute. Missing provider records are idempotent for HTTP 404.; risk: high: deletes a sitemap from a Search Console site property; requires reverse ETL plan, approval, and destructive confirmation; flags: --site-url (non-empty), --feedpath (non-empty)
- Search Analytics
- search-analytics by-date - Read Search Analytics rows grouped by date. [intent=etl availability=implemented stream=search_analytics_by_date]
- search-analytics by-country - Read Search Analytics rows grouped by date and country. [intent=etl availability=implemented stream=search_analytics_by_country]
- search-analytics by-device - Read Search Analytics rows grouped by date and device. [intent=etl availability=implemented stream=search_analytics_by_device]
- search-analytics by-page - Read Search Analytics rows grouped by date and page. [intent=etl availability=implemented stream=search_analytics_by_page]
- search-analytics by-query - Read Search Analytics rows grouped by date and query. [intent=etl availability=implemented stream=search_analytics_by_query]
- Typed Direct Reads
- direct url-inspection inspect - Run the official URL Inspection operation as a typed bounded direct read. [intent=direct_read availability=implemented operation=google-search-console.urlinspection_index_inspect]; risk: low: bounded Search Console JSON read; fixed endpoint, closed request body schema, 1 MiB response cap, and redacted URL-shaped fields; flags: --inspection-url (required, non-empty), --site-url (required, non-empty), --language-code, --page, --page-cursor
- direct mobile-friendly-test run - Run the official Mobile Friendly Test operation as a typed bounded direct read. [intent=direct_read availability=implemented operation=google-search-console.mobile_friendly_test_run]; risk: low: bounded Search Console JSON read; fixed endpoint, closed request body schema, 1 MiB response cap, and redacted URL/screenshot-shaped fields; flags: --url (required, non-empty), --request-screenshot, --page, --page-cursor
- Help topics:
- parity - Google's current Discovery document lists 11 unique Search Console operations. Five reach ETL streams, four reach typed reverse-ETL writes, and URL Inspection plus Mobile-Friendly Test reach typed bounded direct reads. There are no generic raw HTTP, body, query, binary, CDC, excluded, or planned operations.
Commands
Inspect as a manual
pm connectors inspect google-search-console
Inspect as structured JSON
pm connectors inspect google-search-console --json
Agent Rules
- Run pm connectors inspect google-search-console before creating credentials or plans.
- Use --json only when the caller needs structured output; use the manual for human-readable guidance.
- Never ask the user to paste secret values into chat.
- For reverse ETL writes, create a plan, show the preview, wait for explicit approval, then run with the approval token.
04 同仓库更多 Skills
recipe-preview-approve-reverse-etl
Preview and approve a reverse ETL plan safely.
★ 7
recipe-github-prs-to-warehouse
Sync GitHub pull requests into the local warehouse.
★ 7
pm-zoom
Zoom connector knowledge and safe action guide.
★ 7
pm-zonka-feedback
Zonka Feedback connector knowledge and safe action guide.
★ 7
pm-zoho-invoice
Zoho Invoice connector knowledge and safe action guide.
★ 7
pm-zoho-inventory
Zoho Inventory connector knowledge and safe action guide.
★ 7