Can Google actually crawl, render, and index your site?
Crawlability, indexation, Core Web Vitals, and the conflicts that only show up when the raw HTML and the rendered page disagree.
“Is Google able to crawl, render and index me?”
3.4s
180ms
0.04
Search Console’s own verdict, per URL
Technical SEO, as it looks in the app
A page can look perfect in your browser and still be invisible to Google.
Invisible failures
Nothing about a page that Google refuses to index looks broken when you load it yourself.
Pages you paid to build sit outside the index for months before anyone notices.
Search Console's own coverage verdict is joined per URL — Google's answer, not an inference.
Three ways to block yourself
Robots rules, redirect chains, and JavaScript rendering can each shut indexing down on their own.
You fix one, the next one is still holding the page back, and the symptom never changes.
All three are checked the way a crawler reads them, then cross-checked against each other.
Speed scores with no diagnosis
A red Core Web Vitals grade tells you the page is slow, not which part of it is slow.
Engineering time goes to the wrong bottleneck, and the number doesn't move.
LCP is broken into its sub-parts, with field data beside lab, so the culprit is named.
What's in Technical SEO
Every capability shipping in the product today — and what's still coming, named honestly rather than hidden.
On the roadmap — not shipping yet
4 steps, start to finish
The actual pipeline, not a black box — with what each step produces.
- 01Step 1 of 4
Check what's crawlable
Robots rules, sitemaps, and redirect chains are read the way a crawler reads them, not just parsed for syntax errors.
robots.txtSitemapsRedirect chainsUser-agent: *
Disallow: /services/ ← blocks 14 pages
Sitemap: /sitemap.xml ✓ 312 URLs
/old-pricing → /plans → /pricing
One rule, fourteen pages hidden
- 02Step 2 of 4
Pull real indexation verdicts
Search Console's own index coverage data is joined in, so you see Google's actual verdict on each page, not a guess.
Google's own verdictPer URLNot inferred/pricing — Indexed/services — Crawled, not indexed/blog/guide — Discovered, not crawled/about — IndexedJoined from Search Console
- 03Step 3 of 4
Measure Core Web Vitals, field and lab
Real-user field data and lab measurements are compared side by side, down to which part of LCP is slow.
Field + labINP, not FIDLCP sub-partsLCP3.4s└ render delay2.1sINP180msCLS0.04Field data, 28-day rolling
- 04Step 4 of 4
Flag conflicts that only show up on inspection
Canonical tags, mobile/desktop parity, and drift between crawls are checked against each other, not just against a rulebook.
Canonical conflictsMobile parityDrift since last crawlbefore<link rel="canonical" href="/blog/post?ref=nav">
after<link rel="canonical" href="/blog/post">
Self-referencing canonical, parameter stripped
Five disciplines, one loop. Technical SEO is step 1.
- 1Audit & Technical SEOYou are here
- 2On-Page Fixes
- 3Content & Keywords
- 4Off-Page & AI Search
- 5Reporting & Analytics
These jobs chain — most teams don’t stop at just one.
Questions people ask
Google Search Console, joined against your crawl — so what you see is Google's own verdict, not an estimate.
Both — field data (real Chrome users, via CrUX) and lab data are shown together, so you can tell a genuine problem from a one-off test run.
When a page's canonical tag disagrees with what's actually indexed, or two pages point at each other — a common, hard-to-spot cause of split rankings.
Rendering-diff checks (comparing raw HTML to the rendered DOM) are on the roadmap, named honestly as “soon” rather than claimed as live.
On demand today, with drift monitoring flagging what changed between runs; scheduled, automatic re-checks are covered under Site Audit's scheduled-audits roadmap item.
Try Technical SEO on your own site
Sign in to pick up your existing projects, or start a new one and see it run.