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
-
Query on Not Set In Product List Performance in Google Analytics
Hi All, I have query for given below screenshot-1. What is Not Set here? For column no. 2 only purchase and revenue showing other column blank why? I have properly implemented enhance ecommerce via tag manager. And my product list impression, clicks all working fine for all categories now I don't know from where I am getting Not set - Please check screenshot-2. So what is Not set here? Thanks! QcBGT OCrEp
Reporting & Analytics | | Arnold30 -
I'm a beginner with Google Analytics, what is a good place to start?
I'm a beginner with Google Analytics, what is a good place to start? Would love to know some simple ways to set up Google Analytics to keep SEO in check. What are some of your suggestions? How would you go about using GA to do this? and what are the alternatives? Thanks!
Reporting & Analytics | | Eric_S
Eric0 -
Cross domain tracking Google Analytics
Hi there, Got a question on cross domain tracking: We have a couple of TLD's to serve localized content to our visitors, next to our main .com TLD where our app is running as well in a subdomain. Situation is this: Local sites:
Reporting & Analytics | | jorisbrabants
marketingsite.be
marketingsite.com.br
marketingsite.fr Main site: marketingsite.com
app.marketingsite.com Conversion gets triggered when somebody ends up in app.marketingsite.com/firstuse for example. People can sign up at the local site filling in their email but they end up in app.marketingsite.com/firstuse Reading this article on cross domain tracking I'm getting a bit confused on the setup of the tracking code itself. The sample code provided shows these two lines: ga('require', 'linker'); ga('linker:autoLink', ['maindomain.com','targetdomain.com']); Now the question 🙂 Is it correct when I think that maindomain should be replaced with our local TLD's on every one of those, and that targetdomain is where the conversion happens? In this case the .com site?0 -
Why is Google Analytics showing index.php after every page URL?
Hi, My client's site has GA tracking code gathering correct data on the site, but the pages are listed in GA as having /index.php at the end of every URL, although this does not appear when you visit the site pages. Even if there is a redirect happening for site visitors, shouldn't GA be showing the pages as their redirect destination, i.e. the URL that visitors actually see? Could this discrepancy be adversely affecting my search performance? Example page: http://freshstarttax.com/innocent-spouse/ shows up in GA as http://freshstarttax.com/innocent-spouse/index.php thanks
Reporting & Analytics | | JMagary0 -
Google Analytics set up for non-canonicalized domains
Our client's website is non-canonicalized (www.example.com & example.com load the same thing). Google seems to have made a preference for the www, but canonicalizing to www breaks their Flash website. All we're really trying to do at this time is install Google Analytics for them. What's the smartest way to make sure that both www.example.com and example.com are treated exactly the same by Google Analytics? Google Developers: Domains & Directories states that by default visit data will be separately collected between the two domains, although I found no references to the common www/naked domain issue. In stackoverflow: Does google analytics combine naked domains with the www subdomain? Török Gábor says, "Yes, users will be tracked, but the same visitor coming from www.datalookups.com and datalookups.com will be counted as two different visitors." On the same page, Open SEO says, "This is completely false: www.domain.tld and domain.tld are treaded just the same, and get the same value for the HASH code (the number at the start of each __utm cookie). This an exception: every other subdomain.domain.tld will be handeld as a distinct web site". Can any Analytics experts help me sort this out? Thanks!
Reporting & Analytics | | GOODSIR0 -
Google Analytics underreporting
I have a site selling items, I use paypal buttons and get a report using ipn back from paypal telling me when I have sold a item. I also have a Google analytics event setup on the button, and one on the confirmation page.
Reporting & Analytics | | AlanMosley
For example in the last few days I have sold over 10 items from the website, but have only 2 events from the button and none from the confirmation page. The confirmation page depends on the user getting redirected back from PayPal so I can see that being upper reported, but there is no way you can buy without clicking the button.
I have the chrome addon from google to debug your analytics code and it fires every time.
The figures seem to report only about 20% of events over a long period of time. If it was not working at all, I could assume I have not set things up correctly but this is not the case, I get a regular flow of events but at about 205 of sales.
I am very disappointed with GA, seems a waste of time. anyone else had the same expirence?0 -
Google analytics for mobile apps - do we need different id's?
Dear all, if I want to implement Google Analytics for my mobile apps: Do I need different accounts or id's to ensure separate tracking of my website and mobile apps? How did you do it? Thanks!
Reporting & Analytics | | HMK-NL0 -
How Can I Record .zip Traffic in Google Analytics
The company I am with shows traffic coming in to .zip files in Google Analytics. The traffic being recorded stopped a while back, but I know people are still downloading/visiting these .zip ULRs. I'm not sure how they were recording/tracking the .zip URLs (in Analytics) before, but I'd like to track them once again. Does anyone know how to do this? Thanks
Reporting & Analytics | | poolguy0