Can I use same sitemap for both HTTP and HTTPS Properties?

In Google Search Console, I had two properties for, non-www and www, in the http variant. I recently got an SSL for it and added the https variant properties, both non-www and www. It is a WordPress site and I used Yoast SEO to create a sitemap. The sitemap has only http: addresses in it. Can I use the same sitemap for both http and https properties?

Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

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.

Chris StanyonWebDevCommented:
Given the way Google is going, they are looking to give you higher rankings for a site delivered over https, so rather than trying to get everything working over 2 different protocols, you'd be better off configuring your site to always delivery the https version. It would need a couple of tweaks to your Wordpress site (and probably the htaccess file in the project root). You would then tell google that your base domain was the https version and every visit to the site would then serve up the secure version.
jdfreeman2000Author Commented:
Thanks, Chris, What are the tweaks? I have changed Settings -> General -> WordPress address and Site address to the https variant and Yoast automatically created a sitemap with https: addresses
Chris StanyonWebDevCommented:

It's probably easier if I just give you a link to a page that outlines the process. Some of the steps you will have already done. Some you won't. There will be some changes to the way WordPress is configured from the backend (admin). There will probably be a couple of functions that you need to add in yourself. Edits to the wp-config file.

You may also need to edit your .htaccess file, and you will likely need to do some tweaks to the database itself (such as where an image is embedded in a page as http://

Make sure all your resources (scripts / css etc) are set up to be included as protocol agnostic - i.e drop the http: or https:

Here's a decent link that gives you a good overall idea of the steps needed -

It sounds quite a lot to do but most are just 30-second tweaks. The DB edits may be the biggest part of it. In the page I've linked to, they talk about installing a plug-in. I've never found that necessary. Backup your DB before doing any work on it.

It's always easier to do all this setup before you start using your site, but sometimes that's not an option !

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
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
Web Development

From novice to tech pro — start learning today.