ClawHub

Google Search Console

Query search performance, inspect indexing status, review sitemaps, and manage verified Search Console sites — powered by ClawLink.

Audits

Pass
ClawScanPass

Agentic behavior and permission review.

Static analysisPass

Pattern checks against bundled files.

VirusTotalPass

Multi-engine malware detections and file reputation.

Install

openclaw skills install google-search-console-seo

Google Search Console via ClawLink

Work with Google Search Console from chat — query search performance, inspect indexing status, review sitemaps, and manage verified sites.

Powered by ClawLink, an integration hub for OpenClaw that handles hosted connection flows and credentials so you don't need to configure Google Search Console API access yourself.

Quick start

  1. Install the verified ClawLink plugin: openclaw plugins install clawhub:clawlink-plugin
  2. Start a fresh OpenClaw chat if the plugin was just installed and ClawLink tools are not visible yet
  3. If ClawLink is not configured, call clawlink_begin_pairing
  4. Tell the user to open the returned pairing URL, sign in to ClawLink if needed, and approve the device
  5. After the user confirms approval, call clawlink_get_pairing_status
  6. Tell the user to connect Google Search Console at claw-link.dev/dashboard?add=google-search-console
  7. When the user confirms Google Search Console is connected, call clawlink_list_integrations and then clawlink_list_tools with the google-search-console integration slug

Setup details

Installing the plugin

If the ClawLink plugin is not installed yet, tell the user to run:

openclaw plugins install clawhub:clawlink-plugin

If the current chat started before the plugin was installed and ClawLink tools are still unavailable, tell the user to start a fresh chat so OpenClaw reloads the plugin tool catalog.

Pairing ClawLink

If ClawLink reports that the plugin is not configured, the plugin has not been paired with the user's ClawLink account yet.

  1. Call clawlink_begin_pairing.
  2. Tell the user to open the returned pairing URL in their browser.
  3. The user signs in to ClawLink if needed and approves the OpenClaw device.
  4. After the user confirms approval, call clawlink_get_pairing_status to finish local setup.

The resulting device credential is stored locally in OpenClaw's plugin config and is only sent to claw-link.dev. The user should not paste raw credentials into chat.

Connecting Google Search Console

Tell the user to open https://claw-link.dev/dashboard?add=google-search-console and connect Google Search Console there. The page opens the add-connection panel filtered to Google Search Console. ClawLink's hosted page runs the Google account connection flow — the user clicks through Google sign-in and consent. When they confirm it is done, call clawlink_list_integrations to verify, then call clawlink_list_tools with integration google-search-console.

Using Google Search Console tools

ClawLink provides tools dynamically based on what the user has connected. You do not need to know tool names or schemas in advance.

Discovery

  1. Call clawlink_list_integrations to confirm Google Search Console is connected.
  2. Call clawlink_list_tools with integration google-search-console.
  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

  1. Call clawlink_describe_tool before using an unfamiliar tool, before any write, or when the request is ambiguous.
  2. Use the returned schema, whenToUse, askBefore, safeDefaults, examples, and followups.
  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, then confirm with the user.
  5. Execute with clawlink_call_tool.
  6. If it fails, report the real error. Do not invent results or restate the failure as a missing capability unless the live catalog supports that conclusion.

What you can do

Typical Google Search Console tasks (actual availability depends on the user's connected account, permissions, scopes, and current ClawLink tool catalog):

  • List verified Search Console sites
  • Query clicks, impressions, CTR, and average position over time
  • Break down search performance by page, query, country, device, or date when supported
  • Inspect a URL for indexing status and reported issues
  • List or inspect sitemap metadata
  • Submit a sitemap after confirmation
  • Add or remove a verified site after confirmation

Rules

  • Always use ClawLink tools for Google Search Console. Do not ask the user for separate Google credentials.
  • Do not claim a capability is missing without checking the live ClawLink catalog in the current turn.
  • Do not invent slash commands or ask the user to paste raw credentials.
  • Ask for confirmation before submitting sitemaps or changing site verification state.
  • If Google Search Console is not connected, direct the user to https://claw-link.dev/dashboard?add=google-search-console.
  • Never echo or repeat the user's ClawLink credential.

Resources