Moving to HTTPS is safe for SEO when Google receives one consistent message: every old HTTP URL permanently redirects, in a single hop, to the same page on HTTPS, and every internal link, canonical tag and sitemap entry already uses the new address. Rankings may wobble for a few weeks while Google recrawls the site; they settle when the steps below are done in this order.

Step 1: prepare before you change anything

  • Take a full backup of the files and the database, and download it.
  • Export a list of your URLs from the sitemap, your analytics and an SEO crawler, so you can check every important page after the move.
  • Decide on the final form of the address, with or without www. Pick one now, because every extra variant becomes another redirect to manage.
  • List all the hostnames you use (the main domain, www, subdomains) so the certificate covers each of them.
  • Note current organic traffic and key rankings as a baseline, and choose a quiet day for the switch.

Step 2: install the certificate and test HTTPS first

Install the certificate on every hostname on your list, then open the https:// version of a few pages before redirecting anything. The browser should show a valid connection with no warnings. On cPanel-based hosting, the SSL/TLS Status tool shows which domains and subdomains are covered. If you need a different validation level or a wildcard, compare the options in the DV vs OV vs EV guide.

Step 3: update internal links and site settings

Internal links that still start with http:// cause needless redirects and mixed content, so fix them at the source:

  • WordPress: change the WordPress Address and Site Address to https:// under Settings, then General. Replace old URLs in the database with a search-and-replace tool that handles serialized data, such as WP-CLI search-replace or a dedicated plugin, never with a plain text edit of the SQL file.
  • Custom sites: update the base URL in the configuration file and any absolute links in templates and emails.
  • Assets: use https:// or relative paths for images, scripts, style sheets and fonts.

Step 4: find and fix mixed content

Mixed content means an HTTPS page loads some resources over HTTP. Browsers block insecure scripts, style sheets and iframes outright, which can break menus, sliders, forms or payment widgets, and they either upgrade or block insecure images and media. Open the browser's developer tools, check the Console on each key template (home, article, product, cart, contact), and fix every reported URL where it comes from: theme files, page builder settings, widgets or links typed into content. Replace third-party embeds that do not support HTTPS. The Content-Security-Policy directive upgrade-insecure-requests can act as a temporary safety net, but fix the sources rather than relying on it.

Step 5: redirect HTTP to HTTPS with 301s

Use permanent (301) server-side redirects from each old URL to the same path on HTTPS, keeping any query string. Never send all old URLs to the home page; that throws away the relevance each page has built. Combine the protocol and www decisions so that every variant reaches the final address in one hop:

Old addressShould redirect to
http://example.com/pagehttps://example.com/page
http://www.example.com/pagehttps://example.com/page
https://www.example.com/pagehttps://example.com/page

In cPanel, the Domains tool has a Force HTTPS Redirect switch for each domain; if you also redirect www to non-www (or the reverse), check that the result is still one hop, as a single combined rewrite rule in .htaccess may be needed on Apache or LiteSpeed. On a VPS running Nginx, a server block that returns 301 to the HTTPS address does the same job. Afterwards, test a sample of old URLs and confirm each returns one 301 followed by a 200, with no chains or loops.

Step 6: canonicals, sitemaps and other signals

  • Point the canonical tag on every page to its HTTPS URL; a canonical that still says HTTP contradicts your redirect.
  • Regenerate the XML sitemap with HTTPS URLs only, and reference it in robots.txt.
  • Update hreflang annotations if you have Arabic and English versions, plus Open Graph URLs and structured data.
  • Do not block the old HTTP URLs in robots.txt; Google needs to crawl them to see the redirects.

Step 7: Search Console, analytics and integrations

  • Add the HTTPS version to Google Search Console, or use a Domain property verified through DNS, which covers HTTP, HTTPS and all subdomains together.
  • Submit the new sitemap, and use URL Inspection on a few key pages to confirm Google has picked the HTTPS URL as canonical.
  • You do not need the Change of Address tool; it is meant for moving to a different domain, not for a protocol change.
  • Update the site URL in your analytics property, ad accounts, social profiles and any backlinks you control.
  • Update payment gateway return URLs, webhooks and API callbacks that still point to HTTP.

Step 8: monitor, then lock it in with HSTS

For the following weeks, watch the page indexing report in Search Console, 404s and redirect errors in your logs, and organic traffic per landing page against your baseline. Keep the redirects in place permanently; removing them later breaks old links and bookmarks. Once everything has been stable for a while, enable HSTS (the Strict-Transport-Security header) so browsers go straight to HTTPS. Start with a short max-age and raise it gradually, and only consider HSTS preloading when every subdomain works over HTTPS, because preloading is hard to undo.

Mistakes that cost rankings

  • Temporary (302) redirects where permanent 301s belong.
  • Redirect chains, such as HTTP www to HTTPS www and then to HTTPS without www.
  • Canonical tags or the sitemap still listing HTTP URLs.
  • Letting the certificate expire, which greets every visitor with a full-page warning.

If you are still weighing whether the switch is worth it, read why your website needs SSL. If you host with EngHosting, a free SSL certificate appears on the shared, WordPress and reseller plan pages, so step 2 is usually just a matter of activating it; VPS and dedicated server owners, or anyone who needs OV or EV, can order a certificate from the SSL certificates page.

Useful links: Shared Hosting, Linux VPS, Domain Registration, Contact Us.

Need the right hosting recommendation?

Tell EngHosting your website type and budget, and our team will help you choose the right Egyptian or Arabic hosting plan.

Contact on WhatsApp