Landing pages

Pages built for the ad, with forms that post straight into the loop.

This can be commissioned as a fixed-scope project without handing over Google Ads management. The fee is fixed after I check the existing page, brand assets, form route, tracking and hosting constraints.

The gap

Ads pointed at the homepage. Or at an SEO page with a full navigation, three thousand words, a chat widget that opens itself over the call button, and an eight second load on a phone. The visitor came from a search for "emergency boiler repair leeds" and the page is about the company's history.

The other version is the client building their own landing page in a tool that does not talk to the tracking, then wondering why the form fills do not show up in the account.

What we build

Static pages, with no CMS, public login or application database unless the project needs one. They are built for measured mobile performance and a smaller attack surface, but neither speed nor security is assumed: both are tested on the deployed page. One page per job: the service, the area, the price from, the phone number and the form. Navigation is reduced to keep the paid-traffic journey focused.

The form can post through a same-origin endpoint to n8n, with server-verified anti-spam protection. Eligible click identifiers and consent are preserved with the lead, the CRM write and conversion handoff are tested separately, and a tracking number is used where call measurement is agreed.

Competitor comparison pages where there is a real, supportable angle and the client approves the claims and brand use. A specialist whose edge is a benefit the national brand cannot match deserves a page that says exactly that to people searching for the national brand.

With consent, Clarity recordings and heatmaps can suggest where a page or form needs investigation. Repeated abandonment at a field becomes a test hypothesis; it does not prove the field is the cause.

We can also write the brief for your developer if you would rather keep it in-house, and then check what comes back.

The fixed-scope sprint

The proposal fixes the page count and states whether discovery, copy, design, build, form workflow, call route, consent controls, analytics and QA are included. It also states the number of revision rounds, the client inputs needed and the acceptance tests the page has to pass.

The page is tested on the agreed mobile and desktop routes. The form, CRM write, eligible identifier capture and conversion handoff are tested separately because a successful form message does not prove that every later system received the right record.

After launch, the first agreed iteration uses observed behaviour and commercial outcomes. A page with too little traffic or too few qualified outcomes cannot support a reliable winner, so the test plan defines the evidence threshold rather than promising a result after a fixed number of days.

What you get

The agreed page or pages on an agreed static host, with the actual hosting and service costs documented. The source files and deployment route. The form workflow and QA record. A short test plan: what changes first, what is watched, and when the evidence is sufficient to make a decision.

Where practical, the host, domain and connected services sit in client-owned accounts. If the project ends, the handover identifies the source, deployment, forms, tracking and recurring services needed to keep the page running.

What is not included

The sprint is not an SEO site rebuild, a new brand identity, a photography project, open-ended CRM reconstruction or ongoing ad management. Any of those can affect the page, but they are either supplied by the client or scoped separately.

Sources checked

• Google Search Central: block indexing with noindex
• Google Ads: landing page experience
• Microsoft Clarity: data and privacy

Related: Landing pages for ads are not your website · Tracking

Scope a landing-page sprint