Check group 01
Links and redirects
Redirect chains and loops, broken internal links, broken external links, and pages that return an error while still appearing in search.
Instruments · Page Experience
What’s broken on your pages, and which of it still gets search traffic.
A 404 is a bug. A 404 that still took 1,240 impressions in the last 28 days is a different problem, and most technical crawlers report both the same way.
Page Experience runs three boards over a site: Technical Health, Index Coverage and Speed & Vitals. Technical Health findings carry the search traffic that page still gets, so you can sort the queue by the impressions involved rather than by a severity label.
technical health open Δ run
Broken internal links 24 +3
404s still getting traffic 7 0
Redirect chains 11 -4
Canonical mismatches 3 0
/old-stoves-guide 404
1,240 impressions last 28 days
01 · Technical Health
Twelve checks, run against your crawl and Search Console together.
Most technical audits stop at what a crawler can see. Combining the crawl with search performance separates a dead page nobody visits from a dead page people are still finding in search.
Each finding is labeled with who it’s for, a developer or the content team, and roughly how long it takes to put right.
Check group 02
Conflicting indexing signals
Canonical mismatches, indexability conflicts, duplicate URL variants, exact duplicate content, and hreflang tags with no return tag.
Check group 03
Reach and response time
Sitemap rot, money pages with too few internal links pointing at them, and slow server response times measured during the crawl.
finding broken internal link
on /guides/camping-stoves
to /reviews/rocket-2 404
fix by developer · copy-paste
02 · Index Coverage
Ask Google, rather than guess.
Whether a page is indexed isn’t something a crawler can work out. Searchscope asks Google directly through the URL Inspection API and records the verdict.
It distinguishes twelve verdicts, including crawled but not indexed, found but not crawled, excluded by noindex, duplicate, and unknown to Google.
01
Uncertain pages are checked first
Searchscope checks those pages first: the ones that can be indexed but are getting no impressions. That’s where an unexpected verdict changes what you do next.
02
It stays under Google’s daily limit
Google allows 2,000 inspections a day on a property. The automatic run stops at 1,800 and keeps 200 back, so you can still check a page yourself when something comes up.
03
Rechecked on a schedule
The first run starts after a crawl finishes, then runs nightly. A page that isn’t indexed is rechecked at most once every two weeks.
03 · Speed & Vitals
Core Web Vitals, measured by Google’s own tool.
Point an audit at one page, a section, or the whole crawled site. Google PageSpeed Insights measures each page and the results appear here. You get the three Core Web Vitals, the four Lighthouse scores for performance, accessibility, best practices and SEO, and every failing check with what to do about it.
01
Lab and field, kept apart
Lighthouse numbers from Google’s test device, and field data from real Chrome users where enough of them exist. The page shows which is which rather than blending them into one score.
02
Which pages, and which elements
Each failing check lists the pages it affects and the elements responsible, with the fix text Lighthouse itself provides.
03
Trend across audits
Audits are kept, so you can see the trend as a chart. Days when you marked a change as applied are shown on it.
04 · The limits
A check that hasn’t run isn’t a pass.
The quickest way to lose trust in a technical tool is a green check that turns out to mean nothing was measured. Four things are stated rather than smoothed over.
01
Unmeasured isn’t clean
A check that hasn’t run yet is shown as not run. It’s never shown as a zero, and the board above it won’t show an all-clear while it’s outstanding.
02
External links are a sample
Links out to other sites are tested in a sample, up to 100 per crawl, and that limit is shown on the finding itself, not in a footnote.
03
Server response isn’t a vital
The slow-response finding is server response time measured during the crawl. It’s labeled as that, not presented as a Core Web Vital.
04
Stale crawls are labeled
Once the crawl behind a set of findings is more than 30 days old, the board shows its age and suggests a fresh crawl.
Join the beta program
Find the broken pages that still get traffic.
Connect a site and the first Technical Health run starts after the crawl finishes, and Index Coverage starts with it.