We went through the feedback, tasks and conversations of our 45 finished landing page projects and counted which problems came up. Here is the ranking, with what causes each problem and how we deal with it.
| Problem | Landing pages affected |
|---|---|
| Brand fonts, colours and design details | 23 (51%) |
| Mobile layout | 15 (33%) |
| Legal pages, cookies, GDPR | 12 (27%) |
| Domain, hosting and DNS access | 11 (24%) |
| Booking and calendar setup | 8 (18%) |
| Forms and email notifications | 5 (11%) |
| Translations | 4 (9%) |
| Payment and checkout | 4 (9%) |
1. Brand details
About half of our landing pages had feedback on fonts, colours or visual details: a colour stripe in the wrong shade, a font that did not match the brand guide, icons in a different style. Landing pages are often built quickly for a campaign, and the brand guide is not always shared upfront.
How we fix it: we ask for the brand guide, exact colour values and font files at kickoff. If there is no guide, we take colours from the logo file and confirm them before building.
2. Mobile layout
Most landing page traffic comes from mobile ads, so mobile issues matter more here than anywhere. Typical feedback: social icons and buttons not aligned, the call-to-action button pushed below the fold, headlines too large on small screens.
How we fix it: we design mobile sections deliberately rather than letting them stack automatically, and we check the main call to action is visible without scrolling on a phone.
3. Legal pages and consent
Landing pages need an imprint and privacy policy link, and cookie consent if tracking pixels are used – which they almost always are for paid campaigns. On CRM-hosted pages, we host fonts inside the CRM rather than loading them externally.
How we fix it: legal links in the footer and consent handling are part of our landing page template, not an afterthought.
4. Domain and DNS access
The page is ready, but publishing it on the client's domain or a subdomain requires access to DNS settings. The person with the registrar login is often not the marketing contact.
How we fix it: we ask for DNS access or the IT contact at kickoff. For urgent campaigns we can publish on a temporary address and switch later.
5. Booking and calendars
Many lead pages end with "book a call". Calendar connections, availability rules, confirmation messages and reminders all need setup and testing.
How we fix it: we clarify the booking rules before building and test with real bookings, including confirmation emails.
6. Forms and notifications
Forms that must adapt to different audiences, redirects to thank-you pages, and notifications that must reach the right person. In one project, applicants and companies were using the same form, which confused both groups until we adapted the fields.
How we fix it: fewer fields, audience-specific forms where needed, a thank-you page by default, and test submissions before launch.
7. Translations
Bilingual campaigns need every element twice, including form labels, error messages and thank-you pages.
How we fix it: we finish the main language first, then translate from final approved texts.
8. Payments
Some landing pages sell directly: a course, an event ticket, a product. Payment setup adds provider accounts, test payments and confirmation emails.
How we fix it: we request payment provider access early and run test transactions before launch.
Beyond the ranking: tracking
Tracking problems appear rarely in our counts, but only because we set them up as standard: Meta Pixel and Conversions API, Google Ads conversions, GA4 events and UTM parameters. A landing page without working tracking wastes ad budget, so we treat it as part of the build.
What these problems have in common
Most of them are not technical failures. They are missing inputs: a brand guide, a DNS login, a booking rule, a decision on form fields. That is good news, because missing inputs can be prepared.
How these problems affect the timeline
Each problem on its own costs a few days at most. The damage comes when they stack up in the revision phase: brand details in round one, mobile in round two, a form change in round three. Our landing pages with none or one revision round were delivered in a median of 10 days; those with three or more rounds took 24 days. Solving the predictable problems before the first draft keeps a landing page in the fast group.
Prevention checklist
- [ ] Brand guide or exact colours and fonts
- [ ] Audience and single call to action defined
- [ ] Form fields and recipients agreed
- [ ] Booking rules, if a calendar is used
- [ ] DNS access or IT contact
- [ ] Legal page links available
- [ ] Ad and analytics account access for tracking
FAQ
Why do brand details come up so often?
Because landing pages are often commissioned quickly for a campaign and the brand guide is not shared. Sending it at kickoff avoids a whole feedback round.
Can a landing page go live without a cookie banner?
Not if it uses tracking pixels or analytics in the EU. Consent is needed before loading them.
How many revision rounds do landing pages usually need?
The median in our projects was 1. Pages with clear inputs often need none.
Should a landing page have one goal?
Yes. In our experience, one offer and one main action per page converts better and is quicker to agree on than a page trying to serve several audiences.
Can a landing page live on my existing domain?
Usually yes – as a page on your website or a subdomain. We decide based on where the page is built (WordPress or a CRM funnel) and on tracking needs.
Where the numbers come from: our own project records in Odoo – 233 finished projects, 909 tasks and about 4941 logged hours, mostly from 2025–2026. Durations are calendar days from kickoff and we quote medians, so one unusually long project does not distort the picture.
Planning a landing page project?
If you want a realistic plan for your own project, book a short call with our team and we will walk you through the phases, what we need from you and where projects like yours usually lose time. You can also browse finished work in our landing page portfolio.
Comments