The Landing Page Deletion Checklist

Summary

The fastest way to improve a landing page is usually to remove things, not add them. But on a small in-house marketing team, every deletion needs a rationale you can defend to a boss who only sees 'you made it emptier.' This article is a checklist of six cuts — navigation, hedged headlines, competing visual elements, long forms, buried proof, and decorative extras — with the reasoning that explains why each one helps. You'll find a step-by-step example for every cut, plus the caveat that no rule is absolute. Working through the list turns a webpage into a page with one job: move the visitor to a single action. If you skip this process, you'll keep redesigning a crowded page and getting the same results.

The best landing page change you will make this week is a deletion. Not a redesign. Not a new font. Not adding more trust badges. A deletion. A landing page that tries to convince you of three things convinces you of none. The problem almost never is that your page says too little; it says too much.

When you work on a small in-house marketing team, every deletion needs a witness. Your boss will ask why the menu is gone, why the headline is shorter, why the button is louder. You need an answer that is not "it looks better." You need a rationale that stands up to a budget review. This checklist gives you that rationale, one cut at a time.

Your boss is not wrong to question you. They are applying the same filter they apply to every expense: does this pay for itself? A page with nine hundred words and fourteen links is harder to defend than a page with two hundred words and one button. The checklist below is your defense.

Work through it in order. Each cut is independent, but they compound. Cut the navigation, and the headline has to carry more weight. Make the headline carry the message, and the CTA can finally stand out. By the end, you'll have a page with one job and a paragraph for every choice.

Cut the navigation first

A landing page exists for one decision. Every navigation link is an exit ramp.

Say the page is for a free trial of your invoicing software. The menu shows Home, Features, Pricing, Blog. A visitor reads the headline, clicks Features, then Pricing, then leaves. The menu turned a landing page into a brochure. Remove the entire menu. Keep the logo, which sits in the top-left and quietly links home.

Your boss may say "But people need to see pricing." Answer: the pricing page is reachable through the logo. The landing page has one job: move people to the trial. If you must keep navigation for internal politics, put it in the footer, gray it out, and make sure it is nowhere near the headline. If you run this same page for two different audiences — small agencies and enterprise companies — run two pages, not one page with a menu. The logo is the only escape hatch. That is a feature, not a bug.

If you skip this, you hand the visitor a map out of your argument. The page is no longer a page with one goal; it's a corner of the website. This is the first step in any page-decluttering pass.

Write the headline last

A headline is a conclusion, not an introduction.

Here is the method: write the body first. Every bullet point and paragraph you create will repeat the real message. Underline the phrase that shows up the most. Make that phrase the headline. If you don't have a repeated phrase, you don't have a page yet. Write more body copy until you do.

Walk through it: you're building a page for a customer feedback tool. The first draft of the body says "We help product teams listen to their customers, close the loop on feedback, and build the right roadmap." The phrase that shows up again and again is "listen to your customers." That becomes your headline. If you had started with the headline, you'd get something like "Welcome to Our Website" or "The Best Customer Feedback Solution." Both say nothing.

Lock the body copy before the headline. If you skip this, your headline will be a greeting and your best argument will stay buried. When your boss asks "why did you change the headline?", you have a process answer: the headline is the conclusion of the page, so the page came first. That is a defensible methodology, not a taste.

Make the CTA the only bright object

Your page needs one focal point, and it should be the button.

Test it with a screenshot. Convert the page to black and white. If your eye goes to anything but the button, you have a hierarchy problem. Now color the button with the most saturated color you have and check again. The button should win.

Example: a consulting firm page has a big photo, a blue headline, and an orange button. Desaturate the photo and make the headline gray. The orange button becomes the first thing seen. That order is what you want: button first, then headline, then image. Make the button text action-oriented: "Start your trial," not "Submit." That reinforces the focal point.

Run the squint test on every new page. If the button loses, tone down everything around it. Check the button color against the page background too: a button that is bright but blends into the section will still fail. If you skip this, you make the visitor hunt for the action. Most people stop hunting. This is one of the visual hierarchy tweaks that matter most.

Cut the form down to three fields

Every extra form field is a demand for trust the visitor has not given.

Example: the page offers a free report. The form asks for name, email, job title, company, phone number, and number of employees. Visitors wonder why you need the phone number before they get a report. They leave. Change it to name and email. In practice, many teams find this single edit lifts conversions more than any visual change. The number of fields you ask for is a statement about who you think you are. Two fields says "we trust you." Seven says "prove yourself first."

Frame it to your boss as removing a roadblock, not losing data. If you keep a third field, label it optional. If you can, place the form where the visitor has already made a small commitment, like a button click, but keep it visible on the page.

What happens if you skip: your form becomes the place where momentum dies. Caveat: if the page sells a six-figure B2B contract, you need qualifying fields. That's an exception. For most offers, two fields is enough.

Plant proof where the doubt starts

People believe other people before they believe you. Put that belief exactly where the skepticism peaks.

Example: you claim your software reduces support tickets for busy teams. Visitors doubt that line the moment they read it. Put a testimonial from a customer who confirms the drop in the same section, next to the claim. Not at the bottom of the page. Next to it. That answers the question before it gets asked.

Make the proof specific. A quote with a person's name and role outranks an anonymous sentence. A client logo outranks a blank space. A real number, when you have it, outranks a generality. If you have no proof yet, create it. Ask a pilot customer for a one-line quote. Put it up. A short, true quote beats a long, beautiful claim. If a claim has no proof beside it, either add proof or delete the claim. If you skip this, your page is a series of unproven promises. This is part of a system for building trust instantly.

Break a rule when the goal demands it

Every best practice is context-dependent. The delete-first advice fails when the audience needs something before they can act.

Example: a heritage brand asks visitors to trust a history that goes back decades. A small footer link to "Our Story" is not a distraction; it's evidence. A B2B page for a six-figure contract may legitimately need more form fields because the buyer expects qualification. The rule is not "delete everything." The rule is "delete everything that does not serve the goal."

Before you cut anything, ask "Does this help or hinder the single action?" If it helps, keep it. If it does not, cut it. Then show your boss the exact reasoning: "We removed X because Y; we kept Z because W." That is a report, not a redesign debate. When the boss asks "why are you deleting this?", don't say "best practice says so." Say "this element does not help the action, and every element that does not help is a cost." For the full editing approach, see this checklist of defensible landing page changes.

Run this checklist before you design anything new. It's cheaper to delete on a blank page than after the boss has approved the visuals.

The bottom line

The page you build this week will be judged by one metric: did the visitor take the action? Make sure every element serves it. Delete what does not. Keep what does. Then when your boss asks why, you have the answer — not because you liked the change, but because the page now has one job. And if you are asked to defend it, now you can. That is the difference between a page you just redesigned and a page you can stand behind.