Try it yourself
Somebody types your address without the https, or follows an old link. Four sites, four ways of handling GET http://…/services.
Which one gets it right?
-
No redirect at all. The secure site exists, but this visitor never reaches it — they read the whole page over an unencrypted connection with "Not secure" in the address bar.
-
This is the one. Permanent, and to the matching page rather than somewhere general. The visitor lands where they meant to, and search engines consolidate the old address's history onto the secure one.
-
The visitor arrives in the right place, so it looks identical from the outside. But 302 means "temporarily", which tells search engines to keep the http address as the real one — so the move never settles.
-
Secure, permanent, and it throws the visitor onto the homepage instead of the page they asked for. Every deep link into the site turns into "find it yourself". A very common side effect of a blanket redirect rule that forgets to keep the path.
Pick a line. Every one of them has an answer.
Show me the answer
301 Moved Permanently → https://fenwick-plumbing.example/services
This is the one. Permanent, and to the matching page rather than somewhere general. The visitor lands where they meant to, and search engines consolidate the old address's history onto the secure one.
The written version
Sending every visitor to the secure version →
How to check your own site for this, what to change, and how to confirm it worked.
Now the real thing
Run this check on your own site.
The same check, plus twenty-nine others, against your actual pages. Free, no account, about a minute.