Skip to content
VisibilityIQ365 VisibilityIQ365 VisibilityIQ Help

Page Explorer

Page Explorer is the same crawled inventory as Crawled Pages, built for hunting instead of scanning. When you already know roughly what you are looking for — every 404, everything under /blog/, everything marked noindex — Page Explorer lets you filter and search the set down to just those pages and inspect them individually. Reach for it the moment the full list is too long to eyeball.

What you’ll need

Section titled “What you’ll need”
  • A project with a completed audit. Page Explorer reads from the latest run’s crawl, so the page set matches what Crawled Pages shows.

What you’ll see

Section titled “What you’ll see”

The full page set with the same per-page fields as Crawled Pages, plus controls to narrow it.

ControlWhat it does
SearchMatch URLs by substring — type a path fragment like /products/ to isolate a section.
Status filterRestrict to a status class, such as 404s, 5xx errors, or redirects.
Indexability filterRestrict to indexable or non-indexable pages based on their robots directive and canonical.

Filters combine. Search /blog/ with the status filter set to 404 and you are looking at exactly the broken URLs in your blog, nothing else.

How to use it

Section titled “How to use it”

Start from the question. To audit a section, search its path prefix. To chase down server errors, filter to 5xx and read the URLs that surface. To check what is being held out of the index, filter to non-indexable and confirm every page in the result is meant to be there. Once you have isolated a page, inspect its status, canonical, and robots directive in place.

Page Explorer is for finding the right pages quickly; it does not score or remediate. When a filtered page turns out to be a real problem, the matching finding in Issues carries the evidence, the remediation, and the generated fix.

Next steps

Section titled “Next steps”