Blog Single
SEO Audit Checklist for South African Websites
Replace disconnected SEO findings with a risk-ranked roadmap tied to qualified visibility and revenue.
Make the audit answer a commercial question
An SEO audit should explain why a South African website fails to capture or convert relevant search demand. It examines crawler access, indexation, search presentation, user experience and business outcomes. The deliverable is a prioritised change programme, not an export containing thousands of equally weighted warnings.
Define scope before collecting data. Record products, services, locations, sectors, languages, customer types and conversion events. A Johannesburg enterprise consultancy, a Cape Town tourism operator and a nationwide ecommerce store need different architecture and evidence.
Document recent releases, migrations, analytics changes, acquisitions and seasonality. Establish baseline visibility, landing pages, enquiries, ecommerce outcomes and CRM stages. This context prevents the audit from mistaking a reporting change for lost demand or recommending work disconnected from the business.
Inventory properties, templates and ownership
List the primary domain, subdomains, regional or language sections, applications, staging environments, feeds and third-party journeys that influence search or conversion. Identify the owner and technology for each. Search risk often hides in a forgotten campaign subdomain or indexable test site.
Create a template inventory covering the homepage, categories, products, services, locations, articles, search results, filters, profiles and utility pages. Select representative examples with traffic, no traffic, different index states and known conversions. Template analysis reveals scalable causes that URL-by-URL checking misses.
Gather evidence from a crawler, Search Console, analytics, server logs where available, backlink data, CRM records and manual testing. State sampling limits and access gaps. A crawler shows its own discovery path; it does not prove exactly what Google fetched or what a customer experienced.
Separate confirmed defects, opportunities and experiments. Assign an acceptance test and accountable team to each recommendation.
Diagnose crawling and indexation
For every priority template, confirm the response code, redirect behaviour, robots access, page-level directive, canonical, sitemap inclusion and internal discovery. Find soft errors, redirect loops, chains, blocked resources and links that point at retired URLs.
Robots.txt can prevent crawling but is not a universal removal mechanism. Google documents robots meta directives for HTML and the X-Robots-Tag header for non-HTML resources. Ensure the crawler can access a page when it needs to read a noindex instruction, and review current official specifications before changing production rules.
Reconcile XML sitemaps with the intended canonical inventory. Exclude redirects, errors, duplicates and intentionally non-indexable URLs. Use truthful modification dates. Segment sitemaps by meaningful page type or property when that makes monitoring clearer.
Investigate protocol, hostname, case, slash, parameter and tracking variants. Align redirects, internal links, canonicals and sitemaps around one preferred URL. Review hreflang or other alternate signals only where genuinely distinct regional or language versions exist.
Check rendering and frontend delivery
Compare raw HTML with the rendered page and Google’s inspected representation. Critical text, headings, links, structured data, canonical information and product availability should remain discoverable after rendering. Identify scripts that fail, delayed content injection and consent tools that accidentally hide the page.
Test infinite scrolling, load-more components, tabs, accordions and client-side navigation. Search engines need stable URLs and crawlable links for content that should be discovered. Interactions designed only for a user gesture may leave deeper inventory isolated.
Elementor sites require inspection of their generated output. Review excessive wrappers, widget assets, global styles, fonts, background images and third-party scripts. Optimise at template level and regression-test menus, responsive layouts, forms, tracking and editor behaviour before deployment.
Review information architecture and crawl paths
Map how users and crawlers reach high-value categories, services, products, branches and supporting guides. Important pages should appear in a coherent hierarchy and receive contextual internal links. Sitemap-only discovery is a warning that the navigation model is incomplete.
Assess menus, breadcrumbs, pagination, filters and related-content modules. Descriptive anchors should communicate destination purpose. Avoid enormous navigation systems, boilerplate keyword links and tag archives that distribute attention without helping users.
Faceted ecommerce navigation deserves explicit rules. Determine which combinations match material demand and can support unique, maintained landing pages. Control low-value combinations so parameters, sorts and filters do not create an unbounded crawl space. Test that controls do not prevent discovery of canonical products.
Find orphaned pages, broken internal links and dead-end content. Before consolidating apparent duplicates, compare their queries, intent, backlinks, conversion history and audience. Redirect only to a meaningfully equivalent page; otherwise consider a clear removal response.
Match pages to South African search intent
Build a map of priority queries and landing pages using Search Console, customer language and manual result review. Distinguish informational research, local discovery, comparison, procurement and transactional intent. Evaluate the kinds of pages Google currently selects without copying competitors mechanically.
Check whether the opening section answers the searcher’s need, then review depth, proof, examples, objections and next action. Cut generic introductions that repeat national statistics without assisting a decision. Add South African context when regulation, delivery, pricing structure, procurement, sector practice or regional availability genuinely affects the answer.
Review authorship and accountability. Claims should be supportable, volatile information dated and regulated subjects checked by an appropriate specialist. Make the organisation, editorial responsibility and commercial relationship clear. Thin AI-generated variations with swapped place names are not a localisation strategy.
Identify pages competing for the same intent. Decide whether each serves a distinct segment or stage; if not, consolidate or reposition using performance evidence. Preserve valuable URLs and links during any change.
Content quality is not measured by length alone. A concise product page may be complete, while a long guide can still lack the comparison or proof the user requires. Audit information gain, accuracy and task completion.
Inspect titles, snippets and structured information
Check titles and main headings for uniqueness, accuracy and differentiation. Templates should describe each page without truncating the important concept behind repeated brand boilerplate. Meta descriptions can strengthen the proposition even though Google may generate a different snippet.
Validate structured data against the visible page and current Google eligibility rules. Remove unsupported reviews, organisation claims and properties inserted everywhere by a plugin. Valid syntax alone does not guarantee a search feature.
Evaluate performance using field and lab evidence
Test major templates across mobile and desktop. Use real-user field data where available and lab tools to isolate causes. Google’s Core Web Vitals assess loading performance, interaction responsiveness and visual stability; its documentation recommends good results for user experience and Search while recognising broader page-experience factors.
Inspect server response, caching, image formats and dimensions, fonts, CSS, JavaScript execution and third-party tags. Fix the measured bottleneck. Combining several performance plugins can create cache conflicts and hide the source of regressions.
Test on realistic devices and network conditions. Check text size, tap targets, menus, overlays, cookie controls, checkout and forms. A page can pass an automated score while remaining difficult to use or convert.
Audit regional and multilingual implementation
Where the organisation publishes language or regional alternatives, confirm that each version is complete, locally useful and internally linked. Implement alternate annotations consistently only for real equivalents. Do not automatically redirect users by assumed language or location in a way that blocks access.
South African English, Afrikaans and other language content should be reviewed by competent speakers for meaning and service accuracy. Translation is not merely keyword replacement. Maintain a change process so legal, price or availability updates reach every applicable version.
Regional pages need operational distinction. Explain the branch, coverage, team, access, services and evidence specific to Johannesburg, Pretoria, Cape Town, Durban, Gqeberha or another served location. Remove doorway-style pages where the business has no meaningful local proposition.
Assess local search properties
Verify Google Business Profile ownership, eligibility, core details, categories, hours, service areas and linked landing pages. Match each legitimate branch to an accurate page. Resolve duplicates, former locations and practitioner listings through the correct platform process.
Review citations on influential sector and local sources, but do not treat directory quantity as the goal. Audit the process for inviting genuine reviews and responding without exposing private information. Incentivised or gated review practices create platform and trust risk.
Compare local landing-page conversion: telephone links, directions, forms, booking steps and proof. Test that each route reaches an operating team and preserves source information.
Validate analytics, privacy and commercial attribution
Confirm Search Console properties and permissions. Audit analytics deployment, event naming, cross-domain paths, referrals, ecommerce data, internal traffic and consent behaviour. Compare recorded conversions with actual CRM, booking or order totals to detect duplication and loss.
POPIA applies to processing within its scope. Analytics, session tools, call tracking, forms and advertising integrations can process personal information. Review transparency, purpose, access, retention and vendor configuration with qualified privacy input; do not install monitoring merely because it is useful for SEO.
Carry landing page and source context into the CRM. Evaluate sales-accepted leads, meetings, opportunities and revenue alongside traffic. A page attracting large irrelevant volume should not outrank a lower-volume page that reaches the intended buying group.
Review security and change-management exposure
Check HTTPS, mixed content, certificate coverage, unauthorised users, plugin and theme maintenance, hacked pages and Search Console security or manual-action reports. Verify backups and recovery ownership. Never expose staging through guessable URLs without access controls.
For redesigns, mergers, platform moves or domain changes, create an inventory and one-to-one redirect map based on equivalence. Preserve strong content, metadata and internal linking, test before launch and monitor logs, indexing, rankings and conversion afterwards. Freeze avoidable simultaneous changes so causes remain diagnosable.
Convert the audit into owned delivery
Group findings by root cause and template. For each action, state affected scope, evidence, customer or commercial consequence, proposed remedy, dependency, owner and pass condition. Attach examples without implying the sample is the whole problem.
Resolve critical access and indexation risks first, then high-value template and conversion issues. Protect current performance through baselines and release monitoring. Re-crawl, inspect live pages and test customer actions after implementation.
Create dashboards for recurring risks such as index errors, organic landing-page outcomes, Core Web Vitals groups, broken journeys and lead delivery. Record decisions when recommendations are deferred. The audit earns value only when teams can prove what changed.
Turn South African search constraints into a growth roadmap
Nelium can combine crawling, Search Console, rendering, content, local search, analytics and conversion evidence into a prioritised programme. Book a comprehensive SEO diagnostic for your South African website.
Email: business@neliumsystems.com
Questions & Answers
Frequently asked questions
Is a free crawler enough for an SEO audit?
It can reveal useful technical patterns, but it cannot replace Search Console, analytics, business data, rendered testing and human evaluation of intent and conversion.
Are Core Web Vitals the entire technical SEO score?
No. They represent real-user experience metrics. Access, indexation, rendering, security, architecture and content remain separate concerns.
How should an SEO audit handle personal data under POPIA?
Minimise identifiers in exports and govern purpose, access, operators, sharing and retention using current Information Regulator guidance.
How often should a complete SEO audit be repeated?
Use continuous monitoring for critical controls and repeat a scoped audit after material releases, migrations or unexplained performance changes.
Got a Project in Mind? Let’s Talk.
Looking for reliable digital execution? Our experienced team is ready to help you craft scalable, performance-driven solutions from day one.
Phone: +254 710 520 510
Email: hello@neliumsystems.com
