Most dashboards drown you in numbers, and the technical seo metrics that matter are usually buried under a dozen vanity charts. The job is not to track everything — it is to watch the handful of signals that tell you whether search engines can find, render, and trust your pages, then act before those signals turn into lost traffic.
This guide walks through the metrics worth a place on your dashboard, what a healthy number looks like, and where the common thresholds are softer than the tools imply. You will leave knowing which alerts deserve a Monday-morning fix and which are noise you can safely mute.
Crawlability: Can Bots Reach Your Pages?
Before a page can rank, Googlebot has to reach it. The first metric to watch is the ratio of crawled pages to submitted pages in Search Console. If you submitted 2,000 URLs in your sitemap and only 1,400 show as crawled, roughly 30 percent of your site is invisible to search — and that gap is where most technical problems hide.
Pair that with crawl stats: requests per day, average response time, and the share of crawls returning non-200 status codes. A response time drifting past 600 milliseconds tells you the server is slowing crawlers down, which shrinks how many pages get visited per session. On a small site this rarely bites. On a site with tens of thousands of URLs, crawl budget becomes a real constraint, and a slow server quietly starves your newest pages of attention.
Watch the trend, not the single reading. A one-day spike in average response time might be a deploy or a traffic surge. A steady climb over three weeks is a server that needs attention before it drags your crawl rate down with it. Set a baseline the first week you look, then compare against it rather than reacting to every daily wobble.
Indexation: How Many Pages Actually Made It In
Crawled is not the same as indexed. The indexation rate — indexed pages divided by pages you want indexed — is one of the most honest health checks you have. Aim for the number to track close to the count of genuinely valuable pages. If it is far lower, pages are getting excluded. If it is far higher, you are probably indexing junk: filtered category views, tag archives, or session-ID duplicates.
Search Console’s Page Indexing report groups the reasons: “Crawled — currently not indexed,” “Discovered — currently not indexed,” “Duplicate without user-selected canonical.” The first two often signal thin or low-value content rather than a technical fault. Do not chase 100 percent indexation as a goal. A lean, fully indexed 800 pages beats a bloated 8,000 where Google ignores three quarters of them.
Core Web Vitals and Field Data
Speed metrics are where people waste the most effort chasing perfect lab scores. What Google actually uses is field data — Largest Contentful Paint, Interaction to Next Paint, and Cumulative Layout Shift from real users in the Chrome UX Report. Lab tools like Lighthouse are useful for diagnosis, but they simulate one device on one connection and can disagree sharply with what your visitors experience.
The passing thresholds are concrete: LCP under 2.5 seconds, INP under 200 milliseconds, CLS under 0.1, measured at the 75th percentile. Hitting them is worth doing, but keep the impact honest — Core Web Vitals are a ranking factor, not a dominant one. A fast page with weak content still loses to a slightly slower page that answers the query better. Fix speed because it helps conversions and crawling; do not expect it to rescue thin pages.
Segment the field data by device, too. A site can pass on desktop and fail badly on mobile, and since most queries now happen on phones, the mobile numbers are the ones that carry weight. If your lab tools show green but the field data lags, trust the field data — it reflects real hardware, real networks, and the third-party scripts your tag manager loads that a clean test environment never sees.
HTTP Status Codes and Redirect Health
Broken links leak both crawl budget and link equity. Track the count of internal 404s and, just as important, the length of your redirect chains. A single 301 is fine. A chain of four hops — HTTP to HTTPS to non-www to a trailing-slash variant to the final URL — wastes crawler time and bleeds a little authority at every step.
- 404 count — trending up means broken internal links or removed pages still being linked.
- Redirect chain length — keep it to one hop wherever you can.
- 5xx errors — any sustained server errors are an emergency; they stop indexing cold.
- Soft 404s — pages returning 200 but showing empty or error content confuse both users and Google.
These are cheap to monitor and cheap to fix, which is exactly why they get neglected until a redesign multiplies them overnight.
Duplicate Content and Canonical Signals
Duplicate URLs dilute ranking signals across copies of the same page. The metric to watch is the count of pages where Google chose a different canonical than you did — visible in Search Console as “Duplicate, Google chose different canonical than user.” When that number climbs, your canonical tags, internal links, and sitemap are sending mixed messages.
Parameter-heavy sites suffer most. Faceted navigation can spin one product listing into hundreds of near-identical URLs, each competing with the others. Consolidating them with clean canonicals and consistent internal linking usually recovers more traffic than any single speed tweak, because it stops you from fighting yourself in the index.
Turning Metrics Into a Routine
Numbers only help if you check them on a schedule and know your baselines. A workable rhythm is a quick crawl-and-index review weekly, a full technical audit monthly, and an alert set for spikes in 5xx errors or sudden drops in indexed pages. The goal is to catch a problem when it affects 20 URLs, not after it has spread to 2,000.
Doing this by hand across several tools gets tedious fast, which is why many operators lean on a workspace that crawls the site, flags issues with real evidence — actual titles, URLs, and H1 text — and pulls Core Web Vitals field data in one view. SEO Rocket runs quick scans of around 25 pages and deep crawls verified past 900 pages, so the technical seo metrics that matter sit in one place instead of four browser tabs. Whatever setup you use, the discipline is the same: pick the few metrics that predict lost traffic, watch them consistently, and fix the small problems before they compound.
