No performance baseline captured
This is a SurfaceOps measurement gap: you can fix issues, but you cannot prove lift without a baseline.
Symptom
The workflow can still detect structural issues, but it cannot show before-and-after traffic movement yet.
Exact cause
SurfaceOps detected this state because Search Console is connected, but Google has not returned page-level impressions or clicks for the tracked storefront yet. StoreSteady can still detect structural issues, but it cannot quantify impact trends without a baseline.
This is an operational measurement state, not an official Google issue label. It matters inside the workflow more than it matters as a public acquisition page.
Which system wins
This is a SurfaceOps measurement state, not a Merchant Center disapproval. Search Console and internal evidence capture decide whether lift can be proven later.
Correct edit point
Connect Search Console, confirm the correct property, and collect baseline data before making bulk changes you want to measure.
Manual fix steps
- Confirm the verified Search Console property matches the storefront domain.
- Submit your sitemap in Search Console if you have not already done so.
- Wait for Google to crawl and accumulate some page-level impression data.
Validation steps
- Confirm the correct Search Console property is connected and receiving impressions for the storefront domain.
- Wait for Google to accumulate page-level clicks and impressions before judging lift.
- Re-run the audit after new data arrives so StoreSteady can compare before and after performance.
Expected resolution time
A fresh property often needs a little time before impressions and clicks appear in Search Console.
Scan your store for this exact issue
Check whether your storefront is showing the same public signal problem described in this article before you connect the app. Start with no performance baseline.