What is a splash page
A splash page is a full-screen gate that appears before visitors reach your main content and asks them to complete a single action or confirm a single thing before proceeding. It is intentionally interruptive: it stops the visitor's navigation and requires an explicit response.
That description covers a wide range of page types, from a legal age-verification gate on an alcohol retailer to a coming-soon waitlist form for a product not yet launched. What they share is the structure: minimal copy (three to five sentences is typical), one action, and a path forward. The visitor either completes the action or, on marketing splash pages, exits through a clearly visible skip option.
The distinction from other page types matters because the terms are often used interchangeably when they describe different things:
| Page type | Purpose | Copy length | Visitor choice |
|---|---|---|---|
| Splash page | Gate before content: age confirm, language select, email capture, cookie consent | 3-5 sentences | Complete or exit |
| Landing page | Campaign destination: persuade a specific audience to take a conversion action | Long-form, multiple sections | Convert or leave |
| Squeeze page | Email capture: a dedicated URL with a single lead-capture form | Medium, single focus | Submit or leave |
| Homepage | Navigation hub: route different audiences to the right destination | Variable, multiple paths | Multiple routes |
A splash page is an overlay or redirect that precedes the visitor's intended destination. A landing page IS the destination. A visitor who arrives on a landing page chose to go there. A visitor who sees a splash page did not choose to stop. That difference in consent is what determines when a splash page is appropriate and when it is friction that does not pay for itself.
Six legitimate use cases
The deciding question for any splash page is: does this serve the visitor, or does it serve only the site? Use cases that serve the visitor (correct language, required legal gate, real scarcity) justify the friction. Use cases that serve only the site (generic promotion, audience-building for its own sake) rarely do.
Age verification
Required by law for cannabis direct-to-consumer sales in most US states and Canadian provinces. Recommended (not mandated) by industry bodies for alcohol. The gate must state the age requirement clearly, offer an unambiguous underage exit, and implement cookie persistence.
Coming-soon and waitlist
A product or course not yet launched, with genuine scarcity or a real launch date. Captures email addresses from interested visitors in exchange for early access or first notification. Converts at 10 to 30 percent on well-designed pages with a specific benefit and a real deadline.
Language or region selector
Used by sites that serve multiple countries with different pricing, regulatory requirements, or localized content. The splash routes visitors to the correct version. Research from CSA Research found that 76 percent of consumers prefer to buy in their native language (MODERATE, CSA Research). This type is explicitly exempt from Google's mobile interstitials penalty.
Cookie consent
Required under GDPR for most sites serving EU visitors, and increasingly standard globally. Google explicitly exempts cookie-consent overlays from its intrusive interstitials penalty. The consent mechanism must be genuine: the user must be able to decline non-essential cookies without difficulty.
Limited-time promotional gate
A flash sale, a genuine one-time offer, or a real enrollment window. Effective when the deadline is real and the offer is relevant to the visitor. Ineffective when overused, shown to returning visitors repeatedly, or paired with a fake countdown. The key word is genuine: the friction is only worth the conversion if the urgency is real.
Lead capture before content access
Gating a specific piece of content (a free tool, a calculator, a premium article) behind an email capture form. The value exchange must be clear: the visitor should know exactly what they are getting and why an email address is the price. Ask for email only. Each additional field reduces completion.
The cases that consistently damage more than they earn: a generic "sign up for our newsletter" gate shown to all visitors with no specific offer; a promotional splash that runs indefinitely and shows to every return visit; and any splash page where the value exchange is unclear or one-sided. If the visitor cannot answer "what do I get from doing this?" in under five seconds of reading, the splash page is not earning its friction.
What splash pages do to SEO
A splash page does not trigger a direct algorithmic penalty from Google. It does, however, cause indirect ranking damage through three specific mechanisms that are worth understanding before adding one to any page that ranks.
The mobile interstitials penalty
In January 2017, Google began applying a ranking penalty to mobile pages that show full-screen interstitials immediately upon arrival if those interstitials make content difficult to access. The penalty applies to pop-ups that cover the main content, standalone interstitials that require dismissal before accessing content, and layouts where the above-the-fold portion looks like an interstitial even if the content is accessible by scrolling. Exemptions include: age-gate splash pages where the law requires the gate, cookie-consent overlays, and interstitials that use a reasonable amount of screen space. The practical implication: a marketing splash page with no clear exit button, shown immediately to mobile visitors, is penalized. A splash page with a visible exit and a genuine purpose is not.
Doorway pages vs. legitimate splash pages
Google's doorway page policy penalizes pages designed to rank for specific keywords while delivering different content to users, or pages that funnel visitors from multiple search queries into the same destination. The BMW Germany case in 2006, where BMW was deindexed for keyword-stuffed entry pages that redirected users, is the canonical example. A legitimate splash page is not a doorway page: it serves a genuine user need, shows the same content to crawlers and visitors, and does not exist to manipulate search rankings. The distinction Google draws is intent: does the page serve the visitor, or does it serve the site's ranking?
Pages that are created to get search engine traffic but then funnel visitors into the same destination are doorway pages. They're bad for users because they can lead to multiple similar pages in user search results, where each result ends up taking the user to essentially the same destination.
Google Search Central, Doorway pages documentationCrawlability and Core Web Vitals
If a splash page is implemented as a JavaScript redirect rather than an overlay, and the underlying content is not otherwise accessible to crawlers, search engines see only the splash and treat the page as thin or empty. Implement splash pages as CSS or JavaScript overlays on top of the actual page content, not as redirects that prevent crawlers from reaching the content. Additionally, splash pages with large video backgrounds, uncompressed images, or heavy animation libraries degrade Core Web Vitals scores (LCP, INP, CLS), which are confirmed ranking signals. A slow splash page harms the ranking of the page it precedes.
Anatomy of a splash page
Every element on a splash page exists to serve one action. The moment a second action competes for attention, the page becomes a landing page that does not have enough copy to do the job.
A well-structured splash page has five required elements and two optional ones. The required elements are the same regardless of use case:
The visual design follows one rule: every element should be visible without scrolling on a 375-pixel-wide mobile screen, which corresponds to the smallest common device (iPhone SE). If the call to action is below the fold on that screen size, the layout is broken. Over 80 percent of web traffic is mobile-first, and a splash page that requires scrolling before showing the action it asks for will lose most of the visitors it was designed to capture.
For the visual background, a high-quality static image outperforms a video background for load performance, and load performance is one of the largest determinants of conversion on a page this short. Research widely cited by Portent and Unbounce shows that pages loading in one second convert approximately three times higher than pages loading in five seconds, and a one-second delay is associated with roughly a 7 percent reduction in conversion rates. If a video background is necessary to the page's purpose, use a compressed loop of under 5 megabytes and replace it with a static image on mobile connections.
How to build a splash page: 7 steps
Define the single purpose of your splash page before designing anything
Write one sentence that completes this: "This page exists so that visitors can ___." Age verification, language selection, waitlist email capture, cookie consent, and promotional announcement are all valid single purposes. If the sentence has more than one answer, split the purposes or eliminate the splash entirely. A splash page with two competing purposes converts poorly at both and adds double the friction for every visitor who arrives at your site for neither reason.
Write a headline that states the benefit or requirement in ten words or fewer
The headline does the entire persuasion job of the page. For a legal gate: "You must be 21 or older to enter" states the requirement without ambiguity. For a waitlist page: "Get early access before we open to the public" gives the visitor a specific reason to act. For a language selector: "Choose your region for the right pricing and availability" removes friction. Every other word on the page is support for that single sentence. If the headline does not answer "why should I do this?" immediately, it needs to be rewritten before anything else is designed.
Build mobile-first with one visible call to action
Start the layout at 375 pixels wide. Stack all elements in a single vertical column: headline, supporting line, form field or confirmation button, call to action. The call to action button must be visible without scrolling on a mobile screen. Use a high-contrast color for the button that is visually distinct from the background. Button text should use an action verb: "Join the waitlist," "Confirm my age," "Choose my region." Avoid "Submit" or "Continue." Test on an actual device, not only a browser resize, before publishing.
Add a clear exit option that is easy to see and tap
Every marketing splash page needs a visible exit. Place an X button in the top-right corner or a "Skip for now" link below the call to action. The exit must be at least 44 by 44 pixels for mobile tap targets and visible without scrolling. Hiding the exit, making it tiny, or placing it in low-contrast text all trigger Google's mobile interstitials penalty and significantly increase the percentage of visitors who simply leave the site rather than proceeding. The exception is a legal age gate: there, the "under 21" option is not an exit but a redirect to a neutral page, and the gate does not require a general exit option.
Set up frequency capping so returning visitors bypass the splash
Use a cookie to remember visitors who have already seen the splash and route them directly to the main content on all subsequent visits. Marketing splash pages should show at most once per session. A promotional splash shown to every returning visitor on every page load is one of the most reliable ways to drive away the visitors most likely to convert (they have already decided to come back). Legal compliance pages (strict age gates, GDPR consent where re-confirmation is required) may need to show on every visit, but even these should suppress immediately after the visitor has confirmed.
Test load speed and Core Web Vitals before publishing
Keep the total page size under 100 kilobytes. Compress images to under 50 kilobytes each. On mobile, replace video backgrounds with static images or CSS animations. Run the page through Google PageSpeed Insights before publishing and target an LCP under 2.5 seconds and a CLS under 0.1. A one-second delay in load time is associated with approximately a 7 percent reduction in conversion rate (figure widely cited by Portent and Unbounce). For a page as minimal as a splash page, that level of performance is achievable: there is no reason a three-sentence gate page with one button should be slow.
Measure drop-off rate and decide whether the splash earns its friction cost
After publishing, track two numbers: the percentage of visitors who complete the splash action, and the percentage who leave the site entirely without proceeding. If the second number is high relative to what the first number is worth, the splash page is costing more in lost traffic than it gains in captures or compliance. Set a minimum performance threshold before launch: for a waitlist page, that might be 15 percent completion. For an age gate, abandonment data is secondary to legal compliance. For a promotional splash with no legal obligation, the math should be explicit: is what you are gaining worth the percentage of visitors you are losing? If not, remove it.
Common splash page mistakes
Too much content. A splash page that explains the benefits in six paragraphs, lists testimonials, and has three calls to action is a landing page without enough copy to work as one. The rule is one sentence of context and one action. Everything beyond that is content that belongs on the page the visitor was trying to reach, not on the gate in front of it.
Hiding the exit button. A tiny, low-contrast, or below-the-fold exit on a marketing splash page triggers Google's mobile interstitials penalty and causes high abandonment among visitors who have no interest in the splash's offer. An easy exit is not a conversion enemy: a visitor who wants to exit will exit regardless. Making the exit hard only ensures they leave the site entirely instead of proceeding to the page they wanted.
Showing the splash to returning visitors on every visit. The most likely visitors to convert on any marketing goal are people who have already been to the site. Showing a promotional splash to every return visit tells those visitors that the site prioritizes its own marketing goals over their navigation. Frequency capping is not optional for marketing splash pages: it is the difference between a campaign tactic and a persistent annoyance.
Using a fake countdown timer. A countdown that resets on every page load or that counts down to nothing is a deceptive pattern. In markets with strong consumer protection laws (EU, UK, Australia), resetting countdown timers are increasingly flagged as misleading commercial practices. More practically: a visitor who returns after the countdown expires and finds the same timer running from the beginning has learned that the site uses fake urgency. That discovery does more damage to trust than the original conversion was worth.
Blocking search crawlers. If the splash page is implemented as a full-page redirect rather than an overlay on top of the actual content, search engines see only the splash and rank the page accordingly (thin content). Implement splash pages as overlays using CSS or JavaScript so that the underlying content is accessible to crawlers. If a redirect is unavoidable, use a temporary (302) redirect, not a permanent (301), and ensure Googlebot can still reach the content.
Not measuring abandonment. Most teams measure only the splash's completion rate. The more important number is total abandonment: the percentage of visitors who leave the site entirely rather than proceeding, attributable to the splash. A splash page with a 20 percent email capture rate looks successful until the data shows that it doubled the site's bounce rate. Both numbers are needed to decide whether the splash is net positive.
Build landing pages and coming-soon gates in systeme.io
systeme.io's page builder lets you build coming-soon pages, lead capture pages, and waitlist gates. Connect email capture directly to automation sequences so every person who joins your waitlist receives a confirmation and a nurture sequence from day one.
Frequently asked questions
Splash pages do not trigger a direct algorithmic penalty from Google, but they cause indirect ranking damage through three mechanisms. A full-screen splash on mobile without an easy exit triggers Google's intrusive interstitials ranking penalty (active since January 2017). Slow-loading splash pages with large video backgrounds harm Core Web Vitals scores, which are confirmed ranking signals. Splash pages implemented as full-page redirects (rather than overlays) prevent crawlers from reaching the underlying content. Age-gate and cookie-consent overlays are explicitly exempt from the interstitials penalty.
A splash page is a gate that appears before a visitor reaches the main content and requires or offers a single action before allowing access. It is typically three to five sentences of copy with one call to action and one exit option. A landing page is a destination: it exists at a specific URL, has a defined audience from a campaign, and uses long-form copy with multiple sections to persuade visitors to convert. Landing pages are designed to convince; splash pages are designed to gate or capture. A visitor who arrives on a landing page chose to go there. A visitor who sees a splash page did not choose to stop.
Both. A well-designed waitlist splash page for a product with genuine scarcity can convert at 15 to 30 percent according to waitlist platform data. A promotional splash page with no real urgency, shown to returning visitors on every session, typically increases overall site abandonment by adding friction that delivers no value. The question is whether the splash earns its friction cost: does the action it captures or the gate it enforces justify the percentage of visitors who leave without proceeding? Measure both the completion rate and the abandonment rate, and remove the page if the abandonment cost outweighs the capture value.
In the United States, age gates for alcohol websites are recommended by industry bodies but are not federally mandated. Age verification is legally required for cannabis direct-to-consumer sales in most US states and Canadian provinces. Best practice for a legally defensible age gate: state the requirement explicitly, use unambiguous button language ("Yes, I am 21 or older" and "No, I am under 21"), redirect underage visitors to a neutral page rather than a dead-end error, and implement cookie-based persistence. A checkbox alone is considered weaker than a date-of-birth entry, particularly for cannabis compliance.
For an email capture splash page, ask for email only. For a waitlist page, a first name field in addition to email is acceptable if personalization is genuinely planned. Every additional field reduces completion rate. Data from multiple landing page studies consistently shows that shorter forms outperform longer ones, and that removing a single field from a four-field form consistently improves completion. The rule: ask only for information you will use within the next thirty days. If you have no specific plan for a phone number or company name in that window, do not include the field.
In documented cases, yes. One case study cited by Adoric showed a countdown timer on a waitlist page boosting email capture from 3.1 percent to 6.4 percent. This is a single test, not a benchmark, and should be treated as directional evidence. Countdown timers are effective when the deadline is real: a genuinely limited early-bird window, a product with a specific launch date, or a real inventory limit. A countdown that resets on every page load is a deceptive pattern that undermines trust. In markets with strong consumer protection laws, resetting timers face increasing regulatory scrutiny.
Target a load time under one second and an LCP under 2.5 seconds. Research widely cited by Portent shows that pages loading in one second convert approximately three times higher than pages loading in five seconds, and a one-second delay is associated with roughly a 7 percent reduction in conversion rates. For a page as minimal as a splash page, this level of performance is achievable: keep the total page size under 100 kilobytes, compress images to under 50 kilobytes, and replace video backgrounds with static images on mobile. A slow splash page both reduces the action it is asking visitors to take and harms the Core Web Vitals score of the site it precedes.
A doorway page is a black-hat SEO technique: a page designed to rank for a keyword and then redirect visitors to a different destination. Doorway pages are keyword-stuffed, provide no genuine value to users, and are designed to manipulate search rankings. Google penalizes them severely, up to and including deindexing. A legitimate splash page serves a genuine purpose: legal age verification, language routing, GDPR consent, or a specific marketing gate. The distinction Google draws is intent: does the page serve the visitor, or does it serve the site's ranking? A splash page serving a real user need is legitimate. A splash page designed primarily to show keywords to search crawlers while presenting different content to users is cloaking, a form of doorway abuse.