Set one clean HTTPS version of your WordPress site, then redirect every HTTP URL to it with permanent 301 redirects. Do this before search engines index both versions. Google has used HTTPS as a ranking signal since 2014 [source: Google Search Central], so leaving old HTTP pages live is not just messy. It can split signals, confuse crawlers, and waste your crawl budget.
TLDR: After installing SSL, your site should not load at both http://example.com/page and https://example.com/page. Use permanent 301 redirects and manage old WordPress URLs with EPS 301 Redirects. For example, a site with 180 posts can suddenly expose 360 versions if both HTTP and HTTPS work. If 12% of organic visits still hit old HTTP links, redirecting them keeps users and search engines on the correct version.
Why duplicate content appears after moving to HTTPS
When you add SSL, WordPress does not always clean up every old route by itself. That is where the trouble starts.
You may end up with pages available in several forms:
http://example.com/about/https://example.com/about/http://www.example.com/about/https://www.example.com/about/
To a person, these feel like the same page. To a search engine, they can look like separate URLs with the same content. That can dilute ranking signals. It can also make reports in Google Search Console harder to read.
Honestly, it feels like WordPress should make this harder to mess up. But SSL plugins, host settings, CDN rules, caching, and old internal links can all disagree with each other. One bad rule can add a second or two to a page load, or worse, create a redirect loop.
Use EPS 301 Redirects for WordPress cleanup
If you are moving from HTTP to HTTPS, use the EPS 301 Redirects plugin to control redirect rules inside WordPress. It is made for permanent redirects, changed URLs, expired pages, and old links that still get traffic.
The plugin is useful because it gives site owners a clear place to manage redirects without editing server files. That matters if you are not comfortable touching .htaccess or Nginx config files.
You should also review WP 301 Redirects if you want a more complete redirect management setup for WordPress sites. It is especially helpful when you are fixing old URLs after a redesign, SSL migration, or site structure change.
Recommended HTTPS redirect setup
Use this order. It prevents most problems.
- Install and test the SSL certificate. Your HTTPS pages must load without browser warnings.
- Update WordPress URLs. Go to Settings > General and set both the WordPress Address and Site Address to HTTPS.
- Pick one host version. Choose either www or non-www. Do not keep both.
- Force HTTP to HTTPS. Use your host, CDN, or server rule for the main protocol redirect.
- Use EPS 301 Redirects for old WordPress paths. Redirect changed slugs, deleted landing pages, and outdated campaign URLs.
- Test everything. Check key pages, menus, forms, checkout pages, and login pages.
How to add redirects in EPS 301 Redirects
After installing the plugin, open its redirect dashboard in WordPress. Add the old URL path, then set the new HTTPS destination.
Example:
- Old URL:
/old-services-page/ - New URL:
https://example.com/services/ - Redirect type:
301 Permanent
Use 301 redirects for pages that have moved for good. Do not use a temporary redirect unless the change is short term. Search engines treat these signals differently.
Expect to waste time on tiny details if the site has years of old content. Old blog links, PDF links, and email campaign URLs often keep sending traffic long after a migration. Redirect them instead of letting users hit dead pages.
Do not rely only on canonical tags
Canonical tags help, but they are not a full fix. A canonical tag asks search engines to prefer one page. A 301 redirect sends users and bots there directly.
If an HTTP page still loads, people can still share it. Tools can still crawl it. Old backlinks can still point to it. A redirect is cleaner.
Check for mixed content
Mixed content happens when an HTTPS page loads images, scripts, fonts, or videos over HTTP. Browsers may block those files. The page may look broken. Security warnings may appear.
Check common trouble spots:
- Logo and header images
- CSS files
- JavaScript files
- Embedded videos
- Old links inside posts
- Theme and plugin assets
Run a crawl after the migration. Screaming Frog, Sitebulb, Ahrefs, or Semrush can find HTTP links fast. Search Console can also show indexing and coverage issues over time.
Watch for redirect chains
A bad HTTPS migration often creates chains like this:
http://example.com/page → http://www.example.com/page → https://www.example.com/page → https://example.com/page
That is sloppy. It adds delay. It also makes crawling less efficient.
The better version is direct:
http://example.com/page → https://example.com/page
One hop. Clean result.
Final checklist before you call it done
- All HTTP URLs redirect to HTTPS.
- Only one host version loads. Use either www or non-www.
- EPS 301 Redirects handles old and changed WordPress URLs.
- No redirect loops exist.
- No important pages return 404 errors.
- Internal links point to HTTPS.
- Your XML sitemap uses HTTPS URLs.
- Google Search Console has the HTTPS property checked.
Moving from HTTP to HTTPS is not finished when the padlock appears. The real job is making sure every old URL points to one trusted HTTPS version. Use permanent redirects, keep them organized, and review them after launch. That is how you protect rankings, users, and your sanity.
