Entity SEO & JSON-LD Structured Data

What it does

Entity SEO & JSON-LD Structured Data is a Cursor skill: a SKILL.md playbook that AgenticKit installs at .cursor/skills/entity-seo. Cursor's agent loads it when the task matches the skill description, instead of stuffing the same rules into every chat.

Structured data implementation using JSON-LD and Schema.org vocabularies to earn Google rich snippets, knowledge graph cards, and breadcrumbs.

Schema.org markup, SoftwareApplication, Organization, and BreadcrumbList. The file is domain knowledge, not a slash macro. You do not type it. The agent reads it when the job is entity seo.

Why it exists

Default Cursor has no memory of how your team ships positioning, copy, and launch assets. Founders paste the same conventions into chat, then watch the model drift on the next turn. This skill exists so those conventions live on disk and load only when relevant.

It ships in the Marketing Kit. It is wired to the Technical & On-Page SEO Lead (seo-specialist) agent. It is wired to the /seo-fix: Automated SEO Tag & Structured Data Fixer and /seo-audit: Technical SEO & Keyword Cluster Audit commands. That graph is the point: the skill is the standard, the agent is the role, the command is the trigger.

When to use it

• Use Entity SEO & JSON-LD Structured Data when the work is specifically about schema.org markup, softwareapplication, organization, and breadcrumblist.
• Load it before a long session that will touch this surface more than once. A one-line edit does not need the full playbook.
• Use it when you are writing something a buyer will see: landing copy, launch posts, SEO pages, or positioning docs.

When not to use it

• Do not treat the skill as a replacement for a slash command. Skills teach. Commands run a pipeline.
• Do not paste the whole SKILL.md into chat. If Cursor is not loading it, fix the description or invoke the matching command.
• Do not use it to generate spam or spray the same launch post across every channel.

Example workflow

1. Install the Marketing Kit so .cursor/skills/entity-seo lands in the repo.
2. Open a new Cursor agent chat pointed at the files this skill governs.
3. Ask the Technical & On-Page SEO Lead (seo-specialist) to read the skill, or run /seo-fix: Automated SEO Tag & Structured Data Fixer.
4. Review the first artifact against the practices below. If it violates one, stop and correct the file. Do not prompt 'just finish it'.
5. Commit the skill-guided files with the rest of the slice so the next session inherits the same standard.

Example usage

Example prompt: "Read .cursor/skills/entity-seo and apply it to this change. Do not invent extra conventions."

Or trigger the pipeline: /seo-fix: Automated SEO Tag & Structured Data Fixer. That command is written to load this skill.

Check the output against: Implement SoftwareApplication schema with operatingSystem, price, and featureList

Example output

• The skill itself does not write a single output file. It changes what the agent is allowed to produce in positioning, copy, and launch assets.
• When you run /seo-fix: Automated SEO Tag & Structured Data Fixer, expect repo files plus notes under docs/, not a chat-only answer.

Best practices

• Implement SoftwareApplication schema with operatingSystem, price, and featureList
• Add Organization schema with logo, website URL, and verified social media sameAs links
• Include BreadcrumbList schema on nested routes to enhance search result navigation
• Add Article schema with author, datePublished, and headline for blog posts

Common mistakes

• Ignoring "Implement SoftwareApplication schema with operatingSystem, price, and featureList" and hoping a later prompt will clean it up.
• Copying the skill into .cursor/rules as always-on. That burns context and fights Cursor's load-on-match design.
• Running two overlapping skills that contradict each other in the same turn.
• Publishing generated copy without a human pass. The skill is a playbook, not a publisher.