Book a call →

Codnity Growth · Landing pages

Landing Page Design & Build

A product or landing page earns its keep when every section answers one question the buyer is already holding: what is this, will it suit me, what does it cost delivered, and what happens if it is wrong. Sections that answer nothing get cut, which is usually most of the page.

Live in 10 working daysBuilt, not templatedDelivered cost up front

Why the traffic arrives and leaves

Your page is not underperforming. It is answering the wrong questions.

Open your current page and read it as a stranger with a budget and a deadline. These four are what we find almost every time, in this order of frequency.

The page sells the brand, not the product

Count the sentences on your current page where the subject is your company rather than the thing being bought. On most product pages it is over half. A buyer deciding between you and one other brand finds your founding story where the specification should be.

Six sections, no questions answered

Feature grids, a badge row, press logos and a "why choose us" list can fill a page while answering nothing a buyer is actually holding: what is this, will it suit me, what does it truly cost delivered, and what happens if it is wrong.

The real cost is three clicks away

The price is on the page and the shipping, duty and return terms are not, so the number a buyer decides on is not the number they are shown. Surfacing the delivered cost early loses a few browsers and keeps the people who were going to check out.

It loads in four seconds on a phone

Page builders ship 300 to 900KB of framework you never asked for. On mobile, where more of your traffic converts, that is the difference between a scroll and a bounce and no amount of copy work rescues it.

What makes a product page actually convert?

A converting product page answers the buying questions in the order they arrive: what this is, whether it suits me, what it costs delivered, what other people found, and what happens if it is wrong. Anything that answers none of those is competing for attention with the parts that sell.

  • One question per section, answered before the scroll
  • Delivered cost and return terms above the decision, not at checkout
  • Reviews carrying the count, because the number is the evidence
What if it is wrongreturns, stated plainly
What others foundreviews, with the count
What it costs deliveredshipping and duty included
Will it suit mewho it is for, and who it is not
What it isnamed in the first line
The order the questions actually arrive in

Should paid ads go to a product page or a dedicated landing page?

Shopping and branded search should land on the product page, because the buyer already chose the product and anything else adds a step. A dedicated page earns its place when the ad makes a promise the product page does not carry: a bundle, a campaign, a first-order offer.

  • Product page for Shopping and branded search
  • Dedicated page when the ad promises something the PDP does not
  • Never the homepage; the visitor should not have to search twice
What did the ad promise?
This exact product · send to the PDPA bundle or campaign · build the page
One question decides where the click lands

How do you write a collection page that ranks and converts?

A collection page has two jobs most stores only build for one of. It must help someone choose between the products in it, and it must answer the category question a search engine is matching against. Filters and a product grid do the first and nothing at all for the second.

  • Category copy that answers the question, above or below the grid
  • Filters framed as the way buyers actually narrow the choice
  • Internal links to the products the category is best known for
Grid onlyGrid plus answer
Helps a buyer choosePartlyYes
Answers the category queryNoYes
Can be cited by an assistantNoYes
Earns linksRarelySometimes
Why most collection pages rank below a blog post

What should a wholesale or trade page include?

A trade buyer needs different facts to a consumer and usually leaves when they are missing. Minimum order, unit pricing or margin, lead time, stock depth, delivery terms and who to talk to. Most brands hide all of it behind an application form and lose the enquiry.

  • Minimum order and lead time stated, not requested
  • Margin or trade pricing indicated, even as a band
  • A named contact and a route that is not only a form
Named contact
Enquiry lostSlow enquirySome enquiriesQualified enquiry
Form only
Terms hiddenTerms stated
What a trade buyer needs before they will make contact

How fast does a product page need to be on mobile?

Speed is a revenue setting on a product page, not a technical score. Most page builders ship several hundred kilobytes of framework nobody asked for, and on a phone that arrives as a delay between the tap and the price. Codnity builds in code so the weight is what the page needs.

  • Measured on a real mobile connection, not a desktop lab score
  • Hand-built rather than assembled in a builder
  • Images sized for the slot they occupy, not the slot they might
140KBtypical page weight we ship, against the 900KB a builder-assembled page arrives at
Measured on the pages in this unit

How much traffic do you need before A/B testing is worth it?

Testing needs enough conversions per variant to separate a real difference from chance, which for most stores means a few hundred orders a month before the result means anything. Below that, the honest work is fixing what is obviously missing rather than measuring which of two buttons wins.

  • Roughly 400 conversions a month before a test resolves
  • Below it, fix the missing answers instead of testing colour
  • Sequential fixes beat a test that never reaches significance
Fix what is missing
Ship it
Measure orders
Then test
Testing is the fourth step, not the first

What if the page is not the problem?

Roughly a third of the time the page is not what is failing. The product is priced wrong for the market, the delivered cost kills it at the last step, or the traffic was never going to buy. Codnity says so in the first week rather than build a better page that converts the same.

  • Delivered cost tested against the market, not just the shelf price
  • Traffic quality checked before the page is blamed for it
  • If the product is the constraint, we will name it and stop
Page is silent
Rebuild the pageFix the targetingScale itFix the targeting
Page answers
Traffic buysTraffic never would
Only one of these four is a page problem

Where this stops

What Landing pages includes, and what it does not

The second column is the one worth reading.

Included
  • Copy written to the answer standard, every section mapped to a real buyer question
  • Hand-built in code, no page builder, no template, no framework you did not choose
  • One custom visual that shows the product working, not a stock photograph
  • Wholesale and trade pages built for terms, minimums and lead times
  • Conversion tracking wired to your analytics before launch, not after
  • Core Web Vitals measured on a real mobile connection and reported to you
Not included
  • A/B testing below roughly 400 conversions a month, you would be reading noise
  • Stock photography or illustration packs
  • Pages that hide delivery cost or return terms until checkout; we will push back
  • Ongoing content updates. That is the AEO retainer, not this
  • Rescuing a page whose offer is the actual problem, which we will say plainly
The uncomfortable part

About a third of the time the page is not the problem. The product is priced wrong for the market, the delivered cost kills it at checkout, or the traffic arriving was never going to buy. We will tell you that in the first week rather than take the build fee and hand you a beautiful page that converts the same.

We also cut hard. Expect to lose roughly a third of your current sections, including ones someone internally is fond of. If a section answers no question a buyer is holding, keeping it costs you the attention of the ones who would have bought.

Next step

Send us the page that is not converting.

Paste the URL and tell us what you expected it to do. We come back with the sections we would cut, the questions it fails to answer, and whether the problem is the page or the product behind it.

You get a written answer, not an invitation to a discovery call.

Landing pages FAQ

Questions we get asked

Why not use Webflow or a page builder?

Use one if the page will never need to be fast. Builders ship 300 to 900KB of framework you did not ask for, which shows up in Core Web Vitals and in mobile conversion. We hand-build in code and typically deliver the same page at 140KB. On mobile that is the difference between a load and a bounce.