Check this page with an assistantOpens a chat asking it to summarise this article and name the evidence behind each claim.
Claude opens with the prompt on your clipboard: Anthropic does not support prefilled prompts on the web, and we would rather copy it than ship a button that drops it.
Decisions first
Install and verify the Cloudflare Web Analytics beacon, configure route tracking for the site's SPA behavior, and report pageviews and performance by normalized pathname. Keep beacon/RUM data separate from Cloudflare edge request datasets and from Search Console impressions and clicks. Account for blocked beacons, omitted query strings, short unsampled retention, and longer-term sampling before comparing windows or declaring an SEO change successful.
- The JavaScript beacon measures browser-visible activity; Cloudflare edge analytics measures requests at a different collection layer.
- Web Analytics does not log query strings as a reporting dimension, so define a safe page-identity policy around pathnames.
- Cloudflare Web Analytics is not currently a native SearchHandled connector.
Separate three measurement layers
Name browser Web Analytics, edge request analytics, and Search Console explicitly every time a metric leaves its native report.
Cloudflare Web Analytics uses a JavaScript beacon and focuses on privacy-friendly website analytics and performance. Edge analytics observes requests served through Cloudflare and can include bots or requests that never execute JavaScript. Search Console measures Google search visibility and clicks before the destination page loads.
A Google click can fail before the beacon loads; a beacon can be blocked; an edge request may be a bot, asset, prefetch, or cache interaction. These are not defects to normalize away. They are evidence from different scopes.
| Layer | Observes | Common blind spot |
|---|---|---|
| Search Console | Google impressions and clicks | Onsite outcome |
| Web Analytics beacon | Browser pageviews and performance | Blocked or failed beacon |
| Cloudflare edge | Requests at the network edge | Human intent and client rendering |
| Business system | Qualified outcome | Unidentified or unconsented journey |
Validate the beacon and SPA route model
Confirm one full page load and each supported client-side route transition produces exactly the intended pageview with the expected pathname.
For non-proxied sites, install the documented beacon snippet. For sites proxied through Cloudflare, confirm the site's Web Analytics configuration and actual delivered markup. Then inspect network requests and the product view from a clean browser rather than assuming a dashboard tile means every template is covered.
Single-page applications need a route strategy that matches the framework and router. Test initial load, pushState and replaceState behavior, back and forward navigation, hash changes, redirects, 404s, consent states, and duplicate script injection. Record releases that change routing or beacon behavior.
- Initial document load
- Client route transition
- Back/forward
- Redirect
- 404
- Consent state
- Ad blocker
- Duplicate beacon
Normalize pathnames without inventing query detail
Build canonical page identity from pathname, redirects, locale, and known route rules because Web Analytics does not log query strings as a dimension.
The omission reduces the chance of collecting sensitive URL parameters, but it also means parameter-defined pages cannot be reconstructed from this dataset. If a product or locale is meaningful only in the query string, redesign the reporting question or add a separately governed event—not an inferred value.
Map Web Analytics paths and Search Console page URLs to a versioned canonical-page ID. Aggregate each source before joining. Keep raw paths, redirect dates, and unresolved aliases so migrations do not look like traffic losses by accident.
Interpret performance with blocking, retention, and sampling visible
Use Web Analytics for directional page and performance evidence only after noting the collection and retention regime for the exact date window.
Cloudflare documents that some blockers can prevent the Web Analytics beacon while edge analytics remains observable. It also documents a limited unsampled beacon-data window followed by sampled longer-term aggregation, with sampling metadata available. A before/after comparison that crosses regimes needs that caveat.
Pair page-level search visibility with browser performance and qualified business outcomes. Investigate a slow high-impression landing page, but do not claim that a Core Web Vitals improvement caused ranking or revenue without an appropriate design and competing explanations. Report excluded routes, blocked-beacon checks, sample interval, and configuration changes.
Continue the workflow
Validate ten representative routes with and without an ad blocker, including SPA navigation, query parameters, redirects, edge-request comparison, sampling metadata, and Search Console page mapping.
- Search Console vs analytics: keep collection layers and totals distinct
- technical SEO indexing diagnostics: turn page and performance signals into diagnostics
- SEO reporting framework: publish definitions, caveats, and decisions
Questions teams ask
- Is Cloudflare Web Analytics the same as Cloudflare traffic analytics?
No. Web Analytics uses a browser beacon, while edge products observe requests at Cloudflare's network. Their populations, bot exposure, blocking, and metrics differ.
- Does Cloudflare Web Analytics record query strings?
Cloudflare's current dimensions documentation says query strings are not logged. Use governed pathname-based identity and do not infer missing parameter values.
- Can Cloudflare Web Analytics replace Search Console for SEO?
No. It can provide onsite pageview and performance evidence, while Search Console reports aggregate Google search impressions, clicks, CTR, and position.
Primary sources
The SearchHandled Editorial Team prefers first-party documentation and names the limits of each source. Links were checked on the access date.
- Cloudflare Developers: About Cloudflare Web AnalyticsAccessed August 29, 2026
- Cloudflare Developers: Get started with Web AnalyticsAccessed August 29, 2026
- Cloudflare Developers: Web Analytics for single-page applicationsAccessed August 29, 2026
- Cloudflare Developers: Web Analytics dimensionsAccessed August 29, 2026 · Query strings are not logged as a dimension in Web Analytics.
- Cloudflare Developers: Web Analytics FAQAccessed August 29, 2026 · Beacon collection and edge analytics have different blocking, retention, and sampling behavior.
- Google Search Console Help: Performance report: clicks, impressions, CTR, and positionAccessed August 29, 2026 · Defines Search Console metrics; it does not create a user-level analytics join.
