What does white-label technical SEO cover?
It covers every site-level reason a good page fails to rank or get quoted: whether bots can fetch it, whether the search engine chooses to store it, how fast it loads, how it renders and whether its markup tells the truth. The table maps each problem type to the symptom you will see, the fix and what your client receives.
A first audit sorts findings by impact and effort, so the repairs that unblock everything else go first.
| Problem type | Symptom | Fix | What the client sees |
|---|---|---|---|
| Crawlability | Pages missing from search, blocked or erroring URLs in crawl reports | Correct robots.txt rules, fix server errors and dead-end links | A list of pages search engines can now reach |
| Indexation | Pages crawled but not indexed, or duplicates indexed | Apply noindex correctly, merge duplicates, improve thin pages | Missing pages appearing in the index report |
| XML sitemaps | Sitemap lists redirected, blocked or deleted URLs | Rebuild it with indexable canonical URLs only and resubmit | A clean sitemap with a submitted status |
| Canonical tags | The wrong URL ranks, or parameter URLs compete | Set one canonical per page and point duplicates to it | Fewer duplicate URLs in search results |
| Redirects | Chains, loops, temporary redirects used by mistake, broken pages | Send each old URL to its closest page in one permanent step | A falling broken-page count |
| Speed and Core Web Vitals | Slow loads, jumping layouts, laggy taps in field data | Resize images, defer scripts, fix layout shifts, add caching | A before and after of the three Core Web Vitals |
| Mobile usability | Small text, crowded tap targets, content missing on phones | Responsive layout and the same content on mobile as desktop | A site that works on every phone |
| Structured data | Missing or invalid schema, or markup that contradicts the page | Valid JSON-LD that matches visible content | A clean validation report |
| JavaScript rendering | Raw HTML is thin and content only appears after scripts run | Server-side or pre-rendering, and real links in the HTML | Pages whose content shows in a rendered test |
| Log files | Bots spend visits on parameters and errors, not the pages that earn money | Fold or block wasteful URLs and fix internal links | A short note on where crawlers spend time |
| AI crawler access | AI bots blocked, challenged or served blank pages | Decide bot rules per vendor and make content visible in HTML | A note on which assistants can read the site |