Show affected pages: seeing which URLs a finding touches
How the affected-pages list on a finding card works, what the per-URL detail means, and how to use it to fix the right pages first.
One finding, many pages
Rabbot groups findings by change type, not by page. A single card such as “Canonical tag changed” can represent one page or several hundred, because the same kind of problem often lands on every product in a collection at once. The card’s page count, “N pages affected”, is your first read on how big the problem is before you open anything.
Opening the list
Choose Show affected pages on a finding card to expand it. Each row is one URL: a link to the page itself, plus the raw detail Rabbot recorded for that page (for example, what the canonical tag now points to). Choose Hide affected pages to collapse the list again once you are done.
Reading the raw detail
The detail on each row is deliberately literal: the actual value Rabbot read, not a paraphrase. This matters when a fix touches templates rather than individual pages. If every row shows the same wrong value, the cause is usually one shared template or setting, and fixing it there clears every row at once rather than one page at a time.
Working through a long list
You do not have to fix every row in the order it appears. Skim the list for a pattern first: pages sharing a collection, a product type, or a template are often the same root cause. Fix the shared cause, then come back to the card. Rows for pages that are now correct drop off automatically on Rabbot’s next check of them, you do not need to clear them by hand.
When a page will not stop showing up
If a page keeps reappearing on the same finding after you believe you fixed it, check that the fix reached the live page and not just a draft or a cached version. Rabbot reads the page as a shopper would see it, so a change still sitting in an unpublished theme or a CDN cache will not register until it goes live.
What this list does not do
The affected-pages list only shows pages caught by this one finding. It is not a full site audit and it is not a list of every page Rabbot watches, see Which URLs Rabbot monitors for that. If a page you expected to see is missing from the list, it may simply be free of this particular problem while carrying a different one on its own card.
Still stuck? Email support@rabbot.ai and a real person reads it.