Fix Drupal SEO from Cursor
Cursor reads your real Google Search Console data through SEOmatic, finds what is holding your Drupal pages back, and stages the fix. Nothing goes live on Drupal until you approve it, and any edit to an existing page can be rolled back.
- Your real Search Console data
- Fixes staged in Drupal
- Nothing goes live until you approve
About Drupal in SEOmatic
SEOmatic connects to your Drupal site over JSON:API using OAuth2. Agents write new nodes and improve existing ones, and hand you anything your site has no field for rather than failing the whole save.
Last Updated
October 2026
Requirements
A Drupal site with the JSON:API module enabled (it ships with core) and the Simple OAuth module installed. You create a Consumer under Configuration > Simple OAuth whose user has permission to write content, then paste its Client ID and Secret. Meta fields additionally need the Metatag module.
How to Fix Drupal SEO from Cursor
Step 1: Connect Drupal to SEOmatic
SEOmatic connects to your Drupal site over JSON:API, then works on the nodes you already have.
Step 1: Enable the JSON:API module (it ships with core) and install Simple OAuth.
Step 2: In Drupal, go to Configuration, then Simple OAuth, and create a Consumer. Give it a user with permission to write content, then copy the Client ID and Secret.
Step 3: In SEOmatic, go to Connections and select Drupal. Paste your site URL and both credentials, then pick the content type to work in.
Step 4: Agents propose changes with the reasoning attached, you approve what you want, and approved work is written to your site as a diff you can read and undo.
Step 2: Connect SEOmatic to Cursor
Add this to ~/.cursor/mcp.json for every project, or .cursor/mcp.json in one repo, or add the same URL in Settings, Tools & MCP. Approve the SEOmatic sign-in in your browser and pick your site. Or install SEOmatic from the Cursor Marketplace by typing /add-plugin seomatic in Agent chat.
{
"mcpServers": {
"seomatic": { "url": "https://app.seomatic.ai/api/mcp" }
}
}Other ways to connect are on the Cursor page.
Step 3: Ask Cursor, Then Approve
Paste any of these. Cursor answers from your data and stages the fix; you approve it before it reaches Drupal.
- “Which of my Drupal pages lost the most clicks this month, and why?”
- “Stage new titles for my Drupal pages with high impressions and low CTR.”
- “Find Drupal pages Google has not indexed and tell me what is blocking them.”
- “Audit my Drupal homepage and rank the fixes by impact.”
What Cursor Can Change on Drupal
New nodes written from research, plus rewrites of the title and body content on ones already published.
Agents set the URL alias, so your pages keep readable addresses instead of falling back to /node/123.
The agent arrives switched off and starts in approval mode. It earns more rope only when you give it.
A before and after view with the reasoning attached, so you see what changed and why.
Any change rolls back to its previous value. Low-risk edits that cost you traffic revert on their own.
Meta is written through the Metatag module when your site runs it. When it does not, agents hand you that work rather than assuming it is there.
Everything goes through core JSON:API and Simple OAuth, so there is nothing bespoke to install or keep updated.
Articles, basic pages or a bundle your team defined. Agents work in whichever one you point them at.
Only field values change, so your templates, Twig and site configuration stay exactly as they are.
Drupal sites differ enormously in which contributed modules they run, so agents check what your content types and modules actually provide before they write, and tell you about the rest instead of guessing at your field set.
Full details on the Drupal integration page.
Requirements
Drupal
A Drupal site with the JSON:API module enabled (it ships with core) and the Simple OAuth module installed. You create a Consumer under Configuration > Simple OAuth whose user has permission to write content, then paste its Client ID and Secret. Meta fields additionally need the Metatag module.
Cursor
Cursor and a free SEOmatic account, which you can create during sign-in. Use OAuth, not an API key: Cursor does not send a configured Authorization header.
Fix Drupal SEO from Another Agent
- Fix Drupal SEO from Claude
- Fix Drupal SEO from Claude Code
- Fix Drupal SEO from Claude Cowork
- Fix Drupal SEO from ChatGPT
- Fix Drupal SEO from Codex
- Fix Drupal SEO from Gemini
- Fix Drupal SEO from Grok Bot
- Fix Drupal SEO from Perplexity Computer
- Fix Drupal SEO from OpenClaw
- Fix Drupal SEO from Hermes Agent
- Fix Drupal SEO from Manus
Use Cursor on Another Platform
- Fix WordPress SEO from Cursor
- Fix Webflow SEO from Cursor
- Fix Shopify SEO from Cursor
- Fix Ghost SEO from Cursor
- Fix Blogger SEO from Cursor
- Fix Wix SEO from Cursor
- Fix Squarespace SEO from Cursor
- Fix Framer SEO from Cursor
- Fix BigCommerce SEO from Cursor
- Fix HubSpot CMS SEO from Cursor
- Fix Contentful SEO from Cursor
- Fix Strapi SEO from Cursor
- Fix Sanity SEO from Cursor
- Fix Next.js SEO from Cursor
- Fix Lovable SEO from Cursor
- Fix GitHub SEO from Cursor
- Fix Craft CMS SEO from Cursor
Frequently Asked Questions
Can Cursor fix SEO on my Drupal site?
Yes, through SEOmatic. Cursor reads your Google Search Console data, finds what is holding your Drupal pages back and stages the fix. SEOmatic connects to your Drupal site over JSON:API using OAuth2. Agents write new nodes and improve existing ones, and hand you anything your site has no field for rather than failing the whole save.
What can Cursor change on Drupal?
Writes And Improves Nodes: New nodes written from research, plus rewrites of the title and body content on ones already published. Path Aliases, Not Node IDs: Agents set the URL alias, so your pages keep readable addresses instead of falling back to /node/123. Nothing Applies Without You: The agent arrives switched off and starts in approval mode. It earns more rope only when you give it. A Diff For Every Change: A before and after view with the reasoning attached, so you see what changed and why. One Click Revert: Any change rolls back to its previous value. Low-risk edits that cost you traffic revert on their own. Honest About Your Modules: Meta is written through the Metatag module when your site runs it. When it does not, agents hand you that work rather than assuming it is there.
What do I need to connect Drupal?
A Drupal site with the JSON:API module enabled (it ships with core) and the Simple OAuth module installed. You create a Consumer under Configuration Simple OAuth whose user has permission to write content, then paste its Client ID and Secret. Meta fields additionally need the Metatag module.
What do I need on the Cursor side?
Cursor and a free SEOmatic account, which you can create during sign-in. Use OAuth, not an API key: Cursor does not send a configured Authorization header.
Will Cursor publish to Drupal without asking?
No. By default every change SEOmatic proposes waits for your approval before it touches your site, and your assistant is told never to approve on its own. Approved changes are stored with the page's previous state, so any edit to an existing page can be rolled back. If you later want low-risk fixes to go ahead on their own, you can turn that on in your autonomy settings; changes to your URLs or indexing, and new content, still wait for you.
Is it free?
Connecting is free with no card: 5 questions a month from your own data, plus 10 once you connect Search Console, and site audits of up to 30 pages. Staging and publishing fixes is part of paid plans, which start with a 14-day free trial.