Important pages are not showing on Google
The cause may be noindex tags, incorrect canonicals, sitemap gaps, blocked sections, weak internal links, thin pages or duplicate URL signals.
Technical SEO audit for South African websites
Audit-led diagnosis for crawlability, indexing, redirects, canonicals, Core Web Vitals, internal linking, architecture and technical issues that may be holding back organic visibility and enquiries.
Audit-led diagnosis
A technical SEO audit is a diagnostic review of the technical issues that can stop a website from being properly crawled, indexed, understood and prioritised by search engines.
For South African SMEs, ecommerce stores, professional services firms and local service businesses, technical issues can quietly affect enquiries, ecommerce sales and local visibility. A website may look polished to customers while broken redirects, weak internal links, slow templates, duplicate URLs, incorrect canonicals or indexing problems hold back organic performance.
The goal is not to export a long list of tool warnings. The goal is to identify what is wrong, explain why it matters, show which pages are affected and prioritise the fixes that deserve attention first.
When a technical audit is the right move
Technical audits are useful when the website has valuable pages, services, products or content, but organic search performance is not where it should be. This often happens after redesigns, platform changes, template changes, plugin growth, ecommerce expansion, migration work or years of SEO activity without a technical review.
The cause may be noindex tags, incorrect canonicals, sitemap gaps, blocked sections, weak internal links, thin pages or duplicate URL signals.
Old URLs may return errors, redirect to the wrong pages, lose metadata, break internal links or remove pages that previously carried visibility.
Indexing, crawl, sitemap, mobile usability, manual action or page experience warnings need interpretation before your team starts making changes.
A technical audit can create clearer requirements before developers change templates, navigation, redirects, schema, speed or platform settings.
Common technical SEO problems
A useful audit connects these patterns to business impact. It shows whether the issue affects the homepage, service pages, product categories, location pages, blog templates or the entire website system.
Priority pages may not be indexed because of noindex tags, weak internal links, sitemap gaps, blocked URLs, canonical confusion or low-value duplication.
Redesigns and migrations can leave old URLs returning 404 errors, redirect chains, homepage redirects, lost mappings or internal links to outdated URLs.
Incorrect canonicals can tell search engines to prefer the wrong URL or create mixed signals across duplicate, filtered or variant pages.
WordPress, WooCommerce, Shopify and custom sites can create duplicate URL patterns through filters, tags, archives, variants or tracking parameters.
Heavy images, slow hosting, scripts, plugins, bloated themes and layout shifts can affect important page templates and mobile users.
Commercial pages, location pages or category pages may exist without enough internal support from hubs, content, navigation or related pages.
Audit coverage
The exact scope depends on website size, platform and problem history. The focus is to find issues that affect crawling, indexing, search visibility, page experience, internal relevance and implementation quality.
| Audit area | What gets reviewed | Commercial reason |
|---|---|---|
| Search access and indexing | robots.txt, noindex tags, canonical signals, XML sitemaps, blocked sections and priority pages missing from Google. | Pages cannot drive enquiries if they cannot be accessed, indexed or understood. |
| Google Search Console | Indexing trends, sitemap issues, crawl signals, page experience warnings, search changes and manual action notices where relevant. | Search Console evidence helps confirm whether the issue is technical, content-related, migration-related or broader. |
| Site crawl patterns | Broken links, redirect chains, duplicate metadata, crawl-depth issues, orphan pages, status codes and low-value indexed URLs. | Crawl data reveals site-wide patterns that are not always visible from the front end. |
| URL and canonical control | Which URLs should exist, rank, consolidate, redirect or stay out of the index. | Clear URL signals reduce confusion and protect the pages that should carry commercial demand. |
| Performance and Core Web Vitals | Mobile speed, layout shifts, server response, images, JavaScript, CSS and template-level load issues. | Slow templates can weaken user experience and reduce enquiry performance. |
| Internal linking and architecture | How links move between service pages, location pages, product categories, support content and conversion pages. | Important pages need internal support and clear user paths to enquiries. |
| Technical on-page and schema | Titles, descriptions, headings, breadcrumbs, schema, duplicate metadata and template-generated SEO issues. | Templates should support search clarity instead of creating repeated technical errors. |
Developer-ready recommendations
A weak audit says “fix canonicals” or “improve internal linking”. A stronger audit explains the affected URL pattern, why it matters, what needs to change, who should implement it and how to test it after deployment.
“Fix canonical issues.”
Too vague for the developer, owner or marketer to action confidently.
Filtered category URLs are canonicalising to themselves even when those URLs are not intended to rank. Update the category template so non-indexable filters canonicalise to the main category page, then test the sample URLs before deployment.
Includes affected pattern, reason, action and testing step.
Process
The audit starts with the business context and the problem you are seeing. The review then moves through evidence, affected pages, likely impact and implementation priority.
Review recent redesigns, migrations, traffic drops, platform changes, priority pages, lead-generation goals and known Search Console warnings.
Use crawl data, page checks, Search Console data where available and manual inspection of important templates and URLs.
Prioritise issues that may affect visibility, crawling, indexing, user experience, local discovery, commercial pages or enquiry paths.
Provide an executive summary, issue register, affected examples, developer notes, priority order and monitoring recommendations.
Deliverables
The output should help your team move from diagnosis to implementation. The audit should not only list issues — it should show what matters, why it matters and what to do next.
Plain-language explanation of the main technical findings and why they matter.
A structured list of issues, affected examples, impact notes and recommended action.
Fixes grouped by urgency, business impact, technical complexity and implementation order.
Clear instructions for technical fixes where your developer or platform team needs specifics.
Sample pages and templates to help your team locate the issue and test fixes.
What to check after implementation so changes can be validated responsibly.
Audit scope and pricing
A five-page local business website does not need the same audit scope as a large ecommerce store, directory, multi-location site or website recovering from a failed migration. The audit should match the problem rather than force every site into one generic package.
Smaller sites usually need access, indexing, internal linking, template and page-level checks. Ecommerce and larger sites often need deeper URL, crawl, filter, category, pagination, canonical and performance analysis. Migration or recovery projects need stronger redirect, URL history and traffic-change review.
Good fit
Realistic expectations
Fixing technical SEO issues can support crawlability, indexation, user experience and search clarity, but it does not guarantee rankings, traffic, leads, Google Maps positions or ROI. Outcomes depend on competition, content quality, implementation, website history, market demand and Google’s systems.
The role of the audit is to reduce guesswork, prioritise the right fixes and help your team avoid spending more on SEO activity while the website foundation is still unclear.
FAQs
These answers help clarify whether a technical SEO audit, broader SEO audit, recovery review or migration diagnosis is the right next step.
A technical SEO audit is a diagnostic review of crawlability, indexing, redirects, canonicals, sitemaps, internal linking, site structure, performance, schema and template-level issues that may affect organic visibility.
Choose a technical SEO audit when the main concern is crawling, indexing, redirects, migration damage, site speed, canonicals, duplicate URLs, Search Console warnings or technical implementation. Choose a broader SEO audit when you also need content, keyword, competitor, local SEO and conversion review.
It can help diagnose technical causes of traffic drops, especially after redesigns, migrations, URL changes, indexing issues or template changes. Not every traffic drop is technical, so the audit should distinguish technical issues from content, competition, algorithmic or demand changes.
Google Search Console access is very useful because it shows indexing, crawl, sitemap, performance and page experience signals. A technical review can still start without access, but Search Console data helps confirm the evidence.
Yes, where technical implementation is required. Developer-ready notes can explain affected templates or URL patterns, recommended fixes, testing checks and what to monitor after implementation.
Yes. Ecommerce sites often have technical issues around filters, categories, product variants, pagination, canonicals, crawl waste, duplicate URLs, internal linking, slow templates and structured data.
No. Technical fixes can support SEO performance, but rankings and traffic are not guaranteed. Results depend on implementation, competition, content quality, website history, demand and Google’s ranking systems.
Next step
Send your website URL, the issue you are seeing and any recent website changes. The goal is to confirm whether a technical SEO audit is the right next step and what scope makes sense for the problem.