Automate SEO audits with Claude or Codex

98 SEO toolsExplore the catalogue →Google + Bing · GA4 / CrUX optional

Improve your search visibility with AI.

Let Claude or Codex retrieve your Google and Bing data, audit your pages and recommend the fixes to prioritize. Less manual checking, a clear action plan, no SEO expertise required.

Connect your accounts once, then ask in plain language. You review the proposed fixes and track the results.

View installation path

Unavailable metrics are reported as unavailable. Read the data limits

$ uvx gsc-mcp-tools

> Audit my site and give me the three fixes to prioritize for Google and Bing.

Illustrative output, not a live site report

  • Explain a traffic dropCompare clicks and positions, then identify possible causes.
  • Improve a search snippetSuggest a title rewrite for a page with impressions but few clicks.
  • Help a page rank higherFind pages close to page one and suggest content or internal-link changes.
98 registered tools, structured JSON output

Audit scope

What your assistant can check.

Your request determines which checks run. Results retain their sources and boundaries; missing data is reported.

Performance and changes

Clicks, impressions, CTR, positions and page or query contributions across comparable Google windows.

See tools and their limits →

Indexing and sitemaps

Google URL Inspection states and sitemap-declared URLs. Search visibility remains separate from indexing state.

See tools and their limits →

Internal links and destinations

Link zones, underlinked candidates within the sample, HTTP errors and destination redirects.

See tools and their limits →

After the click

GA4 sessions, engagement and events when configured. GSC clicks and GA4 sessions remain different measurements.

See tools and their limits →

Real analysis / 7 October 2026

What the analysis finds on my own site.

I ran Search Console MCP on cc.bruniaux.com, the Claude Code Ultimate Guide. It retrieved Google metrics, selected pages to investigate and checked their content before I proposed the next actions.

28 days: 7 September to 4 October, compared with 10 August to 6 September.

  • 459Clicks+11.95 % vs the previous period
  • 55,921Impressions+48.21 % vs the previous period
  • 0.82 %Click-through rate1.09 % previously
  1. 01Measure

    Compare two equal periods and establish the starting point.

  2. 02Find candidates

    Spot visible pages that get few clicks.

  3. 03Inspect

    Check titles, headings and links on three public pages.

  4. 04Suggest

    Propose actions with evidence and a way to measure their effect.

    Assistant interpretation, to review

A visible page that gets few clicks

/releases/

Observed : The releases page gets 19 clicks from 12,693 impressions. Two latest-version queries appear 936 times without a click.

Suggested action : Inspect the actual search snippets by query, country and device, then test one change if it fits the intent. The page already has a relevant title and a latest-version summary.

An existing answer to make easier to find

/guide/third-party-tools/

Observed : The tools page gets 9 clicks from 7,106 impressions. Two RTK / lean-ctx comparison queries appear 27 times without a click.

Suggested action : Give the existing comparison a descriptive heading and a table-of-contents entry. Track those queries while noting their small sample.

Alerts need review: 106 navigation-only destinations on one page do not establish 106 orphaned pages. Missing security headers were also reported; this run does not establish them as ranking causes.

See the 14 recorded MCP calls

The shared trace contains reviewed excerpts: example metrics, four queries and page checks. Account details, connection configuration and unrelated data are omitted.

  1. get_capabilities10.8 seconds
    {
      "startedAt": "2026-10-07T13:04:58.155Z",
      "args": {},
      "responseProjection": "reviewed excerpt; account details, internal metadata and unrelated data omitted",
      "response": {
        "total": 81,
        "tools": [
          "get_capabilities",
          "list_properties",
          "get_site_details",
          "get_search_analytics",
          "get_performance_overview",
          "compare_search_periods",
          "get_search_by_page_query",
          "get_advanced_search_analytics",
          "analytics_anomalies",
          "quick_wins",
          "traffic_drops",
          "check_alerts",
          "seo_striking_distance",
          "seo_cannibalization",
          "seo_lost_queries",
          "inspect_url",
          "batch_url_inspection",
          "check_indexing_issues",
          "submit_url",
          "submit_batch",
          "list_sitemaps",
          "submit_sitemap",
          "sitemaps_delete",
          "sitemaps_get",
          "ga4_organic_landing_pages",
          "ga4_traffic_sources",
          "ga4_page_performance",
          "ga4_realtime",
          "ga4_user_behavior",
          "ga4_conversion_funnel",
          "traffic_health_check",
          "page_analysis",
          "crux_page_vitals",
          "crux_history",
          "sitemap_audit",
          "schema_validate",
          "schema_generate",
          "drift_baseline",
          "drift_compare",
          "drift_history",
          "discover_performance",
          "news_performance",
          "search_type_breakdown",
          "ai_overviews_impact",
          "page_health_score",
          "content_brief",
          "ga4_funnel",
          "content_quality",
          "hreflang_audit",
          "page_technical_audit",
          "preload_audit",
          "crux_lcp_subparts",
          "indexnow_submit",
          "parasite_risk",
          "ai_visibility_audit",
          "gbp_deprecation_lint",
          "pagespeed_audit",
          "heading_audit",
          "internal_links_audit",
          "link_equity_map",
          "prune_candidates",
          "bing_sites_list",
          "bing_query_stats",
          "bing_page_stats",
          "bing_page_query_stats",
          "bing_rank_traffic_stats",
          "bing_crawl_stats",
          "bing_crawl_issues",
          "bing_crawl_settings_get",
          "bing_url_info",
          "bing_url_traffic",
          "bing_feeds_list",
          "bing_feed_details",
          "bing_url_submission_quota",
          "bing_link_counts",
          "bing_url_links",
          "bing_url_submit",
          "bing_urls_submit_batch",
          "bing_feed_submit",
          "bing_feed_remove",
          "compare_search_engines"
        ]
      }
    }
  2. list_properties9 seconds
    {
      "startedAt": "2026-10-07T13:05:08.977Z",
      "args": {},
      "responseProjection": "reviewed excerpt; account details, internal metadata and unrelated data omitted",
      "response": {
        "count": 1,
        "properties": [
          {
            "url": "sc-domain:cc.bruniaux.com"
          }
        ]
      }
    }
  3. get_performance_overview11.2 seconds
    {
      "startedAt": "2026-10-07T13:05:36.924Z",
      "args": {
        "site": "sc-domain:cc.bruniaux.com",
        "days": 28
      },
      "responseProjection": "reviewed excerpt; account details, internal metadata and unrelated data omitted",
      "response": {
        "site": "sc-domain:cc.bruniaux.com",
        "date_range": {
          "start": "2026-09-07",
          "end": "2026-10-04"
        },
        "totals": {
          "clicks": 459,
          "impressions": 55921,
          "ctr": 0.0082,
          "avg_position": 7.3
        }
      }
    }
  4. compare_search_periods22.5 seconds
    {
      "startedAt": "2026-10-07T13:05:36.924Z",
      "args": {
        "site": "sc-domain:cc.bruniaux.com",
        "days": 28
      },
      "responseProjection": "reviewed excerpt; account details, internal metadata and unrelated data omitted",
      "response": {
        "site": "sc-domain:cc.bruniaux.com",
        "period_a": {
          "start": "2026-08-10",
          "end": "2026-09-06",
          "clicks": 410,
          "impressions": 37731
        },
        "period_b": {
          "start": "2026-09-07",
          "end": "2026-10-04",
          "clicks": 459,
          "impressions": 55921
        },
        "delta": {
          "clicks": 49,
          "impressions": 18190
        }
      }
    }
  5. get_search_analytics43.7 seconds
    {
      "startedAt": "2026-10-07T13:05:36.924Z",
      "args": {
        "site": "sc-domain:cc.bruniaux.com",
        "days": 28,
        "dimensions": [
          "page"
        ],
        "row_limit": 20
      },
      "responseProjection": "reviewed excerpt; account details, internal metadata and unrelated data omitted",
      "response": {
        "site": "sc-domain:cc.bruniaux.com",
        "date_range": {
          "start": "2026-09-07",
          "end": "2026-10-04"
        },
        "rows": [
          {
            "page": "https://cc.bruniaux.com/releases/",
            "clicks": 19,
            "impressions": 12693,
            "ctr": 0.0015,
            "position": 7.2
          },
          {
            "page": "https://cc.bruniaux.com/guide/third-party-tools/",
            "clicks": 9,
            "impressions": 7106,
            "ctr": 0.0013,
            "position": 6.8
          },
          {
            "page": "https://cc.bruniaux.com/guide/architecture/",
            "clicks": 8,
            "impressions": 5231,
            "ctr": 0.0015,
            "position": 6.2
          }
        ]
      }
    }
  6. quick_wins32.5 seconds
    {
      "startedAt": "2026-10-07T13:05:36.924Z",
      "args": {
        "site": "sc-domain:cc.bruniaux.com",
        "days": 28,
        "min_impressions": 50,
        "engine": "google"
      },
      "responseProjection": "reviewed excerpt; account details, internal metadata and unrelated data omitted",
      "response": {
        "site": "sc-domain:cc.bruniaux.com",
        "date_range": {
          "start": "2026-09-07",
          "end": "2026-10-04"
        },
        "opportunities": [
          {
            "page": "https://cc.bruniaux.com/releases/",
            "position": 7.2,
            "clicks": 19,
            "impressions": 12693,
            "ctr": 0.0015
          },
          {
            "page": "https://cc.bruniaux.com/guide/third-party-tools/",
            "position": 6.8,
            "clicks": 9,
            "impressions": 7106,
            "ctr": 0.0013
          },
          {
            "page": "https://cc.bruniaux.com/guide/architecture/",
            "position": 6.2,
            "clicks": 8,
            "impressions": 5231,
            "ctr": 0.0015
          }
        ]
      }
    }
  7. get_advanced_search_analytics10.6 seconds
    {
      "startedAt": "2026-10-07T13:06:48.711Z",
      "args": {
        "site": "sc-domain:cc.bruniaux.com",
        "date_range_days": 28,
        "dimensions": [],
        "data_state": "final",
        "row_limit": 1,
        "search_type": "web"
      },
      "responseProjection": "reviewed excerpt; account details, internal metadata and unrelated data omitted",
      "response": {
        "site": "sc-domain:cc.bruniaux.com",
        "date_range": {
          "start": "2026-09-07",
          "end": "2026-10-04"
        },
        "search_type": "web",
        "dimensions": [],
        "rows": [
          {
            "clicks": 459,
            "impressions": 55921,
            "ctr": 0.0082,
            "position": 7.3
          }
        ]
      }
    }
  8. page_technical_audit23.1 seconds
    {
      "startedAt": "2026-10-07T13:06:48.711Z",
      "args": {
        "url": "https://cc.bruniaux.com/releases/"
      },
      "responseProjection": "reviewed excerpt; account details, internal metadata and unrelated data omitted",
      "response": {
        "url": "https://cc.bruniaux.com/releases/",
        "findings": {
          "status_code": 200,
          "redirected": false,
          "title": "Claude Code Latest Version v2.1.289 | Release History",
          "title_length": 53,
          "meta_description": "Claude Code v2.1.289, released Oct 3, 2026. See the latest version, release history, changelog, breaking changes, and configuration updates.",
          "description_length": 140,
          "meta_robots": "index, follow, max-image-preview:large, max-snippet:-1",
          "canonical": "https://cc.bruniaux.com/releases/",
          "viewport": "width=device-width, initial-scale=1.0",
          "html_lang": "en",
          "security_headers": {
            "x-frame-options": null,
            "x-content-type-options": null,
            "referrer-policy": null
          },
          "robots_txt_blocks_googlebot": false
        },
        "issues": [
          {
            "severity": "low",
            "check": "security_headers",
            "message": "Missing security header: x-frame-options"
          },
          {
            "severity": "low",
            "check": "security_headers",
            "message": "Missing security header: x-content-type-options"
          },
          {
            "severity": "low",
            "check": "security_headers",
            "message": "Missing security header: referrer-policy"
          }
        ],
        "issues_count": 3,
        "critical_count": 0,
        "verdict": "issues_found"
      }
    }
  9. page_technical_audit34.1 seconds
    {
      "startedAt": "2026-10-07T13:06:48.711Z",
      "args": {
        "url": "https://cc.bruniaux.com/guide/third-party-tools/"
      },
      "responseProjection": "reviewed excerpt; account details, internal metadata and unrelated data omitted",
      "response": {
        "url": "https://cc.bruniaux.com/guide/third-party-tools/",
        "findings": {
          "status_code": 200,
          "redirected": false,
          "title": "Claude Code Tools: RTK, ccusage & GUIs | Claude Code Guide",
          "title_length": 58,
          "meta_description": "Compare Claude Code GUIs, TUIs, configuration managers, token trackers, RTK, lean-ctx, ccusage, and other community tools.",
          "description_length": 122,
          "meta_robots": null,
          "canonical": "https://cc.bruniaux.com/guide/third-party-tools/",
          "viewport": "width=device-width, initial-scale=1",
          "html_lang": "en",
          "security_headers": {
            "x-frame-options": null,
            "x-content-type-options": null,
            "referrer-policy": null
          },
          "robots_txt_blocks_googlebot": false
        },
        "issues": [
          {
            "severity": "low",
            "check": "security_headers",
            "message": "Missing security header: x-frame-options"
          },
          {
            "severity": "low",
            "check": "security_headers",
            "message": "Missing security header: x-content-type-options"
          },
          {
            "severity": "low",
            "check": "security_headers",
            "message": "Missing security header: referrer-policy"
          }
        ],
        "issues_count": 3,
        "critical_count": 0,
        "verdict": "issues_found"
      }
    }
  10. page_technical_audit44.9 seconds
    {
      "startedAt": "2026-10-07T13:06:48.711Z",
      "args": {
        "url": "https://cc.bruniaux.com/guide/architecture/"
      },
      "responseProjection": "reviewed excerpt; account details, internal metadata and unrelated data omitted",
      "response": {
        "url": "https://cc.bruniaux.com/guide/architecture/",
        "findings": {
          "status_code": 200,
          "redirected": false,
          "title": "Claude Code Architecture & Agent Loop | Claude Code Guide",
          "title_length": 57,
          "meta_description": "How Claude Code runs its model-tool loop, manages context, executes tools, and isolates subagents, with sourced architecture notes.",
          "description_length": 131,
          "meta_robots": null,
          "canonical": "https://cc.bruniaux.com/guide/architecture/",
          "viewport": "width=device-width, initial-scale=1",
          "html_lang": "en",
          "security_headers": {
            "x-frame-options": null,
            "x-content-type-options": null,
            "referrer-policy": null
          },
          "robots_txt_blocks_googlebot": false
        },
        "issues": [
          {
            "severity": "low",
            "check": "security_headers",
            "message": "Missing security header: x-frame-options"
          },
          {
            "severity": "low",
            "check": "security_headers",
            "message": "Missing security header: x-content-type-options"
          },
          {
            "severity": "low",
            "check": "security_headers",
            "message": "Missing security header: referrer-policy"
          }
        ],
        "issues_count": 3,
        "critical_count": 0,
        "verdict": "issues_found"
      }
    }
  11. get_search_by_page_query11.2 seconds
    {
      "startedAt": "2026-10-07T13:08:34.351Z",
      "args": {
        "site": "sc-domain:cc.bruniaux.com",
        "days": 28,
        "row_limit": 1000
      },
      "responseProjection": "reviewed excerpt; account details, internal metadata and unrelated data omitted",
      "response": {
        "site": "sc-domain:cc.bruniaux.com",
        "date_range": {
          "start": "2026-09-07",
          "end": "2026-10-04"
        },
        "rows": [
          {
            "page": "https://cc.bruniaux.com/releases/",
            "query": "latest claude code version",
            "clicks": 0,
            "impressions": 485,
            "ctr": 0,
            "position": 8.2
          },
          {
            "page": "https://cc.bruniaux.com/releases/",
            "query": "claude code latest version",
            "clicks": 0,
            "impressions": 451,
            "ctr": 0,
            "position": 8.5
          },
          {
            "page": "https://cc.bruniaux.com/guide/third-party-tools/",
            "query": "lean ctx vs rtk",
            "clicks": 0,
            "impressions": 15,
            "ctr": 0,
            "position": 5.9
          },
          {
            "page": "https://cc.bruniaux.com/guide/third-party-tools/",
            "query": "lean-ctx vs rtk",
            "clicks": 0,
            "impressions": 12,
            "ctr": 0,
            "position": 4.7
          }
        ]
      }
    }
  12. heading_audit20.5 seconds
    {
      "startedAt": "2026-10-07T13:08:34.351Z",
      "args": {
        "url": "https://cc.bruniaux.com/guide/third-party-tools/"
      },
      "responseProjection": "reviewed excerpt; account details, internal metadata and unrelated data omitted",
      "response": {
        "url": "https://cc.bruniaux.com/guide/third-party-tools/",
        "h1_count": 1,
        "heading_count": 74,
        "hierarchy_jumps": [],
        "word_count": 15091,
        "words_per_h2": 628.8,
        "issues": [
          {
            "severity": "low",
            "check": "subheading_density",
            "message": "628.8 words per H2 (over 400). More subheadings would make the page scannable."
          }
        ],
        "verdict": "issues_found"
      }
    }
  13. heading_audit29 seconds
    {
      "startedAt": "2026-10-07T13:08:34.351Z",
      "args": {
        "url": "https://cc.bruniaux.com/guide/architecture/"
      },
      "responseProjection": "reviewed excerpt; account details, internal metadata and unrelated data omitted",
      "response": {
        "url": "https://cc.bruniaux.com/guide/architecture/",
        "h1_count": 1,
        "heading_count": 93,
        "hierarchy_jumps": [],
        "word_count": 8276,
        "words_per_h2": 359.8,
        "issues": [],
        "verdict": "healthy"
      }
    }
  14. internal_links_audit38.4 seconds
    {
      "startedAt": "2026-10-07T13:08:34.351Z",
      "args": {
        "url": "https://cc.bruniaux.com/guide/third-party-tools/"
      },
      "responseProjection": "reviewed excerpt; account details, internal metadata and unrelated data omitted",
      "response": {
        "url": "https://cc.bruniaux.com/guide/third-party-tools/",
        "total_links": 343,
        "internal_count": 210,
        "external_count": 133,
        "by_zone": {
          "header": 1,
          "nav": 136,
          "body": 47,
          "footer": 26
        },
        "footer_only_count": 106,
        "self_link_count": 2,
        "issues": [
          {
            "severity": "high",
            "check": "footer_only_links",
            "message": "106 internal target(s) are linked only from nav/footer/aside. Moving the important ones into the body of a relevant page gives them materially more weight."
          },
          {
            "severity": "medium",
            "check": "empty_anchor",
            "message": "1 internal link(s) have no anchor text at all."
          }
        ],
        "verdict": "issues_found"
      }
    }

14 live MCP calls. Three pages audited. Recommendations have not been applied or tested. This snapshot demonstrates the analysis; ranking impact remains unmeasured.

Choose your starting point

One problem, one analysis, actionable fixes.

New to SEO? Start with a site assessment to learn what to analyze and measure. Choose your problem, then ask Claude or Codex. Search Console MCP supplies the data and page audits for the analysis.

  1. I’m new to SEO: where do I start?
    Your assistant analyzes Assess your site and explain what matters
    What you get Your first actions and what to measure

    A starting assessment, three priorities and a simple way to track progress.

  2. My traffic is dropping
    Your assistant analyzes Analyze recent changes
    What you get A diagnosis and affected pages

    Clicks, positions and possible causes, with supporting metrics.

  3. I want better search rankings
    Your assistant analyzes Find ranking opportunities
    What you get A prioritized list of fixes

    Pages to work on, with suggested title, content or internal-link changes.

  4. My pages are hard to find
    Your assistant analyzes Check indexing and technical SEO
    What you get Issues and suggested corrections

    Indexing evidence, page checks and the next action for each issue.

Prompts to use in your assistant

I’m new to SEO: where do I start?

Before running the analysis

Paste this prompt into a compatible AI assistant. It asks the assistant to use Search Console MCP, verify the connection and guide setup if needed. The setup instructions and GitHub workflow links are included in the copied text.

Data needed : Start with your site’s public pages. Connect Google Search Console to measure search visibility and clicks. GA4 and Bing are optional; your assistant explains what it can check with the available data.

Prompt to copy

Replace https://example.com with your site before sending. You can copy the prompt or select its text.

Use Search Console MCP tools (package gsc-mcp-tools) to carry out this analysis.

Before starting, check that its tools are available in this conversation. If not, ask which assistant I use, then guide me through installing the package with uv tool install gsc-mcp-tools, registering its executable in my MCP client and restarting or reconnecting the client. Follow this guide:
https://github.com/FlorianBruniaux/google-search-console-mcp/blob/main/docs/installation.md
Wait until the connection is verified before starting the analysis.

Once connected, call get_capabilities to identify the available tools. For Google data, verify access and my site's property with list_properties; get_capabilities alone does not prove that access. If needed, guide me using:
https://github.com/FlorianBruniaux/google-search-console-mcp/blob/main/docs/google-setup.md
Configure only the sources needed. GA4 and Bing remain optional; keep credentials in the local configuration.

Read this reference workflow and use the MCP tools suited to my request, following their parameters and the sources actually available:
https://github.com/FlorianBruniaux/google-search-console-mcp/blob/main/examples/quick-audit.md
If you cannot read a reference or call a necessary tool, explain what is missing. Include the tools called, periods and data used in your report.

My site: https://example.com (replace with your site).

I know nothing about SEO. Help me improve how people find my site in search: where should I start, what should I analyze, how should I analyze it, and what should I measure? Ask about my site’s goal and audience if you need that context.

Start by inspecting the home page and a small sample of important public pages. Explain what you check and why, without jargon. If Google Search Console is connected, use the latest complete 28 days as a starting point for clicks, impressions, click-through rate and average position. Define each metric in plain language. If data is missing, explain how to connect the needed source and what remains unknown; do not require GA4 or Bing to start.

Give me three prioritized actions, with the affected page, the issue, the suggested change and the reason to start there. For each action, explain what to measure and how to compare a later equivalent period with the starting point. Distinguish observed facts from hypotheses, and explain that average position alone is not enough to assess progress.

Do not apply changes or promise ranking gains.

Illustrative example; the actual report depends on your data

You get a starting assessment, such as a title to clarify on an important page, then a plan to track its clicks, impressions and click-through rate before and after the change. Missing search data is explained rather than estimated.

Read the full workflow →
My traffic is dropping

Before running the analysis

Paste this prompt into a compatible AI assistant. It asks the assistant to use Search Console MCP, verify the connection and guide setup if needed. The setup instructions and GitHub workflow links are included in the copied text.

Data needed : Google Search Console for comparable periods. GA4 can add visitor behavior; Bing is included only where the requested comparison is supported.

Prompt to copy

Replace https://example.com with your site before sending. You can copy the prompt or select its text.

Use Search Console MCP tools (package gsc-mcp-tools) to carry out this analysis.

Before starting, check that its tools are available in this conversation. If not, ask which assistant I use, then guide me through installing the package with uv tool install gsc-mcp-tools, registering its executable in my MCP client and restarting or reconnecting the client. Follow this guide:
https://github.com/FlorianBruniaux/google-search-console-mcp/blob/main/docs/installation.md
Wait until the connection is verified before starting the analysis.

Once connected, call get_capabilities to identify the available tools. For Google data, verify access and my site's property with list_properties; get_capabilities alone does not prove that access. If needed, guide me using:
https://github.com/FlorianBruniaux/google-search-console-mcp/blob/main/docs/google-setup.md
Configure only the sources needed. GA4 and Bing remain optional; keep credentials in the local configuration.

Read this reference workflow and use the MCP tools suited to my request, following their parameters and the sources actually available:
https://github.com/FlorianBruniaux/google-search-console-mcp/blob/main/examples/traffic-drop.md
If you cannot read a reference or call a necessary tool, explain what is missing. Include the tools called, periods and data used in your report.

My site: https://example.com (replace with your site).

Compare the latest complete 28 days with the previous 28 days. Identify the pages and queries losing clicks, and compare their impressions, click-through rate and positions.

Explain the possible causes in plain language, separating observed facts from hypotheses. Use only the sources I have connected; report missing or non-comparable data instead of guessing.

Give me a prioritized list of investigations and suggested fixes, with the affected URL and supporting metrics. Do not apply changes.

Illustrative example; the actual report depends on your data

If a page loses clicks while its positions stay stable, the report can recommend checking its click-through rate and search demand before assuming a ranking loss.

Read the full workflow →
I want better search rankings

Before running the analysis

Paste this prompt into a compatible AI assistant. It asks the assistant to use Search Console MCP, verify the connection and guide setup if needed. The setup instructions and GitHub workflow links are included in the copied text.

Data needed : Google Search Console or configured Bing search metrics, plus public-page audits. GA4 is optional for visitor behavior.

Prompt to copy

Replace https://example.com with your site before sending. You can copy the prompt or select its text.

Use Search Console MCP tools (package gsc-mcp-tools) to carry out this analysis.

Before starting, check that its tools are available in this conversation. If not, ask which assistant I use, then guide me through installing the package with uv tool install gsc-mcp-tools, registering its executable in my MCP client and restarting or reconnecting the client. Follow this guide:
https://github.com/FlorianBruniaux/google-search-console-mcp/blob/main/docs/installation.md
Wait until the connection is verified before starting the analysis.

Once connected, call get_capabilities to identify the available tools. For Google data, verify access and my site's property with list_properties; get_capabilities alone does not prove that access. If needed, guide me using:
https://github.com/FlorianBruniaux/google-search-console-mcp/blob/main/docs/google-setup.md
Configure only the sources needed. GA4 and Bing remain optional; keep credentials in the local configuration.

Read this reference workflow and use the MCP tools suited to my request, following their parameters and the sources actually available:
https://github.com/FlorianBruniaux/google-search-console-mcp/blob/main/examples/keyword-opportunities.md
If you cannot read a reference or call a necessary tool, explain what is missing. Include the tools called, periods and data used in your report.

My site: https://example.com (replace with your site).

Find pages close to page one and pages with impressions but few clicks. Use only the search data I have connected and state the observed period.

Inspect the relevant pages before recommending changes to titles, descriptions, content or internal links. Prioritize the fixes and give the affected URL, target query and supporting metrics for each one.

Explain the recommendations without SEO jargon and suggest how to compare results after the changes. Do not apply changes or promise ranking gains.

Illustrative example; the actual report depends on your data

For a page with impressions but few clicks, the report can propose a title that better matches its main query and explain which metrics to compare after the rewrite.

Read the full workflow →
My pages are hard to find

Before running the analysis

Paste this prompt into a compatible AI assistant. It asks the assistant to use Search Console MCP, verify the connection and guide setup if needed. The setup instructions and GitHub workflow links are included in the copied text.

Data needed : Public pages for technical audits. Google Search Console for indexing status; configured Bing data can add crawl signals.

Prompt to copy

Replace https://example.com with your site before sending. You can copy the prompt or select its text.

Use Search Console MCP tools (package gsc-mcp-tools) to carry out this analysis.

Before starting, check that its tools are available in this conversation. If not, ask which assistant I use, then guide me through installing the package with uv tool install gsc-mcp-tools, registering its executable in my MCP client and restarting or reconnecting the client. Follow this guide:
https://github.com/FlorianBruniaux/google-search-console-mcp/blob/main/docs/installation.md
Wait until the connection is verified before starting the analysis.

Once connected, call get_capabilities to identify the available tools. For Google data, verify access and my site's property with list_properties; get_capabilities alone does not prove that access. If needed, guide me using:
https://github.com/FlorianBruniaux/google-search-console-mcp/blob/main/docs/google-setup.md
Configure only the sources needed. GA4 and Bing remain optional; keep credentials in the local configuration.

Read this reference workflow and use the MCP tools suited to my request, following their parameters and the sources actually available:
https://github.com/FlorianBruniaux/google-search-console-mcp/blob/main/examples/indexing-issues.md
If you cannot read a reference or call a necessary tool, explain what is missing. Include the tools called, periods and data used in your report.

My site: https://example.com (replace with your site).

Help me understand why my pages are hard to find in search. Inspect Google indexing where Search Console is connected, and check the public pages for robots, canonical, sitemap, metadata and internal-link issues.

Distinguish crawl signals from indexing status. Explain what was checked and what remains unknown; do not infer an indexing verdict from Bing crawl data or an accepted submission.

List the affected URLs, the evidence for each issue and the suggested correction in plain language. Do not change pages or submit URLs.

Illustrative example; the actual report depends on your data

If a canonical tag points to a different URL than intended, the report can recommend reviewing the canonical and internal links, then inspecting the URL again.

Read the full workflow →

The server fetches data and runs analyses. Your AI assistant explains the results and proposes fixes. A coding assistant with repository access can help apply the changes you choose.

01 / Data behind the analysis

See where visibility is lost and why pages need attention.

Connect the sources you use. Your assistant can combine search performance, visitor behavior and page audits to guide its recommendations.

Google data

Find which searches bring visitors and which pages lose clicks or positions with Search Console. Optional GA4 shows what visitors do next; CrUX adds real-user loading and interaction metrics.

  • Search performance
  • URL inspection
  • GA4
  • CrUX

Bing data

Find opportunities in Bing search and investigate crawl issues for your verified sites. Compare Google and Bing visibility to see where each engine needs attention.

  • Queries and pages
  • Crawl signals
  • Feeds
  • IndexNow

Public-page analysis

Check the pages themselves for metadata, content, structured-data and internal-link issues that may explain weak performance, without private provider credentials.

  • Metadata
  • Schema
  • Sitemaps
  • Internal links

Google and Bing position semantics remain separate.

02 / Workflow

Automate the audit. Review the fixes. Track the results.

  1. Connect

    Install in Claude, Codex or another MCP client and connect the accounts you use.

  2. Ask

    Describe your goal in plain language, such as understanding a traffic drop or finding ranking opportunities.

  3. Analyze

    Your assistant calls the tools, compares metrics and audits pages to propose a prioritized action plan.

  4. Fix

    Review the recommendations. Apply them yourself or ask a coding assistant with repository access to help.

  5. Measure

    Rerun the analysis to track changes. Schedule recurring checks through your client or an external automation.

For a native audit with bounded attempts and selected roles, read the source workflow guide. The experimental APIs are packaged in 1.6.0; the runner and skills require a checkout.

03 / Get started

Choose 1 install path, then verify access.

Connect your MCP client, then verify each provider separately.

  1. Evaluate once

    Run uvx gsc-mcp-tools without changing a project environment.

    uvx gsc-mcp-tools

  2. Install persistently

    Run uv tool install gsc-mcp-tools and point the MCP client at the installed executable.

    uv tool install gsc-mcp-tools

  3. Verify access

    Run gsc-cli list, then verify each configured provider separately.

    gsc-cli list

    Expected: the registered commands and their one-line descriptions.

Read the client-specific installation guide

04 / Evidence & safety

3 result states: observed, derived, requested.

Unsupported Bing analyses are identified explicitly. Cross-engine deltas require exact, matching observed windows. An accepted submission proves neither crawl nor indexation.

Read the data limits
Observed
API responses and fetched public-page data.
Derived
Calculations tied to an explicit observed window.
Requested
A provider accepted a submission. Crawl and indexation remain unproven.

05 / FAQ

Using your AI assistant for SEO.

What comes out of an analysis?

Your assistant can turn the tool results into a diagnosis of recent SEO changes and a prioritized action plan: affected pages, supporting metrics, suggested title or content edits, internal-link changes and technical issues to investigate. The output depends on your prompt and the data available.

Do I need SEO expertise?

You can ask in plain language and have the assistant explain the metrics and recommendations. Initial installation and account setup are required; the guides walk through them. You still review suggested fixes before applying them.

Does it automatically improve my rankings?

It automates data retrieval and provides analyses that your assistant uses to suggest fixes. A coding assistant can help apply approved changes when it has repository access. Recurring runs require a scheduler or client automation. Ranking gains are not guaranteed; compare your metrics after the changes.

Can 1 Bing API key cover several sites?

One Bing Webmaster API key can access the verified sites visible to that Bing account. Every tool call still names its target site. IndexNow uses a different key verified on each target host.

Which Google APIs do I need?

Configure only the provider families you use. Search Console credentials cover the core search workflows. GA4, CrUX and eligible Indexing API workflows require their own optional configuration.

Does an accepted submission prove indexation?

No. It proves only that the provider accepted the request. Measure crawl and indexation separately in a later comparable check.

Can I use Search Console MCP with Claude and Codex?

Yes. Search Console MCP runs over stdio and works with Claude, Codex and other compatible MCP clients. The executable path and configuration format depend on the client.

Where should credentials be stored?

Keep credentials in the MCP server environment or the client configuration. The public website never receives them, and prompts should not contain secret values.

Start with your own site.

Get your first SEO action plan.

Connect your accounts and let Claude or Codex run your first audit. Get prioritized fixes to improve your search visibility.

uvx gsc-mcp-tools

Read the installation guide