Technical SEO for South African Businesses: What to Check (and Fix)

Your Content Can't Rank If Google Can't Read It. That's the Short Version of Technical SEO.

A Durban e-commerce site was publishing three articles a week for eight months. Decent writing. Reasonable keywords. Zero ranking progress. The owner blamed Google. The real problem: a misconfigured robots.txt was blocking the entire /blog directory. Google never crawled a single article.

Technical SEO is the foundation the rest of SEO stands on. If Google can't crawl your site, nothing else matters. If it can't render your JavaScript, your content is invisible. If your page takes 11 seconds to load on 3G, your mobile users bounce before Googlebot finishes its visit.

This guide walks through what to check, in what order, and how to fix the issues you'll almost certainly find.

What Technical SEO Actually Covers

Technical SEO is the plumbing. It's how your site is built, how it's configured, and how search engines interact with it.

Unlike on-page SEO (which focuses on content) or off-page SEO (which focuses on authority), technical SEO focuses on the infrastructure. Can Google find your pages? Can it render them? Does it understand the relationships between them? Does the site load quickly enough for users not to leave?

Get technical SEO wrong and everything else is wasted effort. Get it right and you've built a foundation that compounds over time.

Crawlability: Can Google Even Find Your Pages?

Googlebot crawls your site by following links and reading instructions. If you're blocking it accidentally, it can't index what it can't reach.

Robots.txt

This file (at yoursite.com/robots.txt) tells search engines what they can and can't crawl. A single misplaced line can block your entire site.

Red flag: Disallow: / blocks everything. This happens more often than you'd think when developers copy staging configs to production. Check it. Right now. Open yoursite.com/robots.txt in a browser.

Common legitimate uses: blocking admin pages (/wp-admin/), filtered URLs (/?sort=price), or duplicate pages. Everything else should be crawlable.

Sitemap.xml

Your sitemap is a list of URLs you want Google to crawl. It should include every page you want indexed and exclude everything you don't (tag archives, internal search results, login pages).

Submit it to Google Search Console. Check for errors. A sitemap that references 404 pages or noindex pages is worse than no sitemap.

Internal Linking Structure

Googlebot follows links. Pages with no internal links (orphan pages) rarely get crawled. Pages buried 6 clicks deep from the homepage get crawled rarely.

Rule of thumb: every important page should be reachable in 3 clicks or fewer from the homepage. If your product page is at /category/sub-category/sub-sub-category/product, you've got a crawl depth problem.

Orphan Pages

Use a crawler like Screaming Frog to identify pages that exist but aren't linked from anywhere on your site. These are orphans. Either link to them or delete them.

Indexability: Which Pages Should Actually Be Indexed?

Crawling is Google finding pages. Indexing is Google storing them for search results. You control both.

Noindex Tags

A page with <meta name="robots" content="noindex"> won't appear in search results. This is useful for thank-you pages, thin pages, and private content. It's disastrous when applied accidentally to important pages.

Check your important pages don't have noindex tags. WordPress sites frequently ship with noindex enabled by default in settings (a checkbox labelled "Discourage search engines"). Uncheck it or your site is invisible.

Canonical Tags

Canonical tags tell Google which version of a page is the original when multiple URLs show the same content. Example: /product?color=red and /product?color=blue might both have a canonical pointing to /product.

Canonical issues are common on e-commerce and filter-heavy sites. Misconfigured canonicals can cause Google to index the wrong version or ignore your content entirely.

Duplicate Content

Two pages with nearly identical content compete with each other. Google picks one and ignores the other. Often it picks wrong.

Common culprits: http vs https versions, www vs non-www, trailing slashes (/ vs no slash), uppercase vs lowercase URLs. Set 301 redirects from the variants to the canonical version. Pick one. Stick with it.

Site Architecture: How Everything Fits Together

Architecture is how your site's pages relate to each other. Good architecture helps both users and search engines.

URL Structure

URLs should be readable, descriptive, and consistent. /services/accounting beats /page?id=247. Keep URLs lowercase, use hyphens not underscores, and avoid query strings where possible.

Breadcrumbs

Breadcrumbs (Home > Services > Accounting) help users find their way around and give Google structural signals. Add them with BreadcrumbList schema for rich results in search.

Category Hierarchy

Your site should have a clear tree structure. Homepage at the top, category pages one level down, subcategories two levels down, individual pages at the leaves. Avoid flat architectures where every page sits at root level, and avoid deep hierarchies where users need 7 clicks to reach content.

Depth From Homepage

Important pages should be 1 to 3 clicks from the homepage. Tools like Screaming Frog visualise click depth. If your highest-intent commercial pages are 4+ clicks deep, reorganise.

Page Speed and Core Web Vitals

Page speed is a confirmed ranking factor. Google measures this through Core Web Vitals: LCP, INP, and CLS.

LCP (Largest Contentful Paint)

How long before the largest element in the viewport renders. Target: under 2.5 seconds. Usually the hero image or main heading. Fix by optimising images (WebP, correct dimensions, lazy loading below the fold), upgrading hosting, and reducing server response time.

INP (Interaction to Next Paint)

How quickly the page responds when a user taps or clicks. Replaced FID in early 2024. Target: under 200ms. Usually caused by heavy JavaScript blocking the main thread. Fix by code splitting, deferring non-critical JS, and removing unused code.

CLS (Cumulative Layout Shift)

How much elements move around as the page loads. Target: under 0.1. Usually caused by images without dimensions, fonts loading late, or ads injecting mid-page. Fix by setting explicit width/height on images, using font-display: swap carefully, and reserving space for late-loading content.

We covered this in depth in our Core Web Vitals guide for SA websites, including specific optimisations for 3G networks.

Test your pages with PageSpeed Insights. It shows both lab data (simulated) and field data (real user measurements over the last 28 days).

Mobile Optimisation: Mobile-First Indexing Is Non-Negotiable

Google indexes the mobile version of your site. If your mobile version is a stripped-down version of desktop, the stripped-down version is what Google ranks.

Checklist:

• Viewport meta tag set (<meta name="viewport" content="width=device-width, initial-scale=1">)
• Content is readable without zooming
• Tap targets at least 48x48 pixels with adequate spacing
• No horizontal scroll
• Same content on mobile and desktop (don't hide sections on mobile)
• Same internal links on mobile and desktop

In SA, mobile matters even more. Over 85% of web traffic comes from mobile. Many users are on mid-range Android devices over 4G, sometimes 3G. Flagship iPhone performance is not your benchmark.

Security: HTTPS and Mixed Content

HTTPS has been a ranking factor since 2014. It's also a trust signal for users. Chrome labels HTTP sites as "Not Secure" in the address bar, which kills conversion rates.

Every page should load over HTTPS. Check for mixed content warnings, which happen when an HTTPS page loads resources (images, scripts, styles) over HTTP. Browsers block mixed content, breaking functionality.

Most hosts offer free SSL via Let's Encrypt. If yours doesn't, switch hosts. This isn't 2015 anymore.

Structured Data: Schema Markup

Schema markup is structured data that describes your content to search engines. It's usually added as JSON-LD in the page head.

Common types for SA businesses:

• Organization: your business details (name, logo, contact, social profiles)
• LocalBusiness: for brick-and-mortar operations with addresses
• Article: for blog posts and guides
• FAQPage: for pages with question-and-answer sections
• Product: for e-commerce product pages
• BreadcrumbList: for navigation hierarchy

Valid schema can trigger rich results (star ratings, FAQ dropdowns, image carousels) that dramatically increase CTR. Use Google's Rich Results Test to validate your markup before shipping.

International and Local SEO: Hreflang and Language Tags

If your site serves multiple regions or languages, hreflang tags tell Google which version to show which user.

For a SA business serving only South Africa in English, set <html lang="en-ZA">. Google uses this as a localisation signal. If you publish in English and Afrikaans, use hreflang pairs linking the two versions.

Common mistake: SA businesses use lang="en" (generic English) or lang="en-US" by default because their CMS is configured that way. Change it to en-ZA. This is a five-minute fix that subtly improves your SA visibility.

JavaScript Rendering: The Hidden Killer

Googlebot renders JavaScript, but with limitations. If your site is fully client-side rendered (content loads after JavaScript executes), Google might not see half your content.

Frameworks like React, Vue, and Angular can all cause issues when misconfigured. Server-side rendering (SSR) or static site generation (SSG) solves this. Astro, Next.js, Nuxt, and SvelteKit all handle this well.

To check: disable JavaScript in your browser and load your page. Is the content still there? If the page is blank, Google's likely having trouble too.

Tools You'll Actually Use

• Google Search Console: free, essential. Shows coverage errors, Core Web Vitals, mobile usability, and search performance.
• Screaming Frog SEO Spider: free up to 500 URLs. The workhorse crawler for technical audits. Paid license is R4,500/year, worth it if you manage multiple sites.
• Lighthouse (Chrome DevTools): built into Chrome. Opens via right-click > Inspect > Lighthouse tab. Gives speed, SEO, accessibility, and best practices scores.
• Chrome DevTools Network tab: shows what's loading, how long it takes, and what's blocking rendering.
• Ahrefs Site Audit / Semrush Site Audit: automated audits with prioritised recommendations. Useful for ongoing monitoring.

Common SA-Specific Technical Issues

Slow Local Hosting

Many SA businesses use international hosting because it's cheaper. The latency hit from SA users accessing US-hosted sites can add 500ms+ to every request. Either use SA hosting (Afrihost, Hetzner, RSAWEB) or put your site behind a CDN with SA edge nodes (Cloudflare has Johannesburg and Cape Town).

3G and 4G Performance

Many SA users are on variable mobile connections. Test your site using Chrome DevTools' Network throttling set to "Slow 3G". If the page takes 15+ seconds to become interactive, your rural and lower-income audiences are bouncing.

Images Not Optimised for Low Bandwidth

A 2MB hero image loads instantly on fibre and slowly on 4G. Use WebP format (30 to 50% smaller than JPEG), serve responsive images with srcset, and lazy-load anything below the fold. Aim for total page weight under 1MB on mobile.

What Is the Difference Between Technical SEO and On-Page SEO?

Technical SEO covers infrastructure: crawlability, indexability, site architecture, speed, schema, mobile-friendliness, security. On-page SEO covers content optimisation on individual pages: titles, headings, keywords, internal linking, content quality.

They overlap. Schema markup is arguably both. Page speed affects both crawling (Googlebot has time budgets) and user experience (which affects rankings indirectly through engagement).

The practical distinction: technical SEO is done at the site level, usually by developers. On-page SEO is done at the page level, usually by marketers or writers. Both are required. Our on-page SEO checklist covers the page-level side in detail.

How Do I Perform a Technical SEO Audit?

Here's a practical audit sequence you can run in a single afternoon:

1. Check robots.txt. Visit yoursite.com/robots.txt. Make sure you're not blocking anything important.
2. Check sitemap.xml. Visit yoursite.com/sitemap.xml. Confirm it exists and is accessible. Submit to Google Search Console.
3. Crawl the site with Screaming Frog. Look for broken links (4xx/5xx errors), missing titles, duplicate metas, redirect chains, and orphan pages.
4. Run Lighthouse on your top 5 pages. Note Core Web Vitals scores. Fix anything scoring below 50.
5. Check Search Console Coverage report. Look for pages that are "Discovered but not indexed" or "Crawled but not indexed". These are your indexation problems.
6. Test mobile usability. Use Search Console's mobile usability report. Fix any flagged issues.
7. Validate schema markup. Run your top pages through Google's Rich Results Test. Fix any errors.
8. Check HTTPS enforcement. Try loading http://yoursite.com. Confirm it redirects to https://.
9. Check hreflang and language tags. Confirm lang="en-ZA" on your pages if you serve SA.
10. Test JavaScript rendering. Disable JS in your browser and reload. Content should still be visible.

This 10-step audit catches maybe 90% of the technical issues most SA sites have. The remaining 10% requires deeper investigation (log file analysis, complex internationalisation, rendering edge cases) that's usually worth bringing in an expert for.

When to DIY and When to Call Help

Most SA businesses can handle basic technical SEO themselves. WordPress has plugins (Rank Math, Yoast) that automate schema, sitemap generation, and many common checks. Page speed improvements are often configuration-level (enable caching, lazy-load images, compress assets).

Call in help when: you're migrating platforms (most rank losses happen here), you have a large e-commerce site with complex filtering, you have international or multilingual requirements, or you're on a custom-built CMS where issues aren't plugin-fixable.

Our AI-powered SEO service runs the 10-step audit automatically against your site and delivers a prioritised list of issues ranked by ranking impact. Create a Raimond account and we'll show you the technical issues your current setup is hiding. No lock-in, no contract, just the actual gap between where you are and where you could be.