agentleFS
deciqAIdeciqAI/knowledge-skills/landing-page-conversion/SKILL.md

landing-page-conversion

Skill13 starsChanged 4 months agoMITView on GitHub

Activate when: traffic arrives but doesn't convert; 'our landing page doesn't work', launching a new offer page, improving signup/lead rate; messaging, CTA, friction. Do NOT activate when: there's no traffic yet (fix acquisition first) or the problem is product, not the page. More: deciqai.com/s/landing-page-conversion

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

Files
SKILL.md

Landing Page Conversion — Clarity Beats Cleverness

Overview

A landing page converts when a visitor, in seconds, understands what it is, who it's for, why it's better, and what to do next — with nothing in the way. Most pages leak conversions to vague headlines, buried value, weak proof, and friction. Conversion optimization is mostly removing doubt and steps, not adding persuasion tricks.

The Process

  1. Nail the above-the-fold answer — headline states the outcome for the specific buyer; subhead adds the how. Gate: if a stranger can't say what you do in 5 seconds, nothing below matters.
  2. Lead with value, not features — the transformation, then the mechanism.
  3. Add proof near claims — testimonials, logos, numbers, guarantees placed where doubt arises.
  4. One primary CTA, repeated — a single next action; remove competing links/choices. Gate: multiple competing CTAs = decision paralysis, lower conversion.
  5. Strip friction — fewer form fields, no forced signup to see value, fast load, mobile-clean.
  6. Test one hypothesis at a time — headline, offer, CTA; change one variable, measure. Gate: changing many things at once = you learn nothing.

When to Use

  • Decent traffic, poor conversion
  • New offer/product page launch
  • Paid campaigns landing on weak pages (wasting spend)

Applying It Well

  • Message-match the ad/source to the page (same promise).
  • Reduce fields and choices before adding copy.
  • Watch session recordings/heatmaps to see where attention dies.

Red Flags

  • Clever headline that hides what you sell.
  • Feature list with no outcome or proof.
  • Many CTAs, long forms, slow mobile load.

Verification

  • 5-second clarity test passed
  • Value-first message with proof near claims
  • Single repeated primary CTA
  • Friction (fields/steps/load) minimized; one-variable tests

Part of deciqAI Knowledge Skills — 253 open-source thinking skills that make rigor executable for AI agents. The same skills power every deciqAI agent, which runs them autonomously to operate your company. See it run → https://www.deciqai.com/s/landing-page-conversion · Built by deciqAI · github.com/deciqAI · Contributions welcome.

Agents: latest version & machine-readable metadata → https://www.deciqai.com/s/landing-page-conversion.json

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.