Performance, Security & Care

Technical SEO

Technical SEO is the part of search that is genuinely an engineering discipline: can a crawler reach your pages, does it get a clean response, does it understand what it found, and is the same content reachable at exactly one URL.

It is not content strategy and it is not link building. What it does is remove the obstacles that stop good content from ranking, and there is no amount of content investment that compensates for a site that returns soft 404s or serves four URLs for every page.

What is included

The work itself

Crawl and index audit

A full crawl compared against Search Console coverage data, identifying orphan pages, crawl traps, wasted crawl budget and anything indexed that should not be.

Duplication and canonicals

Correct canonical tags, consistent trailing slashes and casing, parameter handling, and one preferred protocol and hostname enforced by redirect.

Site architecture

Internal linking and URL structure that makes hierarchy obvious to both crawlers and people, with breadcrumbs backed by structured data.

Structured data

Valid JSON-LD for the types that genuinely apply. Article, BreadcrumbList, FAQPage, Person, Organization, implemented to match visible content, which is what the guidelines require.

Sitemaps and robots

An XML sitemap containing only canonical, indexable URLs, and a robots.txt that blocks what should be blocked without accidentally blocking assets the renderer needs.

Redirects and migrations

Redirect mapping with correct status codes, avoiding chains and loops, and preserving equity through restructures.

JavaScript SEO

Making sure content in a React or Vue application is actually in the rendered HTML, through prerendering or server rendering rather than hoping the crawler executes everything.

International and metadata

hreflang where multiple regions or languages exist, plus titles and descriptions written to be accurate rather than keyword-stuffed.

How I work on it

Process

Adjusted to the job, but this is the shape it usually takes.

  1. Crawl and compare

    What the site exposes versus what search engines have actually indexed. The gap between those two is the work.

  2. Prioritise by traffic at risk

    Issues affecting revenue-generating pages first. Not every warning in an audit tool is worth acting on.

  3. Fix and validate

    Changes verified with live tests and re-crawls, not assumed from the code change.

  4. Monitor

    Search Console watched for several weeks after, because indexing effects are delayed and some regressions only surface later.

Questions

Things people ask

No, and anyone promising that is selling something. Technical work removes obstacles. It makes a site eligible to rank for what it deserves. Ranking still depends on content that answers the query better than the alternatives, and on a site people have reason to link to.

Indexing changes can appear within days for a small site; consolidation after a redirect or canonical fix often takes several weeks. Anything promising results in a fixed number of days is not describing how crawling works.

Not directly. What it does is make eligibility for rich results possible, which affects how your listing looks and how often it is clicked. It must describe content that is actually visible on the page, marking up content users cannot see is a guidelines violation.

Need help with technical seo?

Tell me the situation and what you have already tried. I read the code and the server before quoting anything.

Get in touch