On-Page SEO & Semantic HTML Architecture

What it does

On-Page SEO & Semantic HTML Architecture is a Cursor skill: a SKILL.md playbook that AgenticKit installs at .cursor/skills/on-page-seo. Cursor's agent loads it when the task matches the skill description, instead of stuffing the same rules into every chat.

On-page search engine optimization standards ensuring keyword-targeted titles, optimal meta descriptions, single H1 tags, and semantic HTML5.

Title tag formulas, meta descriptions, single H1 rule, and semantic hierarchy. The file is domain knowledge, not a slash macro. You do not type it. The agent reads it when the job is on page 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) and Content Strategy Lead (content-marketer) agents. It is wired to the /seo-audit: Technical SEO & Keyword Cluster Audit and /seo-fix: Automated SEO Tag & Structured Data Fixer 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 On-Page SEO & Semantic HTML Architecture when the work is specifically about title tag formulas, meta descriptions, single h1 rule, and semantic hierarchy.
• 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/on-page-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-audit: Technical SEO & Keyword Cluster Audit.
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/on-page-seo and apply it to this change. Do not invent extra conventions."

Or trigger the pipeline: /seo-audit: Technical SEO & Keyword Cluster Audit. That command is written to load this skill.

Check the output against: Include primary target keyword and brand name in title tags under 60 characters

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-audit: Technical SEO & Keyword Cluster Audit, expect repo files plus notes under docs/, not a chat-only answer.

Best practices

• Include primary target keyword and brand name in title tags under 60 characters
• Write unique, compelling meta descriptions between 140 and 160 characters
• Ensure every indexable page has exactly one H1 tag summarizing the main topic
• Structure content with logical heading hierarchy (H1 -> H2 -> H3) and semantic tags

Common mistakes

• Ignoring "Include primary target keyword and brand name in title tags under 60 characters" 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.