Fresh
Recent data is available inside the source-specific freshness window.
Monitoring coverage
Know when the evidence is fresh, stale, failed or missing.
Monitoring coverage is the trust layer beneath Store Health. It answers whether each connected source is configured, working and recent enough to support a health conclusion. Without that layer, missing data can look deceptively healthy.
Every source keeps its own state, last successful observation and source-specific freshness window.
What Beseam uses
Concrete evidence contributing to this Beseam workspace.
Stale
A successful observation exists, but it is too old to support a current healthy answer.
Disconnected or failed
The connection is unavailable or returned an error and cannot currently support the answer.
Not configured
No trustworthy record or data has arrived for that source yet.
The evidence path
One trust model across both Beseam workspaces.
- 01
Connect the source
Use the store, search or storefront evidence already in scope.
- 02
Check freshness
Confirm the source is configured, working and recent enough.
- 03
Keep provenance
Attach the source record, affected scope and observation time.
- 04
Route the issue
Give the right owner an investigation path and next action.
01
Different sources age at different speeds.
A storefront event stream becomes stale sooner than a completed crawl. Beseam uses deterministic, source-specific freshness thresholds rather than one arbitrary timestamp for the whole store.
- Shopify catalog and Search Console require recent synchronization.
- Storefront tracker coverage reflects recent observed events.
- Crawl and product-page verification have longer technical windows.
02
Coverage changes the health answer.
Critical evidence can still produce a critical status. But when the primary source is missing, disconnected or failed, the domain becomes unknown. A stale source produces degraded or unknown depending on the active evidence.
- Unknown is not a softer version of healthy.
- Low-severity issues do not degrade a domain on their own.
- Overall healthy requires all domains and reported sources to be current.
03
Coverage gaps become work your team can route.
A stale connector or missing verification run is itself operational information. The team can reconnect a source, run a fresh check or narrow the confidence of an investigation instead of relying on an unsupported status.
- Last successful and last data timestamps remain available.
- Coverage is grouped by discoverability, purchase or monitoring domain.
- The message explains why the source has its current state.
Current product boundary
What Beseam does not claim
- Freshness confirms recent data - not the absence of every issue.
- A configured source with no trustworthy data is not considered healthy.
- Thresholds are deterministic but may evolve with the product.
- Coverage does not replace source-specific investigation.
Questions about monitoring coverage
Why can a store be unknown instead of healthy?
Because a primary source is missing, stale, disconnected or failed. Beseam refuses to infer health when the evidence cannot support it.
Does fresh mean there are no problems?
No. Fresh only means the source is current enough to evaluate. Active issues still determine whether the domain is critical, degraded or healthy.
Can one stale source affect the overall state?
Yes. A would-be healthy overall state is downgraded when reported source coverage is not fully current.
Continue exploring Beseam
Start with your store - and how AI sees it.
Review your Shopify setup, current monitoring coverage and priority AI visibility questions in one focused session.