Integrations/Google Search ConsoleData source

Google Search Console for AI agents

Connect Google Search Console once on clickd with read-only OAuth, and your AI agent can query your site’s real search impressions, clicks, positions, click-through rates and period-over-period traffic shifts directly inside Claude Code, Codex or Cursor.

1. Add all 16 skills to your repositorynpx skills add subinternal/clickd
2. Ask your agentPull clickd_queries and clickd_traffic for example.com, find our top 5 striking-distance pages in positions 4 to 20, and sharpen them in code.

For teams who want their coding agent driven by real Search Console impressions instead of guessed keyword volume.Connect MCPRead as .md

What breaks most often on Search Console

What clickd catches when it fetches the live URL the way Googlebot and AI crawlers do.

See the rulebook
  • Guessed third-party search volumeKeyword databases often report zero volume on the exact B2B and technical queries already sending your site impressions in Search Console.question-headings
  • Striking-distance pages left on page twoPages ranking in positions 4 to 20 already have Google’s trust for the topic and move fastest when titles, headings and internal links are tightened.title
  • Silent click decay on older guidesHigh-performing guides lose clicks over 60 to 90 days as competitors publish fresher answers or search snippets truncate.dated

The Search Console agentic SEO loop

Four steps your agent runs between your codebase and clickd’s live crawler.

  1. 01Claim & connect

    Verify your domain on clickd and grant read-only Google Search Console access in one OAuth step.

    Account -> Search Console
  2. 02Mine real queries

    Your agent calls clickd_queries and clickd_traffic over MCP to group queries by URL, position and CTR.

    clickd_queries
  3. 03Fix in your repo

    Your agent updates titles, opening 40 to 60 word answers, schema and internal links on the target routes.

    keyword-research
  4. 04Verify after deploy

    After you ship, clickd_rescan checks the live HTML and subsequent Search Console reads track position gains.

    clickd_rescan

Worked pattern

Your agent reads Search Console rows directly over MCP without exporting CSVs.

Sample MCP tool call and agent plan

Sample
// 1. Agent queries Search Console through clickd MCP
clickd_queries({ site: "example.com" })
// -> /services/roof-repair: 4,820 impressions, pos 6.4, CTR 1.8%
// -> /guides/hail-damage:   3,190 impressions, pos 11.2, CTR 0.9%

// 2. Agent checks period-over-period click changes
clickd_traffic({ site: "example.com" })
// -> Flags pages slipping in clicks so content-refresh updates them first

Prompts to run on Search Console

Copy any prompt into Claude Code, OpenAI Codex, Cursor or Windsurf.

  • Find striking-distance keywordsPull clickd_queries for example.com, list queries in positions 4 to 15 with the most impressions, and improve the matching pages in our repo.
  • Fix low-CTR page-one titlesFind pages on example.com ranking in positions 1 to 5 with below-average CTR in clickd_queries and rewrite their title tags and meta descriptions.
  • Recover slipping trafficUse clickd_traffic on example.com to find the 3 pages that lost the most clicks over the last 60 days and refresh them with content-refresh.

Skills to pair with Search Console

Included when you run npx skills add subinternal/clickd.

All 16 skills
  • Keyword researchFinds striking-distance keywords (positions 4 to 20), CTR gaps, cannibalized queries and competitor topic gaps using Google Search Console data and clickd, then maps each query to one page and one action.See skill
  • Content refreshFinds pages losing Search Console clicks or carrying stale facts, diagnoses whether the drop is snippet decay, a substance gap or internal overlap, updates the page in code, and checks live with clickd.See skill
  • Rank a pageRuns a campaign to move one page up for one search toward an aim, through five gates in order, each opened only by a proof from a read of the live site, with a weekly read-out and the campaign’s time to rank.See skill
  • On-page SEORewrites title tags, meta descriptions, single H1s, question headings, answer-first openings, image alt text and AI writing tells in your site’s templates and content files, checked live with clickd.See skill

Questions about Google Search Console & clickd

Can clickd or my AI agent change settings inside Google Search Console?
No. clickd requests read-only Search Console access to read impressions, clicks, positions and URLs for sites you claim. Neither clickd nor your agent can remove URLs, change sitemaps or alter ownership in Search Console.
Do I have to export CSV files from Search Console for my agent?
No. Once Search Console is connected to your claimed site on clickd, any agent connected to https://clickd.com/mcp queries fresh data directly with clickd_queries and clickd_traffic.
What if my site is brand new and has no Search Console history yet?
Start without Search Console: clickd_brief, clickd_rivals and clickd_gaps work on any public domain from day one using live crawls and competitor benchmarks.

Other integrations & stacks

All integrations
  • Next.jsTeams shipping on Next.js App Router or Pages Router with Claude Code, Codex or Cursor.Web framework
  • AstroTeams running marketing sites, docs and content hubs on Astro.Web framework
  • ShopifyShopify and Shopify Plus stores on Liquid themes or Hydrogen headless storefronts.Storefront & CMS
  • WordPressTeams managing custom WordPress block/classic themes, WooCommerce stores or headless WordPress.Storefront & CMS
  • WebflowMarketing and design teams running Webflow CMS sites alongside an AI assistant.Storefront & CMS
  • SvelteKitEngineering teams building web apps and marketing sites on SvelteKit and Svelte 5.Web framework
  • Lovable, Bolt, v0 & React SPAsFounders and developers shipping Vite, React SPA, Lovable, Bolt, v0 or Replit apps.App builder