Google Search Console

Google Search Console API integration with managed OAuth. Query search performance analytics, inspect URL indexing status, review sitemaps, and manage verifi...

installs

stars

karma

SkillRank score ↗

8.3/ 10

evaluated by implexa, claude-haiku-4-5 · 2026-06-07

google-search-console-seo provides oauth-managed access to search console apis for seo monitoring. users can query search analytics, inspect url indexing status, manage verified sites, and submit sitemaps via clawlink proxying.

structure

9.0

trigger phrases

8.0

procedure

9.0

edge cases

7.0

documentation

8.0

strengths

view original SKILL.md from clawhubclick to expand

---
name: google-search-console-seo
description: Google Search Console API integration with managed OAuth. Query search performance analytics, inspect URL indexing status, review sitemaps, and manage verified site properties. Use this skill when users want to monitor SEO performance or troubleshoot indexing issues.
---

# Google Search Console

![Google Search Console](https://raw.githubusercontent.com/ClawLink-HQ/clawlink/main/public/images/brand-logos/google-search-console.png)

Access Google Search Console via the Search Console API with managed OAuth authentication. Query search performance, inspect indexing status, review sitemaps, and manage verified sites.

This skill uses [ClawLink](https://claw-link.dev/?utm_source=clawhub&utm_medium=referral&utm_content=google-search-console-seo) for hosted connection flows and credentials so you do not need to configure Google Search Console API access yourself.

### Setup in 3 Steps

| Step 1: Install | Step 2: Pair Account | Step 3: Connect Search Console |
|:---:|:---:|:---:|
| ![Install](https://raw.githubusercontent.com/ClawLink-HQ/clawlink/main/public/images/pairing/initialstep_1.gif) | ![Pair](https://raw.githubusercontent.com/ClawLink-HQ/clawlink/main/public/images/approve_process.gif) | *App-specific connection GIF coming soon* |
| Run the install command in OpenClaw | Sign in and approve the device | Open the dashboard and connect Google Search Console |

## How It Works

```
┌─────────────────┐     ┌──────────────┐     ┌──────────────────┐
│   OpenClaw      │────▶│   ClawLink   │────▶│   Google Search  │
│   (User Chat)   │     │   (OAuth)    │     │   Console API    │
└─────────────────┘     └──────────────┘     └──────────────────┘
         │                       │                       │
         │  1. Install Plugin    │                       │
         │  2. Pair Device       │                       │
         │  3. Connect GSC       │                       │
         │                       │  4. Secure Token       │
         │                       │  5. Proxy Requests    │
         │                       │                       │
         ▼                       ▼                       ▼
   ┌──────────┐           ┌──────────┐           ┌──────────┐
   │  SKILL   │           │ Dashboard│           │  Search  │
   │  File    │           │ Auth     │           │  Console │
   └──────────┘           └──────────┘           └──────────┘
```

## Install

Install the verified ClawLink plugin from ClawHub. After the user confirms, complete the full setup so ClawLink tools are visible in the next OpenClaw chat.

```bash
openclaw plugins install clawhub:clawlink-plugin
openclaw config set tools.alsoAllow '["clawlink-plugin"]' --strict-json
openclaw gateway restart
```

Then tell the user: "OpenClaw has been restarted. Send `/new` as a standalone message to start a fresh chat, then ask for Google Search Console again."

## Quick Start

```bash
# List verified sites
clawlink_call_tool --tool "google_search_console_list_sites" --params '{}'

# Query search analytics
clawlink_call_tool --tool "google_search_console_search_analytics_query" --params '{"site_url": "https://example.com/", "start_date": "2024-01-01", "end_date": "2024-01-31"}'

# Inspect a URL
clawlink_call_tool --tool "google_search_console_inspect_url" --params '{"site_url": "https://example.com/", "inspection_url": "https://example.com/page/"}'
```

## Authentication

All Google Search Console tool calls are authenticated automatically by ClawLink using the user's connected Google account.

**No API key is required in chat.** ClawLink stores the OAuth token securely and injects it into every Search Console API request on the user's behalf.

### Getting Connected

1. Install the ClawLink plugin (see Install above).
2. Pair the plugin with `clawlink_begin_pairing` if it is not configured yet.
3. Open https://claw-link.dev/dashboard?add=google-search-console and connect Google Search Console.
4. Call `clawlink_list_integrations` to verify the connection is active.

## Connection Management

### List Connections

```bash
clawlink_list_integrations
```

**Response:** Returns all connected integrations. Look for `google-search-console` in the list.

### Verify Connection

```bash
clawlink_list_tools --integration google-search-console
```

**Response:** Returns the live tool catalog for Google Search Console.

### Reconnect

If Google Search Console tools are missing or the connection shows an error:

1. Direct the user to https://claw-link.dev/dashboard?add=google-search-console
2. After they confirm, call `clawlink_list_integrations` to verify
3. Then call `clawlink_list_tools --integration google-search-console`

## Security & Permissions

- Access is scoped to sites verified in the connected Google Search Console account.
- **All write operations require explicit user confirmation.** Before executing any site addition, removal, or sitemap submission, confirm the target and intended effect with the user.
- Destructive actions (delete site) are marked as high-impact and must be confirmed.

## Tool Reference

### Site Management

| Tool | Description | Mode |
|------|-------------|------|
| `google_search_console_list_sites` | List all verified sites (URL-prefix and domain properties) owned by the user | Read |
| `google_search_console_get_site` | Get details and permission level for a specific site | Read |
| `google_search_console_add_site` | Register a new site property in Search Console | Write |
| `google_search_console_delete_site` | Remove a site from Search Console tracking | Write |

### Search Analytics

| Tool | Description | Mode |
|------|-------------|------|
| `google_search_console_search_analytics_query` | Query clicks, impressions, CTR, and position metrics | Read |

### URL Inspection

| Tool | Description | Mode |
|------|-------------|------|
| `google_search_console_inspect_url` | Inspect a specific URL for indexing status and issues | Read |

### Sitemap Management

| Tool | Description | Mode |
|------|-------------|------|
| `google_search_console_list_sitemaps` | List all sitemaps submitted for a site | Read |
| `google_search_console_get_sitemap` | Get sitemap metadata (submitted/indexed counts, errors, timestamps) | Read |
| `google_search_console_submit_sitemap` | Submit or resubmit a sitemap for a verified property | Write |

## Code Examples

### List verified sites

```bash
clawlink_call_tool --tool "google_search_console_list_sites" \
  --params '{}'
```

### Query search analytics for a date range

```bash
clawlink_call_tool --tool "google_search_console_search_analytics_query" \
  --params '{
    "site_url": "https://example.com/",
    "start_date": "2024-01-01",
    "end_date": "2024-01-31",
    "dimensions": ["query", "page"]
  }'
```

### Query analytics filtered by country

```bash
clawlink_call_tool --tool "google_search_console_search_analytics_query" \
  --params '{
    "site_url": "https://example.com/",
    "start_date": "2024-01-01",
    "end_date": "2024-01-31",
    "dimensions": ["country"],
    "row_limit": 50
  }'
```

### Inspect a URL for indexing issues

```bash
clawlink_call_tool --tool "google_search_console_inspect_url" \
  --params '{
    "site_url": "https://example.com/",
    "inspection_url": "https://example.com/important-page/"
  }'
```

### Submit a sitemap

```bash
clawlink_call_tool --tool "google_search_console_submit_sitemap" \
  --params '{
    "site_url": "https://example.com/",
    "feedpath": "/sitemap.xml"
  }'
```

### Add a new site

```bash
clawlink_call_tool --tool "google_search_console_add_site" \
  --params '{
    "site_url": "https://newsite.example.com/"
  }'
```

## Discovery Workflow

1. Call `clawlink_list_integrations` to confirm Google Search Console is connected.
2. Call `clawlink_list_tools --integration google-search-console` to see the live catalog.
3. Treat the returned list as the source of truth. Do not guess or assume what tools exist.
4. If the user describes a capability but the exact tool is unclear, call `clawlink_search_tools` with a short query and integration `google-search-console`.
5. If no Google Search Console tools appear, direct the user to https://claw-link.dev/dashboard?add=google-search-console.

## Execution Workflow

```
┌─────────────────────────────────────────────────────────────┐
│  READ OPERATIONS (Safe)                                     │
│  list → get → query → inspect → call                        │
│                                                             │
│  Example: List sites → Query analytics → Show results       │
└─────────────────────────────────────────────────────────────┘
                              │
                              ▼
┌─────────────────────────────────────────────────────────────┐
│  WRITE OPERATIONS (Require Confirmation)                    │
│  describe → preview → confirm → call                        │
│                                                             │
│  Example: Describe tool → Preview → User approves            │
│           → Execute sitemap submission                      │
└─────────────────────────────────────────────────────────────┘
```

1. For unfamiliar tools, ambiguous requests, or any write action, call `clawlink_describe_tool` first.
2. Use the returned guidance, schema, `whenToUse`, `askBefore`, `safeDefaults`, `examples`, and `followups` to shape the call.
3. Prefer listing sites, querying analytics, and inspecting URLs before writes.
4. For sitemap submissions, site additions or removals, or anything marked as requiring confirmation, call `clawlink_preview_tool` first.
5. Execute with `clawlink_call_tool`. Pass confirmation only after the preview matches the user's intent.
6. If the tool call fails, report the real error. Do not invent results or restate the failure as a missing capability unless the live catalog supports that conclusion.

## Notes

- The `site_url` parameter must exactly match the property as returned by `list_sites` — include protocol, subdomain, and trailing slash where applicable.
- `search_analytics_query` only returns URLs with at least one impression; missing rows do not confirm non-indexing.
- Position is an impression-weighted average rank across all queries.
- Sitemap metadata (`errors`, `warnings`, `submitted`, `indexed`) may be returned as strings — cast to integers before comparisons.
- Results may reflect cached data lagging real changes by several days.
- High-volume inspect_url usage can trigger 429 quota errors — limit to priority URLs.
- Numeric fields in sitemap responses can lag several days after submission.

## Error Handling

| Status / Error | Meaning |
|----------------|---------|
| Tool not found | The tool name does not exist in the current catalog. Verify with `clawlink_list_tools --integration google-search-console`. |
| Missing connection | Google Search Console is not connected. Direct the user to https://claw-link.dev/dashboard?add=google-search-console. |
| `NOT_VERIFIED` | Site is not verified in Search Console. Complete verification first. |
| `FORBIDDEN` | No permission level for the requested site. |
| `INVALID_ARGUMENT` | Invalid parameter or missing required field. Review the tool schema with `clawlink_describe_tool`. |
| Write rejected | User did not confirm a write action. Always confirm before executing writes. |

### Troubleshooting: Tools Not Visible

1. Check that the ClawLink plugin is installed:
   ```bash
   openclaw plugins list
   ```
2. If the plugin is installed but tools are missing, tell the user to send `/new` as a standalone message to reload the catalog.
3. If a fresh chat does not help, run:
   ```bash
   openclaw config set tools.alsoAllow '["clawlink-plugin"]' --strict-json
   openclaw gateway restart
   ```
4. After restart, tell the user to send `/new` again and retry.

### Troubleshooting: Invalid Tool Call

1. Ensure the integration slug is exactly `google-search-console`.
2. Use `clawlink_describe_tool` to verify parameter names and types before calling.
3. For write operations, always call `clawlink_preview_tool` first.

## Resources

- [Search Console API Overview](https://developers.google.com/webmaster-tools/search-console-api-original)
- [Search Analytics Reference](https://developers.google.com/webmaster-tools/search-console-api-original/v3/searchanalytics)
- [Sites Reference](https://developers.google.com/webmaster-tools/search-console-api-original/v3/sites)
- [Sitemaps Reference](https://developers.google.com/webmaster-tools/search-console-api-original/v3/sitemaps)
- ClawLink: https://claw-link.dev/?utm_source=clawhub&utm_medium=referral&utm_content=google-search-console-seo
- ClawLink Docs: https://docs.claw-link.dev/openclaw
- ClawLink Verification: https://claw-link.dev/verify

---

**Powered by [ClawLink](https://claw-link.dev/?utm_source=clawhub&utm_medium=referral&utm_content=google-search-console-seo)** — an integration hub for OpenClaw

![ClawLink Logo](https://raw.githubusercontent.com/ClawLink-HQ/clawlink/main/public/images/logo/link_logo_black_small.png)

don't have the plugin yet? install it then click "run inline in claude" again.

extracted intent, inputs with rate limits and edge cases, restructured procedure into numbered steps with explicit inputs/outputs, added decision points for write confirmations and error handling, documented output formats and success signals, and added troubleshooting workflow.

Google Search Console

Item: Google Search Console
Rating: 8.3
Author: Implexa

Access Google Search Console via the Search Console API with managed OAuth authentication. Query search performance, inspect indexing status, review sitemaps, and manage verified sites.

This skill uses ClawLink for hosted connection flows and credentials, so you don't need to configure Google Search Console API access yourself.

intent

use this skill when users need to monitor SEO performance, troubleshoot indexing issues, check search analytics (clicks, impressions, CTR, position), inspect URL indexing status, or manage sitemaps and site properties in Google Search Console. the skill handles oauth authentication through ClawLink's managed credential system, so no manual API key setup is required.

inputs

external connection: Google Search Console via ClawLink

connection type: oauth 2.0 managed by ClawLink
setup: install the ClawLink plugin, pair your device, then connect Google Search Console at https://claw-link.dev/dashboard?add=google-search-console
no api key needed: clawlink stores and injects the oauth token automatically
permissions: access scoped to sites verified in your connected google search console account
environment: requires openclaw with clawlink-plugin installed

required parameters vary by tool:

site_url: exact property url as returned by list_sites (include protocol, subdomain, trailing slash)
start_date, end_date: date range for analytics queries (format: YYYY-MM-DD)
inspection_url: full url to inspect for indexing status
feedpath: sitemap path relative to site root (e.g., /sitemap.xml)
dimensions: breakdown fields for analytics (query, page, country, device, etc.)

rate limits and constraints:

high-volume url inspection (429 quota errors): limit inspect_url calls to priority urls only
analytics data: reflects cached data lagging real changes by several days
search_analytics_query: only returns urls with at least one impression; missing rows do not confirm non-indexing
sitemap metadata: numeric fields (errors, warnings, submitted, indexed) may lag several days after submission

procedure

verify clawlink installation and google search console connection
- input: none
- call clawlink_list_integrations
- output: integration list; confirm google-search-console is present
- if not present: direct user to https://claw-link.dev/dashboard?add=google-search-console
discover available tools
- input: none
- call clawlink_list_tools --integration google-search-console
- output: live tool catalog for google search console
- treat returned list as source of truth; do not guess or assume tools exist
for read operations (list/query/inspect): execute directly
- input: operation type (list_sites, search_analytics_query, inspect_url, list_sitemaps, etc.) and required parameters
- examples:
  - list verified sites: clawlink_call_tool --tool "google_search_console_list_sites" --params '{}'
  - query analytics: clawlink_call_tool --tool "google_search_console_search_analytics_query" --params '{"site_url": "https://example.com/", "start_date": "2024-01-01", "end_date": "2024-01-31"}'
  - inspect url: clawlink_call_tool --tool "google_search_console_inspect_url" --params '{"site_url": "https://example.com/", "inspection_url": "https://example.com/page/"}'
- output: raw api response (sites, analytics rows, indexing status, sitemap metadata)
for write operations (add/delete site, submit sitemap): preview then confirm
- input: operation type and parameters
- first: call clawlink_describe_tool --tool <tool_name> to understand schema and safety requirements
- next: call clawlink_preview_tool --tool <tool_name> --params <params> to show user what will happen
- output from preview: detailed description of the intended action (e.g., "remove example.com from search console tracking")
- only after user confirms the preview: call clawlink_call_tool --tool <tool_name> --params <params>
- output from call: success status or error message
handle tool call failures
- input: error response from tool call
- check error message against error reference table (see decision points)
- output: clear error explanation and recovery steps
- do not invent results or restate failure as missing capability unless live catalog confirms it
troubleshoot missing tools
- input: user reports tools not visible or connection down
- step 1: run openclaw plugins list to confirm clawlink-plugin is installed
- step 2: if installed but tools missing, tell user to send /new as standalone message to reload catalog
- step 3: if still missing, run openclaw config set tools.alsoAllow '["clawlink-plugin"]' --strict-json then openclaw gateway restart
- step 4: tell user to send /new again and retry
- output: tools visible in next chat or error message with root cause

decision points

if user wants to list sites or query analytics:

execute read operation directly via clawlink_call_tool
no confirmation needed

if user wants to add a site, delete a site, or submit a sitemap:

first call clawlink_describe_tool to review schema and safety guidance
then call clawlink_preview_tool to show the user exactly what will happen
only execute clawlink_call_tool after explicit user confirmation
high-impact actions (delete_site) must be confirmed in plain language

if search_analytics_query returns empty rows:

this does not confirm non-indexing; it only means zero impressions in the date range
suggest expanding the date range or checking inspect_url instead

if inspect_url returns 429 quota error:

pause and inform user that quota is exhausted
recommend checking fewer urls or focusing on priority pages
resume after quota window resets (typically hourly)

if site_url parameter doesn't match a verified property:

call clawlink_call_tool --tool "google_search_console_list_sites" to show user the exact property names
require user to pick from the returned list
do not guess or modify the url format

if google search console connection is missing or expired:

direct user to https://claw-link.dev/dashboard?add=google-search-console
after user completes oauth flow, call clawlink_list_integrations to verify
then call clawlink_list_tools --integration google-search-console to refresh tool catalog

if tool call returns FORBIDDEN or NOT_VERIFIED error:

FORBIDDEN: user lacks permission for that site. suggest listing sites to see what they own.
NOT_VERIFIED: site is not verified in search console. direct user to complete verification first.

if parameter validation fails (INVALID_ARGUMENT):

call clawlink_describe_tool --tool <tool_name> to show user the correct schema
ensure all required fields are present and match the specified type (string, date, array, etc.)

output contract

for list operations:

returns array of site properties or sitemaps with metadata (url, property type, verification status, submitted/indexed counts, error counts)
data format: json array of objects
location: printed to stdout as raw api response

for search_analytics_query:

returns array of rows, each containing: query (string), page (string), country (string), device (string), position (float), clicks (int), impressions (int), ctr (float)
data format: json array of objects
position is impression-weighted average rank; rows omitted if zero impressions
results reflect cached data lagging several days behind real changes

for inspect_url:

returns indexing status (indexed, not_indexed, not_submitted, crawled_not_indexed), last crawl time, coverage state, mobile usability, page experience signals, rich results, amp status
data format: json object
location: printed to stdout

for sitemap operations:

list_sitemaps returns array of sitemap entries (path, submitted date, indexed count, error count, warning count)
get_sitemap returns single sitemap metadata object
submit_sitemap returns success status or error message
data format: json
numeric fields may be returned as strings; cast to integers before comparisons

for site add/delete:

returns success confirmation with site url and action (added / removed)
data format: json object with status field
write operations require prior user confirmation

outcome signal

read operations succeeded:

stdout shows json response with expected data (list of sites, analytics rows, indexing details, sitemap metadata)
no error message
user can immediately see results and act on them

write operations succeeded:

stdout shows success message confirming the action (e.g., "site added", "sitemap submitted", "site removed")
no error message
user receives confirmation that matches the preview they approved

connection or setup issue:

error message clearly states problem (missing integration, tool not found, invalid parameter, quota exceeded, forbidden, not_verified)
user sees actionable next step (reconnect at dashboard url, call clawlink_list_tools, verify site, reduce request rate, etc.)
no results are returned; operation halted cleanly

troubleshooting succeeded:

plugins list shows clawlink-plugin installed
fresh chat (/new) shows clawlink tools in the tool picker
clawlink_list_tools returns the full google-search-console catalog
next tool call executes without "tool not found" error

Google Search Console

related skills

Google Search Console

intent

inputs

procedure

decision points

output contract

outcome signal