Skip to reports
Mayfly
Back to websiteView beta access
A working example

Your website, a little clearer.

Switch the chart, inspect a source, or open a page. These are the same report components you’ll use with your own data.

Aug 31 – Sep 6, 2026 · UTC
Example data only. This is a fixed, simulated website report. It never connects to your website or customer data.

Priority brief

Simulated inputs · same scoring as your dashboard
  1. 01

    /pricing

    Full evidence coverage
    Observed priority60 / 100
    Demand
    11 / 25
    2,200 impressions, 140 clicks and +35 estimated upside clicks. Leading query “mayfly example pricing”: position 6.2, 6.4% CTR.
    Engagement
    9 / 25
    34.0% observed low engagement; 1,100 organic visitors reached the matched page variant.
    Field performance
    15 / 25
    Needs work: p75 LCP 3.4 s, INP 186 ms, CLS 0.080. Samples: LCP 862, INP 721, CLS 863.
    Crawl health
    25 / 25
    1 issue, 9 rule-weight points: Page is set to noindex. Critical indexability blocker: 25-point priority.
    Next action

    Page is set to noindex: Remove the noindex directive if this page should rank. Intentional on staging, thank-you, and filter pages — verify before changing.

    4 of 4 signal groups presentNo inputs missing.
How the priority is calculated

Four additive signals, 25 points each. Demand is 10 × impressions / (impressions + 1,000) + 15 × estimated upside / (estimated upside + 100), rounded once. These are diminishing-return scoring anchors, not traffic eligibility thresholds or forecasts. Engagement is the low-engagement percentage / 4. Field verdicts score 0 / 15 / 25 for good / needs work / poor. Crawl health sums published rule weights, capped at 25; a critical indexability blocker receives 25 so it takes precedence over copy changes. Missing inputs add zero and lower confidence. Confidence describes evidence coverage, not the probability a fix will work: high with all four signal groups, medium with three, and low otherwise. One eligible Core Web Vital covers the field group; missing metrics stay listed and do not invalidate an observed crawl, demand, or engagement signal. Each field metric still needs 30 samples and a partial field row cannot receive an all-metrics good verdict.

Daily uniques13.4Kup +14% vs prev
Pageviews21.7Kup +9.4% vs prev
Views / visit1.5down -3.5% vs prev
Bounce rate43%down -7.6% vs prev
Visit duration2m 52sup +12% vs prev

Traffic over time

7 daily buckets
Exact values & measurement notes

Only recorded buckets are shown. Missing buckets are not filled with invented visits; gaps keep their calendar spacing. The line is a monotone curve, which cannot rise above or fall below the two measurements it joins. Weekly and monthly daily-unique counts must not be interpreted as persistent people.

DateDaily uniquesPageviews
Aug 311,4222,120
Sep 11,7242,731
Sep 21,5312,448
Sep 32,1983,590
Sep 41,8272,912
Sep 52,0943,225
Sep 62,5884,646

Worth a closer look

  1. TrafficDaily uniques are up 14.2% period over period

    13,384 daily uniques, compared with 11,721 in the equal-length period before it.

  2. Attention/ is drawing the most attention

    9,024 pageviews in this period, with 46% entry-page bounce.

  3. Experience1 page needs Core Web Vitals work

    /pricing is the first page to inspect. Field data is shown at p75 after 30 samples.

Acquisition

4 shown
SourcesDaily uniques

Share of the 4 shown rows, not all site traffic.

Audience

6 shown
CountriesDaily uniques

Share of the 6 shown rows, not all site traffic. Locations are approximate.

Technology

4 shown
BrowsersDaily uniques

Share of the 4 shown rows, not all site traffic.

Pages worth your attention

Compare activity, then open a page for its performance evidence.

Top 6 by views
6 of 6 loaded pages
PageScroll
9,0247,1801m 7s46%58%
4,3503,6701m 43s35%76%
3,1202,5803m 14s38%82%
2,6501,9803m 47s28%69%
1,6001,4201m 18s37%64%
92881052s32%88%

Daily uniques are site-scoped daily identifiers. Bounce applies only to sessions that started on the page.

Core Web Vitals

Example field measurements · p75
PageLCP p75INP p75CLS p75Verdict
/1.92sn=2,170142msn=1,6300.040n=2,180Good
/pricing3.40sn=862186msn=7210.080n=863Needs work
/docs2.11sn=418159msn=3020.030n=419Good

Each p75 needs 30 usable measurements. “n” is per metric; a dash is ungraded, not zero.

Make the next report yours.

One script for traffic and real-user performance. Search Console when you’re ready.

Check beta access