Fix BigCommerce SEO from Cursor

Your BigCommerce content lives in BigCommerce, not in a repo, so Cursor cannot change it with a file edit. Through SEOmatic it reads your Search Console, picks the products, web pages and blog posts losing clicks and stages the change, which SEOmatic writes through a BigCommerce store API account once you approve. If you keep theme or template code in a repo, Cursor can still fix that part directly.

You: Check /drain-snake-50-ft/ in Search Console and fix its title.

Cursor: From Sep 13 to Oct 10 (28 days), /drain-snake-50-ft/ had 1,240 impressions and 10 clicks at position 7.7 for "50 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 50". I staged a new title, "50 ft Drain Snake with Auto-Feed", to be written to the product's page title in BigCommerce. Approve it here or in SEOmatic and it goes live on BigCommerce.

An example on a demo site; your numbers come from your own Search Console.

In your BigCommerce admin, go to Settings, then API, then Store-level API accounts, and create an account with Content and Products set to modify. Copy the access token, which is only shown once. In SEOmatic, go to Connections and select BigCommerce. Paste the token and your store hash, which is the identifier in your admin URL. The full walkthrough, with every screen, is on the BigCommerce 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.

Paste any of these into Cursor. It answers from your data and stages the fix; you approve it before it reaches BigCommerce.

• “Stage better page titles and meta descriptions for my top products.”
• “Which blog posts on my store are close to page one?”
• “Which BigCommerce product pages get impressions but few clicks?”

More that work well in Cursor:

• “Audit the live site and fix what our code causes”
• “Which URLs has Google not indexed, and why?”
• “Check the preview deploy against production”

After you approve, SEOmatic writes the change through a BigCommerce store API account 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 BigCommerce title changes work?" and it answers from those verdicts.

BigCommerce gives you no built-in way to write a distinct meta description for every product, so on a large catalogue it is hand-written or it is duplicated. Agents are the third option.

Every field, limit and safeguard is on the BigCommerce integration page.

BigCommerce

A BigCommerce store with owner or admin access. You create a store-level API account under Settings > API and grant it Content (modify), Products (modify) and Store Information (read-only). The access token is shown only once, so copy it before you close the dialog.

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, Squarespace, Framer, Drupal, HubSpot CMS, Contentful, Strapi, Sanity, Next.js, Lovable, GitHub, Craft CMS.