Short answer

Before launching a campaign, improve the match between the page and the specific ad, the mobile contact journey and the measurement of genuine enquiries. If the offer is appropriate, fixing the existing page is usually a sensible starting point. A separate landing page makes sense for a distinct proposition; a rebuild makes sense when limitations affect the entire site. This is guidance for choosing a scope of work, not a guarantee of advertising results.

Start with one promise and one URL

Write down exactly what the ad promises: which service, to whom, in which area and with what next step. Then open the destination URL on a phone without using the menu. Does the first screen confirm the same offer? Is it clear where the business operates and what the button does? If visitors must find the advertised service themselves, you are paying to send them to the start of another search.

This does not mean creating a separate page for every keyword. One page can serve several closely related queries. Separation is justified when the audience, service scope or expected action changes. For example, hypothetical offers for emergency repairs and planned inspections may require different information and ways to get in touch. This illustrates a decision, not a client implementation.

Google Ads and Meta Ads: the same test, a different starting point

For a search campaign, begin with the query and ad copy. Google describes landing page experience in terms of relevance and usefulness to someone clicking an ad. Quality Score is a diagnostic tool, not a business objective or a direct input into the auction. Do not commission a redesign on a promise of a particular Quality Score or cheaper clicks.

On Meta, also check continuity between the image or video and the page. Someone attracted by a specific proposition should not land in a general catalogue without an explanation. Meta’s help documentation distinguishes a click from a successfully loaded landing page. Clicks alone confirm neither that someone viewed the offer nor that they made an enquiry. For catalogue ads, also verify the product URL rather than assuming every ad element leads to the website address you entered.

Choose the scope before requesting a quote

The matrix below is purchasing guidance. It does not replace a technical review, but helps distinguish a small repair from a project that genuinely needs its own budget. Record evidence for each problem: the URL, device, screenshot and expected behaviour.

Situation before the campaignReasonable scope of workAcceptance criterion
The offer fits, but getting in touch is difficultImprove the existing page and formThe complete journey works on a phone
The new campaign has a distinct offerA landing page with its own content and measurementThe ad and page promise the same thing
The whole site has mobile or technical barriersDiagnosis and a phased redesignUnderlying causes are removed, not just the old appearance
Enquiries arrive, but reports are inconsistentAudit measurement and integrationsThe test enquiry is recorded without duplication

What the improvement brief should include

1. Content needed to make a decision

The first screen should identify the service and the next step. Follow it with the scope, terms of cooperation, service area and answers to genuine questions before purchase. Remove contradictions between the ad and the offer. If you do not publish a price, explain what affects the quote and what information is needed to prepare it. A claim of a personalised approach is not a substitute.

Evidence must be genuine: your own projects with permission to publish them, a description of your process or specific information about the business. Do not add invented reviews, customer counters or results. When materials are missing, the brief should cover collecting them, not just providing space for attractive cards.

2. A contact journey people can complete

Test the form with the on-screen keyboard, an invalid email address and an empty required field. Users should understand what to correct and whether their message has been accepted. Field labels should remain readable after text is entered; W3C recommends associating labels with form controls. Also check the phone number, email address, messages and actual delivery of the enquiry to the person handling sales.

Limit required fields to information needed at this stage. A detailed specification of the whole project may suit an extensive brief, but not necessarily a simple availability enquiry. Test the form in an agreed manner and mark the submission as a test so it does not create false sales data.

3. Performance in real conditions

Do not accept a site solely because of a report’s colour. Check how it opens on a phone, responds to a button press and shifts during loading. Web Vitals separates these aspects into LCP, INP and CLS. A laboratory result helps identify a problem but is not the same as real users’ experiences. Field data may not yet be available for a low-traffic site.

The provider should identify the cause of a slowdown and the scope of repair: images, scripts, hosting or rendering. “Installing an optimisation plugin” is not an adequate acceptance criterion. Repeat the contact test after the change: speeding up the site must not break the form or hide important content.

Measurement: a button click is not an acquired lead

Define the outcome before launch. For a form, it may be a successfully accepted submission, not merely opening the form or attempting to send it. Google Analytics describes the generate_lead event for submitting a form or requesting information; implementation requires appropriate triggering and verification. A phone-link click signals intent, not proof of a conversation.

Commission checks for duplicate events, behaviour after refreshing the confirmation page and campaign-source tagging. Do not put personal data into URL parameters or analytics events. Account for applicable privacy and consent requirements; installing a tag does not automatically confirm compliance. Describe differences between dashboards alongside the definition and measurement period rather than forcing identical numbers.

The launch decision and a short acceptance checklist

I recommend withholding paid traffic from a URL that does not work, shows a different offer or prevents people from completing the contact journey. If reliable measurement is missing, address that gap first; otherwise you cannot establish what needs improvement. Minor visual imperfections need not block a limited test when the critical journey works.

  1. Open the exact URL from the ad and confirm the final offer after redirects.
  2. Check the first screen, button and form on a phone and a computer.
  3. Confirm delivery of an agreed test submission and the correct message.
  4. Verify the outcome event, traffic source and absence of repeated counting.
  5. Record the site version, responsible person and rollback method.

Provide this checklist, sample ads and a list of problems when requesting a quote. Ask for separate items for content, layout, the form, performance and measurement. This lets you compare scopes, not just prices. A working website is a prerequisite for a meaningful test, but does not guarantee profitability: the offer, audience, creative and handling of enquiries still matter.

Sources and limits of the conclusions

Documentation checked on 9 November 2026. Facts about tools come from the sources below; the scope matrix and order of work are the author’s recommendations. This article does not present the results of a specific campaign.

Need a website prepared for a campaign?

Describe your current site, offer and planned advertising objective in the brief. This is a starting point for deciding whether you need improvements, a landing page or a wider redesign.

Open the website brief (in Polish) ↗