Good content and clean design achieve little if search engines cannot load a website quickly, read it correctly and classify it properly. This is exactly where technical SEO comes in: it ensures that Google and other search engines can find, understand and deliver every page without friction. For small and medium-sized businesses the topic often feels abstract, yet it breaks down into a manageable list that you work through point by point. Load time plays a big role here: around 53 percent (Google) of visitors leave a mobile page again if it takes longer than three seconds to load. This article walks through the seven most important building blocks of technical SEO, from load time through mobile-first, indexing, structured data, sitemap and canonicals to HTTPS. At the end there is a practical checklist you can hold up against your own website, without deep developer knowledge.
Why the Technical Base Decides Visibility
Search engines work in three steps: they crawl a website, meaning they follow links and read pages. They index the content they find, storing it in their directory. And they rank that content when someone enters a matching search. Technical SEO ensures each of these steps runs smoothly. If the website is too slow, it is rated worse and finished loading less often. If it is hard for search engines to read or accidentally blocks crawling, it never even enters the index. And when identical content is reachable under several addresses, a page's strength is split across duplicates instead of working in a bundled way.
The great advantage of technical SEO is that it is predictable. Unlike content, whose effect is hard to forecast, technical points are clearly checkable: a page is either usable on mobile or not, a sitemap exists or is missing, a canonical tag is set or not. That is why the topic lends itself so well to a checklist. Working through the basics cleanly creates a foundation on which content and local visibility can take effect at all. How this foundation interacts with the content basics is shown in our article on SEO basics for businesses.
Briefly explained: crawl, index, rank
Block 1: Load Time and Core Web Vitals
Load time is the most visible technical factor because visitors feel it directly. Google groups the key measurements into the Core Web Vitals and uses them as one of many ranking factors (Google Search Central). Three values are central: the Largest Contentful Paint (LCP), the moment the largest visible content has loaded, with a target below 2.5 seconds. The Interaction to Next Paint (INP), which measures how quickly the page responds to input, with a target below 200 milliseconds. And the Cumulative Layout Shift (CLS), which captures how much the layout jumps while loading, with a target below 0.1.
The commercial lever is considerable: in a large-scale analysis, conversion in retail rose by up to 8 percent (Deloitte) for a load-time improvement of just 0.1 seconds. Typical levers are compressed and modern-format images, a lean weight of scripts and stylesheets, server-side caching and hosting with short response times. The technical background and concrete measures are covered in our article on Core Web Vitals.
- LCP below 2.5 seconds, INP below 200 milliseconds, CLS below 0.1
- Images compressed, in modern size and with fixed dimensions against layout jumps
- Unneeded scripts and fonts removed or loaded deferred
- Server-side caching and compression active
- Hosting with short server response time, ideally in Germany
Block 2: Mobile-First and Responsive Display
Google evaluates websites predominantly based on their mobile version, a process known as mobile-first indexing (Google Search Central). In practice this means: whatever is not visible or not usable on a smartphone hardly counts for the evaluation. A responsive website that adapts flexibly to any screen size is therefore a must, not a nice-to-have. This is not just about a layout that does not break, but about genuine usability: sufficiently large buttons, well-readable text without zooming and forms that can be filled in with a thumb.
A common mistake is that the mobile version shows less content than the desktop variant, for instance because text blocks or images are hidden. Because Google evaluates the mobile version, that content is then lost for visibility. It is better to provide the same content for all devices and only arrange it differently. What a well-thought-out mobile structure looks like is described in our article on mobile-first and responsive design.
- Website adapts flexibly to smartphone, tablet and desktop
- Buttons and links can be hit reliably with a thumb
- Text is readable without zooming, no horizontal scrolling needed
- Mobile version shows the same content as the desktop variant
- Forms and menus are easy to operate on a smartphone
Block 3: Steering Indexing and Crawling
For a page to rank, it must first enter the index. Two tools control this: the robots.txt file and the robots meta directive in the page head. The robots.txt sits in the root directory and tells search engines which areas they may crawl and which not. The robots meta directive with the value noindex instructs a single page not to be taken into the index. Both are powerful and among the most common sources of error: an accidental noindex on an important page or a too-strict robots.txt can make entire areas invisible.
A common trap
Indexing also includes a clean URL structure: readable, short addresses without cryptic parameters, a flat hierarchy and no dead ends through broken links or endless redirect chains. Google Search Console is the most important free tool here because it shows which pages are indexed, where errors occur and how often a website is crawled. If you want to secure visibility after a relaunch, our article on website relaunch mistakes covers the typical pitfalls.
Block 4: Structured Data for Better Display
Structured data is a machine-readable label that explains to a search engine what a page is about. Instead of just seeing text, Google then recognises, for instance, that a piece of information is an opening time, a rating, a product price or a frequently asked question. This is implemented via the Schema.org vocabulary, usually in the JSON-LD format, which sits invisibly in the source code. The benefit: pages with correct structured data can appear as so-called rich results, that is with enhanced displays such as star ratings or expandable questions (Google Search Central). This makes a result in the list more visible, even without a better rank.
For local businesses the LocalBusiness schema is particularly relevant, providing name, address, phone number and opening hours in a structured way. For FAQ sections the FAQPage schema is suitable, for articles the Article schema and for products the Product schema. It is important that the structured data describes the actually visible content and does not pretend anything that is not on the page. How structured data supports local findability is shown in our article on local SEO and the business profile.
- LocalBusiness schema with name, address and phone number for local businesses
- FAQPage schema for genuine question-and-answer sections
- Article or BlogPosting schema for blog posts
- Breadcrumb schema for navigation paths
- Structured data describes only actually visible content
Block 5: The XML Sitemap as a Signpost
An XML sitemap is a list of all important URLs of a website in a format search engines can read directly. It does not replace crawling but helps to find all relevant pages reliably, especially on larger websites or with freshly published content. The sitemap should only contain indexable pages, so no URLs blocked with noindex or pointing to another address via canonical. Once created, it is submitted in Google Search Console and made known through a reference in the robots.txt.
It is important to keep the sitemap current. In many systems and modern websites it is generated automatically and maintained with every change, so that deleted pages disappear and new ones are added automatically. An outdated sitemap that points to pages no longer existing sends contradictory signals and should be avoided. For most smaller websites a single sitemap is enough; very large websites split it into several files with an overarching index sitemap.
Block 6: Canonicals Against Duplicate Content
Duplicate content arises faster than many think: a page is reachable with and without www, with and without a trailing slash, via various parameters or via a print view. To search engines these look like several addresses with the same content, and the page's strength is split instead of working in a bundled way. The canonical tag solves the problem: it names the preferred, official address of a page in the page head. Search engines then consolidate the signals of the variants on this one address.
The principle with canonicals
Besides the canonical tag, clean redirects are important. A permanent address change is redirected via 301 so that the signals of the old address pass to the new one. Long redirect chains, where an address leads to the target through several intermediate steps, should be avoided because they cost load time and dilute signals. Likewise, internal links should point directly to the final address and not to a redirecting intermediate stop.
Block 7: HTTPS and Secure Delivery
HTTPS encrypts the connection between visitor and website and is standard today. Google uses HTTPS as a light ranking signal and browsers mark unencrypted pages as not secure, which costs trust (Google Search Central). A suitable certificate is available free through most hosts and can be renewed automatically. It is important that the entire website really runs over HTTPS and that all resources such as images, scripts and fonts are also loaded encrypted, otherwise so-called mixed content arises, which browsers flag.
Secure delivery includes the unencrypted variant redirecting permanently to HTTPS via 301, so that no one accidentally lands on an unsecured version. Those who want to raise security further add security headers that tell the browser how to handle the page. Security is therefore not only an SEO topic but also a trust topic. What a solid baseline level of protection looks like is described in our article on the basics of website security.
The Checklist at a Glance
The following overview sums up the seven building blocks with their typical priority. The priority is a guide from practice (Projekterfahrung) and can vary by website. Working through the points from top to bottom first covers the big levers and then refines the details.
| Building block | What to check | Priority |
|---|---|---|
| Load time | Core Web Vitals in the green range, lean pages | High |
| Mobile-first | Responsive, usable, same content as desktop | High |
| Indexing | robots.txt and noindex correct, clean URLs | High |
| HTTPS | Whole site encrypted, 301 to HTTPS | High |
| Canonicals | One official address, no duplicates | Medium |
| XML sitemap | Current, only indexable pages, submitted | Medium |
| Structured data | Schema matching the content, valid | Medium |
- Core Web Vitals measured and within the recommended range
- Website is responsive and fully usable on mobile
- Important pages are indexable, no accidental noindex
- URL structure is readable, flat and without dead ends
- Suitable structured data (Schema.org) is in place
- A current XML sitemap is created and submitted
- Canonical tags point to one official address each
- Website runs fully over HTTPS with a 301 redirect
Technical SEO is not a one-off project but a foundation you check regularly, especially after changes to the website. No single technical point lifts a website to the top, but every box ticked clears a possible brake out of the way. Keeping this base clean ensures that good content and local visibility can take effect at all. Which points make the biggest difference for your website is best judged on the actual site, not on a general rule. A sober technical check quickly shows where the biggest lever lies and which order brings the most in your case.