Technical SEO
Technical SEO is the work of removing every reason a search engine or answer engine cannot read, understand or retrieve a site. It is unglamorous, it is first, and skipping it makes every later effort more expensive.
What technical SEO covers
Whether pages can be crawled, whether their content survives rendering, whether they end up indexed, how fast they respond, and whether their structure makes sense to a machine reading them. Everything downstream depends on those five answers.
The first thing to check
Whether the content exists in the raw HTML. Open a key page, choose View Source rather than Inspect, and search for the headline and first paragraph. Google renders JavaScript but does it in a deferred, resource-limited second pass, and most other crawlers do not render at all.
If they are not there, the page is built by JavaScript in the browser. Google will usually still render it. Most AI crawlers will not, because they do not execute JavaScript and they give up quickly. That single finding outranks every other technical issue on the site, because nothing else matters if the content is invisible.
What blocks indexing most often
Rarely anything exotic. The recurring causes are ordinary and usually accidental.
- A robots.txt written as a whitelist. Blocking everything then permitting a named few silently excludes every crawler nobody thought to list.
- A noindex left over from staging. Common after a launch, and it can sit undetected for months.
- Canonical tags pointing somewhere else. Often self-inflicted by a plugin, quietly telling engines to ignore the page.
- Pagination and faceted navigation generating thousands of near-identical URLs that consume crawl attention.
- Orphan pages with no internal links, which engines struggle to find and treat as unimportant.
Response time matters beyond user experience
Crawlers time out. A slow server does not just annoy visitors, it causes pages to be abandoned mid-fetch and re-crawled less often. Time to first byte under roughly 200 milliseconds is the target, and it is a hosting and architecture question more than a plugin question.
Core Web Vitals matter too, but they are a ranking refinement. Response time is closer to a gate.
Markup structure matters
Engines extract passages from structure. Headings used for visual size rather than document hierarchy produce a page that reads correctly to a person and incoherently to a parser. An H3 that follows an H1 with no H2 between them breaks the outline. A page with four H1s has no clear subject.
Semantic elements do similar work. Content inside a proper article or section element is easier to isolate than the same text inside nested generic containers.
What an engagement produces
| Stage | Output |
|---|---|
| Crawl and render analysis | What engines can actually reach and see, as distinct from what the site appears to contain |
| Index coverage review | What is indexed in Google and in Bing, and what is missing from either |
| Performance measurement | Response time and Core Web Vitals, measured on real pages rather than a homepage sample |
| Structure review | Heading hierarchy, internal linking, URL depth, structured data errors |
| Prioritised fix list | Ordered by impact and effort, with the work either done by us or specified for your developers |
Where this fits in the program
It is layer one of Generative Search Signals and the prerequisite for everything in the SEO program. Content work on a site that cannot be rendered is money spent on pages nobody will read. A full audit covers this alongside content and authority.
Frequently asked questions
Can you fix these things, or do you just report them?
Both, depending on access. We implement directly where we have it, and where the site is maintained by an internal team or another vendor we write specifications precise enough to hand over. What we do not do is deliver a list of problems and call it a deliverable.
Our developers say the site is fine. Who is right?
Often both. A site can be well built by software standards and still have search problems, because the requirements are different. Rendering strategy is the usual example: a single-page application is a legitimate engineering choice that happens to be invisible to non-rendering crawlers.
How long does technical work take to show results?
Faster than most search work. Fixing an indexing block can change things within days of a re-crawl. Rendering and performance improvements usually show within weeks. It is the closest thing to a quick win in the discipline, which is another reason it goes first.
See where you stand
We will review your current search visibility and show you what buyers find when they look for what you do.
Contact Us