Fix Next.js SEO from Claude
Claude SEO on your real Search Console data, with fixes you approve in the same chat.

Each local area page used to take us half a day to create and optimize.
With SEOmatic, we can create hundreds of pages in the same time, which helps our clients make the best use of their budget.
It's transformed how we deliver scalable SEO solutions.
Will Hawkins
Marketing Director, Digi-Business UK
Agents read your Search Console data, do the work, and prove what actually moved. You decide what ships.
14-Day Trial for $1, credited to your first payment.
Claude Code reads your real Google Search Console data through SEOmatic, finds what is holding your Next.js rows your routes render back, stages the fix, and tells you whether it worked. In Approval mode nothing goes live on Next.js until you approve it.

November 2026
One claude mcp add command, then claude mcp login seomatic to sign in. A plugin adds 21 SEO skills.
Free to connect and to read your Search Console. Staged fixes are part of paid plans, with a 14-Day Trial for $1, credited to your first payment. See pricing.
On Next.js, the templates live in your code and the content lives in a database. Claude Code fixes the code side in your repo, like a metadata function or a robots rule. SEOmatic writes the content side through the Postgres database your routes read, after you approve. Search Console tells both which pages to start with.
You: Check /services/24-hour-plumber in Search Console and fix its title.
Claude Code: From Sep 13 to Oct 10 (28 days), /services/24-hour-plumber had 2,060 impressions and 17 clicks at position 7.6 for "24 hour plumber". That is a low click rate for page one, so the title is the first thing to test: it reads "24 Hour Plumber". I staged a new title, "24 Hour Plumber: Here in 60 Minutes, Day or Night", to be written to the title column of that row in your Postgres table. Approve it here or in SEOmatic and it goes live on Next.js.
An example on a demo site; your numbers come from your own Search Console.
In SEOmatic, go to Connections and select Next.js. Paste your Postgres connection string. SEOmatic validates it and confirms the database name. The full walkthrough, with every screen, is on the Next.js integration page.
Run this in your terminal, then run claude mcp login seomatic. Sign in to SEOmatic in the browser and pick your site. Add --scope user to the command to use SEOmatic in every project, not just this one.
claude mcp add --transport http seomatic https://app.seomatic.ai/api/mcpOther ways to connect are on the Claude Code page.
Paste any of these into Claude Code. It answers from your data and stages the fix; you approve it before it reaches Next.js.
More that work well in Claude Code:
After you approve, SEOmatic writes the change through the Postgres database your routes read and checks that it is live. Then it measures the result against the page's own baseline and your site's trend: 14 days after a title change, 28 after a content refresh, 90 after a new page. Each change is marked verified, ineffective or regressed, and a low-risk change that loses traffic is rolled back on its own. Ask Claude Code "Did my Next.js title changes work?" and it answers from those verdicts.
Full articles and programmatic pages from research to finished draft, published as rows your routes already render.
The agent arrives switched off. Once on, it ships undoable fixes by itself and waits for you on anything larger, unless you choose Approval mode, where every change waits.
Agents remember the row they wrote and update it, so republishing does not leave you cleaning up copies.
Your app owns the rendering, so agents stay on their side of the line: they research, write and publish rows, and your code decides what happens to them.
Every field, limit and safeguard is on the Next.js integration page.
Next.js
A Postgres database reachable from the public internet, with a table that has an id column, plus INSERT and UPDATE permissions. Works with Supabase, Neon, Railway, Render, RDS and Lightsail. SSL is used automatically.
Claude Code
Claude Code and a free SEOmatic account. No API key and no Google Cloud project: the connection signs in through your browser.
Claude Code works the same way on WordPress, Webflow, Shopify, Ghost, Blogger, Wix, Squarespace, Framer, Drupal, BigCommerce, HubSpot CMS, Contentful, Strapi, Sanity, Lovable, GitHub, Craft CMS.
Can Claude Code fix SEO on my Next.js site?
Yes, through SEOmatic. Claude Code reads your Search Console data, finds the rows your routes render losing clicks and stages the fix, which SEOmatic writes to Next.js once you approve. The three setup steps are on this page.
What can Claude Code change on Next.js?
SEOmatic works on your rows your routes render through the Postgres database your routes read: titles, descriptions and content first, and more where Next.js allows it. Every field and limit is listed on the Next.js integration page.
How do I know if a Next.js fix worked?
SEOmatic measures every change it ships against the page's own baseline and your site's trend, 14 days after a title change, 28 after a content refresh and 90 after a new page, and marks it verified, ineffective or regressed. Claude Code can read those verdicts for you.
What do I need on the Claude Code side?
Claude Code and a free SEOmatic account. No API key and no Google Cloud project: the connection signs in through your browser.
Will Claude Code publish to Next.js 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. Search Console reports, page checks and 30-page site audits are free, as often as you like; live market data uses free questions, 5 a month plus a one-time 10 when you connect Search Console. Staging and publishing fixes is part of paid plans, which start with a 14-Day Trial for $1, credited to your first payment.
The same SEOmatic server and approval rules, from the agent you prefer.
Claude SEO on your real Search Console data, with fixes you approve in the same chat.
Hand Claude Cowork the SEO grunt work: it pulls your real numbers, writes the report into your files, and stages fixes you approve.
ChatGPT SEO on your real Search Console data, with fixes you approve in the same chat.
Two commands give Codex your Search Console data, so it fixes SEO where the bug lives: in your code.
Your real Search Console data in the Gemini app and in Gemini CLI, with fixes you approve.
An always-on SEO teammate: routines that read your Search Console and speak up when something changes.