The short answer
Technical SEO is the work of making a site easy for search engines to crawl, index and render, and fast enough for people to use. It covers crawl budget, indexation, site speed, structured data and JavaScript rendering. Most stalled SEO campaigns are stuck here rather than on content.
What the work covers
- A full crawl, read against Search Console and your server logs
- Indexation cleanup, so the pages you want indexed are, and the rest aren't
- Speed and Core Web Vitals work on the template, not just image compression
- Rendering checks, so what a crawler sees matches what a person sees
- Redirect, canonical and internal linking repairs
- The fixes themselves, deployed by our developers on staging first
Crawled, indexed and ranking are three different things
Half the confusion in SEO starts here. A page has to be crawled before it can be indexed, and indexed before it can rank. Owners treat all three as one thing, then write more content to fix a problem that was never about content.
Crawled means Googlebot requested the URL. That's all it means.
Indexed means Google fetched the page, rendered it and judged it worth storing. Plenty of crawled pages never get here.
Ranking means the indexed page is competing for queries. A page can sit in the index for months and rank for nothing.
How to tell which stage you're stuck at.
Run URL Inspection on the page and read the page indexing report in Search Console. It says it plainly. "Discovered, currently not indexed" means Google knows the URL exists and hasn't bothered fetching it. "Crawled, currently not indexed" means it fetched the page and decided against storing it. "Duplicate without user selected canonical" means it folded the page into another. Three causes, three fixes, and treating them all as "SEO isn't working" is how a year goes by.
Discovered but not crawled is usually a priority problem. The site generates more URLs than it's worth crawling, often through filters and internal search, so the pages you care about sit behind the noise. The fix is fewer URLs, better internal links to what matters, and a sitemap that doesn't list junk.
Crawled but not indexed is a quality or duplication judgement. Thin pages, near identical pages, pages that exist because a template made them. The fix is to merge or remove, not to add 300 words to each.
Indexed but not ranking is the only one where content and links are the answer. Get here and the technical work is done.
Speed, argued honestly
Core Web Vitals are a real ranking signal and a small one. Anyone showing you a red score and implying it's why you're on page three is overstating it. Two sites with similar content and links, the faster wins the tie. That's about the size of it.
The better argument is the one nobody makes. Speed is a large conversion factor. On a phone on mobile data a slow page loses people before they see what you sell, and the ones you lose were only mildly interested, which is most of them. Fixing largest contentful paint on a booking page can pay for itself without moving a ranking.
The work is usually in the template rather than the images: fonts loading late, scripts blocking the render, a hosting stack doing too much per request. Server side problems go to the team running our server maintenance.
Why a site that looks fine can be nearly invisible
Open your site with JavaScript disabled. If the page comes back blank or missing its main content, you've found the problem.
Modern frameworks build the page in the browser after load. Google can render JavaScript, but rendering costs resources, so it happens in a second pass that lags behind the crawl. Other crawlers, including some AI systems, render far less. Content that only exists after a script runs might never be seen.
It bites hardest in navigation. Links built by JavaScript rather than written as anchor tags may not be followed, so whole sections go undiscovered while the pages look perfect to a human. Server side rendering fixes it, and the decision is far cheaper before a rebuild than after. If a rebuild or domain change is coming, read SEO migration first.
How we run it
We crawl and compare
Our crawl against Search Console against your logs. Where they disagree is where the problem lives.
We rank findings by impact
Not by severity colour. One misfiring canonical outranks forty missing alt tags.
Our developers make the fixes
On staging, tested, then deployed. Nothing comes back to you as homework.
We recrawl and confirm
Then watch indexation for a month to make sure it held.
Who this suits, and who it doesn't
It suits larger sites, stores with filters and parameters, sites built on frameworks, and anyone whose rankings stalled for no obvious reason.
It's a poor fit if the site is ten pages and healthy. Spend the money on content and links through SEO instead, and we'll say so after the audit.
Why clients stay
The fixes get done here.
Most technical audits end with a document the client forwards to a developer who half implements it. Ours end with deployed code, because the developers sit near whoever wrote the findings.
AWS certified, and we run servers.
When the problem is the hosting stack rather than the site, we fix that too instead of pointing at it.
"We had an audit done last year and nothing changed."
The usual story. An audit is worth only what gets implemented, so ask who implements it before you buy one.