Member Avatar for samauden

Hello folks,

I have been doing SEO for my client website with http:// version since 2.3 months.I noticed that my client suddenly changed to https:// version. When i searched in Google search console, and clicked on Fetch as Google and when submitted, it showed that Redirected, and linked pages submitted to Index. In the search console the sitemap is of the version http://

One keyword without location got ranked in first page with the https:// version of the website,remaining location specific keywords are in 4th and 5th page on SERPs with the same https:// version.

I would like to know whether i need to create a new account for the new https:// version of the website in the Google Analytics which gives the anlaytics code. Do I need to replace the existing analytics code of the http:// version of the website with the new anlaytics code of https:// verison?

Also, do i submit or click add a property in Google Search Console and add the https:// version of the website. and remove the old sitemap file and upload a new site map file in search console.

I have stopped doing SEO since a week, and i request friends to help me out regarding what changes i need to enforce to continue with the SEO process

regards
auden

  • 3 Contributors
  • 2 Replies
  • 371 Views
  • 3 Weeks Discussion Span
  • Latest Post Latest Post by chirag_2

Dani AI

Generated

Quick summary for : treat this as a normal site move from HTTP → HTTPS. Add the HTTPS variant to Search Console (or — better — verify a single Domain property so all protocol/subdomain variants are covered), submit an HTTPS sitemap, and make sure every old HTTP URL permanently 301→ the new HTTPS URL. You do not have to replace your Analytics account just because the site switched protocols — the same tracking tag will still work — but verify data is arriving and consider creating a separate property/profile only if you want a clean split of historic vs new data. ()

Actionable checklist (do these in roughly this order):

  • Implement server-side 301 redirects for every HTTP URL to the equivalent HTTPS URL and avoid redirect chains.
  • Update rel=canonical to the HTTPS URL on each page and change all internal links to HTTPS.
  • Regenerate your XML sitemap so every URL is HTTPS, submit it in the HTTPS Search Console property, then remove the old sitemap entry once the new one is accepted.
  • Check robots.txt on HTTPS, fix mixed-content (HTTP assets) and, optionally, enable HSTS after you’re confident everything is correct.
    Example redirect (Apache):
    RewriteEngine On
RewriteCond %{HTTPS} !=on
RewriteRule ^ https://%{HTTP_HOST}%{REQUEST_URI} [R=301,L]

    These are the official, recommended steps and explain why you’ll sometimes see temporary ranking/indexing fluctuation while Google reprocesses the redirects. ()

Analytics specifics: the Google tag (gtag.js / GA4) works over HTTPS and does not require a new tracking ID purely due to the protocol switch — just confirm the tag is present on the HTTPS pages and watch Real‑Time to validate. If you’re still on Universal Analytics, set up GA4 now (UA stopped collecting new data in 2023) and run them in parallel while you build historical GA4 data. If you want completely separate reports you can create a new property, but it’s optional. (developers.google.com)

Troubleshooting tips: test a handful of URLs with the URL Inspection tool, watch Search Console coverage and the sitemap indexed counts, keep redirects in place for many months (Google recommends at least a year), and monitor for mixed‑content errors or redirect loops. Tie back to ’s checklist (internal links, canonicals, sitemap) and ’s instinct (update sitemap and verify analytics) — both are correct; the extra steps above make the switchover safer and faster to stabilize. ()

Member Avatar for David_75

I remember that the same thing happened to one of my sites a while back. I went with the safe route and updated my sitemap and Google Analytics code. Have you seen any ranking changes?

Member Avatar for chirag_2
  1. Check that all internal links point to new https version.
  2. Update the canonical tags.
  3. Submit the new sitemap.
  4. Check google search console (webmaster tools) for any errors.
Edited by chirag_2
Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.