If Google is choosing the HTTP version of your WordPress homepage as canonical, first make every signal agree on one HTTPS homepage URL. Confirm the certificate works for that hostname, redirect HTTP and alternate hostname versions directly to it, and align WordPress settings, the rendered canonical tag, internal links, and sitemap. Then check Google’s selected canonical in Search Console; its choice may not update until Google recrawls the pages.
What an HTTP-to-HTTPS canonical issue means
Google treats HTTP and HTTPS versions of a page as separate URLs and selects one representative URL when it finds duplicate or very similar pages. The same can happen with www and non-www versions of a homepage. WordPress may declare one URL as canonical, but that declaration is a signal—not a guarantee that Google will select it. Google weighs redirects, canonical annotations, sitemap entries, and other evidence. Redirects and rel="canonical" annotations are stronger signals than sitemap inclusion. See Google’s canonicalization guidance.
Google generally prefers an HTTPS URL over its equivalent HTTP version. That preference can be undermined by conflicting implementation signals, including an invalid certificate, a redirect to or through HTTP, or a canonical link that points to HTTP. Google also identifies insecure page dependencies other than images as a possible issue. Its HTTPS guidance explains these cases. The certificate must cover the complete hostname, either directly or through a suitable wildcard certificate.
Diagnose what Google and your site are saying
Check the selected canonical in Search Console
Open Search Console’s URL Inspection tool and inspect the homepage URL. Compare the user-declared canonical with the Google-selected canonical. Make sure you inspect the correct URL and the appropriate Search Console property. Google notes that you cannot inspect duplicate-page traffic for a canonical URL in a property you do not own. If Google selected HTTP while your page declares HTTPS, that confirms a mismatch in outcome; it does not, by itself, identify which technical signal caused it. See Google’s URL Inspection troubleshooting guidance.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallChoose one homepage URL
Decide whether the preferred homepage is https://example.com/ or https://www.example.com/. Neither hostname form is inherently required. Choose based on your existing configuration, backlinks and recognition, certificate coverage, and which version is easiest to use consistently. Then treat every other protocol or hostname variation as an alternate that should lead to the chosen URL.
Inspect the certificate and redirect chain
Open the chosen HTTPS URL and confirm that it loads without a certificate warning and that the certificate matches the full hostname. Then test the HTTP homepage and each alternate hostname. Follow the redirects to see whether they reach the preferred HTTPS URL directly or pass through another URL first. Remove any HTTPS-to-HTTP redirect or HTTP intermediate hop. A valid permanent server-side redirect is generally the quickest way to signal a permanent URL consolidation; Google says permanent redirect methods have the same effect on Search, although the time for search engines to notice can differ. See Google’s redirect guidance.
Inspect the homepage’s rendered canonical
View the live homepage source or use browser developer tools to find its rel="canonical" link. It should point to the exact preferred HTTPS URL, including the chosen hostname and trailing-slash form. Check that there is one correct canonical rather than conflicting tags from a theme, SEO plugin, or other component. Google lists incorrectly generated CMS canonicals among common canonicalization problems in its troubleshooting guidance.
Fix the WordPress homepage signals
Set the WordPress URLs to HTTPS
In the WordPress dashboard, go to Settings → General and review WordPress Address (URL) and Site Address (URL). Where your hosting architecture permits, set both to the chosen HTTPS hostname. These fields may need different values in some installations, so do not change them blindly if WordPress core files and the public site are served from different locations. Hosting, proxies or CDNs, and plugins can also affect the effective URL and redirect behavior.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
WordPress core includes redirect_canonical(), which helps redirect requests to a canonical URL. Its presence does not ensure that server rules, hosting settings, plugins, and theme output all agree. See the WordPress developer reference for redirect_canonical().
Correct the tag and redirects at their source
If the rendered canonical points to HTTP or the wrong hostname, correct the setting or component that generates it—often the SEO plugin or theme—rather than adding a second, conflicting canonical tag. If redirects are wrong, correct the rule where it is managed, such as the host, web server, CDN, or redirect plugin. The exact controls vary by provider and site architecture; the goal is for every alternate URL to reach the chosen HTTPS homepage without an HTTP detour or a redirect loop.
Make supporting URLs consistent
- Update internal links so they use the chosen HTTPS homepage and hostname.
- Make sure the XML sitemap lists the preferred HTTPS URLs, not HTTP alternates.
- Use HTTPS URLs in relevant
hreflangannotations rather than HTTP versions. - Confirm the preferred destination is crawlable and returns the intended homepage.
A sitemap supports your choice but is weaker than a redirect or canonical annotation. Consistency across these signals helps Google interpret which URL you intend to represent the page. Google discusses these signals in its canonicalization documentation.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Verify the fix and request reassessment
- Load the preferred HTTPS homepage. Confirm that it opens successfully with a valid certificate for the exact hostname.
- Test the alternate URLs. Open HTTP and the other
www/non-wwwvariations. Confirm that each reaches the chosen HTTPS destination without an HTTP detour or loop. - Recheck the rendered page. Confirm that the homepage’s canonical points to the chosen HTTPS URL and that internal links, sitemap entries, and relevant localization annotations use the same version.
- Inspect the URL in Search Console again. After Google has recrawled the page, use URL Inspection to see whether Google selected the intended canonical. If appropriate, use the tool’s request indexing feature for the important homepage.
Do not expect the Search Console result to change immediately. Google says canonical reevaluation can take up to two weeks after issues are fixed; that is a possible timeframe, not a guarantee. See Google’s canonical troubleshooting guidance.
Quick Recap
If Google still selects HTTP
- Recheck every hostname variant. A forgotten redirect or an inconsistent preferred hostname can keep duplicate URLs in play.
- Look for a conflicting signal you have not checked. Revisit certificate validity, the entire redirect chain, the rendered canonical, and the sitemap and internal links.
- Investigate unexpected redirects or domains. If the page redirects unexpectedly or its canonical points to an unrelated or suspicious domain, check for both configuration mistakes and possible compromise. Google documents malicious injections that add redirects or cross-domain canonical links in its canonical troubleshooting guidance.
- Resolve access problems first. If HTTPS is inaccessible, its certificate is invalid, or redirects loop, fix the underlying hosting or TLS issue before requesting that Google reassess the canonical.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
