Traffic Disappeared After Moving To HTTPS: How to Fix It (South African Guide)

Key Takeaways:
– A sudden traffic drop after moving to HTTPS is usually caused by technical implementation issues, not HTTPS itself.
– The most common culprits are redirect mistakes, mixed content, incorrect canonical tags, and tracking problems.
– You can often recover lost rankings by systematically auditing redirects, indexing, internal links, and analytics.
– South African sites, especially on local hosts, often struggle with duplicate HTTP/HTTPS versions & non-www/www conflicts.
– If you’re stuck, a specialist technical SEO audit can speed up recovery and prevent long-term damage to your organic visibility.

Introduction

If your traffic disappeared after moving to HTTPS, you’re not alone. Many South African businesses migrate to SSL because Google says HTTPS is a ranking signal, only to wake up to a painful surprise: less traffic, fewer enquiries, and a very nervous management team.

When your website is your main lead source for Cape Town, Johannesburg, Pretoria, Durban, or nationwide, this is more than an inconvenience – it directly hits revenue. The good news is that HTTPS itself is not the problem. The real issue is usually how the move was implemented.

In this guide, we’ll unpack the most common reasons traffic drops after HTTPS migration, how to diagnose what went wrong, and the practical steps you can take to recover. We’ll look at examples from South African businesses, explain the technical bits in plain language, and show you which fixes matter most.

If your organic traffic has tanked after going secure, keep reading. By the end, you’ll know exactly where to look, what to fix, and when it makes sense to bring in an SEO specialist.

Why Your Traffic Disappeared After Moving To HTTPS

When traffic disappears after moving to HTTPS, it usually comes down to a handful of technical SEO issues. Understanding these will help you diagnose your specific situation.

HTTPS Itself Is Not the Enemy

Google has been encouraging HTTPS for years and openly states that HTTPS is a lightweight ranking signal. Secure sites are not expected to lose rankings just because they’ve moved to HTTPS.

If you see:

A sharp drop in organic traffic
A lot of URLs suddenly de-indexed
Old HTTP URLs still showing in search

…then the problem is almost always implementation errors, not HTTPS.

Typical Causes of HTTPS-Related Traffic Loss

Here are the most common reasons South African sites lose traffic after going secure:

Broken or incorrect redirects (HTTP not properly redirecting to HTTPS)
Mixed content issues, making Google treat pages as “not fully secure”
Canonical tags still pointing to HTTP versions
Multiple versions of your site accessible (HTTP/HTTPS, www/non-www)
Analytics / tracking misconfiguration (it looks like traffic disappeared, but it’s just being recorded elsewhere)
Slow HTTPS performance due to poor hosting or misconfigured SSL
Incorrect XML sitemaps still pointing to HTTP URLs

The rest of this article walks you through identifying which of these is affecting your site and how to fix them step by step.

Step 1: Confirm the Drop and Where It Happened

Before you panic, you need to confirm what actually dropped. Was it organic traffic, all traffic, or just reported data?

Check Google Analytics (GA4)

Start in your analytics platform:

Filter by source/medium
- Look at Organic Search only.
- Compare traffic 2–4 weeks before and after the HTTPS move.
Check for data gaps
- Is there a day where tracking just stops?
- Did your default URL or domain change in the settings at the same time?
Segment by country
- Focus on South Africa traffic to see how local users were affected.

If organic traffic from South Africa dropped sharply while direct and referral stayed stable, it’s likely an SEO/technical issue, not a full-site tracking problem.

Check Google Search Console (GSC)

Next, check your GSC property:

Performance report
- Compare clicks, impressions, and average position before/after migration.
- Look at Queries and Pages. Are specific landing pages hit harder?
Coverage report
- Look for spikes in Errors or Excluded URLs right after going HTTPS.
- Pay attention to “Duplicate, submitted URL not selected as canonical” and “Indexed, not submitted in sitemap”.
HTTPS report (if available)
- Look for warnings like “HTTPS is invalid and might prevent it from being indexed”.

If your impression count has dropped along with clicks, Google is likely indexing fewer of your pages or preferring the wrong versions.

Step 2: Audit Your Redirects and URL Versions

When traffic disappeared after moving to HTTPS, the first suspect should be your redirects.

Make Sure HTTP Redirects to HTTPS (One Version Only)

Your site should have one canonical version, typically:

`https://www.example.co.za` or
`https://example.co.za`

Every other variation must 301 redirect to that single version.

Check these versions of your site:

`http://example.co.za`
`http://www.example.co.za`
`https://example.co.za`
`https://www.example.co.za`

Only one should be the “final destination”; the others should redirect there via 301 redirects.

How to Test Redirects

You can use:

Your browser address bar (quick test)
Online redirect checkers
curl -I in terminal (if you’re technical)

You’re looking for:

301 status codes from HTTP to HTTPS
No redirect loops (A → B → A → B)
No chains (A → B → C → D; should be A → D directly if possible)

Common South African Hosting Problems

On many local hosting providers (including some popular Cape Town and Johannesburg-based hosts), it’s common to see:

Only home page redirected, but inner pages (e.g. /services/) left on HTTP
Hosting-level redirects conflicting with .htaccess rules
Temporary (302) redirects instead of permanent (301) redirects

This confuses Google, creates duplicate content, and can split your link equity across versions, leading to ranking and traffic loss.

Step 3: Fix Canonical Tags, Sitemaps and Internal Links

If your traffic disappeared after moving to HTTPS, and you’ve fixed redirects, the next priority is your signals of canonicality – how you tell Google which version of each page is “the real one”.

Update Canonical Tags to HTTPS

Inspect a few core pages’ HTML (Home, Services, Blog, Contact):

Look for:

<link rel="canonical" href="http://www.example.co.za/page/">

If your canonical tags still point to HTTP URLs, you’re essentially telling Google:

“Please index the non-secure version, not this one.”

You must:

Update all canonical tags to HTTPS
Ensure they match the final redirected URL exactly (including www vs non-www and trailing slashes)

Most CMSs like WordPress, Shopify, or Wix will handle this for you once you update the site URL settings, but it’s worth checking manually.

Update XML Sitemaps

Your XML sitemap should only contain HTTPS URLs.

Check:

`https://www.example.co.za/sitemap.xml` (or similar)
Verify that every URL begins with `https://` and the correct domain version.

Then:

Generate a fresh sitemap (via SEO plugin or CMS).
Submit it in Google Search Console → Sitemaps.
Remove or deprecate old HTTP sitemaps if they exist.

Fix Internal Links

Internal links pointing to HTTP can cause mixed signals and mixed content.

Inside your site’s content and menus:

Update navigation menus to HTTPS.
Run a search and replace in your database for http://yourdomain.co.za` →https://yourdomain.co.za`.
Don’t forget: images, PDFs, script references, and CSS may still be HTTP.

Many South African business sites that rebranded or rebuilt years back still have legacy HTTP links hiding in older blog posts, especially if you’ve been publishing since pre-2017.

Step 4: Resolve Mixed Content and Security Warnings

Google wants your pages to be fully secure. If your page loads over HTTPS but pulls images, scripts, or CSS over HTTP, it triggers mixed content.

What Is Mixed Content?

Example:

<img src="http://www.example.co.za/images/logo.png">

If the page URL is HTTPS but some assets are HTTP, browsers may:

Show a “Not fully secure” warning
Block certain scripts or resources
Affect user trust and potentially indexing

How Mixed Content Affects Traffic

Mixed content can:

Break key elements (menus, forms, analytics)
Cause poor user experience and low engagement
Lead to weaker ranking signals over time

On e-commerce sites (especially in fashion, electronics, and travel niches common in SA), blocked scripts can kill conversions.

How to Find and Fix Mixed Content

Use tools like:

Browser developer tools → Console (look for mixed content warnings)
Online mixed content scanners
SEO crawlers (Screaming Frog, Sitebulb) configured to check for HTTP assets

Then:

Update all asset URLs to HTTPS.
Where possible, use protocol-relative or root-relative URLs (e.g. /images/logo.png).
Re-run checks until all warnings disappear.

Step 5: Check Analytics and Tagging – Is It Really a Drop?

Sometimes it looks like traffic disappeared after moving to HTTPS, but your tracking is the problem, not your SEO.

Common Tracking Issues After HTTPS Migration

GA4 or UA code removed during the migration
Tracking code still loading from old HTTP script URL
Tag Manager not firing correctly because of blocked mixed content
Domain or property changes in config that broke reports
Cross-domain tracking changes (especially for payment gateways)

Quick Checks in GA4

Real-Time Report
- Visit your site in a private/incognito window.
- Check if your visit shows up in real-time analytics.
Tag Assistant / Debug tools
- Use browser extensions (e.g. Tag Assistant, GA4 DebugView).
- Confirm that page views and events are still firing.
Compare by channel
- If every channel (Direct, Organic, Paid, Referral) abruptly drops to zero, it’s probably not an SEO issue.

Many South African businesses discover that what looked like an SEO disaster was actually a misconfigured GA or GTM install after a developer “cleaned up” the header code.

Step 6: Monitor Indexing, Rankings, and Recovery Timeline

Once you’ve fixed the technical issues, you need to monitor how Google reacts.

How Long Does Recovery Take?

In many cases:

Minor issues fixed quickly: noticeable recovery in 1–2 weeks
Serious redirects/canonical problems: recovery in 4–8 weeks
Long-term damage (months of bad signals): may require a more comprehensive SEO recovery strategy

Google needs time to:

Recrawl your HTTP URLs
Follow redirects to HTTPS
Recognise the new canonical URLs
Recalculate rankings

Key Metrics to Watch in GSC

Check weekly:

Total clicks & impressions (Performance)
Average position for key queries
Index coverage (are more HTTPS URLs being indexed?)
Manual actions (just in case)

If impressions and indexed pages are moving in the right direction, you’re likely on the path to recovery, even if traffic hasn’t fully bounced back yet.

Common HTTPS Migration Mistakes Seen on South African Sites

At SEO Strategist, we’ve worked with many South African businesses whose traffic disappeared after moving to HTTPS. Certain patterns repeat, especially on local shared hosting and cheaper website builders.

Typical Local Scenarios

Dual Version Chaos
- http://example.co.za` andhttps://example.co.za` both live.
- `http://www.example.co.za` redirects somewhere different.
- Google indexes a mixture of them.
Partial Redirects Only
- Home page correctly redirects to HTTPS.
- Important landing pages like /attorney-cape-town or /electrician-johannesburg still serve on HTTP.
No Update to Business Citations
- External links (local directories, media, suppliers) still pointing to HTTP.
- Redirects are in place, but chains or 302s reduce link equity.
Botched CMS Settings
- WordPress Site URL and Home URL not both set to HTTPS.
- A mix of hard-coded internal HTTP links and HTTPS URLs.

Real-World Example (Anonymised)

A Pretoria-based professional services firm:

Migrated to HTTPS via hosting provider.
Only their homepage was redirected to HTTPS.
All service pages (which ranked for key terms like “tax consultant Pretoria”) remained on HTTP.
Canonicals still pointed to HTTP.
XML sitemaps listed HTTP URLs.

Result:

40–50% drop in organic traffic within 3 weeks.
Many previously top-3 rankings fell to page 2–3.

Fix:

Implement full-domain 301 redirects from HTTP to HTTPS.
Update canonical tags, sitemaps, and internal links.
Resubmit sitemaps to GSC and request reindexing of key pages.

Recovery:

Initial improvements in 10 days.
90–95% traffic restored in about 6 weeks.

Technical Checklist: Fixing Traffic Loss After HTTPS Migration

Here’s a step-by-step checklist you can use or share with your developer.

1. Redirects and URL Versions

[ ] Only one version of your domain is accessible:
- https://www.example.co.za` orhttps://example.co.za`
[ ] All other versions 301 redirect to that single version.
[ ] No redirect loops or long redirect chains.
[ ] All HTTP URLs 301 to their HTTPS equivalents.

2. Canonical Tags and Sitemaps

[ ] All <link rel="canonical"> tags point to HTTPS URLs.
[ ] Canonical URLs match the final URL exactly (with/without www, trailing slash).
[ ] XML sitemaps list only HTTPS URLs.
[ ] Old HTTP sitemaps removed or no longer submitted.

3. Internal Links and Assets

[ ] Navigation, footer, and contextual links use HTTPS URLs.
[ ] No internal links still pointing to HTTP versions.
[ ] All images, scripts, and stylesheets load over HTTPS (no mixed content).
[ ] Forms, iframes, and embedded content use HTTPS or appropriate secure embeds.

4. Analytics and Tracking

[ ] GA / GA4 code present on all critical pages.
[ ] Real-time analytics shows your own visits.
[ ] GTM or other tracking containers are loading correctly over HTTPS.
[ ] Domain settings updated if you changed from non-www to www, or vice versa.

5. Google Search Console

[ ] Correct HTTPS property added and verified in GSC.
[ ] XML sitemap submitted for HTTPS version.
[ ] Coverage report checked for new errors.
[ ] Manual actions checked and cleared (if any).

Working through this list systematically fixes the vast majority of “traffic disappeared after moving to HTTPS” scenarios we see.

Comparing a Good vs Bad HTTPS Migration

Use this comparison to see where your site stands:

Aspect	Good HTTPS Migration	Bad HTTPS Migration (Risk of Traffic Loss)
Redirects	All HTTP → HTTPS via 301, one canonical version	Multiple live versions, 302s, loops, or partial redirects
Canonical Tags	All point to HTTPS	Many still point to HTTP or inconsistent domains
XML Sitemap	Only HTTPS URLs, submitted in GSC	HTTP URLs remain, sitemap not updated or not resubmitted
Internal Links	Updated to HTTPS, no mixed content	Mixed HTTP/HTTPS internal links and assets
Analytics Tracking	Confirmed working over HTTPS	Missing, broken, or blocked analytics / GTM
GSC Setup	HTTPS property verified and used for monitoring	Only old HTTP property monitored, no new sitemap submitted
Performance (Speed)	SSL well-configured, minimal speed impact	Slower load times due to SSL misconfig or poor hosting

If your situation looks more like the right-hand column, it explains why your traffic disappeared after moving to HTTPS.

When to Bring in a Professional SEO Team

You can absolutely handle basic checks yourself. But there are situations where bringing in a specialist saves time, money, and stress:

The traffic drop is over 40% and has lasted more than a month.
You rely heavily on organic search for leads or e-commerce sales.
Your site uses a complex setup (custom CMS, multi-domain, subdomains).
You’ve made changes but don’t see any improvements in GSC or Analytics.

A technical SEO audit from a team that regularly handles algorithm recovery and migration issues can quickly pinpoint:

Which technical factors are stopping your HTTPS site from ranking
Where link equity is being diluted or lost
How to prioritise fixes for the fastest recovery

If you’re a South African business and feel out of your depth, this is exactly the kind of problem SEO Strategist (based in Cape Town, working nationally) deals with every week.

Frequently Asked Questions

1. Why did my traffic disappear after moving to HTTPS?

In most cases, traffic disappears after moving to HTTPS because of technical SEO mistakes, not because HTTPS is bad. Common issues include incorrect redirects, mixed content, wrong canonical tags, and outdated sitemaps pointing to HTTP URLs. Fixing these signals usually leads to recovery over the following weeks.

2. How long does it take to recover traffic after an HTTPS migration?

If you fix issues quickly, you can often see early signs of recovery within 1–2 weeks, with more substantial recovery in 4–8 weeks. The exact timeline depends on your site size, crawl rate, and how severe the implementation errors were.

3. Do I need to update all my backlinks to HTTPS?

You don’t have to, as long as your HTTP to HTTPS redirects are set up correctly as 301 redirects. However, updating your most important backlinks (from strong South African sites, directories, or partner sites) to point directly to HTTPS can slightly improve efficiency and reduce redirect chains.

4. Should I worry about mixed content warnings on my site?

Yes. Mixed content can lead to security warnings in browsers, blocked scripts, and a poor user experience. Over time, these factors can reduce your rankings and traffic. It’s best practice to ensure every asset loads over HTTPS and that no HTTP resources remain.

5. Do I need a new Google Search Console property for HTTPS?

Yes. Google treats HTTP and HTTPS as separate properties. You should create and verify a new HTTPS property in Google Search Console, submit your HTTPS sitemap, and monitor that property going forward.

6. Can HTTPS migration affect my rankings on Google.co.za specifically?

Yes, if implemented incorrectly, it can hurt your visibility on Google.co.za and local search results in South Africa. Google’s systems are global, but ranking changes will definitely be felt on your local SERPs, which means fewer local enquiries from cities like Cape Town, Johannesburg, and Durban.

Conclusion

When your traffic disappeared after moving to HTTPS, it can feel like you’ve broken everything by trying to do the right thing. In reality, HTTPS itself is not the enemy. The real problem usually lies in redirects, canonicals, sitemaps, internal links, mixed content, or tracking – all of which can be fixed.

By systematically checking your URL versions, updating your canonical signals, cleaning up internal links and assets, and confirming that analytics is working correctly, you give Google a clear, consistent picture of your new secure site. With those signals aligned, rankings and traffic typically recover over the following weeks.

If you’re a South African business and your organic traffic is a key driver of leads and sales, you don’t need to face this alone. SEO Strategist, based in Cape Town and working with clients across South Africa, specialises in traffic recovery after technical changes and algorithm updates.

If your traffic has dropped and you’re not sure why, request a free SEO audit or consultation. We’ll help you diagnose whether your HTTPS migration, a Google update, or something else is holding you back – and map out a practical plan to restore and grow your organic visibility.

Traffic Disappeared After Moving To Https