Technical SEO is the foundation. If Google cannot crawl your page, the best content won’t help. If Core Web Vitals are red, you rank worse – no matter how good your texts are. If Schema.org is missing, you miss rich snippets and therefore clicks.
I’ll show you here what really matters: the three pillars, the concrete levers, and the most common mistakes I keep seeing in SME audits.
The three pillars
| Pillar | What it means | Why important |
|---|---|---|
| Crawlability | Google can find and read your pages | No crawling, no indexing |
| Indexability | Google stores your pages in the index | No index, no rankings |
| Performance | Pages load quickly, are stable and interactive | Core Web Vitals are ranking factors |
If one pillar wobbles, the entire visibility suffers. The good news: Most problems are solvable – often without developers.
Core Web Vitals: The three metrics
Since 2021, Core Web Vitals have been a ranking factor. Google measures three things:
1. Largest Contentful Paint (LCP) – Load time
What it measures: How quickly the largest visible content has loaded.
Target value: Under 2.5 seconds (75th percentile).
Most common causes:
- Images not compressed (5 MB instead of 200 KB)
- No lazy loading
- Slow hosting
- Render-blocking CSS/JS
In practice: Open PageSpeed Insights, enter your URL. If LCP is red, look at the largest element. Image? Compress with TinyPNG. Text? Check font loading (preload helps).
2. Interaction to Next Paint (INP) – Response time
What it measures: How quickly the page responds to clicks (replaced FID in March 2024).
Target value: Under 200 ms.
Most common causes:
- Too much JavaScript
- Long tasks (>50 ms)
- Third-party scripts
In practice: Chrome DevTools → Performance tab → Start recording → click around. Red tasks = problem. Third-party script? Load asynchronously (async/defer) or remove.
3. Cumulative Layout Shift (CLS) – Stability
What it measures: Whether elements jump during loading.
Target value: Under 0.1.
Most common causes:
- Images without
width/height - Embeds without reserved space
- Late-loading fonts
In practice: Check all <img> tags – set dimensions. Embeds: aspect-ratio in CSS. Fonts: font-display: swap + preload.
Why speed pays off
Human perception of waiting times follows clear patterns:
- 0.1 seconds: Feels instantaneous (Miller, 1968)
- 1 second: Flow of thought stays intact
- 10 seconds: Attention limit reached (Nielsen, 2020)
Biometric studies on digital delays back this up: Streaming delays over 4 seconds produce measurable physiological stress (heart rate +38 %, comparable to watching a horror movie; Ericsson ConsumerLab, 2016). Whether this translates 1:1 to website load times is not directly measured – but the psychological mechanisms (uncertainty, missing feedback) are identical.
The economic consequence: 53 % of mobile visits are abandoned if load time exceeds 3 seconds (Google/SOASTA, 2017). Deloitte (2019) documented in retail: 0.1 seconds faster = up to +8 % conversion.
What I see in audits: The same pattern again and again – the homepage loads in 1.8 seconds, but the services page with the hero image takes 6 seconds. Reason: 4 MB image, no lazy loading. That’s not a technical problem, it’s an organizational problem: Nobody compressed the images before launch.
Crawling & Indexing
Crawl Budget
Google has limited resources. Usually not a problem for SMEs with 50–500 pages – but there are traps:
- Duplicate content:
/page/and/page/?utm_source=... - Orphan pages: Pages without internal links
- Endless filters: E-commerce with thousands of combinations
- 404 errors: Wasting crawl budget
How to proceed: Google Search Console → Indexing → Pages → “Not indexed”. Which reasons?
| Reason | Meaning | Solution |
|---|---|---|
| “Page with redirect” | URL redirects elsewhere | Check if intentional |
| “Discovered – not indexed” | Google knows URL, hasn’t crawled | Add internal links |
| “Crawled – not indexed” | Google saw it, didn’t index | Check content (too thin?) |
| “404 error” | Page doesn’t exist | 301 redirect or 410 |
XML Sitemap
Lists all important URLs. Google uses it as a crawling aid.
Should be included:
- All pages that should rank
- Only 200-status URLs
- Canonical URLs
Should not be included:
- Noindex pages
- Pagination (only page 1)
- URLs with tracking parameters
First aid: Open yourdomain.com/sitemap.xml. Structured list? If not: plugin (WordPress: Yoast, Rank Math) or tool (Screaming Frog). Submit to GSC: Indexing → Sitemaps.
Robots.txt
Tells search engines what they may crawl.
Typical, safe rules:
User-agent: *
Disallow: /wp-admin/
Disallow: /?s=
Allow: /
Sitemap: https://yourdomain.com/sitemap.xml
First aid: Open yourdomain.com/robots.txt. Disallow: /? Remove immediately.
Schema.org: Rich Snippets
Schema.org helps Google understand your content. Used correctly: Rich snippets (stars, prices, FAQs).
Most important types for SMEs
| Type | Marks | Effect |
|---|---|---|
| Organization | Company | Knowledge panel |
| LocalBusiness | Address, opening hours | Local pack |
| Product | Products | Price snippets |
| FAQPage | FAQs | Expandable section |
In practice: Use Schema Markup Validator. Enter URL – which types exist? For WordPress: Rank Math generates JSON-LD automatically.
What I experienced: For a trade customer, clicks from search increased by 23 % after we added FAQPage schema. No ranking boost – just a better presentation in the SERPs.
Mobile-First
Since 2019, mobile-first indexing is standard. Google primarily evaluates the mobile version.
Most common problems:
- Text too small (< 12 px)
- Clickable elements too close (< 48 × 48 px)
- No
<meta name="viewport">
How to proceed: Chrome DevTools → Device Toolbar → “iPhone 12 Pro”. Everything readable? Buttons large enough? No horizontal scroll?
What does this actually achieve?
| Measure | Impact (study-based) | Time effort |
|---|---|---|
| Optimize Core Web Vitals | Up to +8 % conversion (Deloitte 2019) | 2–4 h |
| Fix crawl errors | More indexed pages | 1–2 h |
| Submit XML sitemap | Faster indexing | 15 min |
| Add Schema.org | +23 % CTR (own experience, trade customer) | 1–2 h |
| Mobile optimization | Avoid 53 % bounces > 3s (Google 2017) | 2–4 h |
When the basics are in place, but…
…you still have technical problems (JavaScript rendering, hreflang structures, complex redirects), you need specialized expertise.
The basics you can do yourself. Everything beyond that – server-side rendering, automated crawl monitoring, complex migrations – requires experience.
If the technical complexity is overwhelming, a technical SEO consultant makes sense. Not as a replacement for your understanding, but as an accelerator.
The SEO Short Analysis for €490 shows the five biggest technical levers – prioritized by effort and impact. Or the open calculation shows how every price is composed.
Checklist
- Core Web Vitals for mobile checked (PageSpeed Insights)
- Google Search Console: indexing errors fixed
- XML sitemap generated and submitted to GSC
- Schema.org added (Organization, LocalBusiness, FAQPage)
- Mobile version checked (responsive, readable, clickable)
- Duplicate content avoided (canonical URLs)
Sources
- Google Search Central: Core Web Vitals
- Google Search Central: Mobile-First Indexing
- Miller, R. B. (1968). Response Time in Man-Computer Conversational Transactions.
- Nielsen, J. (2020). Response Times: The 3 Important Limits. Nielsen Norman Group.
- Ericsson ConsumerLab (2016). The stress of streaming delays.
- Google/SOASTA (2017). The Need for Mobile Speed.
- Deloitte (2019). Milliseconds Make Millions.
- Schema.org: Full Vocabulary
Note: This article serves technical assessment and does not replace individual SEO auditing.