Ira Bodnar··Updated ·12 min read

Claude Skills for Google Search Console: 9 SKILL.md Files

Quick answer: Save each Search Console routine as a Claude skill that names the tool to call and the table to return. Ryze AI is the best Claude connector for running these skills on live Search Console data, with one caveat: it has no tool to request indexing.

Below: 9 SKILL.md files grouped by job, install steps for Claude Code and claude.ai, and how to run them on live Search Console data.

Ryze AI · SEO Starter

Search Console skills on live data

  • 3-day free trial, $129 a month
Start free trial

Used by 2,000+ marketers

Uber Eats logoadidas logoDuolingo logoMGM Resorts logoWharton logoLendingClub logoNorton logoEventbrite logoHuel logoTogether AI logoghd logoHack The Box logo

The 9 Claude skills for Google Search Console at a glance

Eight skills only read data. Skill 09 submits or removes a sitemap, and it stops for your confirmation before it does.

  1. 01Striking distance pagesPages ranking just outside the top results

    Connector tools it calls: runRawSearchAnalytics

    Cadence: Weekly

  2. 02Low CTR queriesHigh impressions, few clicks

    Connector tools it calls: runRawSearchAnalytics

    Cadence: Monthly

  3. 03Cannibalization checkQueries answered by more than one page

    Connector tools it calls: runRawSearchAnalytics

    Cadence: Quarterly

  4. 04Click drop diagnosisWhich pages and queries lost clicks

    Connector tools it calls: runRawSearchAnalytics

    Cadence: When traffic falls

  5. 05New query finderQueries that appeared this month

    Connector tools it calls: runRawSearchAnalytics

    Cadence: Monthly

  6. 06Segment splitCountry, device, search appearance and result type

    Connector tools it calls: runRawSearchAnalytics

    Cadence: Monthly

  7. 07URL index checkIndex status of the URLs you name

    Connector tools it calls: inspectUrl

    Cadence: After publishing

  8. 08Sitemap healthErrors, warnings and indexed counts

    Connector tools it calls: listSites, listSitemaps, getIndexationSummary

    Cadence: Monthly

  9. 09Sitemap submit and clean-upResubmit or remove a sitemap

    Connector tools it calls: listSitemaps, submitSitemap, deleteSitemap

    Cadence: After site changes

Tool names are from the Ryze AI connector, shortened here by dropping the google_search_console__ prefix.

What are Claude skills for Google Search Console?

A Claude skill for Google Search Console is a saved SKILL.md file that tells Claude which report to run and what table to hand back. Per Anthropic's Agent Skills docs, the file starts with a name and a description, and Claude loads the rest when a request matches the description.

The name allows up to 64 lowercase letters, numbers and hyphens and cannot contain the words claude or anthropic, so every skill here starts with gsc. The description, up to 1,024 characters, says what the skill does and when to use it.

  1. What it is

    One-off prompt
    A question in chat
    Skill
    A saved file with a fixed routine and output
    Search Console connection
    Tools Claude uses to query the property

  2. Setup

    One-off prompt
    None
    Skill
    Save once per Claude app
    Search Console connection
    One Google sign-in, then pick the Site

  3. Same result each run

    One-off prompt
    No
    Skill
    Same steps each run
    Search Console connection
    Depends on the prompt or skill

Without a connection, export a Performance report from Search Console, paste the rows into the chat and skills 01 to 06 work on that text. For the on-site behavior side of the same pages, see Claude skills for Google Analytics.

How to install the skills in Claude Code and claude.ai

Claude Code

Save each block as ~/.claude/skills/<skill-name>/SKILL.md for yourself, or .claude/skills/<skill-name>/SKILL.md in a project to share it with the team. Type /gsc-striking-distance to run one by name (Claude Code skills docs).

claude.ai

Zip each skill folder and upload it as a custom skill. Anthropic lists this on the Pro, Max, Ultra, Team and Enterprise plans with code execution enabled.

Connect the data

Add the Ryze AI connector at https://connector.get-ryze.ai/mcp in Claude (Ryze AI help center), connect Google Search Console in the Ryze AI app and save the Site.

Anthropic states that custom skills do not sync across surfaces: a skill uploaded to claude.ai is not in Claude Code, and the reverse. Anthropic also advises using skills only from sources you trust, because a skill can direct Claude to call tools. Read each file before you save it. The skills here call only Search Console tools. For the connection steps in detail, see how to connect Claude to Google Search Console.

Ranking skills: find pages that can earn more clicks

These three skills only read. They use one Search Analytics tool, which returns clicks, impressions, CTR and position by query, page, country, device, search appearance or date, up to 25,000 rows per request. Google states that the API returns top rows rather than guaranteeing every row.

01. Striking distance pages

Finds query and page pairs that already earn impressions at positions just past the first page, which are the cheapest pages to improve.

SKILL.md
--- name: gsc-striking-distance description: Lists Search Console query and page pairs ranking at positions 8 to 20 with real impressions. Use when asked which pages to improve first or for a weekly SEO check. --- # Search Console striking distance pages Call google_search_console__listSites if the user has not named a property, then call google_search_console__runRawSearchAnalytics for the last 28 days with the query and page dimensions. Steps: 1. Keep rows with an average position from 8 to 20 and at least 100 impressions. 2. Sort by impressions, highest first. Keep the top 20. 3. For each row, give one concrete change: title, a missing section, or an internal link to the page. Output: a table of page, query, position, impressions, clicks and the suggested change. Say how many rows the tool returned. Change nothing.

Use it when: you start the week and want a short list of pages worth editing.

02. Low CTR queries

Finds queries where the page is seen often and clicked rarely, which usually points at a weak title or snippet.

SKILL.md
--- name: gsc-low-ctr description: Finds Search Console queries with many impressions and a low click-through rate for their position. Use when asked to improve titles or meta descriptions. --- # Search Console low CTR queries Call google_search_console__runRawSearchAnalytics for the last 3 months with the query and page dimensions. Steps: 1. Keep rows with at least 200 impressions and an average position of 10 or better. 2. Compare each row's CTR with the median CTR of rows at a similar position in the same result. 3. List the rows well below that median. 4. Draft 2 title options per page, under 60 characters, that match the query's wording. Output: a table of page, query, position, CTR, median CTR for that position and the two titles. Do not edit anything.

Use it when: you plan a round of title and snippet edits. The median comes from your own rows, so no outside benchmark is used.

03. Cannibalization check

Finds queries that several of your pages receive impressions for, so you can decide which page should own each one.

SKILL.md
--- name: gsc-cannibalization description: Finds Search Console queries where two or more pages of the same site get impressions. Use for a content audit or when rankings swap between pages. --- # Search Console cannibalization check Call google_search_console__runRawSearchAnalytics for the last 3 months with the query and page dimensions. Steps: 1. Group rows by query. Keep queries with 2 or more pages and at least 100 impressions in total. 2. For each query, show every page with its clicks, impressions and position. 3. Mark the page with the most clicks as the likely owner. Output: one block per query with the pages ranked by clicks, and a suggestion for each: merge, redirect, or differentiate the page. Say that pages swapping positions are a sign, not proof.

Use it when: you publish many articles on a topic, or a ranking jumps between two URLs.

Diagnosis skills: explain changes and split the data

Search Console data arrives 2 to 3 days late and covers up to 16 months of history, so each skill ends its date range a few days before today. All three skills only read.

04. Click drop diagnosis

Compares two periods and names the pages and queries that lost the most clicks.

SKILL.md
--- name: gsc-click-drop description: Compares two periods of Search Console data and lists the pages and queries that lost clicks. Use when asked why organic traffic fell. --- # Search Console click drop diagnosis Use the last 28 days and the 28 days before them. End both ranges 3 days before today, because the data is 2 to 3 days late. 1. Call google_search_console__runRawSearchAnalytics for each period with the page dimension. 2. Call google_search_console__runRawSearchAnalytics for each period with the query dimension. 3. Compute the change in clicks, impressions, CTR and position per page and per query. 4. For the 10 biggest losers, say whether impressions fell (visibility) or CTR fell (snippet), or position fell (ranking). Output: two tables (pages, queries) and 3 sentences. Do not name a cause the data cannot show, such as an algorithm update.

Use it when: a traffic report shows a drop and you need the pages to look at first.

05. New query finder

Lists queries that showed your site this month and did not appear in the month before, which feeds the next article topics.

SKILL.md
--- name: gsc-new-queries description: Lists Search Console queries that are new this month compared with the previous month. Use for content ideas or a monthly SEO recap. --- # Search Console new query finder Call google_search_console__runRawSearchAnalytics twice with the query dimension: the last 28 days and the 28 days before them. End both ranges 3 days before today. Steps: 1. Keep queries present in the recent pull and absent from the earlier one. 2. Sort by impressions. Keep the top 25. 3. Group them by topic and mark any that look like a question a page should answer. Output: grouped list with impressions and average position. Note that rows beyond the top rows returned may be missing.

Use it when: you plan next month's articles.

06. Segment split

Breaks the same period down by country, device and search appearance, and repeats it for another result type such as image, video, news or Discover.

SKILL.md
--- name: gsc-segment-split description: Splits Search Console clicks and impressions by country, device and search appearance, and by result type. Use when asked where traffic comes from or whether mobile differs from desktop. --- # Search Console segment split Call google_search_console__runRawSearchAnalytics for the last 28 days (end 3 days before today) once per dimension: country, device, search appearance. Then repeat the device query for each result type the user asks about: web, image, video, news or Discover. Output: one small table per dimension with clicks, impressions, CTR and position. Flag any segment whose CTR or position differs a lot from the site average, and say the data is for the property the user named.

Use it when: a country or device looks off, or you want to know whether Discover or image search sends visits.

Index and sitemap skills: check what Google has

URL Inspection checks one URL at a time, and index coverage for a whole site is not available through the API. These skills work from the URLs you give or from the sitemap lists. Skills 07 and 08 only read. Skill 09 changes Search Console, so it shows the change and waits.

07. URL index check

Inspects each URL you name and reports coverage, verdict, last crawl, canonical, indexing state, mobile usability and rich results.

SKILL.md
--- name: gsc-url-index-check description: Checks the Google index status of URLs the user names, one by one. Use after publishing or when a page does not show in search. --- # Search Console URL index check For each URL the user gives (at most 10), call google_search_console__inspectUrl. Report per URL: verdict, coverage state, last crawl time, Google-selected canonical versus the declared canonical, indexing state, mobile usability and rich results status. Output: a table with one row per URL and a one-line next step. This tool cannot request indexing, so do not say it did. Tell the user to use the URL Inspection tool in Search Console for that.

Use it when: you published a batch of pages and want to know which are indexed. Google's API shows the version in its index and cannot test a live URL.

08. Sitemap health

Lists the properties you can reach, then each property's sitemaps with errors, warnings and submitted versus indexed counts.

SKILL.md
--- name: gsc-sitemap-health description: Reports Search Console sitemap errors, warnings and submitted versus indexed counts for a property. Use for a monthly indexation check. --- # Search Console sitemap health 1. Call google_search_console__listSites and confirm which property to check. 2. Call google_search_console__listSitemaps for it. 3. Call google_search_console__getIndexationSummary for it. Output: a table of sitemap, last submitted, last downloaded, errors, warnings, submitted and indexed counts. Flag sitemaps with errors, sitemaps not downloaded recently, and a large gap between submitted and indexed. Change nothing.

Use it when: you run a monthly indexation check, or after a site migration.

09. Sitemap submit and clean-up

Resubmits a sitemap or removes a stale or duplicate one, after showing exactly what will change.

SKILL.md
--- name: gsc-sitemap-fix description: Submits, resubmits or removes a sitemap in Search Console after confirmation. Use when a sitemap changed or an old one is still listed. --- # Search Console sitemap submit and clean-up 1. Call google_search_console__listSitemaps and show the current list. 2. Ask which sitemap to submit, resubmit or remove. Show the action and the property. Stop here. 3. After the user confirms, call google_search_console__submitSitemap or google_search_console__deleteSitemap for that sitemap only. 4. Call google_search_console__listSitemaps again and show the result. Removing a sitemap only removes it from Search Console; the file on the site stays. Say so before every removal.

Use it when: you launch a new sitemap or retire an old one. To make Claude itself ask before every write, set the write and delete tools to Needs approval, as described under live data below.

Quick prompts: no skill file needed

For a one-time question, a plain prompt is enough once Claude can reach the property.

Prompt
Which Search Console properties can I access, and what permission level do I have on each?
Prompt
Show my top 15 queries by clicks over the last 28 days, with CTR and average position.
Prompt
Inspect these 3 URLs and tell me which Google-selected canonical differs from the one I declared.
Prompt
List my sitemaps with errors or warnings and show me what you would remove before you remove anything.

If an answer looks off, ask Claude which tool it called and for which dates.

How to run the skills on live Search Console data

A skill only describes the routine; Claude needs a connection to run it. The Ryze AI connector gives Claude 7 Google Search Console tools: 5 read, 1 write and 1 delete.

  1. listSites

    What it does
    Lists every property the connected login can access, with permission levels
    Access
    Read
    Used by
    Skills 01, 08

  2. runRawSearchAnalytics

    What it does
    Search Analytics by query, page, country, device, search appearance or date for web, image, video, news or Discover, up to 25,000 rows per request
    Access
    Read
    Used by
    Skills 01 to 06

  3. inspectUrl

    What it does
    Index status of one URL: coverage, verdict, last crawl, canonical, indexing state, mobile usability, rich results
    Access
    Read
    Used by
    Skill 07

  4. listSitemaps

    What it does
    Sitemaps with last submitted and downloaded dates, errors, warnings, submitted and indexed counts
    Access
    Read
    Used by
    Skills 08, 09

  5. getIndexationSummary

    What it does
    Sitemap summary: sitemaps, submitted URLs, errors, warnings, pending items
    Access
    Read
    Used by
    Skill 08

  6. submitSitemap

    What it does
    Submits or resubmits a sitemap
    Access
    Write
    Used by
    Skill 09

  7. deleteSitemap

    What it does
    Removes a sitemap from Search Console; the file on the site is untouched
    Access
    Delete
    Used by
    Skill 09

Setup in the Ryze AI app: open Integrations, find Google Search Console, click Connect, sign in to Google and keep every requested permission checked. Then check the Site (Ryze AI pre-selects the one matching the workspace domain) and click Save. Until a Site is saved the card shows Require setup (Ryze AI help center). You need a verified Search Console property and a Google login with access to it.

Approvals. The skills above ask for confirmation in their own steps, but the control that counts is the connector setting. In Claude, set write and delete tools to Needs approval under Customize, Connectors, Ryze AI, Tool permissions. In the Ryze AI chat, sitemap changes follow the Tool approvals setting, which defaults to Skip all approvals and can be switched to Approve write & delete or Manual approve.

Keyword discovery, article topics, indexation monitoring and the Search Performance dashboard run inside the Ryze AI app as part of the SEO plans, not as connector tools, so no skill here calls them. See the Google Search Console MCP page, the Ryze AI developers page and the pricing page. The 7 tools work through the connector on any active plan or trial, including Paid Ads at $89 a month with a 7-day free trial.

Search Console limits that shape these skills

Data delay and history

Search Console data is 2 to 3 days late and goes back up to 16 months, so the skills end ranges 3 days before today.

Row cap

One Search Analytics request returns at most 25,000 rows, and Google says the API returns top rows rather than every row. Large sites need narrower filters or several requests.

One URL at a time

URL Inspection checks a single URL. Google's quota page lists 2,000 queries per day and 600 per minute per site for the URL Inspection API, so skill 07 caps at 10 URLs per run.

Search Analytics quota

Google's quota page lists 1,200 queries per minute per site for Search Analytics. A skill that makes 2 to 3 calls stays far below it.

No indexing request

Neither the connector nor the inspection API requests indexing or removes URLs from Google. Use Search Console itself for that.

Property type

A URL-prefix property excludes traffic outside that exact prefix. A Domain property covers all subdomains and protocols.

Google's Search APIs page lists no MCP server for Search Console as of November 14, 2026. The Ryze AI connector is a hosted option, so you do not call the Search Console API or manage OAuth yourself.

Troubleshooting: when a Search Console skill fails

Claude has no Search Console tools

Claude keeps the tool list from when you added the connector. If you connected Search Console afterward, remove and re-add the connector, then start a new chat (Ryze AI connector FAQ).

The card says Require setup

No Site is saved yet. Pick the Site in the Ryze AI app and click Save.

The tools do not run

The tools need an active Ryze AI plan or free trial. Without one, the connector can only list workspaces and connect platforms.

Yesterday's numbers are missing

Search Console data is 2 to 3 days late. Move the end date back.

Results look short

The API returns top rows and caps a request at 25,000. Filter by page or country and run the skill again.

Numbers do not match the Search Console screen

Check that the skill used the same property, result type and dates. A URL-prefix property and a Domain property report different totals.

You need a second site

Several Google logins can be connected to one workspace, each with its own Site, and one is the primary. Separate clients belong in separate workspaces.

Sources

Checked November 14, 2026

The verdict

Start with striking distance pages and the click drop diagnosis, which only read and answer the two questions SEO owners ask most. Add the sitemap skill once Claude asks for confirmation before each write, and keep one-off questions as plain prompts.

Ryze AI runs these skills in Claude on live Search Console data. It has no tool to request indexing, and URL inspection stays one URL at a time.

Frequently asked questions

What are Claude skills for Google Search Console?
SKILL.md files that tell Claude which Search Console report to run, which tools to call and how to present the result. Claude loads one when a request matches its description, so a click drop check or striking distance list follows the same steps each time.
Do I need a connection to use these skills?
No. Skills 01 to 06 also work on a Performance report you export and paste into the chat. A connection lets Claude query the live property, inspect URLs and read sitemaps.
Which Claude plan do I need?
Anthropic lists custom skill uploads on claude.ai for Pro, Max, Ultra, Team and Enterprise with code execution enabled. In Claude Code, skills are folders on your computer. For the connector, Anthropic says custom connectors are available on Free, Pro, Max, Ultra, Team and Enterprise, with Free limited to one.
Which skills change Search Console?
Only skill 09 changes anything: it submits or removes a sitemap and pauses for your confirmation first. Skills 01 to 08 only read. To have Claude itself ask before any write or delete, set those tools to Needs approval in Customize, Connectors, Ryze AI.
Show 6 more questions
Can Claude request indexing for a URL?
No. The connector has no tool to request indexing, remove URLs from Google or verify a property. Skill 07 reports index status for the URLs you name, and the URL Inspection tool in Search Console handles requests.
How fresh is the data?
Search Console data is 2 to 3 days late and goes back up to 16 months. The skills end their date ranges 3 days before today.
Why does a report return fewer rows than I expected?
A Search Analytics request returns at most 25,000 rows, and Google states the API returns top rows rather than every row. Narrow the report with a page or country filter.
Does Google offer its own MCP server for Search Console?
Google's Search APIs page, opened November 14, 2026, lists none. Google documents the Search Analytics and URL Inspection APIs, and Ryze AI is a hosted connector so you do not call them yourself.
Can I use these skills on more than one site?
Yes. Several Google logins can be connected to one workspace, each with its own Site, and the tools accept an optional connection_id. Separate clients belong in separate workspaces, and one Claude connection can cover up to 20 workspaces.
Can the skills run on a schedule?
The skills are instructions Claude runs when you ask. Keyword discovery, indexation monitoring and the Search Performance dashboard run inside the Ryze AI app as part of the SEO plans.

Related guides

Google Search Console MCP server

The 7 tools, setup per client and limits.

How to connect Claude to Google Search Console

Step-by-step connector setup.

Claude skills for Google Analytics

10 GA4 skills with the fields each uses.

Claude skills for Google Business Profile

9 skills for reviews, posts and listing data.

Claude skills for SEO: a starter set

A wider SEO skill set for Claude.

Ryze AI: Search Console skills

3-day free trial, $129 a month

Start free trial