OnPage.dev

SEO MCP server

The SEO scanner your AI assistant uses to fix your site itself.

Scan, fix, check before deploy, confirm after. For Google and for AI search.

Remembers every site across chats, projects and clients.

Approve fixes in WordPress with one click. Explains traffic drops, with the Google update behind them.

Runs in Claude · ChatGPT · Cursor · VS Code Checks your site for ChatGPT · Claude · Gemini · Perplexity Ships fixes to WordPress · Shopify · Webflow · Wix · Storyblok · Sanity Contentful · Strapi · Ghost · Magento · GitHub pull request

Install · Content autopilot · WordPress approval · Traffic drops · Preview check · All tools · Why it is different · onpage.dev

Your SEO data · Rank tracker · Cannibalization · Links and AI gaps · Lost links · Disavow · What changed

Site memory · Pull requests · Watch and alerts · Claude Code plugin · GitHub Action · Fix guard

---

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.

New

• Drafts and post updates in WordPress. The content autopilot now ends in wp-admin: new posts arrive as drafts, updates show what changes, one click to approve, undo any time. Plugin 1.1.
• Content in your site's own voice. Content autopilot: content modes voice, calendar and draft plus the content_autopilot prompt: your agent writes, OnPage.dev learns how the site writes, plans a dated calendar, checks each draft for voice, unsourced figures and SEO before you approve, and learns from measured results which formats work on your site.
• Approve fixes in WordPress, one click. Your agent sends the fixes to the free OnPage.dev WordPress plugin. You see old and new value per field, approve, and undo any time. Through Yoast SEO, Rank Math or its own tags. OnPage.dev never logs in.
• Ask about your traffic, no CSV exports. Finds the day traffic broke and the Google update that ran then, from Google's own status dashboard. Plus lost and split queries, the questions AI answers, and Google against Bing, from the Search Console, GA4 and Bing rows your assistant already reads.
• Checks every deploy preview. Holds a Vercel, Netlify or Cloudflare preview against production before you merge: lost titles and canonicals, noindex, broken pages. In chat or as a GitHub Action that comments on the pull request.

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.

Step OnPage.dev Data MCPs Search data: rankings, keywords, backlinks ✅ Uses yours, from Search Console, GA4, Ahrefs or Semrush in the same chat Their core strength Find what is wrong on the page ✅ scan_page , scan_page · deep , layout · render : Google, AI search, speed, accessibility Site audit data in some of them Write the fix from the page itself ✅ get_fix_pack , schema · generate Not what they are built for Ship it where the code lives ✅ 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 Not what they are built for Check it before deploy ✅ scan_page · html and compare · html on unpublished HTML Not what they are built for Tell search engines ✅ request_recrawl · indexnow , plus URL Inspection through your Search Console Not what they are built for Cover the AI Mode fan-out ✅ answer_readiness · questions : every sub-question answered, buried or missing Not what they are built for Win back lost links ✅ backlinks · broken : their broken and lost backlinks plus GA4 404 hits become ranked 301 rules, link edits and an outreach list They list the broken and lost backlinks Fix keyword cannibalization ✅ check_keyword · cannibalization : your competing pages side by side on every on-page signal, with the plan Show which pages compete for a keyword Get into AI answers ✅ <cod