HTTP Page Reindexed as HTTPS: Add Canonical to Head, Or Move All to HTTPS

Feel worried.  Well, well-indexed pages got their URLs changed in Google to HTTPS which is making the pages go to 404.  Have a plan.  Need advice.

Spend the next week moving content over to HTTPS.  Do nothing else.

Or, add a <link> element with the attribute rel="canonical" to the <head> section of these pages: <link rel="canonical"...  And, wait for re-indexing?

Or, do both?

Or, move ONLY the incorrectly renamed (http --> https), but still highly indexed, pages to https.  Then, just add the canonical link to all the ones that are still correctly listed.

My thinking here is: if Google went ahead and switched some pages to https on their own, and we've GOT https, just move as many of them over as we can?

Or, is it a better use of time and staff to fix only the ones we can see that have been switched in Google, and then put the "canonical" on the ones that are still shown correctly in Google as http?  Will that "canonical" tag keep the pages from being reindexed?  Or, is this more of the move to all as https, and inevitable - we should just make them all go to https?


Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

On yourhost, define the secures site to use the same DocumentRoot as the unsecured.

What your webserver?

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
nociSoftware EngineerCommented:
The best is to switch the whole site to https..... (and to be honest, on the monetary side it can be free, if you use letsencrypt).

HTTPS is about security, that is not just confidentiality as many people think, but also credibility and reliability.
Is the data you send the same as the data the receiver gets.

There are ISP's that change data for their customer to include some type of commercial stuff.
either replace ads you include by their own or adding data to a page, ie. they change the data on the fly.
With HTTPS that cannot be done, at least not without consent.
oaktreesAuthor Commented:
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.