---
title: "Getting started — warmup.rocks Docs"
description: "Set up CDN cache warming in five minutes: add your sitemap, verify your domain, start the first warming run and watch your hit ratio climb."
canonical: https://warmup.rocks/docs/
---

# Getting started

warmup.rocks keeps your CDN edge cache warm in 90+ locations worldwide. Setup takes about five minutes and requires no plugin, no script tag and no DNS change to your production traffic.

## How it works, in one paragraph

CDNs like Cloudflare, Fastly and Akamai cache **per edge location** — a page cached in Frankfurt is still cold in Tokyo. warmup.rocks requests your pages through proxies in 42 countries on 6 continents, so each request enters the CDN network in a different region and warms the edge location it lands in. Real visitors then get a cache HIT wherever they are.

## 1\. Create an account

[Register](https://warmup.rocks/app/?register=1) with your email address — we send you a magic sign-in link, no password needed. Every plan starts with a **7-day free trial**; nothing is charged until the trial ends.

## 2\. Create a project

A project is one website. Give it a name and its base URL (e.g. `https://example.com`), then add your sitemap URL. We resolve nested sitemap indexes automatically and keep the URL list in sync on every run — see [Sitemaps & URL discovery](https://warmup.rocks/docs/sitemaps).

## 3\. Verify your domain

Before we warm a site on a schedule, you prove you own it — either with a DNS TXT record or a response header. This takes two minutes and protects site owners from unwanted traffic. See [Domain verification](https://warmup.rocks/docs/domain-verification).

## 4\. Start your first run

Hit _Warm now_ in the dashboard. A run requests every URL from every proxy location and records the CDN, edge location (colo) and cache status (`HIT` / `MISS` / `EXPIRED`) for each request. The first run is mostly MISSes — that's the point: each MISS fills a cache. The second run is where you see the hit ratio climb.

**Tip:** if your site sits behind bot protection (Cloudflare Super Bot Fight Mode, a WAF, rate limiting), set a custom secret header in the project settings and write an allow rule for it. See [Analytics & WAF filtering](https://warmup.rocks/docs/analytics-waf).

## 5\. Put it on a schedule

Choose an interval that matches your cache TTLs — hourly is right for most sites. From then on, warming runs happen automatically and the dashboard tracks hit ratio, response times and colo coverage over time. See [Schedules & intervals](https://warmup.rocks/docs/schedules).