Most SEO audits are surface-level checklists.

They scan for missing meta descriptions, flag a few broken links, and generate a 40-page PDF filled with colour-coded warnings — without ever identifying what is actually blocking rankings.

A real technical SEO audit is diagnostic, not decorative.

It follows a structured model:

Crawl → Index → Render

If Google cannot crawl your pages properly, nothing else matters.
If Google crawls but doesn’t index correctly, rankings stall.
If Google indexes but rendering or performance is broken, visibility collapses in competitive SERPs.

This is the framework we use when auditing South African businesses — from Cape Town service companies to national eCommerce brands.

Let’s break it down properly.

---

Layer 1: Crawl — Can Search Engines Access Your Site Efficiently?

Crawling is the foundation. If Googlebot cannot discover or traverse your site architecture cleanly, your content does not compete — it simply exists.

What We Audit at the Crawl Layer

1. Robots.txt Conflicts

• Accidental disallow rules
• Overly aggressive blocking of parameter URLs
• Blocking JavaScript or CSS resources
• Legacy CMS exclusions that were never cleaned up

Even a single misplaced disallow directive can suppress entire service sections.

---

2. XML Sitemap Hygiene

We check:

• Only canonical URLs included
• No 3xx, 4xx, or 5xx responses
• No noindex pages inside sitemap
• Logical segmentation (services, categories, blog, etc.)

Sitemaps should reinforce architecture — not contradict it.

---

3. Orphan Pages

Orphaned URLs often exist after redesigns or CMS migrations.

We identify:

• Pages in sitemap not internally linked
• Pages indexed but not linked
• High-value pages buried >4 clicks deep

Orphan pages dilute crawl equity and distort index signals.

---

4. Parameter & Faceted Navigation Issues

Common in eCommerce and larger sites:

• Filter URLs generating infinite crawl paths
• Session IDs in URLs
• Sorting parameters causing duplication

Unchecked faceted navigation can waste crawl budget rapidly.

---

5. Crawl Budget Efficiency

Especially important for larger sites.

We review:

• Crawl stats in Google Search Console
• Log file sampling (where available)
• Frequency of low-value URL crawling

If bots spend time crawling filters, they’re not crawling revenue pages.

---

Tools We Use at the Crawl Layer

• Screaming Frog (full crawl mapping)
• Google Search Console (Crawl Stats report)
• Sitebulb (visual architecture mapping)
• Log file analysis (where available)

---

Layer 2: Index — Is Google Storing the Right Pages?

Crawling does not equal indexing.

Indexation is where most ranking issues hide.

What We Audit at the Index Layer

1. Coverage Report Interpretation

We go beyond the surface.

We analyse:

• Crawled – currently not indexed
• Discovered – currently not indexed
• Duplicate without user-selected canonical
• Alternate page with proper canonical

Each of these signals tells a different story.

---

2. Soft 404s

Google sometimes treats thin or low-value pages as soft 404s.

Common triggers:

• Very low word count
• Auto-generated template pages
• Thin location landing pages
• Expired product pages not handled correctly

Soft 404 inflation often suppresses domain-level trust.

---

3. Canonical Conflicts

We check for:

• Canonical loops
• Self-referencing inconsistencies
• Canonical pointing to non-indexable URLs
• Pagination misconfiguration

Canonical chaos can silently block ranking gains.

---

4. Noindex Misuse

Developers often:

• Leave staging noindex directives live
• Noindex category pages accidentally
• Apply noindex to paginated archives incorrectly

These errors rarely surface in basic audits — but they devastate growth.

---

5. Internal Linking Depth

We measure:

• Click depth of service pages
• Contextual anchor strength
• Hub-spoke architecture presence
• Authority flow between content and commercial pages

Pages beyond depth 3 struggle in competitive verticals.

---

6. Index Bloat vs Under-Indexing

Two common extremes:

Index Bloat

• Low-value tag pages indexed
• Thin search result pages indexed
• Duplicate filter URLs indexed

Under-Indexing

• High-value service pages not indexed
• Blog content stuck in “Discovered – not indexed”
• Slow publication processing

Both scenarios require structural fixes — not content rewrites.

---

Layer 3: Render — What Does Google Actually See?

Rendering is where modern technical SEO becomes advanced.

Google renders JavaScript. But not perfectly. And not instantly.

If rendering fails, rankings fail.

What We Audit at the Render Layer

1. JavaScript Rendering Gaps

We check:

• Content loaded only after user interaction
• Tabs hiding core content
• Delayed API calls populating product info
• React/Angular hydration timing issues

If content doesn’t exist in rendered HTML, it may not exist for ranking.

---

2. Core Web Vitals (Including INP)

INP (Interaction to Next Paint) replaced FID.

We evaluate:

• Field data (CrUX)
• Lab data (Lighthouse)
• JavaScript execution delays
• Long tasks >50ms
• Third-party script impact

Performance affects both user conversion and algorithmic trust.

Especially in South Africa, where device and network variability is high.

---

3. Lazy Loading Errors

Improper lazy loading can:

• Block image indexing
• Prevent content rendering
• Break LCP signals

We verify:

• Native lazy loading usage
• Fallback behavior
• Image dimensions defined properly

---

4. Structured Data Validation

We check:

• Schema matches visible content
• No markup injected post-load
• No mismatched product data
• No policy violations

Structured data is eligibility — not a guarantee. But incorrect markup can remove eligibility entirely.

---

5. Mobile-First Rendering

Google indexes mobile-first.

We confirm:

• Content parity between desktop and mobile
• No hidden mobile text
• Correct responsive breakpoints
• No mobile-only canonical errors

---

How We Prioritise Fixes

Not all issues matter equally.

We use a 4-factor priority model:

1. Revenue Impact
2. Crawl/Index Suppression Risk
3. Technical Risk
4. Implementation Effort

We classify fixes into:

Phase 1 – Structural Blockers

• Canonical errors
• Noindex conflicts
• Crawl traps
• Core template issues

These must be resolved first.

---

Phase 2 – Authority Reinforcement

• Internal linking optimisation
• Schema refinement
• Hub architecture
• Content consolidation

---

Phase 3 – Performance & Refinement

• INP optimisation
• JavaScript slimming
• UX improvements
• Conversion path fixes

This phased model prevents teams from “optimising around structural damage.”

---

Real-World Example (Anonymised South African Case)

A mid-sized service business approached us after plateauing on page 2–3 for core keywords.

Audit findings:

• Primary service page 4 clicks deep
• Canonical tag misconfigured on location pages
• 37 low-value tag pages indexed
• Internal linking pointing mostly to blog content

Phase 1 fixes:

• Canonical correction
• Deindex low-value tags
• Re-architect internal linking

Result:

• Service page moved to depth 2
• Indexed pages reduced by 18%
• Rankings improved within 6–8 weeks
• Top 5 visibility achieved for primary keyword cluster

No content rewrite was required.

Only structural correction.

---

FAQ

What is a technical SEO audit?

A structured evaluation of crawlability, indexation, rendering, performance, and site architecture to identify structural barriers preventing search visibility.

How often should one be done?

For most businesses, once annually — or after any major site migration or redesign.

How long does it take?

A proper audit typically requires 1–2 weeks, depending on site size and complexity.

What tools are required?

At minimum:

• Screaming Frog
• Google Search Console
• Lighthouse
• Schema validation tools
• Log analysis (for larger sites)

Is Core Web Vitals still important in 2026?

Yes. Performance remains a foundational signal, particularly INP and LCP, which affect user experience and conversion quality.

---

Why This Matters More in the AI-Era

Search visibility is increasingly layered.

AI systems pull from well-structured, technically sound, clearly indexed content.

If your site architecture is unstable:

• You reduce citation probability
• You reduce eligibility for rich features
• You increase algorithmic distrust

Technical SEO is infrastructure.

Without infrastructure, authority cannot compound.

---

How We Run Technical Audits in Cape Town

For Cape Town and South African businesses, we adapt audits to:

• Local hosting environments
• Network variability
• Mobile-first user behaviour
• Service-business internal linking needs
• Map Pack integration considerations

Our approach is calm, diagnostic, and execution-focused.

No 60-page fluff reports.

Just:

• Structural findings
• Prioritised roadmap
• Implementation clarity

---

If you’d like a structured Crawl → Index → Render breakdown of your site, we can walk through it together and identify what is actually limiting visibility.

No packages.
No inflated promises.

Just structural truth.