Pages exist but never rank
Good content, no impressions. Usually indexation, canonical or internal linking — not the writing.
Home/Technical SEO
Technical SEO that gets pages crawled and indexed
Most ranking problems are not writing problems. They are plumbing problems: pages blocked by robots.txt, duplicate URLs splitting signals, a sitemap full of redirects, or a template that ships three megabytes of JavaScript. Technical SEO is the work of removing those obstacles so the content you already have can rank.
Signs you have a technical problem
You do not need a full audit to suspect something is wrong. These are the usual symptoms.
Search Console shows coverage errors
Excluded pages, soft 404s, duplicate canonicals, or “crawled — currently not indexed” piling up.
Traffic dropped after a rebuild
Redirects missed, URLs changed, or the new template broke structured data and internal links.
Speed scores are red
Core Web Vitals failing on mobile, usually from unoptimised images, render-blocking scripts and layout shift.
What the audit covers
- Crawlability — robots.txt, meta robots, XML sitemaps, orphan pages and crawl depth.
- Indexation — which URLs are indexed, which are excluded, and whether that is intentional.
- Canonicals and duplicates — www/non-www, trailing slashes, parameters, pagination and near-duplicate pages.
- Redirects — chains, loops, 302s that should be 301s, and old URLs that lost their target.
- Site architecture — internal linking, breadcrumbs, hub pages and click depth from the home page.
- Structured data — Organization, LocalBusiness, Service, Article, FAQ and Breadcrumb markup that actually validates.
- Core Web Vitals — LCP, INP and CLS on mobile, with the specific element or script responsible.
- International and mobile — hreflang where needed, mobile parity and tap-target issues.
How the work runs
Access and baseline
Search Console and analytics access, a full crawl, and a record of current indexed pages and Core Web Vitals.
Prioritised list
Every finding is written up with impact, effort and risk. You see what I would fix first and why.
Fixes, not just slides
I implement what I can in the code or CMS, and give your developer exact instructions for the rest.
Verify and monitor
Re-crawl, request indexing, and check the fix in Search Console over the following weeks.
What I work with
Search Console and analytics
The source of truth for impressions, clicks, coverage and query data — not third-party estimates.
Crawlers and validators
Full-site crawls, log checks where available, Rich Results testing and structured-data validation.
Field data over lab scores
Real user metrics from the field decide priorities; lab tools are only a debugging aid.
Questions clients ask
How long does a technical audit take?
A small business site is usually one to three days. Larger sites with thousands of URLs take longer, and you get a clear scope before starting.
Do you implement the fixes or just report them?
Both. I fix what is in my control and hand over precise instructions — with code where useful — for anything that belongs to another developer.
Will technical SEO fix my rankings?
It removes obstacles, which is not the same as guaranteeing positions. It is the part that has to be right before content and links can do their job.
Do you need access to my Search Console?
I need read access, and I set it up so the property stays yours. You can remove access at any time.
Can you work with my existing developer?
Yes. Most of this work is collaborative: I identify and prioritise, they implement, I verify.
Send me the site and the symptoms
A short message with the URL, what changed and what Search Console is showing is enough to start. You get an honest read on whether a technical fix is the right next step.