Google Ads landing page requirements

An advertising budget is spent on clicks and earned back on inquiries. The landing page sits between the two, and it is usually the place where the money disappears: the ad promised one thing, the page showed another, the inquiry from the form never arrived, the event was never recorded.

The ad makes a promise, the page keeps it

Collect your main ad groups and, for each one, write down the intent, the wording, the offer and the next action. The page has to confirm the product, the terms and the audience straight away. It does not need to repeat the ad word for word, but the first screen must not change the subject.

• The headline matches what the person clicked on. Someone searching for a consultation should not land on a purchase form with no explanation.
• The same offer. If the ad names terms or a timeframe, they belong on the first screen rather than in the footer.
• No choosing the category again. Someone who searched for a specific model should not have to start the search over.
• Campaign parameters do not change the terms. They exist for analytics and routing, not to show a different price.

If different ads promise substantially different products, one general page may not be enough. Split landing pages by intent, but do not clone one for every minor phrase. Each version needs an owner, a check and a life cycle of its own.

Quality Score and what it is made of

Google scores every keyword from one to ten. The score is diagnostic. It reflects how useful your ad is to the person searching, and it is made of exactly three parts.

• Expected click-through rate. A forecast based on impression history.
• Ad relevance to the query. How closely the text matches what was searched for.
• Landing page experience. The part the page itself is responsible for.

The bid and ad assets (formerly extensions) are not part of Quality Score. They work at a different level. Position in the auction is decided by Ad Rank, which weighs the bid, the quality of the ad and the landing page, the context of the query and the expected impact of assets and other ad formats.

That is why work on the page pays off in the auction. Given two advertisers bidding the same, the one with better ad and page quality usually ranks higher.

Message match

The chain of expectations has three links: query, ad, first screen. Any break between those links registers as a bait and switch, and the tab gets closed.

Here is a chain that works. Someone searches for scaffolding rental direct from the manufacturer. The ad promises rental from the factory with delivery within a day. The first screen repeats that in the headline, carries the same timeframe in the subheading and offers a quote form. Not a single extra step between intent and action.

Sending narrow traffic to a general home page listing every service means paying for the click and handing the person a search task. The page score falls as well.

For companies with a broad range, the choice between a large site and a set of separate landing pages comes up. Both options are compared separately in our article on landing pages versus multi-page websites.

What the advertising platform actually requires

The platform’s crawlers scan destination pages regularly. These requirements are strict and are checked automatically: the page has to open, run on a valid certificate and comply with the destination policy. An unreachable page or a policy breach means the ad is rejected at review. The policy allows redirects within the same domain, so we check for a 200 on the final address rather than the first one.

Speed is not on that list, and ads are not rejected for being slow. It works through a different mechanism. Google weighs landing page quality in Ad Rank at every auction, which shapes your position and cost per click. Quality Score only reports that assessment in your account.

Speed targets worth aiming at

These are not ad review thresholds but widely used page-experience benchmarks. They are useful precisely because they mark the points where a person runs out of patience.

Someone on mobile data does not wait for heavy scripts. A page that takes four seconds to open loses some of its traffic before the offer is even seen, and each of those clicks has already been paid for.

Transparency about the company and the offer

Besides speed, the platform also assesses how transparent the page is. A page that leaves it unclear who is selling and on what terms scores lower and risks failing review.

• Who the company is. Name, registration details and a way to make contact beyond the form.
• What exactly is offered. What the service or product includes, without vague phrasing.
• Terms visible before the action. A price or how it is calculated, timeframes, what is and is not included.
• The privacy policy reachable. The landing page itself links to it, usually at the bottom.

A separate page or a section of a bigger site

The question comes up whenever there is more than one service. The answer depends not on taste but on how different the intents behind your ad groups really are.

If every group leads to the same service with different wording, one page will cope. If the intent genuinely differs, say one campaign is about an urgent emergency call-out and another about a planned project with a budget, a shared page has to serve both and ends up serving neither. Its first screen says something in the middle, and both audiences feel they have come to the wrong place.

The line falls where the offer itself changes rather than the wording: a different scope, different timelines, a different price or a different person answering the inquiry.

Forms and inquiry delivery

The form is where a paid click either becomes an inquiry or vanishes without trace.

• Minimum fields at the first step. Every extra field sheds some of the people who were already interested.
• Clear errors. The message explains exactly what needs correcting.
• Server-side storage before the email. Email is a notification, not the record. Mail can fail to arrive.
• Double submission is handled. A double tap caused by a delay should produce one inquiry and a confirmation, not two inquiries and an emptied form.
• The thank-you screen does not lie. If the inquiry was not saved, the person should see the truth rather than a false success.

Analytics wired before the first click

The measurement plan is written before launch rather than after the first spend.

• Page view. The fact of loading, not a button press.
• Form seen. How many people scrolled far enough to reach it.
• Fill started. The first keystroke in any field.
• Error. What failed validation and which field people stop at.
• Server-side receipt. A confirmed record on the server rather than a browser response.
• Delivery to the CRM. The inquiry reached the system people actually work in.
• Qualified inquiry. What a sales manager confirmed as a genuine lead.

Events carry the same names and parameters across every version of the page. They record the page, the campaign and the form, without unnecessary personal data. A structural change gets a marker so the statistics do not blend different conditions.

The goal in the ad account is set to the event that matches the business result. If optimization only sees a thank-you page opening, a refresh or a direct visit creates a false conversion and the algorithm learns from invented data.

Campaign and measurement setup is part of our Google Ads management service, and setup from scratch starts at $200.

Consent and what stays measurable

Some metrics depend on what the visitor chose about cookies. The team has to know which figures are complete server-side records and which depend on the browser and will be partial.

Working around someone’s choice by hidden means is not worth it. It breaks platform rules and sooner or later costs you the account. The internal record of an inquiry is always kept on your server, because that is your own order data. Passing the event on to the ad platforms, however, respects the consent state and the consent mode configuration. If the visitor declines, some measurement runs in a limited form and remarketing does not run at all. Putting the tag on a server does not override the visitor’s choice. For the figures that depend on consent, the margin of error has to be taken into account.

The controlled launch

The page goes live first without the main traffic. The team checks the content, the mobile version, speed, legal links, the form, delivery to the CRM, the events and the notifications. Someone records the outcome and the page version.

Then a small amount of real traffic is let through to see how the page behaves on actual networks and browsers. This is not an A/B test or a conversion optimization program. The single goal is to confirm the whole route technically before the full budget goes live.

Walk the route under different conditions

A controlled launch is not confined to one laptop on the office network.

• A phone on mobile data. A real connection on the move.
• Declining optional consent. Complete the form after refusing, because some flows break exactly there.
• Another browser with consent granted. To see the difference in what gets recorded.
• The actual final address of every ad. Together with the page title and the content of the first screen.

Go through the failure states separately. Enter a wrong contact, submit the form twice, drop the connection before confirmation. The message has to explain whether the inquiry was accepted and what to do next. A false success screen is worse than a visible error, because the team never learns about the loss.

Check the notifications that recipients get. The email should carry the source, the time, the fields needed and a link to the record, without exposing anything unnecessary to an outside channel. One record is created in the CRM with the right status.

What to watch after the start

• Spend against inquiries, not against clicks. A cheap click with nothing behind it costs more than an expensive one that converts.
• The gap between events. If hundreds see the form and a handful start filling it, the problem is the form rather than the ads.
• Page availability. During a campaign it needs checking on a schedule, not when inquiries dry up.
• Releases under control. Even a small plugin or CRM change can stop delivery. After every deployment, send a test inquiry.

Technical oversight of the page during an active campaign is part of project support and development: a page can stay perfectly visible at the moment inquiries stop arriving.

The checklist before opening the budget

• Every ad points at its own first screen. Verified by clicking rather than by reading a list of URLs.
• Speed is fine on a phone. Measured on mobile data, not on office Wi-Fi.
• The form saves server-side. Verified with a test inquiry located by its reference.
• Events are named consistently. They carry the campaign and the page.
• The goal is set to a result. Not to a thank-you page opening.
• Failure paths have been walked. Error, repeat submission, dropped connection.
• There is a way to stop the ads quickly. And a named person who will do it.

Conclusions

What Google scores is whether the person got what they came for. Every requirement follows from that: matching the ad, speed, clear terms and a form that works.

The most expensive mistake is opening the budget before walking the route. The page loads, the form submits, the inquiry never arrives, and three days of clicks are paid for nothing.

If you are about to run ads to a page you already have, give us the URL together with your ad groups. We will walk each route, measure speed on mobile data and check whether a test inquiry reaches the end. Often the page only needs correcting rather than rebuilding, and then you get a list of fixes. If a new one is needed, we build it to the platform’s requirements from the start, as part of our landing page development service.