evams®Discuss your project ↗

Launch preparation

How to prepare a website for advertising: a checklist

Preparing a website for advertising means checking the entire journey from the ad to a received enquiry. Even a well-configured campaign loses its purpose if the mobile form does not work, the offer is unclear, or enquiries reach an inbox that nobody checks.

This checklist suits a service website, landing page or small online shop. Work through it before increasing the budget. Record a specific outcome at every stage: which page was checked, which action was completed and who is responsible for the fix. “It seems to work” is no substitute for a test enquiry.

Connect the ad to a specific offer

Visitors should recognise on the page what made them click the ad. If the ad offers a property valuation, the first screen should explain that valuation: which details are needed, what the owner will receive and what happens next. The company's general story can sit further down. It should not obscure the answer to the original request.

For each ad group, record the promise, landing-page address and target action. Check that the region, language, product, terms and restrictions match. An ad for a service in Tartu should not lead, without explanation, to a page that mentions only Tallinn. An Estonian-language ad should preferably lead to a complete Estonian version, including the form and submission confirmation.

What should be clear without a phone call

Explain who the service is for, what the work includes, how the price is calculated and what happens after an enquiry. If pricing depends on initial information, list that information. Instead of a vague “individual approach”, show the stages: receiving information, clarifying the task, making an offer and agreeing on it. This helps the visitor assess the next step.

Test the mobile page yourself

Open the website on a phone and use it as a new visitor would. Check text readability, button contrast, field sizes and the menu. A cookie banner, chat widget and sticky button should not cover the form at the same time. Important terms must remain accessible when the text is enlarged.

Tap the phone number and email address, open the language selector and go back from the form. Try filling in fields with the mobile keyboard: does it hide the button, is an international number easy to enter, and are previous entries retained after an error? For a shop, also test selecting a product variant, changing the quantity and proceeding to payment.

Check the browser inside social networks separately: a significant share of visits may open there. If you use an external booking or payment service, test the transition to it and the return to your website. A working home screen says nothing yet about completing an order.

Assess speed and interface stability

Start with actual obstacles: an oversized hero image, a slow-loading form, shifting blocks and delayed button responses. Compress images without losing necessary detail, specify their dimensions and remove unnecessary third-party scripts. Do not autoplay video purely for decoration.

The Web Vitals documentation gives good benchmarks of LCP up to 2.5 seconds, INP up to 200 milliseconds and CLS up to 0.1; field-data assessment uses the 75th percentile. These measure loading, responsiveness and visual stability. They help diagnosis but do not replace checking the content and form.

A laboratory test and real visitors' experience can differ. Run checks on key landing pages, not just the homepage. A new website may not yet have enough field data: use laboratory diagnostics and manual testing initially, then return to the measurements after launch.

Run an end-to-end enquiry test

Submit an enquiry with a unique label, such as “launch test, time and language”. Check not only the success message but also the record in the system, the assigned employee, the notification and the saved source. Then confirm that the manager can reply to the customer and find the enquiry again.

  • Valid data creates one enquiry with the required fields.
  • Empty required fields produce a clear message.
  • A server error is not presented as a successful submission.
  • Repeated clicks do not create several identical deals.
  • If the integration fails, the enquiry is retained for retransmission.
  • The visitor receives a clear confirmation and an expected next step.

For an online shop, add successful and failed payment tests. The order, payment and purchase event are different records: they should consistently reflect the outcome. Make sure refreshing the confirmation page does not create a second purchase in reports. Label test orders and exclude them from commercial analysis.

Set up measurement of meaningful actions

Before launch, define the main event: a received enquiry, confirmed booking or paid order. Button clicks and form openings can be tracked separately as intermediate actions. If every action is called a conversion without clarification, the report will show activity but will not explain the result.

Check events in debug mode, purchase amount and currency, and the absence of duplicates. Save a test link with UTM parameters and verify that permitted data reaches the CRM. Do not put a phone number, email address or name in the page URL or campaign parameters. Source-naming rules are discussed in detail in the article on analytics from click to sale.

What to check when cookies are rejected

The form must also work for visitors who reject optional cookies. Advertising and analytics technologies must respect their choice. According to guidance from Estonia's AKI, placing additional identifying analytics and advertising cookies requires prior, freely given consent. A statement in a banner is not enough: check which technologies actually load.

Separate processing an enquiry from subscribing to marketing emails. Wording, grounds for processing and retention periods must match the actual process. Platform settings or Consent Mode alone do not replace this review.

Prepare the team for the first enquiries

Assign a primary and backup owner. Agree on working hours, how complex requests are handed over and a first-response time the team can actually meet. Do not promise an immediate call if nobody is on duty in the evening.

Prepare a short first-contact script: confirm the request, clarify essential information and agree on the next action. The CRM needs clear statuses and rejection reasons. Do not mix unsuitable enquiries, duplicates, spam and potential buyers who are still deciding. Otherwise, it will be difficult to tell whether the problem lies in advertising or handling enquiries.

Use criteria to decide whether to launch

CheckReadiness conditionWho confirms
OfferMatches the ad and is available in the required languageMarketer and service owner
Form or orderSuccessful and error scenarios have been testedDeveloper
MeasurementThe meaningful event is recorded without duplicationAnalytics specialist
HandlingAn owner and next step are definedSales manager
MonitoringA spending limit and reasons to pause are setBudget owner

A broken form, lost orders and inaccurate pricing are reasons to postpone sending traffic to the affected page. Secondary improvements can go into a plan. Use the initial launch to test the chain with real enquiries, and link budget increases to verified data quality and enquiry handling.

Frequently asked questions before launching advertising

Can we start without a perfect website?

Yes, if the offer and terms are clear, the target action works and enquiries are handled. There is no need to wait for a large blog or complex animation. But advertising cannot compensate for a broken form or an unavailable product.

Do we need a separate page for every ad?

No. Separate pages where the offer and visitor intent differ substantially. Several ads for the same service can lead to one suitable page. Different services and audiences sometimes need separate journeys.

How often should the checks be repeated?

After changes to the form, payment system, CRM, consent banner or page template. Also test the customer journey if enquiries drop unusually. A saved test checklist helps quickly distinguish a technical fault from a change in advertising demand.