Skip to main content
Cloudflare adds crawler requests that reach your site through its network, including cached pages and requests blocked before WordPress runs. Heralded reads your analytics and writes nothing to Cloudflare. While Cloudflare approves Heralded’s connection, it appears under Coming soon on Connections.

Connect your site

You need a site whose traffic passes through Cloudflare and permission to read its zone analytics.
  1. Open your brand’s Connections settings page and select Connect on the Cloudflare row.
  2. In Connect Cloudflare, review Reads and Does under Access. If you manage a workspace with several brands, choose For every brand or this brand only.
  3. Select Continue with Cloudflare, sign in and allow read-only access to your zones and analytics.
  4. If Choose opens, confirm the zone with Done. Only zones that serve your brand appear, with an exact match first. The connection’s pane opens with a confirmation.
Choose the workspace option to make the account available to your other brands. Each brand reads only a zone that serves its domain.

When counts arrive

Choosing the zone starts a pull of the past 29 completed days. Heralded updates counts daily after that. Requests from the current day arrive after the day ends. A busy zone’s first pull may pause for several minutes while Cloudflare’s query quota resets. Counts feed the crawler figures in each page’s stats. A weekly report keeps the counts it read. The first pull fills the latest weekly report’s crawler counts if that report saved none.

What the counts mean

Heralded identifies bots by their user agent. A successful response counts as served. A missing page counts as not found. Other errors count as blocked because the bot could not read the page. Redirects do not count separately; the destination request carries the result. Verification depends on what Cloudflare identifies for that bot on that day. If Cloudflare verifies any of its requests, the remaining requests without verification count as unverified. If it verifies none, verification is unknown. Unknown does not mean unverified. Counts on very busy zones are estimates. Heralded uses Cloudflare’s reported count directly. It does not multiply it by a sampling interval. If Cloudflare cannot return a complete day, Heralded keeps the last successful pull and tries again. It does not store a partial count as a complete day. When Cloudflare and WordPress both report a day, Heralded uses Cloudflare’s counts for that day. It does not add the two sources together.

Disconnect

Open the Cloudflare row, then the ⋯ menu and Disconnect on the workspace’s connection to revoke access to that account. On a brand using the workspace’s account, Disconnect removes only that brand’s binding. Workspace admins can tick Also remove it from the workspace in the same question, which stops every brand reading through it. Past weekly reports keep their numbers. Removing a brand’s override falls back to the workspace’s account when it has one matching zone.