agentleFS
RomeoSEORomeoSEO/seo-skills/skills/landing-page-writer/SKILL.md

landing-page-writer

Skill7 starsChanged 14 days agoMITView on GitHub

Plan, write or fill out a product, feature or service landing page so it is complete and true to the product, building from the site's own proof, pricing and screenshots first, with every claim sourced. Use for "write a landing page", "this page looks empty", "build a page for our new feature", "turn this keyword into a landing page", or a landing page that gets visits but few sign-ups.

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 6 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  • could be automatic: a setting could enforce it
  1. Distinctive:

    The product is the source of truth: Every feature, step and button name matches what the product does today, in the product's own words: …

    line 81
  2. Distinctive:

    Screenshots leak: Use test or demo data when possible.

    line 96
  3. Distinctive:

    Fit the search: When the page targets a query, read what ranks.

    line 110
  4. Distinctive:

    The customer's words: Write the outcome the reader wants in the words they use.

    line 116
  5. Distinctive:

    Inventory the site: Read the homepage, pricing, about, docs and help, existing feature pages, case studies and related blog posts.

    line 145
  6. Distinctive:

    Honesty pass: Read every sentence as a skeptical buyer: is it true today, in the product, for the plan they'd buy?

    line 169

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Landing page writer

Plans and writes landing pages for one product, feature or service: what the page must contain, where each piece already exists on the site, and the copy for every section. It checks the page against a completeness list (a real look at the product, a sample of what the customer gets, proof, how it works, how it differs, pricing, what happens after sign-up, the objections) and fills gaps from the site's own material before writing anything new. Every claim is traced to the product or a source. It hands back the page, a completeness table, an asset inventory and a claims sheet.

Romeo's rule: Most landing pages look empty because the good stuff lives on the homepage. Go get it before you write a single new word.

Use this when

  • A new product, feature or service needs its own page.
  • A landing page looks thin, empty or "not like a real product", or gets visits but few sign-ups.
  • search-intent-match said a query needs a landing page, not an article.
  • A page lists features as claims, with no product screenshots, no sample of the output, no proof and no price.

Don't use this for

  • Articles, guides and how-tos → seo-blog-writer
  • "Best X", "X vs Y" and "X alternatives" pages → comparison-page-writer
  • Checking an existing page against its search query (title, headings, content gaps against the ranking pages) → on-page-seo-review. Run both on an important page: that skill compares with competitors, this one checks the page is complete and true to your product.
  • Titles and descriptions only → title-meta-ctr
  • Structured data → schema-markup
  • One page per city, plan or integration at scale → programmatic-seo-plan

What you need

Required

  • The product, feature or service, who the page is for, and the one action it should get (start a trial, book a call, request a quote, buy).
  • The site's own pages: homepage, pricing, about, help or docs, existing feature pages, case studies, and blog posts on the topic. URL fetching or a crawl, or the user pasting them.
  • The product itself: an account, a demo, its docs, screenshots, or the code. Feature names, steps and outputs come from here, never from memory.
  • For a software product: real screenshots of the screens this page is about, or a way to take them (an account with realistic data, a demo workspace).

Helpful

  • The target search query, and Search Console data for the current page.
  • Sales and support notes: the questions people ask before buying, and why deals are lost.
  • Reviews, testimonials and case studies, with permission to quote them.
  • The site's design components (an existing feature page to copy from), and analytics for the current page.

No tools?

Open the homepage, pricing and about pages in a browser and copy every piece of proof, every price and every product screenshot you find into the asset inventory, with its URL. Sign in to the product and take your own screenshots of the real screens. Search the target query in a private window and note what kind of pages rank.

Ground rules

  • Reuse before you write. Inventory the site first: testimonials, review scores, customer numbers, logos, the founder's story, case studies, prices and plan names, trial terms, guarantees, screenshots, demo videos, sample outputs, FAQs. A thin landing page next to a rich homepage is the most common problem this skill finds.
  • The product is the source of truth. Every feature, step and button name matches what the product does today, in the product's own words: read the interface, the docs or the code. A claim you can't check doesn't go on the page. Say plainly what it doesn't do when buyers would assume it does.
  • Show the product. For software, real screenshots of the real interface are what make the page read as a product, not a brochure: at least one in the first screen and one per major section. Crop to the part the copy talks about, put it in a light browser or app frame, and write alt text that says what the screen shows. A coded mock-up of a screen is fine as a supplement (it stays sharp and can be annotated) but never as the only look at the product. For a service, show the deliverable: a sample report, a before and after, a real (anonymised) project.
  • Samples are labelled as samples. Example data in a screenshot or mock output is marked "Sample" or "Example". Never present invented numbers as a real customer's results.
  • Screenshots leak. Use test or demo data when possible. Before saving or sharing a capture, check it for names, email addresses, customer records, account details, credentials and other private information, and remove or obscure them without misrepresenting the product. Get the user's permission before publishing any real data, even their own.
  • Proof must be real. Quotes, ratings, logos and numbers only with a source and permission. In the US the FTC's rule on fake reviews and testimonials (16 CFR Part 465, in force since October 2024) bans made-up or misattributed reviews; other markets have similar rules. "Trusted by thousands" needs the number behind it.
  • One page, one job. One main call to action, repeated at the top, the middle and the end, plus at most one low-commitment option (a free tool, a sample report, a demo video). No fake urgency, countdowns or invented scarcity.
  • Fit the search. When the page targets a query, read what ranks. If the top results are guides, a pure sales page rarely ranks: add a short "how to do it" section and link a full guide. If they're product pages, compare their sections with yours. Cover related searches the reader uses (for a "content gap tool", also "keyword gap" and "competitor gap") where they honestly fit, such as a comparison section.
  • The customer's words. Write the outcome the reader wants in the words they use. Jargon only when the reader searches with it. Short sentences, one idea each.
  • Complete beats long. Length comes from covering the checklist, not from a word count. A missing section is fine when you decided it: write down why.

The completeness checklist

SectionIts jobWhere the material usually is
HeroThe promise in the reader's words (with the target query when there is one), one main action, one low-commitment action, and a real look at the productProduct, keyword research
How it worksThree or four steps, named as the product names themProduct interface, docs
The product, up closeScreenshots of the main screens, each with a one-line caption on what it showsProduct account, existing screenshot library
What you getA sample of the output: report, dashboard, deliverableProduct, sample data
What makes it differentThe mechanism that sets it apart from the alternatives, including doing it by handProduct, competitors' pages
ComparisonA fair look at the alternatives, with the reader's criteriaCompetitors' own pages (comparison-page-writer rules)
ProofTestimonials, numbers, a case study, the founder's story, logosHomepage, about page, review sites, sales
Who it's forThe situations and roles it fits, and who it's not forSales notes, customer list
What happens nextWhat happens after sign-up and after the main action: setup, delivery, results trackingOnboarding, product
PricingPlan, price, trial terms, what's included, or a link when prices live on one page onlyPricing page
FAQReal objections: setup, data access, cancellation, limits, "how is this different from X"Sales and support notes, "People also ask"
Teaching sectionA short how-to, when the search results are guidesExisting guide on the blog
Final call to actionThe main action again, with what happens when they clickProduct

Steps

  1. Confirm the job. Product or feature, reader, the one action, the target query (if any), and whether this is a new page or a rework.
  2. Inventory the site. Read the homepage, pricing, about, docs and help, existing feature pages, case studies and related blog posts. Fill in the asset inventory: every piece of proof, price, screenshot, video, sample and FAQ, with where it lives and how this page could reuse it. Note the pages that should link to the new page (homepage feature list, related features, related posts, free tools).
  3. Read the product. Walk through the feature as a customer would. Write down the exact names of screens, buttons, steps and outputs, what it needs to work (connections, data, plan), its limits, and what happens after the main action. Take or request screenshots of every screen the page will mention.
  4. Read the search (if SEO is a goal). For the target query and two or three close variants: what kind of pages rank, which sections they share, the "People also ask" questions and related searches. Decide whether the page needs a teaching section and which related searches it can cover honestly.
  5. Check completeness. Mark each checklist row for the current page (or the plan for a new page): Have, Thin, Missing or Left out, with the source you'll use and the action. A row left out needs a reason.
  6. Write the page. Section by section, in the checklist's order unless the search results suggest another. Tag each factual claim with its source in the claims sheet. Place screenshots where the copy talks about that screen. Write the title (query first, under about 60 characters), meta description and slug, and the internal links in both directions.
  7. Honesty pass. Read every sentence as a skeptical buyer: is it true today, in the product, for the plan they'd buy? Is every sample labelled? Is every testimonial real and permitted? Remove what fails.
  8. Plan the measurement. Name the one conversion event to track and what to compare after launch (sign-up rate from this page, and search clicks if SEO is a goal), then hand it to posthog-change-impact or your analytics.

What to hand back

Return all of this, in this order:

**What I found:** <the page's state in one sentence, e.g. "6 of 13 sections missing, no product screenshots, proof only on the homepage">
**What matters most:** <the two or three changes that make the biggest difference>
**What to do first:** <screenshots, permissions or facts still needed>

## Completeness
| Section | Status | Source | Action |
| --- | --- | --- | --- |
| Hero | Have / Thin / Missing / Left out | <page or product screen> | <what to do, or why it's left out> |

## Asset inventory
- <asset> | <where it lives (URL)> | reuse as <section> | permission: yes / ask / n.a.

## Page
title: <query or promise first, short>
meta_description: <one or two sentences>
slug: <short-slug>

# <H1>
<Copy for each section, with screenshot placements: [Screenshot: <screen>, caption: <...>, alt: <...>]>

## Claims sheet
- "<claim as written>" | <source: product screen, doc URL, pricing page> | checked <date>

## Internal links
- Add to this page: <anchor> → <URL>
- Link to this page from: <URL> (<where on that page>)

## Asset queue
- <screenshot or sample still needed> | <screen and data to show> | status: have / needed

## What I could not check
- <claim or feature>: <why, and what would verify it>

Stop and flag if

  • The product can't be seen (no account, docs or screenshots). Don't describe features from memory or marketing copy.
  • You're asked to invent testimonials, ratings, customer counts, logos or results, or to show real customer data without permission.
  • The page would compete with an existing page for the same search; check with keyword-cannibalization-check first.
  • The search results are all guides and the business won't add any teaching: say the page is unlikely to rank and suggest a guide plus a landing page instead.
  • The category is regulated (finance, health, legal, insurance). Get expert and legal review before publishing.
  • The output is unacceptable if a software page has no real product screenshot, any sample isn't labelled, any claim lacks a source, or a checklist row is missing without a reason.

Next step

  • seo-content-qa with the page and the claims sheet.
  • schema-markup for the page's structured data.
  • internal-linking-plan to add the links into the page, then cms-publishing-adapter to publish.
  • posthog-change-impact to measure whether the new page converts better.

Part of the free RomeoSEO skill library: https://romeoseo.com/skills

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.