with Faisal TusherSEO · Foundation
Technical SEO
The building blocks
What goes into Technical SEO
Core Web Vitals Simulator
Adjust the field metrics to see how Google's thresholds classify a page.
How I do it
The process
- 1
Crawl
Full-site crawl to map status codes, depth, canonicals, directives and orphan pages.
- 2
Compare
Crawl vs sitemap vs indexed pages to find what's missing, extra or duplicated.
- 3
Prioritise
Score each issue by pages affected × business value × effort.
- 4
Ticket
Developer-ready tickets with examples, expected behaviour and acceptance tests.
- 5
Verify
Recrawl, request indexing, monitor coverage and CWV in Search Console.
Principles I follow
- Start with a crawl and compare it with the XML sitemap and Search Console's indexed pages — the gaps tell the story.
- Fix status-code problems (4xx, redirect chains, soft 404s) before anything cosmetic.
- Set one canonical per piece of content; consolidate thin or duplicate URLs.
- Prioritise Core Web Vitals fixes on templates, not individual pages, so one change improves thousands of URLs.
- Validate structured data and monitor rich-result reports after release.
Measurement
The numbers I watch
Indexed / submitted ratio
indexed URLs ÷ URLs in sitemap
Low ratio signals quality or crawl issues.
Crawl errors
4xx/5xx and redirect chains found per crawl.
Core Web Vitals pass rate
good URLs ÷ all URLs
Field data from the CrUX / Search Console report.
Average click depth
Important pages should sit within three clicks of home.
Tools I use
- SRSemrush
- SCGoogle Search Console
- G4Google Analytics (GA4)
- WPWordPress
What you get
- Technical audit with prioritised backlog
- Redirect map for migrations
- Schema implementation spec
- CWV improvement plan per template
Product pages not indexing
A catalogue has thousands of filter URLs competing with category pages.
Canonicalise filters to the parent category, block crawl traps, and resubmit a clean sitemap of canonical URLs only.
Illustrative exampleSlow mobile LCP
Hero images are served at desktop size and loaded lazily.
Serve responsive, modern-format hero images, preload the LCP image and stop lazy-loading above-the-fold media.
Illustrative exampleHow often should a technical audit run?
A full audit quarterly and after any migration or redesign; lightweight automated crawls weekly.
Does speed directly improve rankings?
Page experience is a ranking signal but rarely decisive alone — its bigger impact is on conversion rate and crawl efficiency.
Related
Continue exploring
- SEO AuditHow a full SEO audit is structured — technical, on-page, content, performance, mobile and structured data — with an interactive (simulated) SEO analysis demo.SEO Center
- On-Page SEOOn-page SEO methodology: search intent, title tags, meta descriptions, headings, URLs, internal linking and UX, with a live SERP snippet preview tool.SEO Center
- Google Search ConsoleUsing Google Search Console: performance reports, query analysis, index coverage, sitemaps, Core Web Vitals and CTR by position, with an interactive CTR curve.SEO Center
- E-commerce SEOE-commerce SEO for large catalogues: category architecture, product pages, faceted navigation, product schema and Merchant Center, with a schema generator.SEO Center
- International SEOInternational and multilingual SEO: market vs language targeting, URL structures, hreflang implementation and localisation — with an hreflang tag generator.SEO Center
