Automated SEO Tag & Structured Data Fixer

What it does

/seo-fix is a Cursor slash command. Type it in chat to run a saved workflow: Automated SEO Tag & Structured Data Fixer.

Automatically fixes technical SEO issues: generates unique keyword-rich title tags, 140-160 character meta descriptions, Open Graph cards, and JSON-LD schemas.

Generates missing meta titles, Open Graph tags, canonicals, and JSON-LD schemas. Unlike a skill, a command is something you invoke on purpose. The agent does not decide to run /seo-fix for you.

Why it exists

Founders retype the same multi-step prompt until it rots. /seo-fix exists so the pipeline, all 4 steps of it, is a file in .cursor/commands, versioned with the repo.

It ships in the Marketing Kit. It is wired to the Technical & On-Page SEO Lead (seo-specialist) agent. Required skills: Entity SEO & JSON-LD Structured Data; On-Page SEO & Semantic HTML Architecture.

When to use it

• Use when optimizing existing pages for search indexing and rich social sharing.
• Use /seo-fix when you want that pipeline, not a freeform chat. If you only need one step, use a narrower command or a single agent.
• Start a new chat. Do not run this command in a thread that just touched production SQL.

When not to use it

• Do not run /seo-fix as a substitute for reading the diff. The command produces files; you still gate them.
• Do not chain it into a 40-turn chat. Fresh context is part of the design.
• Do not run it if you have not filled CURSOR.md. The pipeline will invent a stack.

Example workflow

1. Generate unique, keyword-targeted meta titles ending in brand name
2. Generate 140-160 char meta descriptions with natural keyword placement
3. Construct Open Graph and Twitter summary_large_image card tags
4. Implement Schema.org JSON-LD structured data markup

Example usage

Type this in Cursor chat: /seo-fix Add JSON-LD SoftwareApplication schema and OpenGraph image tags

The command file tells the session which agents to adopt and which skills to read. You should see phase headers, not a single dump of code.

If a phase fails its gate, stop. Do not add 'just continue'.

Example output

• Expected artifact: Relevant page.tsx and layout.tsx files

Best practices

• Keep the prompt specific. /seo-fix Add JSON-LD SoftwareApplication schema and OpenGraph image tags is the shape: object, constraint, and outcome.
• Let the listed agents work in order: seo-specialist.
• Save outputs in the repo. Chat-only answers evaporate.
• Marketing commands write to docs/marketing/ so the next command can read positioning before it writes a landing page.

Common mistakes

• Typing /seo-fix with no object ('do the thing'). The pipeline will guess.
• Re-running the command in the same chat after a failed gate instead of fixing the failing file.
• Editing the command file to skip review so it 'goes faster'.
• Skipping the Entity SEO & JSON-LD Structured Data skill that the command depends on.