Moz Q&A is closed.
After more than 13 years, and tens of thousands of questions, Moz Q&A closed on 12th December 2024. Whilst we’re not completely removing the content - many posts will still be possible to view - we have locked both new posts and new replies. More details here.
Will changing the property from http to https in Google Analytics affect main unfiltered view?
-
I set my client up with an unfiltered view in Google Analytics. This is the one with historical data going back for years, so I don't want to do anything that will affect this view. Recently, the website moved from HTTP to HTTPS. There's a setting for the property that will allow me to change the property name to https://EXAMPLE.com and change the default URL to https://EXAMPLE.com. Questions:
1. If I change the property name and the default URL, will this somehow affect my unfiltered view in a way that I'll lose historical data or data moving forward?
2. I have heard that changing the default URL to HTTPS will help me avoid a common problem others have experienced (where they lose the referrer in Google Analytics and a bunch of their sessions go to direct / other). Is this true?
-
Hi, I'm so glad i found this. I have a similar situation. We are changing from http to https.
Just to make sure i understand this correctly. We do not need to change anything in GA. But modifying the property name to https will reinforce what we did?
Thank you. Julie
-
I love the professional passion, Verónica and Paul!
VerĂłnica, Paul's response was more specific to my question about Google Analytics, but I appreciate you bringing up related issues with Google Search Console.
-
It clarifies, thanks! That's the info I needed. I appreciate it.
-
"The wrong name in the 'Property name' field or wrong setting in the http_ or https doesn't affect the data collection in your GA account." _I know - which is why I explained that changing the protocol there to HTTPS won't have any effect on the archive View either, which was the OP primary question.
"...verify all the properties and choose the preferred one" will not have any effect on "help[ing] me avoid a common problem others have experienced" as you state. That problem (Referral visits recorded as Direct in GA) is caused by the referral data being stripped out of the request when it travels from an HTTP site to an HTTPS site. There's nothing in GSC that can have any effect on this - it is entirely controlled by the server headers of the connection request.
There's nothing about Kevin's original question that has anything to do with or can be addressed in Search Console.
P.
-
Hi Paul,
The wrong name in the 'Property name' field or wrong setting in the http or https doesn't affect the data collection in your GA account. The data is collected via UA number in the GA tag for your website regardless of the domain your GA tag is on.
Assuming GA is linked to Google Search Console, where it is essential to verify all the properties and choose the preferred one for getting accurate data, plus this will "help me avoid a common problem others have experienced".
MÂŞ VerĂłnica
-
He's talking about the effect of updating the default URL in the Google Analytics Property Settings, Veronica - nothing to do with Google Search Console.
P.
-
Lemme try that again
1. Updating the protocol in your GA Property settings won't have any harmful effect on your archive view (or any other view).
2. Setting the Property address to HTTPS isn't what's going to determine if the incoming referral data is available - that's been determined before the visits actually arrive by the browser connection and server headers. If the visit to HTTP is coming from HTTPS, the referrer data was stripped out before the request was sent. GA just uses whatever it receives. (My point was, even if you don't set the protocol to HTTPS in your Profile, the referrer data will come through anyway. But getting your GA set to the correct HTTPS address reinforces this, so still a good idea.)
Hope that clarifies?
Paul
-
Hi, Paul. Sorry, I wasn't sure from your response...
1. I understand that "updating the protocol to HTTPS won't have any negative effect on your archival GA view." By this, I think you mean updating the actual website protocol (not making changes in Google Analytics.)
So, within Google Analytics, if I change the property name and the default URL to HTTPS, will this somehow affect my archival view of Google Analytics in a way that I'll lose past data or data moving forward?
2. I think you are saying that if I change the property name and the default URL to HTTPS within Google Analytics, I "should" be able to see the referrer properly and not lose the referrer and a bunch of their sessions to direct / other. Is this right?
-
The short answer, Kevin, is no, updating the protocol to HTTPS won't have any negative effect on your archival GA view.
Just having the visitor connection resolve at the HTTPS address "should" transmit the referrer info fully (it's the browser that determines this, not GA), but always good to back this up by having the GA property properly configured for the HTTPS update.
Little sidenote - since your site is now HTTPS, any referrals it sends to other non-HTTPS sites will get stripped. If it's important to you to have those other sites recognise you sent them traffic (this is important in some partnership/affiliate,/advertiser situations for example) you can add a Meta Referrer tag to your site so that it will send at least some of the referrer info even to a non-HTTPS site. You can select how much info gets passed based on your security sensitivities.
That what you were looking for?
Paul
-
Hi Kevin,
Assuming that you set up a 301 (permanent redirect) from the http to the https:
How to do it?:
https://support.google.com/webmasters/answer/6332964?Where?
https://www.google.com/webmasters/tools/What properties?:
http://example.com/
https://example.com/
http://www.example.com/
https://www.example.com/After all those were done:
Into this property only: https://example.com/ (Assuming that you prefer the https non www version)
verify the robot texts
upload a sitemap
fetch as google
You will see data starts to be shown and index within a few days.Forgot to mention the bad news on regard a migration to https, due to Google considers the https a new website, it will crawl all as "a new website".
That is great at first, though any failure from old times will appear with "red flags" because the 2017 algorithms will work. I mean broken links, 404s and so, that you didn´t know those were there, will be shown up.
That is why it is highly advisable to perform an SEO audit and fix up all, before a migration.
Although, in many years of SEO practice, only one client came before the migration.
You do NOT change the Analytics code, therefore it will continously showing old data and new data into the same view. Good luck!
MÂŞ VerĂłnica
Got a burning SEO question?
Subscribe to Moz Pro to gain full access to Q&A, answer questions, and ask your own.
Browse Questions
Explore more categories
-
Moz Tools
Chat with the community about the Moz tools.
-
SEO Tactics
Discuss the SEO process with fellow marketers
-
Community
Discuss industry events, jobs, and news!
-
Digital Marketing
Chat about tactics outside of SEO
-
Research & Trends
Dive into research and trends in the search industry.
-
Support
Connect on product support and feature requests.
Related Questions
-
Losing referrer data on http link that redirects to an https site when on an https site. Is this typical or is something else going on here?
I am trying to resolve a referral data issue. Our client noticed that their referrals from one of their sites to another had dropped to almost nothing from being their top referrer. The referring site SiteA which is an HTTPs site, held a link to SiteB, which is also an HTTPs site, so there should be no loss, however the link to SiteB on SiteA had the HTTP protocol. When we changed the link to the HTTPs protocol, the referrals started flowing in. Is this typical? If the 301 redirect is properly in place for SiteB, why would we lose the referral data?
Reporting & Analytics | | Velir0 -
Google analytics suddenly stopped tracking all my landing pages
Hey guys. I love the new update of GA. Looks so clean. So, of course, I was excited to see how my landing pages were doing. I went to behavior, all content, all pages. And I noticed it's only showing me 19 pages out of the 93 I have indexed. And none of the top ones at all! Can't find them anywhere in GA! Anyone seen this before? Thank you so much
Reporting & Analytics | | Meier0 -
Google Analytics - Average Position
Hi Just trying to get some clarity on Google Analytics Average Positions in "Aquistions/Search Engine Optimisation". For a very competitive keyword Google Analytics is saying i am on average position of 6. Â Is this Page 6? Â I am assuming position six would be 1.6?
Reporting & Analytics | | Cocoonfxmedia0 -
Google Analytics Showing Inflated Product Revenue
Hi- For the month of Feb on two of our sites we are seeing inflated product revenues. I have not seen this before and I am not having any luck searching for answers. Here is the issue: Product B sells for $159.95 For the month of Feb we sold 3 thus revenue should be ~$479.85 GA is showing Product B's revenue at $3,360.00 I read online that sometimes folks will bookmark the receipt page and that can cause this and we would need to put a catch in place for this but I am guessing this is not the case as it is happening on two sites. Please let me know if you have any questions.
Reporting & Analytics | | K2_Sports0 -
Google Analytics and DNS change
Our new alumni application is going be tested at domain uva.imodules.com . We are going to collect traffic data with a Google analytics account number UA-884652-XX. So going to uva.imodules.com/myPage.html would send its data to Google Analytics with that account number.     Then when it is ready for production we are going to just change the domain name of the application and switch the DNS over to dardencommunity.darden.virginia.edu . So going to dardencommunity.darden.virginia.edu /myPage.html would send its data to  Google Analtics with that SAME account number.  Aside from having the testing domain data in the same profile are there any other issues/problems we may run into?
Reporting & Analytics | | Darden0 -
Setting up Google Analytics for Subsites
I currently have one main .com site and am planning on launching geo-location subsites .co.uk, .com.au, .ru, etc... Traffic will flow between both sites and some of the content on the subsites will be duplicate and therefore include a canonical tag to the main site. I want to set up GA to capture who is going to the subsites and vice versa and correctly capture crossover traffic.  Any advice on implementing advanced analytics directly (or links to sources that will direct me the right direction for this project)
Reporting & Analytics | | theLotter0 -
Setting up Google Analytics default URL
If someone has set: the default url in Google Analytics to a non-www address (http://mysite.com) then placed the UA tracking script from that GA account within the CMS framework of the website... ... and then set the permanent 301 redirect in the htaccess file to redirect to the www address (http://www.mysite.com). How less accurrate will my GA analytics measurements be considering the default url within GA is non-www and the permanent 301 redirect in htacess is to the www-address? Anyone know how reliable GA reports are until the default url in GA analytics is changed to match what is the redirected url in htaccess file? _Cindy
Reporting & Analytics | | CeCeBar0 -
Google Analytics Admin account not allowing us to add other users?
Our Google Analytics Administrator account is not giving us access to the User Manager, and because of that we are unable to add users; have you ever ran in to a problem such as this, if so what was your solution. Thanks a Billion impressions, Vijay E2qE9.jpg
Reporting & Analytics | | vijayvasu0