- A new domain has no history or accumulated trust, so traffic systems treat it more cautiously than an aged one.
- Let the safe page establish itself first — give the domain a plain, genuine presence before any routing is layered on.
- Ramp gradually: start loose and low-volume, then tighten and scale only as the domain builds a track record.
- Watch the real-vs-safe ratio during warmup; a sudden swing usually means you ramped too fast.
Why new domains are treated cautiously
Traffic systems lean on history to judge a domain. An established domain has a crawl record, a pattern of normal behavior, and accumulated signals that say "this is a real site." A domain registered days ago has none of that, so the default posture toward it is caution. This is not specific to any one setup — it is how new domains are treated generally — but it means a routing configuration that looks unremarkable on an aged domain can stand out on a fresh one. Understanding what signals systems weigh helps here; see how platforms read these setups.
Let the safe page establish itself first
Before layering any routing on a new domain, give it a plain, genuine presence. Put up the safe page, let it be crawled, let the domain exist as an ordinary small site for a while. This gives the domain a baseline of normal history so that when routing is added later, the domain is no longer a complete blank. The safe page you build here is the same credible, self-consistent page described in the two-surface structure guide, and building it to accrue its own standing is covered in building a credible safe page.
Ramp gradually, not aggressively
The core discipline of cold-start is patience. Start with low volume and loose rules, then tighten and scale only as the domain builds a record. Two things ramp together: traffic volume and rule strictness. Pushing high volume through a day-old domain, or applying aggressive filtering from the first hour, are the two most common ways a warmup goes wrong. How strict to set the rules at each stage is its own topic — see tuning pass rate — but during warmup, err loose and low.
Signals to watch during warmup
Warmup is a period to watch closely, not set-and-forget. The most informative single signal is the real-vs-safe ratio over time: a stable, gradually-settling ratio suggests the ramp is healthy, while a sudden swing usually means you scaled or tightened too fast. Reading these numbers correctly is a skill of its own, covered in reading the analytics. Segment the view by device and source too, because a new domain can behave differently across mobile in-app traffic — see mobile traffic routing.
Knowing when a domain is warmed
There is no fixed timer; a domain is warmed when it has a stable track record and its metrics settle into a consistent pattern under a normal load. At that point you can operate the routing at its intended strictness and volume. Rushing this stage is the single most common cold-start mistake — the domain that is ramped patiently tends to be the one that stays stable. For the boundary between what is safe practice and what draws scrutiny throughout, keep the red-line checklist in view.