DidYouSEO

com.didyouseoPublished by didyouseo.comOfficial publisherv1.0.1Updated Oct 27, 2026

SEO audits, Search Console, GA4, keyword and backlink data for Claude, ChatGPT and Cursor.

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingData & AnalyticsBusiness & Commerce

Overview

AI-generated overview

DidYouSEO connects an assistant to SEO audits, Google Search Console, GA4, keyword and backlink data through a remote MCP endpoint or a local stdio bridge.

What you can do
  • Run full SEO audits of any URL, fetch past audit results, and manage sites with latest site and page scores
  • Read Search Console queries with clicks, impressions, CTR and position, compare period changes, and spot keyword cannibalization
  • Pull GA4 organic traffic, engagement, key events, top landing pages and visits from AI assistants
  • Look up keyword volume, difficulty, CPC and intent, generate keyword ideas, and summarize backlinks for a domain
  • Run free checks on any URL: PageSpeed Insights, meta tags, robots.txt, schema validation, SERP preview, Core Web Vitals, Open Graph and hreflang
When to use it
Useful when you want an assistant to audit pages, diagnose organic search performance, or research keywords and backlinks without switching between SEO dashboards. Fits marketing and content work where Search Console or GA4 data is already connected.
Requirements
A DidYouSEO account signed in via OAuth on first use. Either the remote endpoint at didyouseo.com or the npm package @didyouseo/mcp run with npx for clients that only support local stdio servers; the bridge opens a browser window for sign-in. Search Console and GA4 tools need those services connected in DidYouSEO.
Before you install
Keyword and backlink lookups cost one DidYouSEO AI credit per call, drawn from paid plans; free accounts see only a preview of Search Console and GA4 results. The server reads your Search Console and GA4 data and can register sites in your account. Sign-in grants the server access to your DidYouSEO account.

Installation

In SourceWeft

  1. Open DidYouSEO in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.didyouseo%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "didyouseo": {
      "type": "http",
      "url": "https://didyouseo.com/mcp"
    }
  }
}

README

@didyouseo/mcp

Connect DidYouSEO's SEO tools to any AI assistant that supports the Model Context Protocol (MCP).

DidYouSEO runs a remote MCP server at https://didyouseo.com/mcp. Clients that support remote MCP servers (Claude, ChatGPT, Cursor) can connect to that URL directly and sign in with OAuth — no install needed. This package is a small stdio bridge for clients that only support local MCP servers.

Tools

21 tools in five groups.

SEO audits and your sites (sign-in required)

  • run_seo_audit — full SEO audit of any URL: score, issues and fixes
  • get_audit_result — fetch a previous audit by id
  • list_sites / register_site — manage the sites in your account
  • get_site_score / get_page_score — latest SEO scores for a site or page

Google Search Console (connect Search Console in DidYouSEO)

  • get_search_console_keywords — real queries: clicks, impressions, CTR and position
  • get_search_console_changes — biggest click gainers and losers between two periods
  • get_search_console_cannibalization — queries where several of your pages compete

Google Analytics 4 (connect GA4 in DidYouSEO)

  • get_ga4_organic_traffic — organic sessions, engagement, key events, top landing pages and visits from AI assistants (ChatGPT, Perplexity, Gemini, Claude, Copilot)

Keywords and backlinks (1 DidYouSEO AI credit per call; failed lookups are refunded)

  • get_keyword_data — search volume, difficulty, CPC and intent for up to 10 keywords
  • get_keyword_ideas — up to 50 keyword ideas for a seed phrase, sorted by volume
  • get_backlink_summary — domain rank, backlinks and referring domains for any domain

Free checks for any URL

  • run_pagespeed_insights — Lighthouse scores, real-user Core Web Vitals and speed fixes
  • analyze_meta_tags, check_robots_txt, validate_schema (checks Google's rich result requirements), serp_preview, check_core_web_vitals, check_open_graph, check_hreflang (validates codes and return links)

Every tool runs after you sign in with your DidYouSEO account (OAuth, on first use). A free account can use every tool: Search Console and GA4 results are a short preview on the free plan, and keyword and backlink lookups use the AI credits that paid plans include each month. See https://didyouseo.com/pricing.

Use a remote connector (recommended)

If your client supports remote MCP servers, just add the URL:

https://didyouseo.com/mcp

You'll be prompted to sign in with DidYouSEO the first time.

Use the stdio bridge

For clients that only support local (stdio) servers, add this to the client's MCP config:

json
{  "mcpServers": {    "didyouseo": {      "command": "npx",      "args": ["-y", "@didyouseo/mcp"]    }  }}

A browser window opens for sign-in on first run.

Local development

Point the bridge at a local DidYouSEO instance:

bash
DIDYOUSEO_MCP_URL=http://localhost:3000/mcp npx @didyouseo/mcp

License

MIT

Source: README.md at commit 7bcedcf

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.1LatestOct 20, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts