Optimize Ecommerce Store with Cursor: Product HTML the Crawler Can Read
Human-Edited & Verified • Deterministic AI-assisted research. Editorial standards.
AI Edited
Last updated: 24 September 2026
Optimize ecommerce store with Cursor means the agent edits product templates, titles, and structured data in the repo so the first HTML response already contains the product name, price, and availability.
TLDR
- Google recommends unique titles and descriptions per product URL, and crawlable links to those URLs (ecommerce guide).
- Product structured data needs a name, image, and offer details that match the visible page (Product markup).
- Cursor project rules live in
.cursor/rulesas.mdcfiles..cursorrulesis legacy (Cursor rules). - First-party GSC (24 Aug–21 Sep 2026): this URL had 7 impressions and 1 click at position ~23. The CSV cluster volume is 1,166. Keep the slug.
- Category copy and audits stay on other URLs. This page is the Cursor install recipe.
Contents
- What to change in the repo
- Pin rules so Agent edits templates
- Product markup that matches the page
- What this URL does not own
- FAQ
- Related reading
- Sources
What to change in the repo
Google’s ecommerce guidance asks for a unique URL per product, a title and description that match that product, and internal links from category pages. Faceted filters that create endless parameter URLs should be canonicalized or blocked, not dumped into the sitemap.
In Cursor, the job is a file edit:
- Open the product template.
- Put the product name in the H1 and the
<title>. - Render price and availability in HTML, not only after a client fetch.
- Point the canonical at the clean product URL.
The Cursor hub lists the rest of the catalog. The method skill for store structure is ecommerce SEO.
Pin rules so Agent edits templates
AI Edited
Cursor documents project rules in .cursor/rules/*.mdc. Put the store constraints there: one H1, no invented prices, canonical without tracking parameters, images with width and height.
npx @seoskillsai/cli add cursor --all
npx @seoskillsai/cli run seo-ecommerce --agent cursor --target "https://example.com"
Chat output is not a ranking page. Commit the template. The content recipe covers article files. This URL covers product and category templates.
Product markup that matches the page
Product rich results require structured data that agrees with visible content. Google lists name and image, plus offer fields such as price and availability, on the product page itself (Product). A JSON-LD block that names a different SKU than the H1 fails that check.
Merchant listings have extra policies for title, image, and identifier. Those policies are not a second ranking URL on this site. Keep them in the template checklist.
What this URL does not own
| Job | URL |
|---|---|
| Store method, any agent | /skills/seo-ecommerce |
| Article drafting in Cursor | /cursor/seo-content |
| XML discovery of product URLs | /skills/seo-sitemap |
First-party impressions here are still small. Do not retitle the hub at /cursor to chase this query.
FAQ
Where should product copy be written?
In the template or CMS field that renders in the first HTML response. A Cursor chat transcript is not that field.
Does Product schema replace unique titles?
No. Schema can enable a rich result when the visible page already states the same name, image, and offer.
Which rules file does Cursor read?
.cursor/rules markdown (.mdc). The old .cursorrules file is legacy.
Should every filter URL be in the sitemap?
No. Submit the canonical product and category URLs. Parameter variants belong behind a canonical or a crawl control.
Is this the same page as the content recipe?
No. /cursor/seo-content is for articles. This URL is for store templates.
Related reading
Sources
Cursor IDE Configuration Blueprint (.cursorrules)
Paste this configuration block directly into your .cursorrules:
{
"skills": {
"seo-ecommerce": {
"merchantReturnPolicy": true
}
}
}What the Cursor .cursorrules E-Commerce AI SEO & Product Schema Analyzes
Automated diagnostic data points evaluated during every execution run.
| Diagnostic Category | Specific Data Points Checked | Algorithmic Impact |
|---|---|---|
| Merchant Listings | Price, currency, availability, shipping details, return policies | Secures Google Shopping rich snippet carousels |
How to Execute E-Commerce AI SEO & Product Schema in Cursor IDE
Imperative configuration instructions with ready-to-run commands.
Step 1: Inject Product Schema
Auto-generate structured data for product catalogs.
seoskillsai ecommerce schema --catalog products.jsonDeploy This Skill on Other AI Coding Agents
Symmetric Twin Topics: Identical SEO capability configured for other agentic runtimes.