Skip to main content

Contact

What are you interested in?

Back to Glossary (T)
Glossary · T

Technical SEO.

Technical SEO ensures that search engines can crawl, render, understand and index a website without problems. It includes loading time, clean status codes and redirects, robots.txt and the XML sitemap, canonical tags, mobile display, structured data and an architecture without dead ends.

Illustration of "Technical SEO": Document "Technical check" Technical checkHTTPSrobots.txt + SitemapNo internal 404sCanonical TagsCore Web Vitals3 redirect chains

Technical SEO — Explained in Detail

Technical SEO is the foundation on which content can rank at all. The best text is useless if Google cannot find the page, cannot render it or classifies it as a duplicate of another page. Technical SEO therefore deals with how a crawler such as Googlebot experiences a website: which pages are reachable, which status codes they return, how quickly they load, and which version of a page is the authoritative one?

Typical building blocks are the robots.txt, which controls which areas may be crawled, the XML sitemap as a directory of the important URLs, the canonical tag against duplicates, 301 redirects for changed addresses, HTTPS, hreflang for multilingual sites and loading time, measured by the Core Web Vitals. Then there is the question of whether content is in the HTML or only loaded later via JavaScript, which can make crawling harder.

With the rise of AI search systems, technical SEO has gained an additional layer. Many AI crawlers do not execute JavaScript and only see what is in the delivered HTML. A website that renders its content on the server (server-side rendering) is readable for these systems; a pure client-side app often is not. Today it also includes the deliberate decision about which AI crawlers are allowed in the robots.txt.

For most SME websites, technical SEO is not an ongoing project, but it is mandatory with every relaunch, every new page structure and every change of CMS. Many ranking drops that occur after a relaunch have technical causes: missing redirects, noindex directives set by mistake or a staging environment that was publicly indexed.

The most common technical errors on SME websites

In practice the same patterns keep occurring: several reachable versions of the home page (with and without www, with and without a trailing slash), old URLs that return 404 after a relaunch, images at full camera size that ruin loading time, pages without an incoming internal link, a sitemap with redirected or deleted addresses, and form thank-you pages that end up in the Google index.

None of these errors is dramatic on its own, but together they cost crawl capacity, dilute signals and lead Google to rank the wrong page. A structured pass with Search Console, a crawler and PageSpeed Insights finds most of them within a few hours.

Example: relaunching a fiduciary firm's website

A fiduciary and accounting firm in Winterthur has its website rebuilt. The old addresses were /index.php?id=12, the new ones /steuererklaerung. Without redirects, the new website loses all the signals of the old pages, and visitors from old Google results land on an error page. Technical SEO here means: capture all old URLs (sitemap and crawl), redirect each one with a 301 to the new page with matching content, submit the new sitemap in Search Console and monitor indexing during the first few weeks.

The whole process is described in the entry on website relaunches. If you want the technical state of your website checked, you will find it in the website audit from CHF 1,500; the free SEO check gives a quick initial assessment.

Related Page

Indexing

Frequently Asked Questions About Technical SEO

Crawling and indexing (robots.txt, sitemap, noindex), status codes and redirects, canonical tags, loading time and Core Web Vitals, mobile display, HTTPS, hreflang for multilingual sites, structured data and the question of whether content is in the HTML without JavaScript.

Especially then. A new website lays the foundation for everything that follows. Errors in the structure, redirects or indexing are easier to avoid before going live than to repair later.

A first look is possible with Google Search Console (the page indexing report), PageSpeed Insights and a crawler such as Screaming Frog. For a complete assessment with priorities, a structured audit is recommended.

Ready for Your Project?

Apply this knowledge to your website — DLM Digital will help you.