Technical SEO for SMEs: The Non-Negotiables

Most SMEs think technical SEO is complicated, expensive, and best left to specialists. The reality: 80% of technical SEO is straightforward. The same issues appear on site after site. Fix them once, maintain them properly, and you’ve handled the foundation.

This guide covers what actually matters for small and medium businesses. No jargon. No theoretical best practices. Just the things that move rankings.

The Foundation: Crawlability and Indexability

Before worrying about keywords or content, search engines need to:

1. Find your pages (crawlability)
2. Add them to the index (indexability)
3. Understand what they’re about (content signals)

If any of these fail, nothing else matters. You could have perfect content on a page that Google can’t find.

Crawlability Checklist

• XML Sitemap: Does it exist? Is it submitted to Search Console? Is it up to date?
• Robots.txt: Are you accidentally blocking important pages?
• Internal linking: Can a crawler reach every important page within 3 clicks from the homepage?
• Orphan pages: Do any important pages have zero internal links pointing to them?

Indexability Checklist

• No accidental noindex: Check meta robots tags on key pages
• Canonical tags: Are they pointing to the right URLs?
• Duplicate content: Are multiple URLs serving the same content?
• Search Console coverage: What’s excluded and why?

Quick Check Search Google for site:yourdomain.com. The number of results should roughly match the number of pages you want indexed. If there’s a major discrepancy (way more or way fewer), you have an indexing problem to investigate.

Core Web Vitals: The Speed Metrics That Matter

Google measures three specific performance metrics:

Largest Contentful Paint (LCP)

Target: Under 2.5 seconds

How quickly does your main content appear? This is usually your hero image, heading, or primary content block.

Common fixes:

• Compress and properly size images
• Use modern image formats (WebP)
• Implement lazy loading for below-fold images
• Reduce server response time

Cumulative Layout Shift (CLS)

Target: Under 0.1

Does content jump around as the page loads? Nothing frustrates users more than clicking a button that moved because an ad loaded above it.

Common fixes:

• Set explicit dimensions on images and videos
• Reserve space for ads and embeds
• Avoid inserting content above existing content
• Use font-display: swap for custom fonts

Interaction to Next Paint (INP)

Target: Under 200 milliseconds

When someone clicks, taps, or types, how quickly does the page respond?

Common fixes:

• Reduce JavaScript execution time
• Break up long tasks
• Remove unused JavaScript
• Defer non-critical scripts

Mobile Experience

Google uses mobile-first indexing. Your mobile site is your site. Desktop is secondary.

Non-Negotiable Mobile Requirements

• Responsive design: Content adapts to screen size
• Readable text: No pinching to zoom required
• Tap targets: Buttons and links are at least 48px apart
• No horizontal scrolling: Everything fits the viewport
• Same content: Don’t hide important content on mobile

Test your pages on actual phones, not just browser dev tools. Load times and usability often differ from simulations.

HTTPS and Security

HTTPS is baseline. Non-negotiable. If your site still runs on HTTP:

1. Get an SSL certificate (free through Let’s Encrypt or your host)
2. Implement site-wide HTTPS
3. Redirect all HTTP URLs to HTTPS
4. Update internal links and resources
5. Update canonical tags and sitemap

Mixed content (HTTP resources on HTTPS pages) also breaks trust signals. Check for images, scripts, or stylesheets still loading over HTTP.

URL Structure

Good URLs are:

• Descriptive: /services/seo-audit not /page?id=47
• Concise: /contact not /get-in-touch-with-our-team-today
• Consistent: Pick a format and stick to it
• Lowercase: Avoid case sensitivity issues
• Hyphen-separated: /web-design not /webdesign or /web_design

Trailing Slashes

Pick one format (with or without trailing slash) and stick to it. Redirect the other version. Having both live creates duplicate content.

Structured Data

Structured data helps search engines understand your content and can enable rich results (stars, prices, FAQs in search results).

Priority Schema Types for SMEs

• LocalBusiness: Essential for local search presence
• Organization: Brand information and social profiles
• FAQPage: Can display FAQ accordions in search results
• Product: For e-commerce, shows prices and availability
• Review/AggregateRating: Display star ratings
• BreadcrumbList: Shows navigation path in results

Validate your structured data using Google’s Rich Results Test. Invalid schema is worse than no schema.

Schema Priority Don’t try to implement every schema type. Start with LocalBusiness or Organization, add BreadcrumbList, then consider page-specific types. Quality over quantity. Invalid or misleading schema can hurt more than help.

The Technical SEO Audit Process

Here’s how I approach technical audits:

Phase 1: Crawl the Site

Use a tool like Screaming Frog, Sitebulb, or Ahrefs Site Audit to crawl your site. Look for:

• Broken links (4xx errors)
• Server errors (5xx errors)
• Redirect chains (more than one hop)
• Missing or duplicate titles
• Missing or duplicate meta descriptions
• Missing H1 tags
• Orphan pages
• Deep pages (more than 3 clicks from home)

Phase 2: Check Search Console

• Coverage report: What’s excluded?
• Core Web Vitals: Any failing URLs?
• Mobile Usability: Any errors?
• Manual Actions: Any penalties?
• Security Issues: Any flagged problems?

Phase 3: Test Key Pages

• PageSpeed Insights on homepage, top landing pages, and conversion pages
• Mobile-friendly test
• Rich Results test for structured data

Phase 4: Prioritise Fixes

Not everything needs fixing immediately. Prioritise by:

1. Issues blocking crawling or indexing (critical)
2. Issues affecting Core Web Vitals (high priority)
3. Issues on high-traffic pages (high impact)
4. Quick wins (low effort, any impact)
5. Nice-to-haves (everything else)

Common Mistakes to Avoid

Mistake 1: Ignoring JavaScript Issues

If your content loads via JavaScript, Google might not see it. Check how your pages look in Search Console’s URL Inspection tool. Compare the rendered HTML to what you expect.

Mistake 2: Over-Optimising URLs

URLs don’t need keywords stuffed into them. /best-cheap-seo-services-london-uk isn’t better than /seo-services. Keep them clean and descriptive.

Mistake 3: Chasing Perfect Scores

A 100/100 PageSpeed score is nice but not necessary. Focus on actual user experience and Core Web Vitals thresholds, not arbitrary scores.

Mistake 4: Fixing Everything at Once

Make changes incrementally so you can track impact. A massive overhaul makes it impossible to know what helped or hurt.

Maintenance Over Time

Technical SEO isn’t a one-time project. Build these into your routine:

Weekly

• Check Search Console for new errors
• Verify key pages are still indexed

Monthly

• Run a site crawl and compare to previous month
• Check Core Web Vitals trends
• Review any new 404s or redirects

Quarterly

• Full technical audit
• Structured data validation
• Competitor technical comparison

Start Here

If you’re not sure where to begin:

1. Run your homepage through PageSpeed Insights
2. Check Search Console coverage report
3. Verify your XML sitemap exists and is submitted
4. Test your site on a real mobile phone

These four steps will reveal your most pressing technical issues. Fix those first, then work through the rest systematically.

Technical SEO is maintenance, not magic. The sites that rank well aren’t doing anything exotic. They’re just doing the basics consistently.