Technical SEO and website technical optimization

A site can have good content and still be ignored by Google, because half of its pages aren't indexed, it's slow on mobile or the same page lives at three different URLs. Technical SEO finds problems like these and fixes them, together with your developers or instead of them.

Technical SEO
01

What is technical SEO?

Technical SEO is the part of SEO that isn't about the text, but about everything underneath it: how Google reaches your pages, what it sees when it opens them and which URL it treats as the main one. Content decides whether a page deserves a good position. The technical side decides whether Google gets to read it at all.

That's why we usually start here. There's no point writing new copy for pages that aren't in the index.

02

What a technical problem looks like in practice

It's rarely one big mistake. More often it's a series of small ones: old URLs left without redirects after a redesign, a store filter generating thousands of near-identical pages, a canonical tag pointing to the wrong address and a 3 MB hero image on the homepage.

None of these takes a site down on its own. Together they mean Google spends its time on pages that don't matter and sees the ones that sell late or not at all. In Search Console it shows up as a growing "Crawled - currently not indexed" list and impressions dropping for no obvious reason.

03

What we check

We start with the data Google already has about your site in Search Console, plus our own crawl of the whole site. We compare the HTML the server returns with what appears after JavaScript runs, and check status codes for every URL, the sitemap, canonical and hreflang tags, structured data and speed for real users, not just in a lab test.

On a small site this takes a few days. A store with tens of thousands of products takes longer, because most of the time goes into separating what matters from what is just noise.

04

Areas of technical SEO

Each area has its own page with the details. On your site they probably don't all matter equally.

Core Web Vitals and site speed

How fast the main content loads, how long a click takes to respond and whether the page jumps around while loading.

Site speed and Core Web Vitals

Crawling and indexing

Why some pages aren't in Google and how to stop the bot wasting time on URLs that don't matter.

Crawl and indexation

Structured data

Schema markup for products, articles, your business and breadcrumbs, so a search result shows more than a title.

Structured data and rich results

Multilingual sites

Hreflang, URL structure per language and country, and the errors that make Google show the wrong version.

International SEO

JavaScript sites

React, Vue and Angular applications whose content Google doesn't see, or sees late.

JavaScript SEO

Sitemaps and canonical tags

Which URLs Google should follow and which one is the main version when the same content exists in several places.

Sitemap and canonical tags

HTTPS and security

Certificates, mixed content, security headers and browser warnings that turn visitors away.

Website security and HTTPS checks

Redirects and 404 errors

Old URLs after a redesign, redirect chains and pages that return errors.

Redirects and 404 errors

05

When a technical check can't wait

Before and after any major change: a redesign, a move to another CMS, a new URL structure, a new language or merging two sites into one. Migrations are when traffic built over years is easiest to lose, and the mistakes only get noticed once rankings drop.

We also recommend a check when traffic is falling while the content hasn't changed, or when Search Console shows far fewer indexed pages than the site actually has.

06

Recommendations a developer can act on

A report with three hundred "warnings" from some tool helps nobody. We write every item as a task: which URL, what's wrong, what needs to change in the code or server settings and how to confirm it's fixed.

Because we build websites and applications ourselves, we know what each change costs. When your team doesn't have the time, we make the fixes ourselves, on WordPress, Ibexa, Symfony or whichever JavaScript framework you use.

07

How we work

  1. Access to Search Console and analytics, a full crawl and a speed check based on real users.
  2. A list of problems ranked by their effect on traffic and how hard they are to fix.
  3. Fixes, made by your team with our instructions or by us.
  4. A check after the changes and indexing monitoring over the following weeks, until Google has processed them.
FAQ

Questions about technical SEO

A fixed indexing issue or wrong canonical tag usually shows up within a few weeks, once Google recrawls the pages. Speed improvements appear in the Core Web Vitals report after 28 days, because Google reports an average for that period.

On-page SEO is about what's written on the page: titles, copy, meta descriptions and internal links. Technical SEO is about whether and how Google reaches that page and what it sees when it opens it.

Up to a point. But if a page isn't indexed, or Google sees an empty page instead of the text, the quality of the text doesn't matter. Technical work doesn't win rankings on its own, but it can block them.

The first check and fixes are a one-off project. After that the site keeps changing: new pages, plugins, marketing scripts. So we recommend a short check every few months and a mandatory one before any major change.

The first check and the fixes are paid as a one-off project, and the price depends on the size of the website and the number of issues. Before that, we take a free look at Search Console and send you a proposal.

Think your site has a technical problem?

Send us the URL. We'll look at Search Console and tell you whether something is holding the site back, before you pay for anything.

Request a free estimate →