How to Add a Domain in Cloudflare Easily 2026

Logging into Cloudflare drops you on Account home, a dashboard that already gives a useful overview if you manage more than one property: a Domains card listing each site with its recent traffic, a Workers and Pages card for any deployed projects, Zero Trust security shortcuts, and an Audit logs feed showing recent account activity. A Next steps panel on this same screen nudges you toward things like enabling single sign-on or inviting teammates — worth a glance, but not required before adding a new domain.

From Domains in the left sidebar, starting the onboarding flow opens a screen titled "Connect your domain" with the subhead "Make your site faster, more secure, and more reliable." It's a single required field — Domain name, with a placeholder example like example.com — plus a Continue button and a collapsed link reading "Configure DNS records import and AI crawler preferences" for anyone who wants to adjust the defaults before proceeding.

Typing a domain name and expanding that preferences link reveals two decisions Cloudflare wants up front. The first, "How should DNS records be imported?", defaults to "Import DNS records automatically," marked Recommended, which scans your domain's current records so mail and hosting entries carry over without you re-entering them by hand. The second, "Control how AI crawlers scrape content for training," defaults to "Block AI crawlers on all pages," with a toggle underneath for "Instruct AI bot traffic with robots.txt" — a newer setting reflecting how much AI training crawler traffic has grown, letting you block it site-wide from the moment your domain is connected.

Clicking Continue moves you into plan selection, where the Free tier sits alongside paid options. For a typical small site, the Free plan is enough to get started — it includes DNS management, proxying, and Cloudflare's baseline security features, with paid tiers adding things like advanced page rules, image optimization, and more granular analytics. Nothing about the DNS import or AI crawler choices you made on the previous screen is affected by which plan you pick here.

After the scan finishes, Cloudflare shows the records it found and imported, and this is worth actually reading rather than clicking past — check specifically that your MX records for email are present and that the A or CNAME rows pointing at your hosting are correct. An automatic import is reliable most of the time, but a record with an unusual TTL or a subdomain your provider set up manually can occasionally be missed, and it's much easier to catch that now than after your nameservers have already switched over.

The last step happens outside Cloudflare entirely: it assigns your domain a unique pair of Cloudflare nameservers, and you need to log into whichever registrar your domain is actually registered with and replace the existing nameservers with those two values. Propagation after that change can take anywhere from a few minutes to about 24 hours depending on your registrar and your domain's previous DNS TTL settings, and Cloudflare's dashboard will show the domain as active once it detects the new nameservers are live.