Technical SEO: what really blocks your site in search engines
Technical SEO covers the work that lets search engines crawl, understand and index a site. On its own it sells no product, but it sets the ceiling for everything else: excellent content on a poorly crawled site does not rank, and the budget that produced it is wasted.
- Technical SEO is a condition of entry, not a growth lever. You fix it once, then you monitor it.
- The top priority is indexing. A page absent from the index cannot be measured, cannot be tested, does not exist.
- Web performance indicators matter most when they are poor. Improving them beyond the threshold returns little.
- On a large catalogue, the real technical issue is not speed, it is the number of URLs generated.
- It is a one-time expense that unlocks a recurring one. Paid in the wrong order, it is paid twice.
On this page
Technical SEO
Technical SEO is the set of work that makes a site crawlable, understandable and indexable by search engines. It covers crawler access to pages, loading speed, visual stability, the handling of errors and redirects, canonical tags and structured data. It sets the effectiveness of content without ever replacing it.
Indexing comes before everything else
For an executive team, this work is a piece of factory compliance. It sells no product, no one notices it when it is done, and nothing comes off the line when it is not. Its budget particularity is that it is one-time: you fix it, then you monitor it. Committing a content or advertising budget before it is fixed amounts to paying twice for the same result.
If you have already invested in content without seeing any movement, the cause is here in one case out of three, and it can be checked in an hour.
It is the least spectacular part of technical SEO and by far the most profitable. Before discussing milliseconds, you need to know how many of your important pages are actually in Google's index.
The question is settled in the Search Console indexing report. Three situations recur, and they have nothing to do with one another.
| What the report says | What it means | What to do |
|---|---|---|
| Discovered, currently not indexed | Google knows the URL but has not crawled it yet | Often a matter of priority: strengthen internal linking and the perceived value of the site |
| Crawled, currently not indexed | Google read it and decided not to keep it | Check for duplication and real added value |
| Blocked by robots.txt | Crawling is disallowed, often by mistake | Check the rule, it is frequently too broad |
| Excluded by the noindex tag | An explicit instruction not to index | Confirm it is intentional, often a leftover from development |
| Alternate page with proper canonical tag | Google chose another version as the reference | Check that this choice matches yours |
The noindex tag inherited from a staging environment is the most frequent incident after a launch. An entire site can vanish from the index for weeks without any alert firing, because nothing is broken from the visitor's point of view. Sales from search stop, and no one knows why before the monthly report. The real cost of that silence is the month of revenue lost before the diagnosis.
On a large catalogue, the trade-off is made on expected revenue rather than technical severity, a method detailed in our article on site speed for a large catalogue.
What to check before committing a visibility budget
It is a one-time expense that governs a recurring one. As long as it is not fixed, any content or advertising budget works under an invisible ceiling. The check that matters most takes under an hour and costs nothing: knowing how many of your pages that sell are in Google's index today.
- How many of our commercial pages are indexed, and how many should be?
- Which pages did Google see and decide not to keep, and why?
- Are there any blocking instructions left over from a launch or a staging environment?
- Are our three performance measurements poor, adequate or excellent, and which one do we tackle first?
- How many days of work before that ceiling is lifted?
The useful answer gives a number of indexed pages, a number of missing pages and an order. A hollow answer talks about technical optimization, a score obtained from a measurement tool, or proposes rebuilding everything.
Whether your site is under a technical ceiling, and what it is costing you in the meantime, can be checked in a single meeting. A 90-minute consultation settles it, with a written summary your team or your provider can execute.
The performance indicators, weighted correctly
This is the section where the most money is spent for the least result, because the thresholds are easy to measure and easy to sell.
Three measurements sum up the loading experience of a page. They carry technical names but describe simple things, and they have a direct effect on two line items: the site's conversion rate and the cost of your advertising clicks, which Google adjusts according to the quality of the landing page.
The display time of the largest element
How long before the visitor sees the main element of the page, usually an image or a heading. The recommended threshold is 2.5 seconds. It is the measurement that matters most, because it corresponds to the impression of slowness.
Cumulative visual shift
The amount of movement the page undergoes while it loads. A button that shifts at the moment you tap it is the typical symptom. The threshold is 0.1, and the usual culprits are images without declared dimensions and banners inserted after the fact.
Responsiveness to interaction
The delay between the visitor's gesture and the page's visible response. The threshold is 200 milliseconds. Overruns almost always come from an excess of third-party scripts run at load time.
Going from poor to adequate on these three measurements has a real effect. Going from adequate to excellent has little. Every dollar invested to gain three tenths of a second on a page that already meets the threshold is almost always better spent elsewhere.
Errors, redirects and chains
404 errors do not penalize a site in themselves. A deleted page that returns a 404 is normal and expected behaviour. The problem appears elsewhere.
The 404s that matter
The ones internal links point to, and the ones that still receive visits or external links. The first waste crawling and internal authority. The second lose visitors and link equity. The rest can stay as they are.
Redirect chains
A URL that redirects to a second, which redirects to a third, wastes crawl time and part of the signal. After several hops, search engines sometimes stop following. On a site that has been through two or three redesigns, these chains pile up without anyone seeing them.
The soft redirect
Redirecting fifty deleted pages to the home page is the most common reflex and one of the most useless. Google treats these redirects as disguised 404s. A redirect is worth something when the destination page answers the same intent as the origin page.
| Case | Right response |
|---|---|
| Page merged into another | 301 redirect to the absorbing page |
| Page deleted, topic covered elsewhere | 301 redirect to the equivalent page |
| Page deleted, no equivalent | 410 status, no redirect |
| Page temporarily removed | 503 status with a return date |
| Misspelled URL in a link | Fix the link, do not add a redirect |
What stays in-house is the business decision behind every technical trade-off: which product families deserve to be indexed, which are there only for customer service, which pages can disappear with no effect on sales. A provider who decides this alone gets it wrong, because the answer depends on your margins and not on the structure of the site. What gets delegated is the full execution: reading crawl reports, managing redirects, structured data and continuous monitoring call for a daily practice that no non-technical in-house team maintains.
What changes on a large catalogue
This is where the technical budget becomes profitable, because a single fix applies to thousands of listings that each carry sales.
On a thirty-page site, technical SEO comes down to speed and a few tags. On a catalogue of several thousand products, the subject changes nature entirely.
The problem is no longer the slowness of a page, it is the number of URLs the site generates. Each combination of filters creates a distinct URL, and the total quickly exceeds the number of real products. Search engines then spend most of their crawling on pages with no commercial value, while the new listings wait.
It is architecture work, not optimization. It consists of deciding, URL family by URL family, what deserves to be indexed, what deserves a canonical tag, what deserves a noindex tag and what deserves to be blocked. The detail of this method is developed in our article on crawl budget and faceted navigation.
Where to start
The order decides the return on the budget. An indexing fix brings in visits as soon as the page is recrawled, an optimization of tenths of a second on a page that already meets the threshold brings in none.
This sequence settles most situations, and it saves the time of an audit that treats everything at the same level.
| Rank | Check | Effort |
|---|---|---|
| 1 | Are the important pages indexed? | Low |
| 2 | Is a noindex tag or a robots rule blocking by mistake? | Low |
| 3 | Do internal links point to live pages? | Medium |
| 4 | Are the performance indicators below the thresholds? | Medium to high |
| 5 | Are the redirect chains cleared? | Medium |
| 6 | Is the structured data valid? | Low |
| 7 | Is the number of URLs generated under control? | High, large sites only |
Technical SEO does not win rankings. It removes the reasons for not winning them.
Falia analysis gridA quick check on your site
The place of the technical layer within SEO as a whole is described in our article on what SEO is. The execution side is covered on the SEO agency page, and infrastructure questions on WordPress hosting.
Position gaps between mobile and desktop have their own causes, set out in position gaps between mobile and desktop.
Already running a marketing team? See how we plug in as reinforcement on organic search.
Frequently asked questions about technical SEO
What is technical SEO?
It is the set of work that makes a site crawlable, understandable and indexable by search engines. It covers crawler access, loading speed, visual stability, errors, redirects, canonical tags and structured data. It sets the effectiveness of content without replacing it.
Do 404 errors hurt SEO?
Not in themselves. A deleted page that returns a 404 is normal behaviour. The 404s that matter are the ones internal links point to, which waste crawling, and the ones that still receive visits or external links.
Should you redirect deleted pages to the home page?
No. Google treats these redirects as disguised 404s. A redirect only has value if the destination page answers the same intent as the origin page. With no equivalent, a 410 status is preferable.
What performance thresholds should you aim for?
The largest visible element displayed in under 2.5 seconds, cumulative visual shift under 0.1, and responsiveness to interaction under 200 milliseconds. Going from poor to adequate has a real effect, going from adequate to excellent has little.
Why are my pages not indexed?
The most frequent causes are a noindex tag inherited from a staging environment, a robots.txt rule that is too broad, added value judged insufficient by Google, or a canonical tag that points to another page as the reference version.
Is a technical audit necessary every year?
Rarely. Technical SEO is fixed once then monitored. A new audit is justified after a redesign, a migration, a change of platform, or when a drop in indexing is observed in Search Console.
- Google Search Central, Core Web Vitals, accessed July 2026.
- Google Search Central, Introduction to robots.txt, accessed July 2026.
- Google Search Central, Redirects and Google Search, accessed July 2026.
- Google Search Central, Large site owner's guide to managing your crawl budget, accessed July 2026.

Geneviève puts the strategy for your engagement into action. She leads all our web development projects: Shopify, WordPress and the new ways of building a site with AI. She manages our team of developers and translates your business needs into technical language. She runs your organic search (SEO), your visibility in AI answers (GEO) and your site's conversion rate optimization (CRO). Her work is at the heart of three goals: Attract customers with SEO and AI, Improve your site's conversion, and Strengthen your visibility in AI answers. With Gabriel, she also builds the landing pages for your advertising campaigns. She writes mainly about SEO, AI visibility and web design.
About Falia →