- The two surfaces are the safe (review) page and the real (offer) page; the routing engine decides which one each visitor lands on.
- The safe page should be a genuine, self-consistent page on its own topic — not an empty shell — so it reads as a real site to automated checks.
- The real page is your actual offer; keep its structure standard so it does not itself look engineered.
- Most setups are spotted through structural tells — mismatched domains, thin safe pages, obvious redirects — not through the routing logic itself.
What the two surfaces are
Every traffic-routing setup has two destinations behind one public link. The first is the safe surface — often called the review page — a compliant page that any automated check or crawler is meant to see. The second is the real surface: the actual landing page you want genuine users to reach. The routing engine sits in front and, in a few milliseconds, decides which surface a given click resolves to based on rules you configure. For the mechanics of that decision, see how the architecture works.
The key idea is that the two surfaces are independent pages, not two states of one page. That independence is what lets each be optimized for its audience — but it also creates the failure modes covered below, because the two pages have to feel like they belong to the same, legitimate site.
What the safe page should actually contain
The most common structural mistake is treating the safe page as a throwaway. An empty template, a single line of text, or a page that clearly has nothing to do with the campaign reads as engineered. A safe page should be a genuine, self-consistent page on a plausible topic, with real navigation, real copy and a coherent purpose. It should be able to stand on its own if someone lands on it directly. Building the safe page so it can accrue its own history also helps its standing over time — see building a credible safe page.
A practical test: would this page look reasonable as the homepage of a small, real business in that niche? If yes, it is doing its job. If it only makes sense as "the page the checks see," it is a tell.
Structuring the real page
The real page is your actual offer, so most of the effort goes into conversion — but structure still matters for the routing setup as a whole. Keep the real page's markup standard: normal HTML, normal assets, no unusual client-side tricks that would make it stand out from an ordinary landing page. If you run more than one real page for testing, route between them by weight rather than by stacking redirects. Practical routing details, including how strict to make the rules, are covered in tuning pass rate.
Structural mistakes that make a setup easy to spot
Most setups are not caught by the routing logic itself — they are caught by structural tells. The frequent ones: a safe page hosted on an obviously different domain from the link; a thin or boilerplate safe page; a 302/redirect chain where a same-URL render would be more natural; and mismatched signals between the two surfaces (different languages, mismatched branding, inconsistent metadata). For the broader list of what gets setups flagged, read the red-line checklist and how platforms detect these setups.
A useful discipline is to check your own setup the way an outside tool would — request both surfaces under different conditions and compare. See how to check a page for the approach.
Keeping the two surfaces coherent
The overarching goal is coherence: both surfaces should feel like parts of the same legitimate site. Same domain where possible, consistent design language, plausible internal links, and metadata that does not contradict itself. On mobile the two surfaces can behave differently because of WebView and referrer quirks — that is a topic on its own, covered in mobile traffic routing. And if your real page is really just an audience-tailored version of the same content, you may not need a two-surface split at all — see where the line with compliant personalization is.