First-party observed data
Search Visibility Benchmarks 2026 (First-Party)
First-party, aggregated search-performance observations from BoringToolsKit Search Console, published as citable benchmarks: impression growth from 82 to 6,723 across consecutive 28-day windows, the daily trajectory, and impression share by query cluster. Queries are aggregated counts, not user data; numbers are self-reported first-party measurements, not independent audits.
Reviewed July 26, 2026 · Self-reported first-party aggregates from Search Console; not an independent audit. Queries are aggregated, never user data.
What does search visibility look like for an 853-tool site in its first growth phase?
First-party, aggregated search-performance observations from BoringToolsKit Search Console, published as citable benchmarks: impression growth from 82 to 6,723 across consecutive 28-day windows, the daily trajectory, and impression share by query cluster. Queries are aggregated counts, not user data; numbers are self-reported first-party measurements, not independent audits.
What assumptions does this benchmark use?
Rows are first-party aggregates pulled from the Search Console performance API on September 1, 2026. Windows: July 7–August 4 and August 5–September 1, 2026. Counts are aggregated query impressions, never user-level data. Future updates will re-pull and re-stamp this table; treat the pull date as the dataset version.
What does the scenario table show?
| Metric | Window B Jul7 Aug4 | Window A Aug5 Sep1 | Change | Notes |
|---|---|---|---|---|
| impressions (window total) | 82 | 6723 | 82x | |
| clicks (window total) | 0 | 1 | near zero | ranking breadth arrived; selection lags |
| indexed query-page rows | 48 | 4961 | 103x | |
| site search CTR | 0.000 | 0.00015 | flat | opportunity sits at positions 45-90, not the 8-12 zone |
| edge daily uniques (Aug 25 peak week) | n/a | 384 -> 1,962 (Aug 31 peak) | 5x weekly | Cloudflare edge, incl. crawlers |
| mortgage query cluster impressions | 0 | ~228 | new | spot-check clusters, Aug 5-Sep 1 |
| apy calculator query cluster impressions | 0 | ~276 | new | 5 query variants, Aug 5-Sep 1 |
How should you use these numbers?
Use the table to understand sensitivity, then replace every assumption with current values relevant to your decision. The linked calculator provides editable inputs. Do not treat a hypothetical row as a quote, policy, tariff, compensation survey, or purchase instruction.
Open the related calculator → · Explore the topic collection →
What source supports the method or context?
Google Search Console — performance reports (first-party data). This source supports terminology or calculation context; it does not endorse BoringToolsKit’s hypothetical scenario values.
Calculation and publication rules: BoringToolsKit methodology.