Transitioning to HTTPS, Do i have to submit another disavow file?
-
Hi Mozzers!
So we're finally ready to move from http to https. Penguin is finally showing us some love due to the recent algorithm updates. I just added the https to Google search console and before 301 redirecting the whole site to a secure environment.....do i upload the same disavow file to the https version?
Moreover, is it best to have both the http and https versions on Google Search console? Or should I add the disavow file to the https version and delete the http version in a month?
And what about Bing?
Help.
-
If Bing will allow you to do it then yes. I can't add "other" version for my websites so probably Bing covers "all".
-
What about for Bing? Do i create 4 variations?
-
so ok, just for disavows.
-
yes.
-
Just for adding disavow. Because you have redirects set well right?
-
Krzysztof,
Does that mean I have to add sitemaps to all 4 versions as well? Including data highlighter schema? Or the purpose of these 4 it to redundant disavow files?
Thank you
-
Hi Shawn
Yes. Make sure you have all properties in your Google Search Console: www.domain.com, domain.com, https://domain.com, https://www.domain.com even if you have redirects. If you don't, create them, verify, and upload disavow file to all 4 "versions". If you got some subdomains, do the same for them too.
Don't delete. Add to all 4.
Krzysztof
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
-
Https Referral Issues
Hi Moz! We are having some trouble passing along referral data to our linked websites. We are an advertising platform that counts on our clients seeing our traffic in analytics. We recently switched to HTTPS and implemented the meta referral <always>however, we are still experiencing issues with clients not seeing our referral traffic. Are there other ways to make a full-proof fix so they will always see us as a referral? I know the referral tag should help but it isn't supported by all browsers. </always> Also, would there be an issue if we have our site (https) linked to their http site that redirects to https? Even with the referral tag, we are seeing issues. I feel so lucky that our actual transition to https went fine but now with all this referral traffic on clients analytics, I am concerned we are losing the credit we should get for the traffic to their site. Thanks Moz Community!
Reporting & Analytics | | GoAbroadKP0 -
Google Analytics Set-Up for site with both http & https pages
We have a client that migrated to https last September. The site uses canonicals pointing to the https version. The client IT team is reluctant to put 301 redirects from the non-secure to the secure and we are not sure why they object. We ran a screaming frog report and it is showing both URLs for the same page (http and https). The non-secure version has a canonical pointing to the secure version. For every secure page there is a non-secure version in ScreamingFrog so Google must be ignoring the canonical and still indexing the page however, when we run a site: we see that most URLs are the secure version. At that time we did not change the Google Analytics setup option to use: "https" instead of "http" BUT GA appears to be recording data correctly. Yesterday we set up a new profile and selected "https" but our question is: Does the GAnalytics http/https version make a difference if so, what difference is it?
Reporting & Analytics | | RosemaryB1 -
Https question
I had a site with an ssl certificate on. It has now been taken off. We are getting 404 errors on the weekly report for pages that were indexed as https What is the best way to get rid of these? How can I take them off the map or do we need to put the ssl back on? Thanks
Reporting & Analytics | | sharpster0 -
Moving to https - Webmaster Tools
Okay so I've moved a site I work on to https finally... wasn't easy, but I won't go into the whys and hows of that. Everything is working fine on the site and my rankings are holding steady but when I went into the GWT today I noticed that my main site (www.domain.com) has lost inquiry and traffic data almost entirely. So I quickly added and verified the https://www.domain.com URL (even though it doesn't ask for the protocol when adding a site) and saw the traffic.. kind of. Only 2 inquiries and a few pages indexed. Now I realize I need to submit a new sitemap and am currently working on that but don't know which account to upload it to. Do I really need two GWT sites separately and why is the other one still getting the impressions and clicks? Basically I'm looking for somebody to shed some light on how to handle this migration from a GWT standpoint. I've attached 3 screenshots to illustrate what I'm talking about. Should be obvious what's what to those who read this post. The Analytics shot is to show that I haven't actually lost traffic in this time and eliminate the fear of penalty or anything of the sort. Thanks! wbPpwVw.png YJifLiR.png cRVgqRN.png
Reporting & Analytics | | jesse-landry0 -
Webmaster Tools, why does it show 486 pages submitted to web, and only 40 indexed?
I am confused on what a client account shows in WMTs, client account is http://multiview.com. They have a graph showing 486 pages submitted to web, but only 40 are indexed. Also, they recently re-launched, i.e in April 2014, and the new site has about 40 pages indexed.... so I am guessing that the 486 number relates to all the pages that are showing errors in retrieving...i.e. 28 soft 404 errors, 10 access denied errors, 808 not found errors. Does this make sense to explain why there is such a gap between 486 and 40?
Reporting & Analytics | | DianeDP0 -
Want to track AJAX form submits. Is this correct?
Hi! I would like to track everytime a visitor clicks a AJAX contact form's submit button. I created an event in Google Analytics and plan to add some javascript to the submit button code. This is the current submit button code: This is how it'll look after I add the category, action, etc.: Is this correct or am I missing something? Please let me know if you need further detail. Thanks a lot!
Reporting & Analytics | | alfredo.uy0 -
Getting traffic for another site
Hi Everyone, Our website url/brand is very close to another website url/brand. We are non-competing entities. It appears as though this other company has begun a marketing program which has resulted in our traffic skyrocketing. However, it seems to have also resulted in our Pages/Visit and Visit Duration to decrease and our Bounce Rate to increase. Can anyone suggest how to deal with this type of scenario? Thanks,
Reporting & Analytics | | AC_Pro
Robert0 -
SEO implications of moving from https to http
We're considering moving from 100% https to http to improve performance. What, if any, SEO implications are there? Do search engines need redirects when changing from https to http pages?
Reporting & Analytics | | BlueAcorn0