{"id":22316,"date":"2026-08-27T14:55:14","date_gmt":"2026-08-27T12:55:14","guid":{"rendered":"https:\/\/www.curiaweb.ch\/?post_type=docs&p=22316"},"modified":"2026-08-27T14:55:15","modified_gmt":"2026-08-27T12:55:15","password":"","slug":"activate-ssl-https-wordpress","status":"publish","type":"docs","link":"https:\/\/www.curiaweb.ch\/en\/hilfe\/wordpress\/ssl-wordpress-https-aktivieren\/","title":{"rendered":"Activate SSL in WordPress: Securely migrate website to HTTPS"},"content":{"rendered":"

A WordPress website should nowadays fundamentally have HTTPS<\/strong> be accessible. HTTPS encrypts the connection between your visitors' browser and the web server, thereby protecting, for example, login data, form inputs, and other transmitted information from being easily intercepted during transmission.<\/p>\n\n\n\n

For HTTPS to work, your website requires a valid SSL\/TLS certificate<\/strong>. With CURIAWEB web hosting, the technical foundation for this is already provided. Nevertheless, especially with existing WordPress installations, it may be necessary to update WordPress itself from http:\/\/<\/code> on https:\/\/<\/code> to convert.<\/p>\n\n\n\n

\n

Important:<\/strong> Having an existing SSL certificate does not automatically mean that your entire WordPress website is already being correctly served via HTTPS. WordPress, internal URLs, and redirects must also be configured correctly.<\/p>\n<\/blockquote>\n\n\n\n

What is the difference between SSL, TLS, and HTTPS?<\/h2>\n\n\n\n

The terms SSL, TLS, and HTTPS are often used interchangeably, but technically they do not mean the exact same thing.<\/p>\n\n\n\n

    \n
  • SSL<\/strong> The original technology for encrypting connections. The term \u201eSSL certificate\u201c is still commonly used today.<\/li>\n\n\n\n
  • TLS<\/strong> The modern successor to SSL and the encryption technology actually used today.<\/li>\n\n\n\n
  • HTTPS:<\/strong> The encrypted version of HTTP. The \u201eS\u201c stands for \u201eSecure\u201c.<\/li>\n<\/ul>\n\n\n\n

    When people in everyday life talk about an SSL certificate, they usually mean a certificate that enables an encrypted HTTPS connection.<\/p>\n\n\n\n

    Why should WordPress use HTTPS?<\/h2>\n\n\n\n

    HTTPS is not only relevant for online shops or websites with sensitive customer data. A standard corporate website or blog should also be transmitted with encryption.<\/p>\n\n\n\n

    This applies in particular to:<\/p>\n\n\n\n

      \n
    • WordPress logins via \/wp-admin\/<\/code><\/li>\n\n\n\n
    • Contact forms<\/li>\n\n\n\n
    • Customer and user accounts<\/li>\n\n\n\n
    • WooCommerce stores<\/li>\n\n\n\n
    • Comments and other form inputs<\/li>\n\n\n\n
    • personal data transmitted via the website<\/li>\n<\/ul>\n\n\n\n

      Modern browsers also label websites without HTTPS as not secure or warn users about an unencrypted connection. HTTPS is therefore part of the basic technical configuration of a professional website today.<\/p>\n\n\n\n

      SSL at CURIAWEB<\/h2>\n\n\n\n

      With CURIAWEB hosting packages, SSL certificates are available for the hosted domains. Certificate management takes place at the hosting server level or via cPanel.<\/p>\n\n\n\n

      Before making any changes to WordPress, you should therefore first check whether a valid certificate already exists for the domain in question.<\/p>\n\n\n\n

      A simple initial check is to access your website via:<\/p>\n\n\n\n

      \nhttps:\/\/deine-domain.ch\n<\/div><\/figure>\n\n\n\n

      Replace your-domain.ch<\/code> through your actual domain.<\/p>\n\n\n\n

      If the website loads without a certificate warning, a valid certificate is generally present for the domain being accessed.<\/p>\n\n\n\n

      \n

      Note:<\/strong> Do not switch WordPress to HTTPS as long as there is no working SSL certificate for the domain. Otherwise, your website may no longer be accessible correctly after the change.<\/p>\n<\/blockquote>\n\n\n\n

      Before switching to HTTPS: Create a backup<\/h2>\n\n\n\n

      With a new WordPress installation, HTTPS is often already correctly set up. With an older website, however, numerous URLs with http:\/\/<\/code> be stored in the database.<\/p>\n\n\n\n

      Therefore, you should always create a recent backup before making major changes to an existing website. This applies especially when URLs within the WordPress database need to be replaced later.<\/p>\n\n\n\n

      A backup should at least contain:<\/p>\n\n\n\n

        \n
      • the WordPress files<\/li>\n\n\n\n
      • the WordPress database<\/li>\n\n\n\n
      • the file wp-config.php<\/code><\/li>\n\n\n\n
      • additional configuration files, if necessary<\/li>\n<\/ul>\n\n\n\n
        \n

        Recommendation:<\/strong> Never make changes to URLs or the WordPress database without a current backup. An incorrect search and replace can damage a WordPress installation.<\/p>\n<\/blockquote>\n\n\n\n

        Switch WordPress to HTTPS<\/h2>\n\n\n\n

        If the SSL certificate is working, you can check which URLs WordPress is currently using.<\/p>\n\n\n\n

        To do this, log in to your WordPress admin area and open:<\/p>\n\n\n\n

        Settings \u2192 General<\/strong><\/p>\n\n\n\n

        There you will normally find the two fields:<\/p>\n\n\n\n

          \n
        • WordPress Address (URL)<\/strong><\/li>\n\n\n\n
        • Website address (URL)<\/strong><\/li>\n<\/ul>\n\n\n\n

          In a normal WordPress installation, these might look like this, for example:<\/p>\n\n\n\n

          http:\/\/deine-domain.ch<\/code><\/p>\n\n\n\n

          For HTTPS they must be as follows:<\/p>\n\n\n\n

          \nhttps:\/\/deine-domain.ch\n<\/div><\/figure>\n\n\n\n

          So change it http:\/\/<\/code> in https:\/\/<\/code> and save the settings.<\/p>\n\n\n\n

          \n

          Warning:<\/strong> Only change these URLs if you are sure that the SSL certificate for the domain is working. Incorrect information for \u201eWordPress Address\u201c or \u201eSite Address\u201c can cause the website or WordPress admin area to become inaccessible.<\/p>\n<\/blockquote>\n\n\n\n

          Why are there two different WordPress URLs?<\/h2>\n\n\n\n

          On many websites WordPress Address<\/strong> and Website address<\/strong> identical. But that does not necessarily have to be the case.<\/p>\n\n\n\n

          The WordPress Address<\/strong> denotes the location where the WordPress installation is technically located. The Website address<\/strong> refers, on the other hand, to the URL visitors use to access the website.<\/p>\n\n\n\n

          For special installations, these values can be different, for example if WordPress was installed in a subdirectory.<\/p>\n\n\n\n

          Therefore, do not simply change both values in an existing custom configuration without first checking how WordPress was installed.<\/p>\n\n\n\n

          Automatically redirect HTTP to HTTPS<\/h2>\n\n\n\n

          After the switch, the unencrypted HTTP version of your website should not remain accessible parallel to the HTTPS version.<\/p>\n\n\n\n

          A call from:<\/p>\n\n\n\n

          http:\/\/deine-domain.ch<\/code><\/p>\n\n\n\n

          should automatically switch to:<\/p>\n\n\n\n

          \nhttps:\/\/deine-domain.ch\n<\/div><\/figure>\n\n\n\n

          be forwarded.<\/p>\n\n\n\n

          This redirection ensures that visitors and search engines consistently use the encrypted version.<\/p>\n\n\n\n

          Depending on the server configuration, HTTPS redirection may already be set up automatically or can be enabled via the hosting configuration. An additional manual modification of the file .htaccess<\/code> is therefore not necessary in every case.<\/p>\n\n\n\n

          \n

          Important:<\/strong> Do not just copy any HTTPS redirect from the internet into your .htaccess<\/code>. Incorrect or duplicate redirect rules can cause redirect loops and make your website inaccessible.<\/p>\n<\/blockquote>\n\n\n\n

          What is mixed content?<\/h2>\n\n\n\n

          After switching to HTTPS, the website can in principle be accessible via HTTPS and still continue to load insecure content. This problem is called Mixed Content<\/strong> referred to as.<\/p>\n\n\n\n

          A classic example:<\/p>\n\n\n\n

          The actual page is loaded via:<\/p>\n\n\n\n

          \nhttps:\/\/deine-domain.ch\n<\/div><\/figure>\n\n\n\n

          However, one image within this page is still being loaded via:<\/p>\n\n\n\n

          http:\/\/deine-domain.ch\/wp-content\/uploads\/beispiel.jpg<\/code><\/p>\n\n\n\n

          This means the HTTPS page still contains an unencrypted HTTP resource.<\/p>\n\n\n\n

          Mixed Content can occur, for example, in:<\/p>\n\n\n\n

            \n
          • pictures<\/li>\n\n\n\n
          • Stylesheets (CSS)<\/li>\n\n\n\n
          • JavaScript files<\/li>\n\n\n\n
          • Web fonts<\/li>\n\n\n\n
          • Videos or embedded media<\/li>\n\n\n\n
          • Theme settings<\/li>\n\n\n\n
          • Page Builder<\/li>\n\n\n\n
          • Plugins<\/li>\n\n\n\n
          • hard-coded URLs<\/li>\n<\/ul>\n\n\n\n

            Why do old HTTP URLs persist after the migration?<\/h2>\n\n\n\n

            WordPress stores numerous information in its database. If a website was originally built using HTTP, complete URLs may still be stored there with http:\/\/<\/code> be saved.<\/p>\n\n\n\n

            This affects, for example, images, links, widgets, theme settings, or page builder content.<\/p>\n\n\n\n

            The change of the WordPress address under Settings \u2192 General<\/strong> does not necessarily replace such already saved URLs automatically.<\/p>\n\n\n\n

            Therefore, it may be necessary to specifically target old URLs in the database from:<\/p>\n\n\n\n

            http:\/\/deine-domain.ch<\/code><\/p>\n\n\n\n

            on:<\/p>\n\n\n\n

            \nhttps:\/\/deine-domain.ch\n<\/div><\/figure>\n\n\n\n

            to replace.<\/p>\n\n\n\n

            Do not replace HTTP URLs directly with phpMyAdmin<\/h2>\n\n\n\n

            A common mistake is to run a simple SQL query via phpMyAdmin and directly replace all occurrences of a URL.<\/p>\n\n\n\n

            You should avoid this in WordPress if you don't know exactly which data is affected.<\/p>\n\n\n\n

            WordPress, themes and plugins can contain so-called serialized data<\/strong> save it in the database. Among other things, this involves taking into account the length and structure of data values. Improper replacement can damage these data structures.<\/p>\n\n\n\n

            For extensive URL changes, you should therefore use a WordPress-compatible search-and-replace method that can handle serialized data.<\/p>\n\n\n\n

            \n

            Warning:<\/strong> Do not perform a global search and replace directly in the WordPress database if you are not sure how serialized data is handled. Always create a complete backup beforehand.<\/p>\n<\/blockquote>\n\n\n\n

            Detect mixed content in the browser<\/h2>\n\n\n\n

            If the browser reports problems despite HTTPS, you can use the browser's developer tools.<\/p>\n\n\n\n

            In many browsers you open these via the developer tools and then switch to the Console<\/strong>. Mixed content issues are often displayed directly there.<\/p>\n\n\n\n

            Typical messages indicate that a page loaded via HTTPS is trying to retrieve a resource via HTTP.<\/p>\n\n\n\n

            The displayed URL helps you figure out which image, script, stylesheet, or other element still needs to be adjusted.<\/p>\n\n\n\n

            Clear cache after HTTPS transition<\/h2>\n\n\n\n

            After changing URLs or redirects, you should clear existing caches. Otherwise, you might continue to see an older version of your website and thus believe the transition did not work.<\/p>\n\n\n\n

            Depending on the WordPress configuration, there may be multiple cache levels:<\/p>\n\n\n\n

              \n
            • browser cache<\/li>\n\n\n\n
            • WordPress cache plugin<\/li>\n\n\n\n
            • Server cache<\/li>\n\n\n\n
            • Page Builder Cache<\/li>\n\n\n\n
            • CDN or proxy cache<\/li>\n<\/ul>\n\n\n\n

              Therefore, after the changeover, clear the relevant caches and then test the website again.<\/p>\n\n\n\n

              HTTPS with a CDN or Cloudflare<\/h2>\n\n\n\n

              If you are using an external CDN, proxy, or DNS service like Cloudflare, the HTTPS configuration may require additional settings.<\/p>\n\n\n\n

              In this case, an encrypted connection may exist between both the visitor and the CDN, as well as between the CDN and your CURIAWEB server.<\/p>\n\n\n\n

              Therefore, the SSL settings of the external service must match the web server configuration. An incorrect setting can lead to redirection loops or certificate issues, for example.<\/p>\n\n\n\n

              \n

              Note:<\/strong> If your website is run via an external proxy or CDN and a redirection loop occurs after switching to HTTPS, check its SSL or HTTPS configuration first.<\/p>\n<\/blockquote>\n\n\n\n

              HTTPS and WordPress SEO<\/h2>\n\n\n\n

              Switching from HTTP to HTTPS changes your website's URL. From:<\/p>\n\n\n\n

              http:\/\/deine-domain.ch\/beispielseite\/<\/code><\/p>\n\n\n\n

              becomes<\/p>\n\n\n\n

              \nhttps:\/\/deine-domain.ch\/beispielseite\n<\/div><\/figure>\n\n\n\n

              To ensure that search engines clearly recognize the HTTPS version as the preferred variant, the technical configuration should be consistent.<\/p>\n\n\n\n

              Check in particular after the switch:<\/p>\n\n\n\n

                \n
              • HTTP is permanently redirected to HTTPS<\/li>\n\n\n\n
              • Internal links use HTTPS<\/li>\n\n\n\n
              • Canonical URLs use HTTPS<\/li>\n\n\n\n
              • the XML sitemap contains HTTPS URLs<\/li>\n\n\n\n
              • Images and other internal resources are loaded via HTTPS<\/li>\n<\/ul>\n\n\n\n

                If you manage your website in Google Search Console or other webmaster tools, you should also check after a major change whether the new HTTPS configuration is recognized correctly.<\/p>\n\n\n\n

                What to do if WordPress is no longer accessible after the migration?<\/h2>\n\n\n\n

                If you changed the WordPress URL and afterwards neither the website nor the admin area can be accessed correctly, it is often due to an incorrect URL or a faulty redirection.<\/p>\n\n\n\n

                Typical symptoms are:<\/p>\n\n\n\n

                  \n
                • Too many redirects<\/li>\n\n\n\n
                • Redirect loops<\/li>\n\n\n\n
                • a white or unreachable page<\/li>\n\n\n\n
                • Redirection to an incorrect domain<\/li>\n\n\n\n
                • Certificate warnings<\/li>\n\n\n\n
                • The WordPress login is no longer working<\/li>\n<\/ul>\n\n\n\n

                  In this case, check first whether your domain is actually reachable via HTTPS and whether the certificate is valid.<\/p>\n\n\n\n

                  If you no longer have access to the WordPress admin area, the WordPress URLs can also be changed via the file if necessary wp-config.php<\/code> can be specified. However, this is a technical troubleshooting step and should only be performed if you are familiar with editing WordPress configuration files.<\/p>\n\n\n\n

                  If you are unsure, do not change database values or server configurations at random, but contact CURIAWEB Support.<\/p>\n\n\n\n

                  How to check the HTTPS migration<\/h2>\n\n\n\n

                  After completing the work, you should not only check the home page. Test several different areas of your website.<\/p>\n\n\n\n

                    \n
                  1. Open your website via https:\/\/deine-domain.ch<\/code>.<\/li>\n\n\n\n
                  2. Call additionally http:\/\/deine-domain.ch<\/code> Open it and check whether it automatically redirects to HTTPS.<\/li>\n\n\n\n
                  3. Open several subpages and blog posts.<\/li>\n\n\n\n
                  4. Check images, menus, and internal links.<\/li>\n\n\n\n
                  5. Testing contact forms.<\/li>\n\n\n\n
                  6. Open the WordPress admin area.<\/li>\n\n\n\n
                  7. Check the browser console for mixed content messages.<\/li>\n\n\n\n
                  8. Clear existing caches and repeat the test.<\/li>\n<\/ol>\n\n\n\n

                    For a WooCommerce store, you should also test the cart, checkout, and customer account.<\/p>\n\n\n\n

                    SSL certificate and HTTPS are two parts of the same transition<\/h2>\n\n\n\n

                    For a fully encrypted WordPress website, two things must work together:<\/p>\n\n\n\n

                    1. The web server requires a valid SSL\/TLS certificate.<\/strong><\/p>\n\n\n\n

                    Without a valid certificate, the browser cannot establish a trusted HTTPS connection to the domain.<\/p>\n\n\n\n

                    2. WordPress must consistently use HTTPS.<\/strong><\/p>\n\n\n\n

                    This includes the WordPress URLs, internal resources, redirects, and, if applicable, URLs already saved in the database.<\/p>\n\n\n\n

                    Only when both areas are correctly configured is the website completely switched to HTTPS.<\/p>\n\n\n\n

                    \n

                    Recommendation:<\/strong> Always fully check a WordPress website after an HTTPS migration. A padlock icon on the homepage alone does not prove that all subpages, resources, and redirects are configured correctly.<\/p>\n<\/blockquote>\n\n\n\n

                    Problems with SSL or HTTPS on CURIAWEB?<\/h2>\n\n\n\n

                    If your domain does not receive a valid SSL certificate despite active hosting, HTTPS does not work, or you can no longer access your WordPress website after a change, you do not need to make changes to server or WordPress files on a whim.<\/p>\n\n\n\n

                    In this case, contact CURIAWEB support and provide the affected domain and, as precisely as possible, the error message displayed. This helps to determine more quickly whether the problem lies with the certificate, WordPress, a redirect, or another configuration.<\/p>\n\n\n\n

                    Summary<\/h2>\n\n\n\n

                    For a secure WordPress website, you need a valid SSL\/TLS certificate and a WordPress installation correctly configured for HTTPS. First, check if your domain has https:\/\/<\/code> accessible without a certificate warning. Afterwards, you can check the WordPress and site address and change them from HTTP to HTTPS if necessary.<\/p>\n\n\n\n

                    Ensure that HTTP calls are permanently redirected to HTTPS and that no old HTTP resources are loaded as mixed content. For older websites, additionally saved URLs in the WordPress database may need to be updated. Always create a backup before making such changes and use a method for database changes that can handle WordPress and serialized data.<\/p>\n\n\n\n

                    When the certificate, WordPress URLs, redirects, and internal resources are correctly configured, your WordPress website will be delivered completely and consistently via HTTPS.<\/p>","protected":false},"excerpt":{"rendered":"

                    Eine WordPress-Website sollte heute grunds\u00e4tzlich \u00fcber HTTPS erreichbar sein. HTTPS verschl\u00fcsselt die Verbindung zwischen dem Browser Ihrer Besucher und dem Webserver und sch\u00fctzt damit beispielsweise Login-Daten, Formulareingaben und andere \u00fcbertragene Informationen vor dem einfachen Mitlesen w\u00e4hrend der \u00dcbertragung. Damit HTTPS funktioniert, ben\u00f6tigt Ihre Website ein g\u00fcltiges SSL\/TLS-Zertifikat. Bei einem CURIAWEB Webhosting wird die technische Grundlage […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_joinchat":[],"footnotes":""},"doc_category":[80],"doc_tag":[],"class_list":["post-22316","docs","type-docs","status-publish","hentry","doc_category-wordpress"],"year_month":"2026-09","word_count":2001,"total_views":"6","reactions":{"happy":"0","normal":"0","sad":"0"},"author_info":{"name":"Silvio Mazenauer","author_nicename":"admin-curia","author_url":"https:\/\/www.curiaweb.ch\/en\/author\/admin-curia\/"},"doc_category_info":[{"term_name":"WordPress","term_url":"https:\/\/www.curiaweb.ch\/en\/hilfe-kategorie\/wordpress\/"}],"doc_tag_info":[],"knowledge_base_info":[],"knowledge_base_slug":[],"_links":{"self":[{"href":"https:\/\/www.curiaweb.ch\/en\/wp-json\/wp\/v2\/docs\/22316","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.curiaweb.ch\/en\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/www.curiaweb.ch\/en\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/www.curiaweb.ch\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.curiaweb.ch\/en\/wp-json\/wp\/v2\/comments?post=22316"}],"version-history":[{"count":1,"href":"https:\/\/www.curiaweb.ch\/en\/wp-json\/wp\/v2\/docs\/22316\/revisions"}],"predecessor-version":[{"id":22318,"href":"https:\/\/www.curiaweb.ch\/en\/wp-json\/wp\/v2\/docs\/22316\/revisions\/22318"}],"wp:attachment":[{"href":"https:\/\/www.curiaweb.ch\/en\/wp-json\/wp\/v2\/media?parent=22316"}],"wp:term":[{"taxonomy":"doc_category","embeddable":true,"href":"https:\/\/www.curiaweb.ch\/en\/wp-json\/wp\/v2\/doc_category?post=22316"},{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/www.curiaweb.ch\/en\/wp-json\/wp\/v2\/doc_tag?post=22316"}],"curies":[{"name":"WP","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}