Fix Squarespace 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.
Cursor reads your real Google Search Console data through SEOmatic, finds what is holding your Squarespace products back, stages the fix, and tells you whether it worked. In Approval mode nothing goes live on Squarespace until you approve it.

November 2026
One mcp.json entry, or Customize > MCPs in the sidebar, with OAuth sign-in. If the browser does not open, start the sign-in from the seomatic entry.
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.
Your Squarespace content lives in Squarespace, not in a repo, so Cursor cannot change it with a file edit. Through SEOmatic it reads your Search Console, picks the products losing clicks and stages the change, which SEOmatic writes through the Squarespace Commerce API once you approve. If you keep theme or template code in a repo, Cursor can still fix that part directly.
You: Check /shop/drain-snake-25-ft in Search Console and fix its title.
Cursor: From Sep 13 to Oct 10 (28 days), /shop/drain-snake-25-ft had 1,760 impressions and 14 clicks at position 7.4 for "25 ft drain snake". That is a low click rate for page one, so the title is the first thing to test: it reads "Drain Snake". I staged a new title, "25 ft Drain Snake for Sinks and Tubs", to be written to the product's search title in Squarespace. Approve it here or in SEOmatic and it goes live on Squarespace.
An example on a demo site; your numbers come from your own Search Console.
In SEOmatic, go to Connections, select Squarespace and click Connect with Squarespace. You log in on Squarespace's own page and approve access to your products. That is the whole setup. Prefer keys? You can instead generate a Developer API Key with Products permissions in Squarespace settings and paste it. SEOmatic validates it as you type. The full walkthrough, with every screen, is on the Squarespace integration page.
Add this to ~/.cursor/mcp.json for every project, or .cursor/mcp.json in one repo, or open Customize in the sidebar and add the same URL under MCPs. Cursor opens the SEOmatic sign-in in your browser; approve it and pick your site. If it does not open, find seomatic under Customize > MCPs and start the sign-in there.
{
"mcpServers": {
"seomatic": { "url": "https://app.seomatic.ai/api/mcp" }
}
}Other ways to connect are on the Cursor page.
Paste any of these into Cursor. It answers from your data and stages the fix; you approve it before it reaches Squarespace.
More that work well in Cursor:
After you approve, SEOmatic writes the change through the Squarespace Commerce API 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 Cursor "Did my Squarespace title changes work?" and it answers from those verdicts.
Product names, descriptions, URL slugs and search listings, written new or rewritten on products already live.
Blogs and regular pages have no Squarespace API. Agents never propose work there, so you get no queue that cannot run.
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.
Squarespace opens up its Commerce API and nothing else, so this integration is deliberately narrow. Within products it does real work, and outside them it does not pretend to.
Every field, limit and safeguard is on the Squarespace integration page.
Squarespace
A Squarespace site with store owner access and products in your store. Connecting with your Squarespace login works on any plan; the API-key fallback needs an Advanced plan. If your site is a blog or a brochure site with no commerce, there is nothing here for agents to work on.
Cursor
Cursor and a free SEOmatic account, which you can create during sign-in. Use OAuth, not an API key: because SEOmatic advertises OAuth, Cursor starts the sign-in before it sends any configured Authorization header.
Cursor works the same way on WordPress, Webflow, Shopify, Ghost, Blogger, Wix, Framer, Drupal, BigCommerce, HubSpot CMS, Contentful, Strapi, Sanity, Next.js, Lovable, GitHub, Craft CMS.
Can Cursor fix SEO on my Squarespace site?
Yes, through SEOmatic. Cursor reads your Search Console data, finds the products losing clicks and stages the fix, which SEOmatic writes to Squarespace once you approve. The three setup steps are on this page.
What can Cursor change on Squarespace?
SEOmatic works on your products through the Squarespace Commerce API: titles, descriptions and content first, and more where Squarespace allows it. Every field and limit is listed on the Squarespace integration page.
How do I know if a Squarespace 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. Cursor can read those verdicts for you.
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: because SEOmatic advertises OAuth, Cursor starts the sign-in before it sends any configured Authorization header.
Will Cursor publish to Squarespace 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.
One command connects your Search Console to the terminal, so Claude Code fixes SEO in the code.
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.