Landing Page Structure Reviewer

What it does

Maps a landing page's existing sections against a standard high-converting sequence (hero, social proof, benefits, objection-handling, call to action), flags missing sections and any call to action buried below a reasonable scroll depth, and suggests a reordering with rationale. Works from the actual published section content rather than a generic template checklist.

Install

This skill isn't packaged in an installable registry. It's a plain SKILL.md file you can copy directly. Copy it from the SKILL.md tab and save it at the path for your assistant:

Use it in your AI assistant

Claude Code

.claude/skills/landing-page-structure-reviewer/ (or ~/.claude/skills/landing-page-structure-reviewer/ for all projects)

GitHub Copilot (VS Code)

.github/skills/landing-page-structure-reviewer/

OpenAI Codex

.codex/skills/landing-page-structure-reviewer/

Cursor

.cursor/skills/landing-page-structure-reviewer/ (or ~/.cursor/skills/landing-page-structure-reviewer/ globally)

Compatibility

Any WordPress site. Works with block editor or page builder content the agent can read section by section.

The complete SKILL.md for this skill:

---
name: landing-page-structure-reviewer
description: Use when a user wants a landing page reviewed for conversion structure, mentions a page that isn't converting, or asks whether their sections are in the right order.
---

# Landing Page Structure Reviewer

## When to use
The user has a landing page (product, campaign, or signup) and wants its section order and content checked against conversion-focused structure, not just a general design review.

## Procedure
1. Map out the page's existing sections in order: hero, any proof elements, benefits/features, pricing, FAQ, calls to action, and so on.
2. Compare against a standard high-converting sequence: a clear hero with one primary message, social proof, concrete benefits, objection-handling (FAQ or guarantees), and a clear call to action.
3. Flag any standard section that's missing entirely, particularly social proof or a clear primary call to action.
4. Check how far a visitor has to scroll before hitting the first call to action, and flag it if that's unreasonably deep for the page's purpose.
5. Note sections that repeat the same point without adding new information, a common source of a page feeling longer than it needs to be.
6. Suggest a reordering with a one-line rationale per change, rather than rewriting the page's content itself.

## Guardrails
- Don't rewrite section copy unless asked, this skill is about structure and order, not copywriting.
- Treat "best practice" as a starting hypothesis, not a rule, flag where the page's specific audience or offer might justify deviating from it.