Skip to content

Services Get found

the content is fine, the site is the problem

Technical SEO services, from the crawl up

from $200

Technical SEO services: crawling, indexing, canonicals, redirects, speed and structured data, fixed at the level Google actually reads. Not a crawler score.

What's included

  • Crawl and index audit against live Search Console data
  • robots.txt, noindex, and X-Robots-Tag conflicts resolved
  • Canonicals, duplicates, and parameter URLs sorted out
  • Redirect chains, 404s, and soft 404s cleaned up
  • Sitemaps rebuilt so they submit and validate cleanly
  • Structured data added where it earns something, not everywhere
  • Core Web Vitals faults identified and fixed or handed over with specifics

Price

What moves the number is how many page templates the site has, not how many pages. Twenty templates is twenty audits; two thousand pages on four templates is four.

See every service price

Most sites that are not ranking do not have a content problem. They have a site that Google struggles to crawl, cannot decide how to index, or reads differently from how a person reads it. That layer is invisible from the front end, which is why it goes unfixed for years.

Why Search Console comes before the crawler

Technical SEO is what I do all day, and Search Console is the primary tool rather than an afterthought. That distinction decides most of the outcome. A crawler tells you what is theoretically wrong with a page. Search Console tells you what Google actually did with it.

The two disagree constantly, and the disagreement is where the real faults are. A page can pass every crawler check and sit at “crawled, currently not indexed”. A page a crawler flags in red can be indexed and ranking fine. Working from the crawl alone produces a tidy list that changes nothing, which is why so many sites have had technical SEO done and are still broken.

So the method is to hold both up together: the crawl says what exists, Search Console says what Google made of it, and the work is in the gap.

What actually gets found

The recurring faults are unglamorous and expensive. A robots.txt rule blocking a directory somebody forgot about. A staging noindex that shipped to production. Two canonical systems fighting, so Google picks its own and it is the wrong one. Redirect chains four hops deep from three migrations ago. A sitemap listing URLs that 404, which quietly costs you trust on every URL in it.

None of those are visible from the front end of the site. All of them are visible in an afternoon if you look in the right place.

What you get back

Not a 300 item audit PDF. A short list of faults ordered by what they are costing you, the ones I fixed, and the ones you need a developer for, written specifically enough to hand over. Every fix goes back through Search Console and gets watched until the status changes, because a fix nobody verified is not a fix.

Where to start instead

If you want the diagnosis before the work, the SEO audit is that, on its own. If you already know which URLs are missing from Google, indexing is the faster and cheaper route.

The checks themselves are not a secret. The technical SEO audit checklist is the whole list, in fix-first order, with what a failure looks like on each one. Run it yourself if you would rather not hire anyone.

If you are working out whether the problem is the site or what is on it, on-page SEO vs technical SEO has the test that sorts any task into the right pile, and technical SEO vs content SEO covers how to split a budget between the two.

Tell me the domain and I will say what is actually wrong with it.

  1. step 1 · crawl and pullI crawl the site and pull the same period from Search Console, so the crawl shows what exists and GSC shows what Google made of it. Faults live in the gap between the two.
  2. step 2 · fix in priority orderBlocking faults first, the ones stopping pages from being indexed at all. Then the ones costing rankings. Then the ones that are only untidy. You get told which is which.
  3. step 3 · resubmit and watchFixed URLs go back through Search Console and get tracked until the status changes. A fix nobody verified is not a fix.

before you ask

Common questions.

How is technical SEO different from the indexing service?

Indexing is the narrow job: get specific URLs into Google and prove it per URL. Technical SEO is the wider one, covering why they were not getting in and what else on the site is losing rankings. If you already know which URLs are missing, start with indexing.

Do you need access to my site to do this?

Search Console access is essential, because it is the only honest record of what Google did with your pages. Site or hosting access makes fixes faster, but if you would rather implement yourself I write the changes up file by file and check the result afterwards.

Will you break anything?

Changes go in one group at a time, with what changed written down, so anything can be reversed. On sites where a mistake is expensive I write the change up and hand it to your developer instead of applying it myself.

Is this a one-off job or something ongoing?

The bulk of it is one-off, and that is the honest answer even though a retainer would suit me better. A backlog of redirect chains, canonical conflicts and a broken sitemap gets fixed once and stays fixed. What comes back is what the site keeps generating: a new plugin adding parameter URLs, a migration re-breaking redirects, a theme update dropping the canonical tag. That is upkeep rather than technical SEO, and it belongs on a maintenance plan or nowhere.

My last agency already did technical SEO. Why is the site still broken?

Usually because what they delivered was a crawler report rather than a set of changes. A tool flags what is theoretically wrong on the page; it cannot see what Google decided about that URL, so the list gets worked through, every row turns green, and the pages are still not indexed. The other common version is real fixes that were never verified afterwards, so nobody noticed the sitemap still returned an error or the noindex was reapplied on the next deploy. Both are checkable in an hour against Search Console.

Everything else I run.