A little preparation.
A clearer result.

Get started

1. Create a free beta account and save your recovery code.
2. Add your website using its canonical HTTPS address.
3. Verify ownership using one of the methods below.
4. Import your sitemap or add public URLs manually.
5. Start a warming run, then review each page’s result.

The beta includes three websites and 1,000 warming units per calendar month. Each run checks up to 500 URLs; start with a small sample.

Verify ownership

Your website settings show a unique verification token. Choose one method:

• DNS: add a TXT record at _cachecharger.yourdomain.com with the token as its exact value.
• File: serve the token as plain text at /.well-known/cachecharger.txt on your website.
• WordPress: install the connector, paste the token in Settings → CacheCharger, and save.

Then select “Verify website.” DNS changes may take time to appear. Each hostname is verified separately; use the HTTPS hostname your site serves without a cross-domain redirect.

Warming and schedules

Import URLs from a sitemap or sitemap index. Discovery follows only the verified origin and reads a bounded number of sitemap documents. Adjust the sitemap URL in website settings; WordPress commonly uses /wp-sitemap.xml.

Schedules are optional: every 6, 12, or 24 hours, or weekly. The scheduler checks due sites every 15 minutes. A run continues after you close the dashboard. There is one active run per website, with a pause between pages and backoff after server errors or rate limiting.

Schedules reuse your saved URL inventory. Reimport your sitemap when you want to refresh it, or use the WordPress connector to queue published changes.

Reading your results

Each result records the HTTP response, CF-Cache-Status, selected cache headers, timing, and the location suffix returned in CF-Ray, when available.

• Warmed: a later request returned HIT after an earlier non-HIT response.
• Already warm: the first observation returned HIT.
• Uncached: no fresh HIT was confirmed. The diagnostic helps you investigate.
• Blocked or error: the request could not establish a useful result.

The Cloudflare-hosted beta reports response-header time, not browser load time or true network TTFB. Security DNS lookups are outside the final response-header timing interval. A first request may itself warm a page. DYNAMIC and BYPASS responses are diagnosed immediately rather than repeatedly requested.

Percentage changes are shown only for successful observations returning matching Cloudflare location evidence. They describe the observed pair, not a guaranteed causal speed improvement. Negative changes are retained. No cache is purged for these comparisons.

One Cloudflare-hosted probe does not prove worldwide coverage. The dashboard’s hit percentage covers checked pages, not real visitor traffic. URL-level details are retained for 30 days; aggregate run history remains available.

WordPress connector

Download the connector from your website’s Integrations tab. It supports ownership verification and queues the changed public URL, homepage, posts page, and relevant public archive pages after a published post changes. Drafts, autosaves, revisions, and non-public post types are ignored.

1. Upload the ZIP through Plugins → Add New Plugin.
2. Paste your verification token and verify the site in CacheCharger.
3. Generate a website integration key. Save it in the connector with your website ID.
4. Publish or update a public post. Changes are coalesced before warming.

Keys are scoped to one website. Generating a replacement revokes the previous key. The connector does not change Cloudflare settings or purge your cache. Generic purge hooks are available for developers; automatic support for third-party cache plugins will be added after compatibility testing.

Download WordPress connector

Safe defaults

Only public HTTPS pages on the verified origin are eligible. Query-string URLs, common account/admin/cart/checkout routes, and your custom exclusions are skipped. Robots.txt rules are respected. Private addresses, unusual ports, off-site redirects, and oversized downloads are rejected.

Warming cannot make personalised content safe to cache. Configure cache rules carefully and keep authenticated or customer-specific pages excluded. No global firewall bypass or cache purge is required.

Save the recovery code shown when you create an account. It is required if you forget your password; email-based recovery is not part of the beta. Recovering an account rotates the code and signs out existing sessions.

What’s next

The architecture separates the dashboard, job scheduling, observations, and probe execution. The next additions are geographically controlled probes, selected-page Lighthouse tests, regression alerts, and agency workflows. These are roadmap items, not current beta capabilities.