← ClaudeAtlas

optimizing-on-pagelisted

Use when optimizing a single page for SEO — fixing title and meta, tightening H1/H2 hierarchy, improving internal linking and anchor text, auditing alt text, capturing featured snippets, or aligning a page with search intent. Auto-triggers on "optimize this page", "fix the SEO on this URL", "polish this blog post", "title and meta", "improve internal linking", "alt text audit". Per-page workhorse — takes a URL or markdown/MDX file path, ships ONE focused PR with title/meta/H/link/alt edits. Pairs with finding-underserved-keywords (feeds keywords in), auditing-technical-seo (clears blockers first), and adding-schema-markup (hands JSON-LD off).
benskamps/seo-superpower · ★ 0 · Data & Documents · score 70
Install: claude install-skill benskamps/seo-superpower
# Optimizing On-Page ## Overview The per-page workhorse. While `auditing-technical-seo` works at the site level and `finding-underserved-keywords` decides *what* to target, this skill executes the per-URL surgery: rewrite the title, tighten the meta, fix the H1/H2 spine, weave in internal links with descriptive anchor text, sweep alt text, and front-load a featured-snippet-capable answer. One URL in, one focused PR out. No site-wide refactors, no Notion docs. ## When to use - "Optimize this page" / "fix the SEO on `/blog/foo`" - A single blog post, landing page, or doc page needs polish - `finding-underserved-keywords` produced a keyword cluster to integrate into one page - A page ranks position 5–15 but the title/snippet is the bottleneck - An internal-linking or alt-text sweep was requested for one URL - You inherited a markdown/MDX file and need to ship it SEO-tight **Don't use for:** site-wide audits (`auditing-technical-seo`), pre-launch setup (`seo-bootstrap`), JSON-LD work (`adding-schema-markup`), or keyword discovery (`finding-underserved-keywords`). ## What this skill checks - **Title tag** — under ~600px (~50–60 chars), primary keyword in first 30–35 chars, no brand-doubling [1]. - **Meta description** — 140–155 chars (mobile truncates ~120) [2]; intent-aligned, value prop early. - **H1** — exactly one per page, ≤60 chars, distinct from `<title>` (no H1=title duplication), reads like a headline not a keyword string [3]. - **H2/H3 nesting** — logical hierarch