Technical & On-Page SEO Lead

What it does

Technical & On-Page SEO Lead is a Cursor agent playbook named seo-specialist. AgenticKit installs it so a session can adopt this role instead of acting as a generic coding assistant.

The seo-specialist agent maximizes organic search traffic. It conducts technical audits, generates structured JSON-LD schemas, optimizes meta titles and descriptions, creates topical keyword clusters, and builds programmatic SEO architectures.

Optimizes page structure, schema markup, keyword clusters, and rank factors. SEO specialist for Cursor providing technical SEO audits, schema markup (JSON-LD), keyword clustering, canonical links, and search indexing.

Why it exists

A pile of agent files is not a team. seo-specialist exists so one job, technical & on-page seo lead, has a written brief, required skills, and a stop condition.

It ships in the Marketing Kit. Skills it must read: On-Page SEO & Semantic HTML Architecture; Entity SEO & JSON-LD Structured Data; Pillar-and-Cluster Content Architecture. Commands that adopt this role: /seo-audit: Technical SEO & Keyword Cluster Audit; /seo-fix: Automated SEO Tag & Structured Data Fixer; /blog-post: SEO Blog Post & Technical Tutorial Generator.

When to use it

• Ranking high on Google for high-intent developer keywords
• Fixing duplicate titles, missing meta tags, and schema errors
• Scaling organic inbound search traffic with programmatic pages

When not to use it

• Do not ask seo-specialist to do a different role's job. If you need a migration, switch agents.
• Do not keep the same chat after this agent has finished its artifact. Start a reviewer in a new thread.
• Do not invoke every agent in the kit for a small change.

Example workflow

1. Install the Marketing Kit so .cursor/agents/seo-specialist is on disk.
2. Run /seo-audit: Technical SEO & Keyword Cluster Audit, or start a chat and tell Cursor to adopt the seo-specialist role.
3. The agent should read: On-Page SEO & Semantic HTML Architecture; Entity SEO & JSON-LD Structured Data; Pillar-and-Cluster Content Architecture.
4. It produces the artifact for this role only, then stops.
5. A different agent or you review. Same-chat self-review is not a review.

Example usage

Example: "You are seo-specialist. Ranking high on Google for high-intent developer keywords. Read on-page-seo before you edit."

Or let the pipeline invoke it: /seo-audit: Technical SEO & Keyword Cluster Audit.

Capabilities you should actually see: Technical SEO audits (crawling, canonicals, robots.txt, sitemaps)

Example output

• seo-specialist should leave files or a written verdict, not a vibe check. Technical SEO audits (crawling, canonicals, robots.txt, sitemaps) JSON-LD structured data implementation (SoftwareApplication, Article, FAQ)
• Marketing agents write markdown under docs/marketing/ so later commands can reuse positioning and voice.

Best practices

• Technical SEO audits (crawling, canonicals, robots.txt, sitemaps)
• JSON-LD structured data implementation (SoftwareApplication, Article, FAQ)
• On-page heading hierarchy and semantic HTML optimization
• Programmatic SEO architecture and keyword cluster mapping
• One role per chat unless a command is explicitly orchestrating a sequence.

Common mistakes

• Using seo-specialist as a synonym for 'the Cursor agent'. It is a brief, not the product.
• Skipping the required skills and hoping the role name is enough.
• Publishing the first draft of launch copy without a human edit.
• Invoking this agent and three unrelated ones in the same prompt.