Visits and page views
Compare recorded visits with page views for the selected project and reporting range.
Web Analytics for SEO Decisions
Connect a matching Cloudflare zone and review visits, page views, pages per visit, mobile share, device trends, referrers, countries, browsers, and operating systems inside the same Screpy project as your SEO work.
TL;DR
Too Long; Didn't Read
Show summary Hide summary
TL;DR
Too Long; Didn't Read
What is Screpy Web Analytics?
Screpy Web Analytics is a project-level view of connected Cloudflare Web Analytics data. It compares visits, page views, pages per visit, mobile share, and device trends for a selected range, then shows the leading referrers, countries, browsers, and operating systems by visits.
Measure traffic volume
- Visits reports the visit count available for the selected project and date range.
- Page views reports recorded page-load activity for the same range.
- Pages per visit divides page views by visits to add a simple depth signal.
Compare time and devices
- Choose 24 hours, 7 days, 30 days, 60 days, or 90 days without leaving the project.
- Metric cards compare the selected range with the immediately preceding equal-length period when comparison data is available.
- The visits chart separates desktop, mobile, tablet, and other device traffic using hourly or daily buckets.
Review sources and markets
- Referrers lists the leading referring hosts by recorded visits.
- Countries lists the leading visitor countries for the selected range.
- Each breakdown keeps the five leading available rows visible for a focused comparison.
Interpret the scope correctly
- Browser and operating-system breakdowns add technology context without identifying individual visitors.
- Search Console remains the source for Google queries, impressions, clicks, CTR, and average position.
- Web Analytics does not currently report conversions, events, session recordings, or a popular-pages table.
Start with four traffic metrics.
Read visits, page views, pages per visit, and mobile share together, then use available previous-period changes to decide which movement deserves investigation.
- Compare visit and page-view volume
- Add depth with pages per visit
- Read mobile share beside the traffic total
See how visits change by device.
Follow desktop, mobile, tablet, and other visits across hourly or daily buckets so a total change does not hide a device-specific pattern.
- Switch between five reporting ranges
- Compare four device categories
- Read hourly or daily traffic buckets
Find the leading sources and markets.
Compare the leading referring hosts and countries by visits, then validate the pattern in the campaign, content, or search data that can actually explain it.
- Review the five leading referrers
- Compare the five leading countries
- Keep every row tied to the selected range
Review browser and operating-system traffic.
Use the leading browser and operating-system rows to prioritize compatibility checks without treating a traffic breakdown as proof of a performance or conversion problem.
- Compare browsers by visits
- Compare operating systems by visits
- Use the pattern to focus manual testing
Focused website traffic analytics for SEO teams
Review the traffic metrics and breakdowns Screpy actually provides, without mixing them with search-query, conversion, or session-level analytics.
Pages per visit
Use page views divided by visits as a simple depth signal, then investigate the pages and intent elsewhere.
Mobile share
See what percentage of recorded visits came from mobile devices during the selected range.
Previous-period change
Compare each headline metric with the immediately preceding equal-length period when the source provides enough data.
Visits by device
Follow desktop, mobile, tablet, and other visits in hourly or daily chart buckets across the selected range.
Referrer breakdown
Review the five leading referring hosts and the visit count recorded for each one.
Country breakdown
See the five leading available countries by visits for the current date range.
Browser and OS breakdowns
Compare the five leading browsers and operating systems by visits to focus compatibility review.
Move from connected traffic data to a testable question.
Connect the right zone, enable Web Analytics, choose a useful range, establish the traffic baseline, and use each breakdown to narrow—not invent—the explanation.
- 01
Connect the matching Cloudflare zone
Authorize the Cloudflare account that can access the website zone attached to the active Screpy project. Update the token when the zone or required permission is unavailable.
- 02
Enable Web Analytics for the zone
Use the project setup state to enable Web Analytics when it is disabled. Data cannot appear until the matching zone and Web Analytics status are ready.
- 03
Choose one reporting range
Select 24 hours, 7 days, 30 days, 60 days, or 90 days based on the event or decision under review instead of comparing unrelated time windows.
- 04
Read volume before the breakdowns
Start with visits, page views, pages per visit, mobile share, and available previous-period changes so every device or audience observation stays tied to the same baseline.
- 05
Segment the movement and verify the cause
Use device, referrer, country, browser, and operating-system patterns to narrow the question, then confirm search, campaign, release, availability, or page evidence in the tool that measures it.
Use traffic context where it changes the next decision.
The view is most useful when a defined SEO, release, referral, market, or compatibility question can be checked against one consistent reporting range.
Add traffic context to an SEO review
Compare site traffic with Search Console, ranking, crawl, and performance evidence for the same period without claiming that one movement caused the other.
- Shared date context
- Traffic baseline
- Separate source evidence
Investigate a device-specific change
Use the visits-by-device chart and mobile share to see whether a total change is concentrated on desktop, mobile, tablet, or other traffic before testing the affected experience.
- Device trend
- Mobile share
- Focused testing scope
Review referral and market concentration
Check the leading referrers and countries after a partnership, campaign, launch, or localization change, then validate the specific source and landing experience outside the summary.
- Leading referrers
- Leading countries
- Manual source validation
Prioritize compatibility checks
Use browser and operating-system visit counts to focus QA on the environments represented in current traffic while keeping compatibility conclusions tied to real tests.
- Browser mix
- Operating-system mix
- Evidence-led QA
Keep website traffic analytics inside its real scope.
Screpy provides a focused Cloudflare traffic summary beside SEO workflows. It does not turn aggregate traffic into query attribution, conversion analytics, or proof of causation.
Traffic is not search-query data
Web Analytics does not report Google queries, impressions, CTR, average position, or query-to-page relationships. Use the connected Search Console workflow for those questions.
The page is not conversion analytics
Screpy does not currently show popular pages, custom events, goals, funnels, session recordings, or campaign attribution in this view.
Breakdowns are focused summaries
Referrer, country, browser, and operating-system cards show up to five leading rows by visits. They are not complete visitor, session, or user-level datasets.
Movement does not prove causation
A change can reflect demand, referrals, campaigns, seasonality, releases, outages, or measurement conditions. Confirm the explanation with the source data relevant to the decision.
Choose the analytics view that matches the question.
Use Web Analytics for broader site traffic, Search Console for observed Google search performance, or AI and Bot Traffic for verified crawler requests to website URLs.
Review visits, page views, pages per visit, mobile share, device trends, and leading audience breakdowns for the connected zone.
Inspect Google queries, pages, clicks, impressions, CTR, average position, and supported search dimensions for the connected property.
Review verified crawler categories, request trends, transfer volume, response outcomes, and non-2xx paths for the matching zone.
Related SEO guides
Learn the concepts behind this workflow and apply them with practical SEO guidance.
SEO
How to Use GA4 Reports for SEO Performance
GA4 reports for SEO performance: filter organic traffic, compare landing pages, engagement and key events, and tie Search Console queries to conversions.
Read article Digital Marketing
How to Know if Your Website Traffic is Good or Not?
Understand whether your website traffic is healthy by tracking quality metrics, traffic sources, user behavior, conversions, and growth opportunities.
Read article GEO
How Do You Track ChatGPT Traffic for Your Website and Competitors?
Track ChatGPT traffic in GA4, analyze landing pages, engagement and conversions, then benchmark competitor referral trends while accounting for referrer data.
Read article SEO
What SEO Alerts Should You Monitor Before Traffic Drops
SEO alerts to track in GA4 and Search Console: indexing and crawl errors, ranking volatility, Core Web Vitals shifts, plus security or manual actions.
Read articleWeb analytics questions, answered.
Understand the connected data source, metrics, reporting ranges, breakdown limits, setup requirements, and the difference between traffic and search-performance analysis.
What can I measure with Screpy Web Analytics?
You can review visits, page views, pages per visit, mobile share, previous-period changes, visits by device, and the five leading referrers, countries, browsers, and operating systems for the selected range.
Where does Screpy Web Analytics data come from?
The page uses Web Analytics data from a connected Cloudflare account and the zone matched to the active Screpy project. Metric availability depends on the connection, zone access, Web Analytics status, selected range, and available traffic.
What must I connect before data appears?
Connect Cloudflare with access to the matching website zone and enable Web Analytics for that zone. Screpy shows a setup or token-update state when the account, zone, permission, or Web Analytics status is not ready.
Which reporting ranges can I use?
You can select 24 hours, 7 days, 30 days, 60 days, or 90 days. The device chart uses hourly buckets for the short range and daily buckets for longer ranges when data is available.
What is the difference between visits and page views?
Visits reports the visit count available from the connected source, while page views reports recorded page-load events. One visit can include multiple page views, which is why Screpy also calculates pages per visit.
How are previous-period changes calculated?
Screpy compares the selected range with the immediately preceding range of equal length. When the source cannot provide a usable comparison, the metric remains visible without a change percentage.
Which device categories are shown?
The visits chart separates desktop, mobile, tablet, and other device traffic. Mobile share reports mobile visits as a percentage of all recorded visits in the selected range.
What appears in the referrer and audience cards?
Each card shows up to five leading available rows by visits: referring hosts, countries, browsers, and operating systems. These are focused summaries, not complete visitor-level or session-level records.
Does Screpy Web Analytics show popular pages, conversions, or custom events?
Not currently. The page does not include a popular-pages table, conversion goals, custom events, funnels, session recordings, or campaign attribution. Use the analytics system responsible for those measurements when the decision depends on them.
Does Web Analytics replace Google Search Console?
No. Search Console reports Google queries, impressions, clicks, CTR, average position, pages, and other search dimensions. Web Analytics reports broader site traffic and audience breakdowns. Use both when investigating whether search visibility and site activity moved together.
Does a traffic change prove that an SEO change worked?
No. Traffic can change because of search demand, referrals, campaigns, seasonality, releases, outages, or measurement conditions. Use the date, device, referrer, market, Search Console, ranking, crawl, and performance evidence needed to test a specific explanation.
Connect traffic movement with the evidence behind it.
Bring the matching website zone into Screpy, review one consistent range, and investigate the device, source, market, or technology pattern without overstating what aggregate traffic can prove.