Landing page, destination page, lander, squeeze page: which term to use

The question comes up on almost every project: is it a landing page, a destination page, a lander, or a squeeze page? It sounds like a debate for vocabulary enthusiasts. In practice it has three very concrete consequences. First on scoping: the terminology wobble usually hides a deeper misunderstanding about what a landing page actually is — and what it isn't. Second on reading ad platforms, which don't all use the same word for the same thing. Third on SEO: people don't type the same phrase into Google, and a page that recognizes only one label cuts itself off from part of its audience.

Where the terms come from

Landing page is the original expression from online marketing: the page a visitor "lands" on after clicking an external link — an ad, an email, a search result. It's the default professional term almost everywhere. Destination page describes the same object from the advertiser's side: not where the visitor lands but where the click is sent, and it's the phrasing you meet inside ad interfaces and their reporting columns. Lander is shorthand among media buyers and affiliates, usually implying a page built fast for one campaign. Squeeze page is narrower: its only purpose is capturing an email address. Splash page is different again — an interstitial shown before the real content, often an age gate or a language choice, and not a conversion page at all. Micro-site is the odd one out: several pages on their own domain for one campaign, which is no longer a single landing page.

What ad platforms actually call it

This is where vocabulary stops being a matter of taste. On the Google Ads side, the reporting has long used destination for the URL an ad points to, alongside columns tied to the experience on that page. On the Meta side, the wording differs: the platform separates a click on the link from the fact that the page actually loaded and was viewed, through a metric built around the idea of landing page views. Exact labels shift with interface redesigns, so there's no point quoting them word for word in a document that will live for months — check the label currently shown in your own account, in your account's language, at the time you write. What matters is the underlying concept; see our guides on the landing page for Google Ads and on landing page views in Meta Ads.

• In a client report, quote the platform's label, not your own translation. If the dashboard says one thing and the report another, the reader has to map the two himself — and will ask about it.
• Never swap one metric's name for another. A link click and a landing page view don't measure the same thing; calling both "visits" hides the gap you should be analyzing.
• Name the source of every number. The same page can show three traffic figures depending on whether you read the ad platform, the analytics tool or the server logs. Naming the tool ends a vocabulary argument that is really about counting method.
• Lock the wording into your naming convention. Campaign names alternating between "LP", "lander" and "dest" make filtering painful six months later.

The real misunderstanding: what a landing page is not

When a client hesitates between these words, the underlying question is rarely linguistic: they don't yet know what kind of page they're ordering. A landing page — whatever you call it — is defined by a constraint: one action expected from the visitor, and a page built entirely to make that action obvious. That criterion rules out several things it gets confused with.

• The homepage. It serves a mixed audience and deliberately offers several paths: the offer, pricing, contact, company. That's the opposite of a landing page's logic.
• The brochure site. A set of pages presenting a business over time, with full navigation. Worth settling before you quote: see landing page versus brochure site.
• An e-commerce product page. It lives inside a catalog, with breadcrumbs, search and related products. It can receive paid traffic without being dedicated to one campaign.
• A contact page. A form doesn't make it a landing page: it lacks the promise, the proof and the argument that get a visitor to fill it in — see the anatomy of a landing page that converts.
• A page inside a funnel. A long-form sales page, a thank-you page or an upsell page belong to a longer sequence; the landing page is its first step, not the whole thing.

Why betting on a single word is an SEO mistake

The vocabulary problem has been documented in human-computer interaction for decades. A study by Furnas, Landauer, Gomez and Dumais published in 1987 in Communications of the ACM shows that when people are asked to spontaneously name the same object or the same action, the variability of the words they pick is very large: in every domain tested, two people chose the same term with a probability below 0.20 (Furnas, Landauer, Gomez & Dumais, 1987, Communications of the ACM). The authors conclude that a system recognizing only one "preferred" word fails in a large share of cases, and recommend accepting a wide range of synonyms — what they call unlimited aliasing. The parallel with search is direct: a page that uses a single label mechanically cuts itself off from the phrasings most people actually type.

Turning that into a page that ranks

In practice, the search intents behind these terms don't fully overlap. Someone typing "squeeze page template" is at a different stage from someone typing "SaaS landing page examples" — the first wants a specific mechanism, the second already knows the format and wants inspiration. A well-built page therefore commits to one primary term in the title and the opening paragraph, then introduces the variants in the body, in secondary subheadings and in the FAQ, without stacking synonyms inside one sentence. The fundamentals are those of any page you want to rank, laid out in our guide on getting a landing page to rank on Google.

• One primary term per page, not three. Pick the one matching the intent you target and hold it in the title, the URL and the first paragraph.
• Variants in the body, not in the title. One defining sentence up front ("a landing page — sometimes called a destination page — is…") covers the near-synonyms without hurting readability.
• Watch your internal anchor text. Varying anchors across the different terms sends a richer signal than repeating one phrase site-wide.
• Don't map terms one-to-one across languages. The equivalents don't carry the same weight from market to market: our article on the multilingual landing page explains why translating a key term word for word loses the ranking you were after.
• Keep ad and page wording aligned. The word used in the ad should reappear in the page headline; otherwise the visitor spends a second checking they're in the right place.

Choosing your words per document

There's no universally correct term, only one that fits the reader. In a brief, use the word the delivery team uses: if designers and developers say "LP", a spec written in "destination pages" buys you a round of clarification emails. In a proposal, use the client's word and add one line defining the deliverable — that prevents the classic misunderstanding where the client thought they were buying a full site; see how much a landing page costs. On a page meant to rank, let the queries decide. And for internal communication, settle it once: a three-line glossary at the top of the shared doc does more for a team than any debate about jargon. When doubt persists about the deliverable itself, showing beats defining — which is why walking through landing page examples before signing is time well spent.

The word matters less than the object it points to: one page, one action, one message aligned with the traffic source. Once the vocabulary is settled with the client, the conversation goes back to structure and execution. The 10 LanderKit templates (€89 each, €229 for the full pack) cover the most common cases — course, coaching, digital product, SaaS waitlist, e-commerce, local agency, webinar, newsletter, restaurant, real estate — and give you something concrete to put on the table when the terminology discussion drags on.