Technical SEO Services — Fix the Foundations That Decide Whether You Rank at All

A full crawl, and a ranked list of what is actually costing you traffic.

I crawl the site the way a search engine does, cross-reference it against Search Console, and separate the issues that are genuinely suppressing rankings from the ones that only look alarming in a plugin.

• Full site crawl with rendering enabled
• Index coverage and exclusion reasons
• Status codes, redirects and broken links
• Duplicate, thin and orphaned URLs
• Prioritised fix list with effort and impact

Decide deliberately what Google sees — and what it never should.

Most sites either block something they need indexed or let thousands of parameter and filter URLs into the crawl. Both waste the attention Google is willing to give you.

• robots.txt rules reviewed line by line
• Noindex and canonical strategy per template
• Parameter and faceted URL handling
• Pagination and infinite-scroll handling
• Index coverage errors resolved and re-validated

Every page that matters should be a few clicks from the homepage.

Depth is a ranking problem. Pages buried five or six clicks down get crawled rarely and rank poorly, no matter how good they are. I restructure the paths so importance and reachability line up.

• Crawl-depth map of the whole site
• URL structure and folder hierarchy review
• Hub and category page structure
• Orphan pages found and linked
• Breadcrumbs and navigation consistency

Fix speed for the people actually visiting, not for a lab score.

I work from field data first — what real users on real devices experienced — and only then use lab tools to find the cause. A perfect Lighthouse score on a desktop fibre connection proves very little.

• Field Core Web Vitals by template and device
• LCP, INP and CLS causes identified
• Image, font and script loading fixes
• Render-blocking and third-party script review
• Re-measured after every deployment

One page, one URL, one canonical — consistently.

Trailing slashes, uppercase variants, HTTP and HTTPS, www and non-www, tracking parameters and print versions all quietly split the same page into several. Google then picks one, often not the one you wanted.

• Canonical tags audited across every template
• Protocol, www and trailing-slash consistency
• Tracking and session parameter handling
• Duplicate and near-duplicate consolidation
• hreflang review for multi-language sites

Move the site without dropping the rankings you already paid for.

Most traffic losses after a redesign come from redirects that were built at the last minute, or not at all. The mapping should exist before anything goes live, and be checked the hour it does.

• Full old-to-new URL redirect map
• Redirect chains and loops eliminated
• Pre-launch staging crawl and sign-off
• Launch-day and week-one monitoring
• Recovery plan if rankings do move

Tell search engines the truth about what exists and what matters.

A sitemap full of redirects, 404s and noindexed URLs teaches Google to trust it less. It should be a clean list of exactly the pages you want indexed, and nothing else.

• Sitemaps rebuilt to include only indexable URLs
• Split sitemaps by content type for diagnosis
• robots.txt cleaned and documented
• Submission and coverage monitoring in Search Console
• Bing Webmaster Tools set up in parallel

Make sure the content you can see is the content Google gets.

If your copy, links or metadata only appear after JavaScript runs, indexing becomes slower and less reliable. I compare the raw HTML with the rendered page and close the gap.

• Raw HTML versus rendered DOM comparison
• Links and content missing before render
• Client-side routing and history handling
• Lazy-loading that hides content from crawlers
• Server-side or static rendering recommendations

Schema that validates, matches the page, and keeps working.

Structured data is added at template level so it stays consistent, and it is monitored afterwards — because the most common problem is markup that was correct once and silently broke in a later release.

• Schema type chosen per template
• Organisation, breadcrumb and article markup
• Product, FAQ and review markup where valid
• Validation against Search Console enhancement reports
• Ongoing monitoring for new errors

See what Google actually crawls — not what you assume it crawls.

Server logs are the only place you can watch real bot behaviour. On large sites they usually reveal that most of the crawl is being spent on URLs nobody wants indexed.

• Bot hits by URL, template and status code
• Crawl frequency of your important pages
• Budget wasted on parameters and redirects
• Pages Google has never requested
• Fixes verified in the logs afterwards