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
-
Do I need a separate Google Analytics ID for a subdomain on my website?
Hello Everyone, I would like to know if I need a separate Google Analytics ID for a subdomain on my website? I have a sub-domain within my website, and the software for the site on the subdomain is asking for a Google Analytics ID. Should I be using the same Google Analytics ID as the main domain or should I be creating a new Google Analytics profile or ID? Thanks. Ryan
Reporting & Analytics | | RyanUK0 -
Is there a way to apply the same google analytics filter to multiple properties?
I manage WordPress multiple sites for my clients. Some of these clients are SEO customers. One issue I have with the analytics reports is the occurrence of spam and ghost spam. I know how to create filters to block however there are always more and more. Is there away to export the filter and import it to all the other properties i manage? Or do they just have to be done manually every time i need to block spam?
Reporting & Analytics | | donsilvernail1 -
Google Analytics - Next Page Path is the Same URL?
Hey Everyone, I have a Google analytics question. I'm looking through a client's site and when I look at the next page path, I get the same URL as the next path. For example, on the homepage, the next page path I get is the homepage again? This happens for all URL's, is this an implementation error? Is there a way to fix this? Thanks!
Reporting & Analytics | | EvansHunt0 -
Google analytics vs Webmaster tools data
Hi Which is more accurate WT or GA data ? Since GA reporting a KW (thats very recently fallen from page 1 to 3 hence looking into data to find the cause) in the Organic part of Search tab as having generated just 1 visitor over a month (hence presuming fall could be due to low visits from a page 1 result) whilst under Search Engine Optimisation tab (data sourced from WT i think) its reporting 5 click thrus from 150 impressions over same period resulting in a quite good 3.33% CTR (hence wouldn't expect to be the cause of a fall) and what i would have thought GA would report as 5 visits instead of the 1 they do report !? The reason im looking for answer in the data is because no on-page has changed and still scoring a grade A and off page metrics have all improved across the board (apart from small drop in majseo's Trust Flow) such as increased links, RD, Citation Flow, Ref Subnets etc etc etc Cheers Dan
Reporting & Analytics | | Dan-Lawrence0 -
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 -
Multiple domains to one payment sub-domain in Google Analytics
Hi Mozzers, I have a series of sites (~25) that are all regional e-commerce sites with the same URL structure eg. www.[region]-product.com as well as a 'master' site (eg www.product.com). I also have a single Adwords PPC account which point to all of the regional sites as well as the master site. As part of the payment/checkout process you only ever get taken to a sub domain of the master site (eg payment.product.com). My question is: Is it wise to use the single PPC Adwords account to set up an Analytics account under which I list all of the regional sites and the master site? Once that's done I'm not entirely sure how I can track sales from a regional site to the payment process of the master site and have sales correctly assigned to the right domain. On the payment process I can only use one site ID tracking code so I'm not even sure I can correctly assign a transaction to a single site if multiple sites use the same payment pages. Example: Visit to region-product.com > Quote form submitted to payment.product.com > Payment completed on payment.product.com > Sale is assigned to which domain? Can anyone who understands what I'm trying to achieve comment on the plausibility of this? Many many thanks!
Reporting & Analytics | | panini0 -
Google Analytics - Cross Domain Tracking Goals
Hi guys, looking at the best way to organize this - Site 1 - Shoe Store - (Old site with analytic history - UA-12345-1) Site 2 - Clothing Store - (Brand New UA-54321-1) Right now i have 2 separate GA Accounts for the sites. But i would like to track goals from Site 2 to Site 1. For that i need to set up cross domain tracking. So i take it i would need to create another account under Site 1 - (UA-12345-2) and put that new code on Site 2? Or do the UA numbers have to be exact? example both 12345-1? In which case, i would need to set up 2 different profiles with filtering? Main concern is i want to keep separate data for both sites, espically if UA's will be the same. Trying to visualize - UA-12345-1 Profile 1Shoes/Master Profile 2 Shoes Profile 3 Clothes Or UA-12345-1 Shoes UA-12345-2 Clothes Thanks, Mike
Reporting & Analytics | | IsHot0 -
Google Analytics Best Practice Set up for Clients
Hi When setting up new Google Analytics accounts for clinets what is the preferred/best practice. At present we have our own company google account and add new clinets this way (to our account) - the disadvantage with this, we can only grant them limited account access otherwise they would be able to view all the accounts we cretaed. Plus we can't link their adwords to the GA account we cretaed them. Is it best practice to set the client up with their own Google Account and then we just link to their account. Advise would be appreciated, thank you.
Reporting & Analytics | | daracreative0