A technical SEO checklist is a structured audit of the behind-the-scenes factors that determine whether Google can find, crawl, index, and rank your website — and for South African businesses, the stakes are higher than most checklists acknowledge. As of July 2024, Google completed its shift to mobile-first indexing for every website on the planet: your mobile version is now the version Google reads, ranks, and makes decisions from. In South Africa, where mobile devices dominate web browsing — reflecting the sub-Saharan Africa pattern where mobile accounts for over 70% of all web traffic — a technical flaw on mobile is not an inconvenience: it is a direct ranking penalty.
This checklist covers the seven technical areas that most commonly block South African websites from ranking: crawlability, indexation, Core Web Vitals, HTTPS and site security, mobile optimisation, structured data, and the SA-specific factors that global checklists ignore — local hosting latency, load shedding risk, and language targeting. Work through each section in order; earlier areas create the conditions for later ones to matter.
Quick Answer
A technical SEO checklist for South African websites covers seven core areas: crawlability (robots.txt, sitemaps, crawl budget), indexation (canonicals, noindex, duplicate content), Core Web Vitals (LCP ≤2.5s, INP ≤200ms, CLS ≤0.1), HTTPS and uptime, mobile optimisation, structured data/schema, and SA-specific factors including server location and language targeting. With Google's mobile-first indexing now applying to 100% of websites, fixing mobile technical issues is the single highest-return starting point for most South African sites.
Jump to a Section
Want a Technical Audit Done for You?
Tell us your site URL and we will identify the technical issues suppressing your Google rankings — crawl errors, Core Web Vitals failures, indexation gaps, and more.
Request a Technical AuditCrawlability: Can Googlebot Actually Reach Your Pages?
Crawlability is the foundation of all search engine optimisation: if Googlebot cannot reach a page, nothing else on your checklist matters. Most crawlability problems on South African websites come from misconfigured robots.txt files, blocked resources, or URL structures that bury important content too deep in the site hierarchy.
| Crawlability Check | What to Look For | Tool |
|---|---|---|
| robots.txt | No accidental blocks on CSS, JavaScript, or key page paths; sitemap URL declared | Google Search Console > Robots.txt tester |
| Crawl errors | 4xx errors on pages with internal links; 5xx server errors indicating hosting instability | GSC > Coverage report |
| Site depth | Important pages reachable within 3 clicks from the homepage | Screaming Frog, Sitebulb |
| XML sitemap | Contains only canonical, indexable URLs; no noindex pages; submitted to GSC | Google Search Console > Sitemaps |
| Redirect chains | No chains longer than 2 hops; permanently moved pages should use 301 — audit for 302s applied where 301 is appropriate | Screaming Frog |
| Internal links to key pages | Every priority page receives at least one internal link from a crawled page | Screaming Frog |
Crawlability Takeaway
Google's documentation confirms sitemaps are most valuable for sites with 500 or more pages, new sites with few external links, or sites with significant video and image content. For smaller SA business websites, clean internal linking from your homepage is a sufficient crawl signal — submitting a sitemap full of low-quality URLs is counterproductive. Check for orphan pages that sit outside your internal link structure entirely; Googlebot cannot discover what nothing points to.
For a deeper walkthrough of fixing crawl problems systematically, see our guide on how to improve crawlability for South African sites.
Indexation: Are the Right Pages in Google's Index?
Indexation problems fall into two categories: pages that should be indexed but are not, and pages that should not be indexed but are. Both harm rankings — the first by hiding content from Google, the second by diluting your crawl budget and confusing Google's understanding of which pages matter.
| Indexation Check | What to Look For | Common SA Cause |
|---|---|---|
| Canonical tags | Self-referencing canonical on every page; no canonical pointing to a different live page | WordPress theme duplication, staging URLs |
| Noindex tags | No accidental noindex on live pages; pagination, search results, and thin pages correctly noindexed | SEO plugin misconfiguration |
| Duplicate content | No near-duplicate pages competing for the same keyword; URL parameters handled | WooCommerce category + tag URL duplication |
| GSC Coverage report | Understand every "Excluded" reason; review "Crawled — currently not indexed" pages | Thin content, soft 404s |
| Faceted navigation | Filter/sort URLs either canonicalised or blocked via robots.txt | WooCommerce default configuration |
Faceted navigation trap: WooCommerce's default configuration creates unique URLs for every combination of product filter — colour, size, price range. A store with 5 filter categories and 10 values each can generate tens of thousands of thin URLs. Google crawls them all, indexing none, while burning through your crawl budget. The fix is to canonicalise filtered URLs to their category parent or block them via robots.txt — but not both simultaneously, as that creates a conflicting signal.
Our full guide on improving website indexation covers the GSC Coverage report in detail and shows how to read every exclusion reason correctly.
Core Web Vitals: Are You Meeting Google's Performance Thresholds?
Core Web Vitals are the three user experience metrics Google uses as a confirmed ranking signal: Largest Contentful Paint (loading speed), Interaction to Next Paint (responsiveness), and Cumulative Layout Shift (visual stability). Google measures these at the 75th percentile of real user sessions — meaning 75% of your visitors must experience a "Good" rating for the page to pass.
| Metric | Good | Needs Improvement | Poor | What It Measures |
|---|---|---|---|---|
| LCP | ≤ 2.5s | 2.5–4.0s | > 4.0s | Time to largest image or text block loading |
| INP | ≤ 200ms | 200–500ms | > 500ms | Delay between user interaction and browser response |
| CLS | ≤ 0.1 | 0.1–0.25 | > 0.25 | Unexpected layout shifts during page load |
In South Africa, Core Web Vitals failures are disproportionately common because most SME websites are built on shared hosting with WordPress themes loaded with third-party plugins. A significant proportion of websites globally fail the LCP "Good" threshold on mobile — and on shared SA hosting with international server locations, mobile LCP regularly exceeds 4 seconds. One documented case of a South African business switching from Dublin-based hosting to a local Johannesburg server recorded LCP improving from over 3 seconds to 1.1 seconds — purely from reducing server distance.
Core Web Vitals Takeaway
Check your Core Web Vitals for your South African site in Google Search Console under Experience → Core Web Vitals. The field data report shows your real-user performance; the lab data tools (PageSpeed Insights) show what is technically possible. Fix LCP first — images with explicit width/height attributes, served in WebP format, and loaded on a server with low latency to SA are the fastest wins. CLS is usually caused by images without dimensions or late-loading fonts; INP by excessive JavaScript execution.
HTTPS, Security, and Site Reliability
HTTPS has been a confirmed Google ranking signal since August 2014. Google itself describes it as a "lightweight" signal — it will not overcome weak content — but running HTTP in 2026 sends a trust-damaging warning to users in Chrome and removes any competitive advantage the signal offers. Every South African business website should be on HTTPS as a baseline, not an upgrade.
| Security Check | What to Verify |
|---|---|
| SSL certificate active | Valid certificate installed; no browser security warnings on any page |
| Mixed content | No HTTP resources (images, scripts, fonts) loaded on HTTPS pages; check browser console |
| HTTP → HTTPS redirect | All HTTP URLs 301-redirect to HTTPS equivalents; no redirect loops |
| www vs. non-www | One preferred version set in GSC; the other 301-redirects to it |
| Uptime monitoring | Monitoring in place; hosting provider has documented generator or UPS backup |
SA uptime note: Load shedding in South Africa is measurably better than it was — the country recorded only 26 hours of outages across the entirety of 2025. But the risk of recurrence is real given ageing grid infrastructure, and your hosting infrastructure matters regardless. When a site returns 5xx errors consistently, Googlebot reduces crawl frequency. Sites that were down regularly during Stage 6 periods saw slower indexing of new content for months afterwards, even after uptime was restored. Confirm your host has generator-backed data centre infrastructure or run your site on a CDN with South African edge nodes.
Mobile Optimisation: The SA Non-Negotiable
Mobile optimisation is the most underestimated item on any South African technical SEO checklist. Since July 2024, Google crawls and indexes 100% of all websites using its mobile crawler — there are no exceptions. This means your mobile version determines your Google rankings for both mobile and desktop searches. If your desktop site has content, internal links, or structured data that your mobile version hides, that content does not exist in Google's eyes.
| Mobile Check | What to Verify |
|---|---|
| Responsive design | Site renders correctly at 360px, 390px, and 414px viewport widths (most common SA mobile sizes) |
| Content parity | Mobile version has identical main content, internal links, and headings as desktop |
| Tap targets | Buttons and links at least 48×48px with 8px spacing; no accidental taps on adjacent elements |
| Font size | Body text minimum 16px; no content requiring pinch-to-zoom |
| Mobile page speed | LCP ≤2.5s on mobile (test with PageSpeed Insights, mobile mode) |
| Viewport meta tag | <meta name="viewport" content="width=device-width, initial-scale=1"> present on every page |
The commercial urgency is straightforward: 2017 Google research found that 53% of mobile visitors abandon pages that take longer than 3 seconds to load. For a South African audience where mobile is the primary — often the only — device used to browse the web, slow mobile performance is not a ranking problem in isolation. It is simultaneously a user experience problem, a bounce rate problem, and a conversion problem.
Structured Data: Helping Google Understand Your Content
Structured data (schema markup) is the machine-readable layer that tells Google what your content is about, not just what it says. Correct schema implementation enables rich results in search — review stars, FAQ dropdowns, product pricing, event listings — and feeds Google's AI-generated summaries with structured, attributable information.
| Schema Type | Best For | Rich Result |
|---|---|---|
| LocalBusiness | Every SA business with a physical address or service area | Business name, address, hours in knowledge panel |
| FAQPage | Pages with question-and-answer sections | FAQ dropdowns in SERP |
| Product | Ecommerce product pages | Price, availability, review stars |
| Article / BlogPosting | Blog posts and news articles | Author, date, article type |
| BreadcrumbList | Any site with multi-level navigation | URL breadcrumbs in search results |
| Review / AggregateRating | Products, services, businesses with reviews | Star ratings in snippet |
South African businesses frequently overlook LocalBusiness schema, which is the single schema type with the clearest direct impact on local search visibility. Including your correct South African address, trading hours, and service area inside LocalBusiness markup takes 15 minutes and directly feeds the information Google shows when someone searches for your business by name. Test any schema you implement using Google's Rich Results Test (search.google.com/test/rich-results) before deploying, and consult Google's Search documentation for structured data guidelines.
For a comprehensive walkthrough of implementation, read our guide on schema markup for South African websites.
Structured Data Takeaway
Schema markup only works when your page content actually supports it. Do not add FAQPage schema to a page with no visible FAQ content, or Product schema to a category page. Google's structured data quality guidelines are enforced through Search Console's Rich Results report — errors there mean your schema is parsed but not eligible for rich results. Start with LocalBusiness and BreadcrumbList for most SA business sites; layer in FAQPage and Article for content-heavy sites.
SA-Specific Technical Factors: Hosting, Language, and Infrastructure
South African websites face technical considerations that no global checklist accounts for. These are not edge cases — they affect the majority of SA business websites built in the last decade.
Server Location and TTFB
Time to First Byte (TTFB) is the delay between a browser requesting a page and receiving the first byte of data from the server. For South African users, server distance has an outsized impact. In one documented SA case study, switching from international hosting to a local server reduced TTFB from 0.95 seconds to 0.15 seconds — consistent with the physics of server distance, though actual results vary by host, stack, and connection type.
If your site is hosted in Europe or the US and serving primarily South African visitors, TTFB alone can push you into "Needs Improvement" Core Web Vitals territory regardless of how well-optimised your code is. A CDN with South African edge nodes (Cloudflare has a Johannesburg presence) is a viable intermediate solution if migrating your entire hosting stack is not immediately practical. For a broader look at your options, see our guide to website hosting in South Africa.
Language Targeting and hreflang
South Africa has 11 official languages, and a meaningful number of SA business websites serve content in both English and Afrikaans — sometimes on the same URL, sometimes on different versions. Mixing languages on the same URL without hreflang tags confuses Google's language targeting. The correct implementation is to use hreflang="en-za" for English South African content and hreflang="af-za" for Afrikaans, with each version pointing to the other via self-referencing hreflang tags. Missing return tags (where version A points to version B but version B does not point back to version A) cause Google to ignore the entire annotation set.
Hosting Uptime and Crawl Budget
Consistent server uptime matters to search rankings because Googlebot adjusts its crawl frequency based on your server's response reliability. A site that returns 5xx errors intermittently trains Googlebot to crawl it less often — meaning new pages take longer to appear in search results. South Africa's load shedding risk has reduced significantly (26 hours total in 2025), but the infrastructure question remains live: choose hosting with documented generator backup or a CDN with South African edge nodes to maintain reliable response times during any grid instability.
Unsure Which Technical Issues Are Hurting Your Rankings Most?
Share your site with us and we will run a Core Web Vitals and crawlability check — and tell you exactly what to fix first to move the needle fastest.
Get a CWV and Crawl ReviewWhy South African Businesses Choose Growth Pulse Media for Technical Search Optimisation
Technical search engine optimisation is one of those disciplines where the implementation details matter as much as the strategy. A robots.txt block in the wrong location, a canonical pointing to a staging URL, or a mobile layout that hides key internal links — any of these can silently suppress rankings for months before anyone notices. Our work on SEO for South African websites covers the full technical and content stack, not just the visible output.
What we bring that most generalist agencies do not: Dirk built and scaled an actual South African ecommerce business before founding GPM — he has paid the hosting bills, seen the WooCommerce crawl traps firsthand, and dealt with Core Web Vitals failures on a WordPress stack running 14 conflicting plugins.
We work with a deliberately limited client roster, which means senior attention on every technical audit rather than a junior checklist passed down the chain. Every recommendation on our technical SEO checklist is prioritised by ranking impact, not by implementation complexity — if the highest-return fix is an .htaccess redirect, that is what we recommend, not a platform migration.
Who This Technical SEO Checklist Is NOT For
Sites that are not yet live or not yet indexable. Technical search optimisation only matters when Googlebot can reach your site. If you are in development, on a staging server, or have your entire domain blocked via robots.txt, fix those conditions first.
Businesses looking for quick-rank shortcuts. Technical SEO removes the barriers to ranking — it does not create the content, authority, or topical relevance that drives rankings. A technically perfect site with no substantive content does not outrank a mediocre-tech competitor with 50 genuinely useful pages.
Teams expecting a one-and-done fix. Technical health is not a project you complete — it is an ongoing state you maintain. New pages create new canonicalisation risks; plugin updates break Core Web Vitals; site migrations introduce redirect chains. This checklist is a baseline, not a certificate of completion.
Very new websites with no content strategy. If your site has fewer than 20 pages of substantive content and no link profile, technical fixes will have minimal visible impact. The bottleneck is content and authority, not technical configuration. Build that foundation first, then run this checklist when there is something meaningful to optimise.
Ready to Turn Technical Fixes Into Ranking Gains?
Tell us about your site and your current traffic situation and we will give you an honest assessment of where technical SEO fits in your overall growth plan.
Get an Honest Site AssessmentTechnical SEO Checklist: Frequently Asked Questions
What is the difference between technical SEO and on-page SEO?
Technical SEO covers the infrastructure that allows search engines to crawl, index, and render your website — robots.txt, sitemaps, HTTPS, Core Web Vitals, structured data, and server configuration. On-page SEO covers the content visible to users: title tags, headings, keyword usage, internal linking, and copy quality. Both are necessary; technical fixes create the foundation that on-page optimisation builds on. A technically perfect site with no relevant content ranks for nothing; a content-rich site with crawl blocks ranks for nothing either.
How do I check if my South African website has technical SEO problems?
Start with Google Search Console — it is free and shows real data from Googlebot's interactions with your site. The Coverage report identifies indexation problems; the Core Web Vitals report shows performance against Google's thresholds; the Sitemaps report confirms your sitemap was submitted and parsed correctly. Supplement with PageSpeed Insights to identify specific LCP, INP, and CLS failures. For a full crawl-level audit, tools like Screaming Frog (free up to 500 URLs) or Sitebulb identify broken links, redirect chains, and missing canonical tags across your entire site.
Does hosting location affect SEO for South African websites?
Yes — server location affects Time to First Byte (TTFB), which contributes directly to LCP and therefore Core Web Vitals. South African users connecting to a server in Dublin or the US experience additional latency from physical distance alone. For a site serving predominantly South African visitors, a local server or a CDN with South African edge nodes (Cloudflare has a Johannesburg point of presence) meaningfully improves real-user performance data, which is what Google's Core Web Vitals algorithm reads. If your current host is overseas and your Core Web Vitals are failing on mobile, server location should be the first variable you investigate.
Is mobile-first indexing different from having a mobile-friendly website?
Yes. A mobile-friendly website is one that displays correctly on a mobile device. Mobile-first indexing means Google uses your mobile version as the primary input for its index and ranking decisions — for both mobile and desktop searches. A site can be mobile-friendly (no layout errors on a phone) but still lose rankings if the mobile version hides content, strips internal links, or serves lower-quality structured data than the desktop version. Since July 2024, this applies to every website without exception. Run Google's Mobile-Friendly Test and then manually compare your desktop and mobile versions side by side for content parity.
How often should I run a technical SEO audit?
Run a full technical audit after any significant site change — a platform migration, theme update, major URL restructure, or large-scale content addition. For ongoing monitoring without a trigger event, a quarterly check of your Google Search Console Coverage and Core Web Vitals reports catches most regressions early. Monthly uptime monitoring and a crawl of new sections as you add them is good practice for sites publishing regularly. The most damaging technical problems are the ones that go unnoticed for months — ongoing monitoring is more valuable than infrequent deep audits.
Get Your Technical Search Optimisation Right, First Time
We audit South African websites across every technical layer — crawlability, indexation, Core Web Vitals, HTTPS, mobile parity, schema, and hosting infrastructure. Our recommendations are prioritised by ranking impact, not by what is easiest to implement. Senior attention on every engagement. No obligation — we will get back to you within 24 hours.
Request Your Technical SEO Audit