Serve the page over HTTPS
Search and browsers expect HTTPS. Redirect HTTP to HTTPS and update canonicals. Follow the steps below on your stack, then re-check the live URL.
Search and browsers expect HTTPS. Redirect HTTP to HTTPS and update canonicals.
We remember this on this browser so the next guide opens with the same CMS.
At a glance
| Time | ~20 min |
|---|---|
| Category | SEO |
| Steps | 3 |
| Stacks | WordPress, Shopify, Webflow, Next.js, HTML, more |
Steps
Enable an SSL certificate on the host (Let’s Encrypt is typical).
Redirect all HTTP URLs to HTTPS.
Update canonicals and internal links to https://.
In HTML / static
Enable HTTPS on the host (Let’s Encrypt) and 301 HTTP → HTTPS.
FAQ
- What does “Serve the page over HTTPS” fix?
- Search and browsers expect HTTPS. Redirect HTTP to HTTPS and update canonicals.
- How long does this usually take?
- About 20 minutes on most CMS and code stacks when you already have access to edit the page.
- Where do I start?
- Start with: Enable an SSL certificate on the host (Let’s Encrypt is typical). Then use the platform picker on this page for placement notes.