Which problem is costing you the most traffic?
A list of problems is not a plan. This reads your own search data to find the pages that actually earn clicks, checks each one, and orders the faults by the traffic sitting on them. The page earning forty clicks a month with a broken canonical comes first, however interesting the others look.
Reads your connected search data and fetches your highest-traffic pages. Nothing is stored.
Not connected. Sign in and Connect Search Console to read Google's own verdict for this page. The check below still runs from public signals without it.
How this check works
Shipwork reads which pages earned clicks in the last 28 days from your own connected search property, fetches the highest-traffic ones, and checks each for the things that quietly remove a page from search: an error status, a noindex, a canonical pointing elsewhere, a missing title. The findings are then ordered by the clicks each page earns.
What the traffic at risk checker reads
The check reads your connected search data for the last 28 days and ranks pages by the clicks each one earns. It takes the top pages with at least one click, up to twelve, then fetches each one and checks the signals that quietly remove a page from search: a status other than 200, a noindex directive, a missing canonical, a canonical that points elsewhere, a missing title, a long title and a missing description.
It then weights each problem by the clicks on that page, so the total at risk is the traffic sitting on pages with an error or warning. It needs a connected search property, because without the click data there is no way to order the list. It fetches a bounded set, so it describes the pages that earn the most, not every page.
How to read the result
A clean result means the highest-traffic pages returned 200, are indexable and each has a title and a coherent canonical. That is the strongest available signal that the traffic you already have is not about to be lost to a page-level fault. It does not measure future opportunity, which the priorities list covers.
An error finding, a non-200 status or a noindex, sits on traffic at immediate risk. Canonical and title problems are warnings. A long title or a missing description is informational, because it affects the snippet rather than access. A page the check could not fetch is reported as a gap with no severity, so it never outranks a real problem.
Common causes and why they matter
Faults on high-traffic pages usually arrive from a template or deployment change: a noindex left on after staging, a canonical pointing at an old host, a migration that changed a URL, or a plugin that rewrote titles. Because these pages already earn clicks, the cost of leaving them is measurable rather than speculative.
A noindex or an error status removes the page from search entirely, so its clicks fall to zero. A canonical pointing elsewhere transfers preference to another URL. A missing title or description changes what searchers see and can reduce clicks even when the page still ranks. The order reflects clicks, so a small fault on a busy page outranks a large fault on a quiet one.
How to fix the top finding
Start with the single page the check names first. Remove an unintended noindex, restore a 200 response, point the canonical at the page's own URL, and give the page a distinct title and description. Fix it at the template or plugin level so the same fault does not affect the next deployment.
On Shopify, check theme settings, the noindex on pages and the canonical output; on WooCommerce, check the SEO plugin and any staging flag. After fixing, confirm the page is indexable and rerun the check with the same connected property. Then move to the next page on the list.
When to use related search data checks
Use the fix priorities list for opportunity, the traffic you might win, which rarely matches this exposure list. Use search data to connect the property this check reads.
When a page is not indexed at all, see why pages are not indexed and the indexability check.
Questions
How is this different from the fix priorities list?
Why only the highest-traffic pages?
Do I need Search Console connected?
How many pages does the check inspect?
Why is one of my pages missing from the list?
What does a non-200 status mean in this list?
Keep reading
What this reads
- Ranks your pages by the clicks a fault is costing, from your own Search Console data.
- Reads the property you connected; no data leaves your account.
- Every figure is your own impressions and clicks, not an estimate.
Cool, just ran an audit and got some insights! Let’s see if I can fix them :)
Whoah! this site is crazy, nothing to roast at all
cool as heck, tried it on my blog and the insights it gave are helpful and not bluff.