01 · The problem
Most technical SEO problems are invisible from the homepage.
The site loads, the pages look right, and traffic still flattens or quietly declines. When we look, it is usually one of these.
Pages that exist but are not indexed
Search Console shows hundreds of URLs as discovered or crawled but not indexed. Some are duplicates, some are thin, and some are exactly the pages you most want found, sitting behind a canonical tag, a noindex left over from staging, or an internal link structure that buries them.
Crawl budget spent on the wrong URLs
Filter combinations, tag archives, search result pages and parameter variations can multiply a site of a few hundred pages into tens of thousands of crawlable URLs. Search engines spend their time on those instead of on the pages that sell.
A relaunch that lost the old rankings
New design, new URLs, and the redirects were either missing, chained, or pointed everything at the homepage. The equity built up over years did not transfer, and nobody noticed until the monthly report.
Slow where it counts
Core Web Vitals failing on mobile, usually on the templates that matter most: product pages, service pages, landing pages. Heavy scripts, unoptimized images and layout shifts from late-loading elements.
02 · What we cover
Six areas, checked against your site, not a generic list.
Crawling
What search engines can reach
robots.txt, XML sitemaps, internal linking, orphan pages, parameter handling, and server log analysis where logs are available, so we know what is actually being crawled rather than what should be.
Indexing
What search engines choose to keep
Canonical tags, noindex directives, duplicate and near-duplicate content, pagination, and the Search Console coverage report read line by line rather than skimmed.
Architecture
How the site is organized
URL structure, click depth, category and hub pages, breadcrumbs, and whether the pages that matter commercially are the ones the site structure treats as important.
Structured data
What search engines understand
Organization, LocalBusiness, Product, Service, FAQ, Article and Breadcrumb markup where it genuinely applies, validated, free of duplicate or conflicting entities, and kept honest: no self-awarded review stars.
Performance
Core Web Vitals on real templates
LCP, INP and CLS measured on field data where it exists, then fixed at the source: image delivery, font loading, render-blocking scripts, third-party tags and caching.
Migrations
Relaunches without the traffic drop
URL mapping, one-to-one 301 redirects, preserved metadata, a pre-launch crawl of staging, and a post-launch check that the old URLs resolve where they should.
03 · How we work
Measure, rank, fix, verify.
Crawl and baseline
A full crawl of the site, Search Console and analytics data, and a Core Web Vitals baseline. We need to know what normal looks like before we change anything, otherwise there is no way to show the work did something. This step is also available on its own as an SEO audit.
A ranked list, not a spreadsheet of warnings
Every issue is ranked by how much it is likely to cost you and how much effort it takes to fix. Crawling tools flag hundreds of things. Most do not matter. The list you receive is short enough to act on.
RuleIf a fix will not change how search engines crawl, index or rank the site, it does not go on the list.
Fixes in the code
Template changes, redirect rules, sitemap and robots configuration, structured data, performance work. Done by us, or alongside your developer if you have one, and deployed through staging first where that exists.
Verification
Each fix is checked in the live page source and in Search Console, then re-measured a few weeks later once search engines have recrawled. You see the before and after, not just a list of tickets closed.
Technical SEO depends on accurate measurement, so it pairs naturally with our data tracking work. For sites being rebuilt, it is part of every web design project from the start.
Once the site is healthy, keeping it that way is part of our maintenance service: monthly checks of coverage, redirects and Core Web Vitals, so a plugin update or a new template does not quietly undo the work.
Common questions
Is technical SEO the same as an SEO audit?+
An audit is the first step, not the service. Most audits end with a spreadsheet of several hundred warnings and no indication of which ones matter. We produce a short, ranked list and then fix the items on it in the code, templates and server configuration, so the work ends with changes shipped rather than a document.
Do you do link building or write content?+
No. Technical SEO makes sure the pages you already have can be crawled, understood and served quickly. Content strategy and link acquisition are separate disciplines, and if you need them we will say so and point you to people who do them well.
Can you work on a site you did not build?+
Yes, most of this work is on sites built by someone else. We need Search Console access, read access to analytics, and a way to deploy changes, whether that is admin access, a staging environment or working alongside your developer.
How soon will we see results?+
Fixes to crawling and indexing are usually visible in Search Console within a few weeks, as pages are recrawled. Ranking changes take longer and depend on far more than technical health, so we will not promise positions. What we measure and report is whether the problems we fixed are gone.
Is my site platform a problem?+
Rarely on its own. WordPress, WooCommerce, headless builds and static sites can all be made technically sound. The issues we find usually come from plugins, themes, migrations and years of small changes, rather than the platform itself.
We are about to relaunch or migrate. When should we involve you?+
Before launch, ideally while the new URL structure is still being decided. Most traffic losses after a relaunch come from missing redirects, changed URLs and staging settings that leak into production, and all of those are far cheaper to prevent than to recover from.
