resolutionathens/tron-marketing-ai

/landing-page-seo — Landing-page optimization spec

Durable delivery gate

Resolve the durable destination before drafting the SEO spec. Follow the durable deliverable contract: select Drive or Confluence, capture review/owner/handoff metadata, work in a uniquely created scratch directory, publish through the matching publisher skill, return the complete success block, and clean scratch on success and failure. The published URL is the approved source for the engineering implementer; this skill never writes repository content or performs Git operations.

Turn a target keyword set + a page into a concrete on-page change list a developer can implement. Git-free: produces the spec; a git user makes the edits.

Inputs

• The page (live URL and/or its repo source .vue/content file) and the primary + supporting keywords (from tron:keyword-research).
• Run tron:seo-audit first if you don't already have the page's current state.

To name the source file behind a route, ask the owning repo rather than guessing at its layout — check-link resolves a route the same way the framework does, including catch-alls:

C="${CLAUDE_PLUGIN_ROOT:-$CLAUDE_SKILL_DIR/../..}/tools/content/content.sh"
bash "$C" check-link /<route> --repo <checkout>   # → {"exists":true,"resolved":"app/pages/…"}

The spec (what to deliver)

# On-page SEO spec — <page>

**Primary:** <kw> · **Supporting:** <kw, kw, kw>

| Element          | Current | Recommended                          |
| ---------------- | ------- | ------------------------------------ |
| Title            | <…>     | <≤60 chars, primary kw front-loaded> |
| Meta description | <…>     | <≤155 chars, benefit + kw, CTA>      |
| H1               | <…>     | <single, kw-aligned>                 |
| URL slug         | <…>     | <short, kw>                          |

## Heading outline

H2/H3 structure that covers the intent + supporting terms.

## Content additions

- <section to add / expand, with the gap it fills>

## Internal links

- Add link from <page> → <this page> with anchor "<kw>"

## Schema

- Add <Product/FAQ/Breadcrumb> JSON-LD: <fields>

## Technical / CWV

- <e.g. preload hero, lazy-load below fold> (from /site-audit)

Rules

• Match search intent before keyword density. Don't keyword-stuff.
• One page = one primary keyword. Keep titles/metas within length budgets.
• Every recommendation is specific and implementable — no "improve content" hand-waves.

Handoff

Draft $WORK/onpage-spec-<slug>.md, publish it to the resolved durable destination, and return the approved-source URL as Durable source. For website-bound work, set Website handoff to the named engineering publishing skill that owns the target surface; do not include repository paths, implementation syntax, branch steps, or deployment instructions. Summarize the title/meta/H1 changes and the single highest-impact fix for the engineering handoff.