Technical SEO.So Google can see the site at all.
The best copy in the world is worth nothing if Google cannot read it, or if it takes seven seconds to load. Technical SEO is the part nobody sees, and the part without which the rest does not work.
What you get
Six areas we check and fix.
This is not a list from a tool. Every item is checked by hand, because tools flag things that are not problems and stay quiet about the ones that are.
Indexing
The first question is always whether the page is in the index at all, and only then where it sits.
- robots.txt and meta robots
- The sitemap and whether it is accurate
- Canonical tags and duplicates
- Crawl budget on large sites
- Pages burning budget for no reason
Speed and Core Web Vitals
LCP, INP and CLS by page template, on mobile before desktop.
- Image weight and format
- Fonts and render blocking
- Third-party scripts and tracking
- Caching and CDN
- Rendering on a real mobile device
Site structure
How many clicks it takes to reach the most important page, and where the authority leaks.
- Click depth to the key pages
- Internal linking and anchor text
- Pages with no internal link at all
- Pagination and filters
- Navigation and breadcrumbs
Errors and redirects
Redirect chains and dead URLs quietly eat authority for years.
- 4xx and 5xx errors
- Redirect chains and loops
- http and https mixed together
- Trailing slashes
- URLs with parameters
Structured data
Schema that earns rich results and helps AI search engines understand you too.
- Organization and LocalBusiness
- Product, Article and FAQ
- Breadcrumb
- Errors in the schema you already have
- Testing in the rich results tool
International and mobile
Hreflang and the mobile version - the two places where mistakes stay hidden longest.
- Hreflang tags and whether they point back
- Differences between the mobile and desktop version
- Interstitials and pop-ups
- Language and regional targeting
- AMP, if you still have it
How it runs
From finding to fix.
-
Week 1
Crawl and measure
Screaming Frog, Search Console and log files. We look at what Google sees, not what we think it sees.
-
Week 2
Prioritising
Every finding gets an impact and effort score. We fix what is worth the most, not what is easiest.
-
Weeks 3 - 6
Fixes
We do the work, or your team does it to our spec. Every change is verified once it is live.
-
After
Monitoring
One bad deploy undoes all of it. That is why a regular check follows the fixes.
Who this is for
Who it works for, and who it does not.
It makes sense if:
- Your traffic dropped with no obvious reason
- You have a large site or a store with thousands of pages
- You changed the site or the platform in the last year
- You have been publishing content for months and nothing moves
It does not make sense if:
- Your site has ten pages and runs fine - there is nothing here to fix
- The problem is the content, not the technical side, and Search Console already shows it
- There is nobody to implement the changes and you do not want us doing them
If the audit shows the technical side is not your problem, we will tell you where it is. A paid audit that says "this is all fine" is a useful answer too.
Frequently asked questions