seo-mcp-server

<p align="center">
  <a href="https://onpage.dev/mcp"><img src="assets/onpage-dev-banner.png" alt="OnPage.dev: free SEO and AI-visibility checks for AI assistants" width="720"></a>
</p>

<h1 align="center">OnPage.dev MCP server</h1>

<p align="center">
  <b>The SEO scanner your AI assistant uses to fix your site itself.</b><br>
  Scan, fix, check before deploy, confirm after. For Google and for AI search.<br>
  <b>Remembers every site across chats, projects and clients.</b>
</p>

<p align="center">
  <a href="https://onpage.dev/mcp"><img alt="Hosted MCP server" src="https://img.shields.io/badge/MCP-hosted-4f46e5"></a>
  <img alt="Free, no API key" src="https://img.shields.io/badge/price-free%2C%20no%20key-0a7a43">
  <img alt="37 tools" src="https://img.shields.io/badge/tools-37-4f46e5">
  <img alt="109 jobs" src="https://img.shields.io/badge/jobs-109-4f46e5">
  <a href="https://github.com/seoonpage/seo-mcp-server/actions/workflows/test.yml"><img alt="Tests" src="https://github.com/seoonpage/seo-mcp-server/actions/workflows/test.yml/badge.svg"></a>
  <a href="LICENSE"><img alt="MIT license" src="https://img.shields.io/badge/license-MIT-0b0b0f"></a>
</p>

<p align="center">
  <sub><b>Runs in</b></sub>&nbsp;&nbsp;
  <img src="assets/logos/claude.png" width="22" height="22" align="absmiddle" alt="">&nbsp;Claude&nbsp;&nbsp;&nbsp;
  <img src="assets/logos/chatgpt.png" width="22" height="22" align="absmiddle" alt="">&nbsp;ChatGPT&nbsp;&nbsp;&nbsp;
  <picture><source media="(prefers-color-scheme: dark)" srcset="assets/logos/cursor-dark.png"><img src="assets/logos/cursor.png" width="22" height="22" align="absmiddle" alt=""></picture>&nbsp;Cursor&nbsp;&nbsp;&nbsp;
  <img src="assets/logos/vscode.png" width="22" height="22" align="absmiddle" alt="">&nbsp;VS&nbsp;Code
  <br><br>
  <sub><b>Checks your site for</b></sub>&nbsp;&nbsp;
  <img src="assets/logos/chatgpt.png" width="22" height="22" align="absmiddle" alt="">&nbsp;ChatGPT&nbsp;&nbsp;&nbsp;
  <img src="assets/logos/claude.png" width="22" height="22" align="absmiddle" alt="">&nbsp;Claude&nbsp;&nbsp;&nbsp;
  <img src="assets/logos/gemini.png" width="22" height="22" align="absmiddle" alt="">&nbsp;Gemini&nbsp;&nbsp;&nbsp;
  <img src="assets/logos/perplexity.png" width="22" height="22" align="absmiddle" alt="">&nbsp;Perplexity&nbsp;&nbsp;&nbsp;
  <sub><b>Ships fixes to</b></sub>&nbsp;&nbsp;
  <img src="assets/logos/wordpress.png" width="22" height="22" align="absmiddle" alt="">&nbsp;WordPress&nbsp;&nbsp;&nbsp;
  <img src="assets/logos/shopify.png" width="22" height="22" align="absmiddle" alt="">&nbsp;Shopify&nbsp;&nbsp;&nbsp;
  <img src="assets/logos/webflow.png" width="22" height="22" align="absmiddle" alt="">&nbsp;Webflow&nbsp;&nbsp;&nbsp;
  <img src="assets/logos/wix.png" width="22" height="22" align="absmiddle" alt="">&nbsp;Wix&nbsp;&nbsp;&nbsp;
  <img src="assets/logos/storyblok.png" width="22" height="22" align="absmiddle" alt="">&nbsp;Storyblok&nbsp;&nbsp;&nbsp;
  <picture><source media="(prefers-color-scheme: dark)" srcset="assets/logos/sanity-dark.png"><img src="assets/logos/sanity.png" width="22" height="22" align="absmiddle" alt=""></picture>&nbsp;Sanity&nbsp;&nbsp;&nbsp;
  <img src="assets/logos/contentful.png" width="22" height="22" align="absmiddle" alt="">&nbsp;Contentful&nbsp;&nbsp;&nbsp;
  <img src="assets/logos/strapi.png" width="22" height="22" align="absmiddle" alt="">&nbsp;Strapi&nbsp;&nbsp;&nbsp;
  <picture><source media="(prefers-color-scheme: dark)" srcset="assets/logos/ghost-dark.png"><img src="assets/logos/ghost.png" width="22" height="22" align="absmiddle" alt=""></picture>&nbsp;Ghost&nbsp;&nbsp;&nbsp;
  <img src="assets/logos/magento.png" width="22" height="22" align="absmiddle" alt="">&nbsp;Magento&nbsp;&nbsp;&nbsp;
  <picture><source media="(prefers-color-scheme: dark)" srcset="assets/logos/github-dark.png"><img src="assets/logos/github.png" width="22" height="22" align="absmiddle" alt=""></picture>&nbsp;GitHub
</p>

<p align="center">
  <a href="#install-in-one-minute">Install</a> ·
  <a href="#they-bring-the-data-onpagedev-closes-the-loop">Data vs results</a> ·
  <a href="#uses-the-seo-data-you-already-have">Your SEO data</a> ·
  <a href="#a-rank-tracker-that-knows-what-matters">Rank tracker</a> ·
  <a href="#which-of-your-pages-wins-the-keyword">Cannibalization</a> ·
  <a href="#disavow-without-the-risk-and-manual-actions-cleaned-up">Disavow</a> ·
  <a href="#bring-your-own-crawl">Your own crawl</a> ·
  <a href="#what-changed-since-the-last-audit">What changed</a> ·
  <a href="#links-to-win-and-ai-answers-to-enter">Links and AI gaps</a> ·
  <a href="#and-the-links-you-lost">Lost links</a> ·
  <a href="#the-whole-loop-inside-your-ai-agent">The whole loop</a> ·
  <a href="#from-finding-to-done">From finding to done</a> ·
  <a href="#seen-by-every-reader">Every reader</a> ·
  <a href="#real-user-speed">Real-user speed</a> ·
  <a href="#ships-as-a-pull-request">Pull requests</a> ·
  <a href="#keeps-watching-after-you-ship">Watch and alerts</a> ·
  <a href="#built-for-agents">Built for agents</a> ·
  <a href="#what-it-can-do">Tools</a> ·
  <a href="#why-it-is-different">Why it is different</a> ·
  <a href="#claude-code-plugin">Claude Code plugin</a> ·
  <a href="#github-action-seo-gate">GitHub Action</a> ·
  <a href="#github-action-fix-guard">Fix guard</a> ·
  <a href="https://onpage.dev">onpage.dev</a>
</p>

---

<p align="center">
  <picture>
    <source media="(prefers-color-scheme: dark)" srcset="assets/ask-check-ship-dark.png">
    <img src="assets/ask-check-ship-light.png" width="900" alt="You ask in your AI tool (Claude, ChatGPT, Cursor, VS Code), OnPage.dev checks how AI search sees your site (ChatGPT, Claude, Gemini, Perplexity), and ships the fix to your CMS (WordPress, Shopify, Webflow, Wix, Storyblok, Sanity, Contentful, Strapi, Ghost, Magento, GitHub) or any CMS at the edge.">
  </picture>
</p>

Most SEO tools give you a report. OnPage.dev gives your assistant something to **do**: write the fix, check it before you publish, and confirm it worked. It also checks what AI search sees, not only Google: which AI crawlers may read your site, whether your content is ready to be quoted, and whether you have an `llms.txt`.

```
You:        Fix the SEO on our pricing page and keep going until it scores 90 or more.

Assistant:  scan_page            46/100  no meta description, no H1, title 14 characters
            get_fix_pack         title, description and canonical, written from the page
            schema · generate    Product JSON-LD, 2 values to fill in
            (edits pricing.html)
            scan_page · html     92/100  before deploying, all errors gone
            scan_page · rescan   94/100  live, +48 since the first scan

            Done. 46 to 94. Two prices in the JSON-LD still need your real values.
```

## They bring the data. OnPage.dev closes the loop.

The SEO MCP servers from Ahrefs, Semrush, SE Ranking and DataForSEO are built for data: what ranks, who links, what people search. Then the real work starts. OnPage.dev does that part, inside the same chat, and uses their numbers to decide what to fix first.

<p align="center">
  <picture>
    <source media="(prefers-color-scheme: dark)" srcset="assets/loop-dark.png">
    <img src="assets/loop-light.png" width="720" alt="Step 1, data from Ahrefs, Semrush, SE Ranking or DataForSEO, is passed to OnPage.dev, which takes over: 2 find, 3 fix, 4 check, 5 ship, 6 notify, 7 prove. The results flow back into your data and the loop starts again.">
  </picture>
</p>

<table>
  <tr><th align="left">Step</th><th align="left"><img src="assets/logos/onpage.png" width="26" height="26" alt=""><br>OnPage.dev</th><th align="left"><img src="assets/logos/ahrefs.png" width="22" height="22" alt="">&nbsp;&nbsp;<img src="assets/logos/semrush.png" width="22" height="22" alt="">&nbsp;&nbsp;<img src="assets/logos/seranking.png" width="22" height="22" alt="">&nbsp;&nbsp;<img src="assets/logos/dataforseo.png" width="22" height="22" alt=""><br>Data MCPs</th></tr>
  <tr><td><b>Search data: rankings, keywords, backlinks</b></td><td>✅ Uses yours, from Search Console, GA4, Ahrefs or Semrush in the same chat</td><td>Their core strength</td></tr>
  <tr><td><b>Find what is wrong on the page</b></td><td>✅ <code>scan_page</code>, <code>scan_page · deep</code>, <code>layout · render</code>: Google, AI search, speed, accessibility</td><td>Site audit data in some of them</td></tr>
  <tr><td><b>Write the fix from the page itself</b></td><td>✅ <code>get_fix_pack</code>, <code>schema · generate</code></td><td><i>Not what they are built for</i></td></tr>
  <tr><td><b>Ship it where the code lives</b></td><td>✅ WordPress, Shopify, Webflow, Wix, Storyblok, Sanity, Contentful, Strapi, Ghost or Magento fields through your own connection, or a Git pull request for Next.js, Nuxt, SvelteKit, Astro, Angular, React or Vue</td><td><i>Not what they are built for</i></td></tr>
  <tr><td><b>Check it before deploy</b></td><td>✅ <code>scan_page · html</code> and <code>compare · html</code> on unpublished HTML</td><td><i>Not what they are built for</i></td></tr>
  <tr><td><b>Tell search engines</b></td><td>✅ <code>request_recrawl · indexnow</code>, plus URL Inspection through your Search Console</td><td><i>Not what they are built for</i></td></tr>
  <tr><td><b>Cover the AI Mode fan-out</b></td><td>✅ <code>answer_readiness · questions</code>: every sub-question answered, buried or missing</td><td><i>Not what they are built for</i></td></tr>
  <tr><td><b>Win back lost links</b></td><td>✅ <code>backlinks · broken</code>: their broken and lost backlinks plus GA4 404 hits become ranked 301 rules, link edits and an outreach list</td><td>They list the broken and lost backlinks</td></tr>
  <tr><td><b>Fix keyword cannibalization</b></td><td>✅ <code>check_keyword · cannibalization</code>: your competing pages side by side on every on-page signal, with the plan</td><td>Show which pages compete for a keyword</td></tr>
  <tr><td><b>Get into AI a