SEO Web Analytics

Review recorded website visits, page views and audience trends beside your SEO work. Connect a matching Cloudflare zone to see what changed, then use the right evidence to investigate why.

Explore website traffic Explore the Cloudflare integration
Screpy Web Analytics dashboard showing visits, page views, pages per visit, mobile share, device trends, referrers, countries, browsers, and operating systems
Uber logo in Screpy SEO platform customer trust section
Philips logo in Screpy SEO platform customer trust section
FedEx Express logo in Screpy SEO platform customer trust section
Bosch logo in Screpy SEO platform customer trust section
Champion logo in Screpy SEO platform customer trust section
Iconfinder logo in Screpy SEO platform customer trust section
T-Mobile logo in Screpy SEO platform customer trust section
Carrefour logo in Screpy SEO platform customer trust section
Stanley logo in Screpy SEO platform customer trust section
Skoda logo in Screpy SEO platform customer trust section

Connect Website Analytics

Bring recorded browser traffic into the same Screpy project as your SEO work. Connect your Cloudflare account, match the website zone and enable Web Analytics before interpreting the numbers.

  • The connection needs a valid token with access to the matching zone and its analytics.
  • The matched analytics site can include subdomains; this view does not isolate one project hostname or URL path.
  • Automatic collection requires eligible proxied pages and a working browser beacon; blockers or delivery failures can leave visits unrecorded.
  • Setup, unavailable and failed-report states are different from measured zero traffic.

Understand Visits and Page Views

Read the traffic cards as distinct measurements. A rise in page views does not automatically mean more people visited or completed a useful action.

  • Visits count recorded entries from another website or a direct link, rather than unique people.
  • Page views count recorded page loads; one visit can include several views.
  • Pages per visit divides page views by visits, rounded to two decimals; without visits, the ratio remains unavailable.
  • These totals do not measure time on page, bounce rate, purchases or completed signups.

Compare Website Traffic Periods

Put a traffic change in a defined time window before connecting it to a release or SEO decision. Each card compares the selected interval with the immediately preceding interval of equal duration.

  • Choose 24 hours, 7, 30, 60 or 90 days; the default view is 7 days.
  • The 24-hour range ends at the last completed UTC hour; longer ranges include the current partial UTC day.
  • Change is the difference divided by the previous value, multiplied by 100; a zero previous value leaves the comparison unavailable.
  • Mobile-share change is relative percent, not percentage points: a rise from 20% to 30% is +50% relative change.
  • A previous-period comparison is not a matched-weekday experiment or proof that SEO caused the change.

Analyze Traffic by Device

See whether a traffic movement is concentrated on desktop, mobile, tablet or other devices. The stacked chart shows visits per hour for 24 hours and per day for longer ranges.

  • Each bar separates the four device categories for the selected reporting interval.
  • Mobile share is mobile visits divided by all visits; tablets are a separate category.
  • Device counts help prioritize investigation, but do not measure page speed or prove that an experience works correctly.

Review Website Referrers

Find the hosts behind the largest recorded referral counts. Use the list to choose a source to investigate after a partnership, mention or campaign.

  • Up to five referring hosts are ranked by visits in the selected interval.
  • Entries without a referrer host are omitted, so this list does not show all direct or unknown traffic.
  • A host count is not a referring-page URL, campaign attribution or proof that a backlink produced a conversion.

Explore Traffic by Country

See which countries contribute the most recorded visits. Use the country mix to choose a market for further research without confusing website activity with local search rankings.

  • The country card shows up to five country codes and their visit counts.
  • Blank country records are omitted; the displayed rows are not the complete geographic distribution.
  • Country-level traffic does not identify a person's city, language, purchase intent or conversion.

Check Browser and OS Traffic

Focus compatibility checks on the environments represented in current traffic. Browser and operating-system cards summarize separate dimensions of the same reporting interval.

  • Each card lists up to five categories by visits; an Unknown label can remain when the source lacks a name.
  • These separate lists do not identify browser–OS pairs or establish compatibility; verify the actual experience before diagnosing a problem.

Talk about Web Analytics. With SEO MCP.

Ask about Quick Wins built from available search, crawl and connected Cloudflare traffic signals through SEO MCP. Cloudflare access covers those opportunities, not the complete analytics or bot-traffic dashboard.

  1. Screpy: Hello! Let’s look at Web Analytics for example.com. What would you like to know?
  2. You: Which traffic-based Quick Wins should I review for example.com?
  3. Screpy: Review pages with search opportunities and traffic signals in the same project. Cloudflare-based opportunities need a connected zone and available data; full analytics and bot-traffic records are not exposed through MCP. Quick Wins context: Search opportunities: Available project data. Cloudflare signals: Connection required.
  4. You: Turn that into a short action plan.
  5. Screpy: I’ll keep the evidence and recommendations separate. Review the findings, choose one change and check the results afterward. Your next steps: Review: Check the source and date of each finding.. Decide: Choose the first change to make.. Verify: Compare the results after the change..
  6. You: Can you explain the evidence in plain language?
  7. Screpy: Yes. Ask about a supported result and I can explain what it shows, where it comes from and what is still uncertain. Missing data stays unavailable; recommendations are not automatic fixes.

Move from connected traffic data to a testable question.

Connect the matching zone, confirm Web Analytics collection and choose a consistent period. Read the totals, isolate the relevant device or audience pattern and verify the explanation in the tool that measures it.

  1. 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.

  2. Enable Web Analytics for the zone

    Enable Web Analytics when the project shows the setup control. Confirm that the website can collect browser reports; an enabled status alone does not prove data arrived.

  3. 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.

  4. 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.

  5. 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.

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.

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.

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.

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.

Web Analytics FAQ

Understand the connected data source, metrics, reporting ranges, breakdown limits, setup requirements, and the difference between traffic and search-performance analysis.

Which reporting ranges can I use?

Choose 24 hours, 7, 30, 60 or 90 days. The 24-hour view uses completed UTC hours; longer views use daily buckets and include the current partial UTC day. Available data depends on collection and source access, not just the selected range.

What must I connect before data appears?

Connect your own Cloudflare account with a valid token and access to the matching zone. Enable automatic Web Analytics and confirm eligible proxied pages collect browser reports. Screpy distinguishes missing connection, unmatched zone, token updates, status failures and disabled collection.

How are previous-period changes calculated?

Screpy compares the selected interval with the immediately preceding interval of equal actual duration. Relative change is (current minus previous) divided by previous, multiplied by 100. A zero previous value suppresses the comparison. Mobile-share change also uses relative percent, not percentage points.

Where does Screpy Web Analytics data come from?

The connected Cloudflare Web Analytics site supplies browser page-load reports, with classified bots excluded. Collection can miss blocked or undelivered reports and can include subdomains of the matched zone; it is not a complete server-request log.

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. Demand, referrals, campaigns, seasonality, releases, outages and collection changes can affect traffic. Compare the same periods and verify the proposed cause with search, campaign or product evidence.

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.

Can SEO MCP read all Web Analytics data?

No. SEO MCP can return supported traffic-based Quick Wins for an accessible project with the required connection and data. It does not expose these metric cards, the device chart or the complete audience breakdowns. Review those in the Web Analytics dashboard.

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.

What appears in the referrer and audience cards?

Each card shows up to five categories ranked by visits. Blank referrer hosts and country codes are omitted, so the referrer list excludes direct or unknown sources. Browser and OS names may be Unknown. These are separate summaries, without combined filters or complete visitor records.

What is the difference between visits and page views?

A visit is a recorded entry from a different website or a direct link, not a unique person. Page views are recorded page loads. Pages per visit is their ratio, rounded to two decimals; no visits leaves that ratio unavailable. It is not measured engagement time or a conversion rate.

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.