If you had to delete your entire website but keep only one section live, what would that section be?
by•
Over time, I’ve realized how much effort we put into our websites on landing pages, pricing, testimonials, product tours and yet, most visitors only ever deeply interact with one or two sections depending on your ICP.
For developer-first products, that’s usually docs.
For consumer apps, maybe it’s onboarding or pricing.
For enterprise tools, perhaps case studies or ROI calculators.
The rest is mostly noise or at least secondary.
It made me wonder:
If you had just one section on your website that truly converts, educates, or builds trust, what would you keep and why?
Would it be the one that brings traffic?
Or the one that brings conviction?
181 views
Replies
Theysaid
Good point! In that case, I’d keep the product section it’s where people really understand what you’re building and how it helps them. If that page clearly shows value, everything else (pricing, testimonials, etc.) naturally follows.
Triforce Todos
I’d keep the docs. If you’re building for developers, good documentation is your marketing. It shows care, clarity, and capability, all in one place.
We're building a dev-first product and I'd choose docs, testimonials and my feature story.
I’d keep the case studies section. Nothing builds conviction like real proof of impact.
A designer here, your main page which should your product page should be what you should likely keep. to make it convert it has to tell a story about what your product is all about, using accurate pictures, videos and illustrations. So they know problem your product would solve for them as this is the only reason they would want to take look at the pricing.
Most mistakes that are being made is that a lot of founders wants a whole lot of information on the product page which most times can be overwhelming to users which can result to a churn.
I'd also say you should list out your most important features, keep the description minimal for quick read starting from your hero page and if possible you might need a little video about your product if it's ready to help users quickly know what you are building. Also for starters I'm thinking how about you let them sign in to use your product and let them use your product to an extent to which they'd be willing to pay if it get's locked to use that feature. you could do that by putting a limit to which they can use it, that way they get to see if it solves their problem and can be willing to pay if they would want to proceed.
I would keep outcome and comparison section as this could add a lot of value in decision taking.