OnPage.dev

What OnPage.dev MCP server does

The OnPage.dev MCP server connects an AI assistant to SEO checks and remediation workflows. It can inspect a page, identify issues such as missing metadata, missing headings, weak titles, canonical problems, broken pages, or unwanted noindex directives, then provide fixes based on the page being analyzed. The README describes 37 tools covering page audits, structured data, search analysis, AI-visibility checks, deployment validation, and publishing workflows.

The service also looks beyond traditional Google SEO. It checks how sites may be read and quoted by AI search systems, including crawler access, content readiness, and the presence of an llms.txt file. This makes it relevant for teams evaluating both search-engine indexing and visibility in ChatGPT, Claude, Gemini, or Perplexity.

How it works

An assistant calls the hosted MCP tools from a supported client. A typical workflow starts with a page scan, produces a fix pack or generated schema, and runs another scan before deployment. After publication, the page can be checked again to compare the live result with the initial audit. The README presents this as a find, fix, check, ship, and prove cycle rather than a report-only workflow.

The tools can also analyze information already available from Google Search Console, GA4, and Bing. They support questions about traffic drops, split or lost queries, AI-answer opportunities, links, rankings, and differences between Google and Bing. Google status information is used to associate traffic changes with a Google update when one occurred at the same time.

Tools and capabilities

Documented capabilities include:

• Scanning pages and rescanning them after changes.
• Generating SEO fixes from page content.
• Creating or checking structured data, including Product JSON-LD.
• Checking AI-search visibility and crawler access.
• Comparing deployment previews with production.
• Finding traffic changes, lost links, query cannibalization, and AI-content gaps.
• Sending changes to WordPress, Shopify, Webflow, Wix, Storyblok, Sanity, Contentful, Strapi, Ghost, or Magento.
• Creating GitHub pull requests for changes.
• Watching sites and sending alerts after deployment.

Setup and configuration

OnPage.dev MCP server is hosted and is advertised as free to use without an API key. The README lists Claude, ChatGPT, Cursor, and VS Code as environments where it runs; this directory’s client compatibility list maps the named MCP-capable environments to Claude Desktop, Cursor, and VS Code. The provided material does not include a connection snippet or client-specific configuration block, so installation details should be taken from the project’s current instructions.

For WordPress, the workflow uses a free OnPage.dev plugin. The agent can send proposed changes for review, showing old and new field values before approval. The README says the plugin can work through Yoast SEO, Rank Math, or its own tags, and that OnPage.dev does not log in to WordPress.

Limitations and notes

The material does not document individual tool names, input schemas, rate limits, authentication beyond the no-key claim, or the exact setup syntax for each client. CMS publishing is described for the listed platforms, while GitHub delivery is described through pull requests. WordPress approval requires the separate plugin and a human approval step. Some generated structured-data fields may still require real values from the site owner.