HTTPS, wtf!?!
-
Searching for any variation of the companies name or domain name returns the correct www.domain.com/ as the result domain, but searching for any variations of site:domain.com/ returns HTTPS://www.domain.com/
Even if I search site:domain.com -blog -product -forum -store -everything -etc
I've done that all the way down to 3 results, none of them are HTTP://www.domain.com/
WTF?!?! does this mean?
I know it means duplicate content, but beyond that. If I 301 to correct domain, or remove the HTTPS version in google webmaster tools will anything drastic happen?!!?
Thanks!
-
Thanks
-
Appreciate the help
-
Thanks for the help
-
I think your best bet is rel=canonical. Furthermore, Google agree:
http://www.google.com/support/webmasters/bin/answer.py?hl=en&answer=139394
This section is directly related to your issue:
How do I specify a canonical page?
snip
If you publish content on both http://www.example.com/product.php?item=swedish-fish and https://www.example.com/product.php?item=swedish-fish, you can specify the canonical version of the page. Create the element:
Hope that helps.
-
The guy that worked on this site before was for some reason trying to set up a multiple domain security certificate.
The site's like 10 years old, and of course I have sitemap that is linked through robots.
Any answers related specifically to my question would be appreciated
-
1st of all, do you have https on your website ? It would be a good idea to disallow robots through robot.txt from indexing sensitive parts of the website (user login etc etc).
Then submit a website through a sitemap. ( You can also mention sitemaps in your robot.txt).
That should get the ball rolling. You shouldnt expect huge benefits over a short period of time, but it will slowly show up.
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
-
Is it time to go https sitewide?
Hello mozzers, We are currently running a Magento 1 store and in the planning phase of migrating to Magento 2. As an eCommerce website, it goes without saying that we use secure pages for all pages where exchange of sensitive information is required, however, we do not use https on all pages. I recently read this Moz article stating that the adoption of sitewide https is at around 50% for top websites. I see Moz is also using it. I know that at this time right now, Google states not giving an SEO bump for https pages, but part of me thinks the time might be right (while re-platforming to M2) to make the move if this is what the future is going to be. Do you agree? Is this something that everyone will eventually have to do?
Algorithm Updates | | yacpro13
I am ambiguous about whether 301 redirects would be needed for http -> https ?
Also, is there a how-to or checklist to making the switch to sitewide https in order not to inadvertently cause an SEO drop? Thanks!0 -
Search traffic plummeting after HTTPS fumble - what to do now?
Hi all, Our website typically gets about 80% of our traffic from organic Google search over thousands of keywords (i.e., no single keyword (or group of) drives a large portion of our traffic). It's a nine year old website, and we have been growing steadily -- including about 30-40% year-over-year growth for the past 9-months. That is, up until Feb 2nd. On February 2nd, we switched to HTTPS. Everything was done per Google's recommendations: pages individually 301'd to HTTPS pages, no security warnings, added the new site in Webmaster Tools, etc. Google started to pick up our new site -- albeit 3 weeks into the transition, traffic was still significantly down. However, the big problem that we discovered was our ad revenues were getting destroyed. We're an ad based business and our CPMs were tanking, some of our ad partners were having problems serving ads, etc. We were losing a lot of money. So, we made the decision to reverse the HTTPS change and go back to HTTP. That was on Feb 22nd. Our traffic started to recover, and our ad rates did recover. However, 2-weeks after switching back -- March 8 -- our traffic started to fall and has continued to do so. Our traffic is now half of what it was a year ago, and only 1/3 of what it was before we made any changes. I am totally at a loss for what to do. I have spent endless hours digging through Webmaster Tools with no real insights. Here's the most I've been able to glean: Google picked up the new HTTPS site a lot faster than it has reverted back to the HTTP. Particularly for AMP pages. We had about 2,000 indexed AMP pages, which were quickly picked up when we switched to HTTPS, but since changing back to HTTP Google has been slow to re-index the HTTP. Only 935 AMP indexed pages now. According to Webmaster Tools, our overall ranking position has not been affected (the overall average). However, in a sampling of keywords I notice that a number of keywords seem to have been dropped completely from ranking, while others show the same rank position but Google seems to only be showing us in the results intermittently -- e.g., rank is unchanged, but impressions and clicks are much lower. I do not know what to do at this point, and sadly, I'm starting to get desperate for some help. I feel like all the hard work of almost a decade is slipping away and I have no idea how to change course. I've done absolutely everything I can think of from a technical standpoint. Am I being penalized for abandoning the switch to HTTPS? Should I now try and reverse course again, and switch BACK to HTTPS? Is this a temporary bobble that Google's algo will 'forget'? It's a super high quality website with long, unique, detailed articles. Not spammy and we have never had a manual action against us. I don't know what to do. Please help! Here's a link to the website. Thank you in advance.
Algorithm Updates | | tustind0 -
Http vs Https Related Rankings Drop?
I've noticed in a number of keyword ranking tools (Moz included) that our rankings have dropped substantially for a number of our top performing keywords precisely 7 days back. When you view the attached screenshot you'll see there was a drastic drop in the overall organic impressions as well as a drop in keyword rankings. I also noticed that all the keywords which have dropped in rank now show with the https version of our home page url. I've read up on this and it believe that this should not cause a drop in rankings but we have even added https as a domain in webmaster tools with no improvement. Quite simply, has Google de-indexed our http home page url which was previously tied to our higher rankings for our core keywords? How can we get this back without "disavowing" our https version of the site. We're not doing anything to game search results so I dont think we're being penalized, simply there is some sort technical glitch taking place between recognizing HTTP vs HTTPS versions of our site. Our home page is goo.gl/qVPRwf and an example keyword is "wedding ring sets his and hers" Can anyone recommend further debugging steps or have an understanding of what can be done at this point? Also, if it helps, I have studied the Help Center, read the FAQs and searched for similar questions with no success.wedding ring sets his and hers impressions%20-%20ranking%20drop.png?dl=0
Algorithm Updates | | punitshah0 -
Https & Google Updated Guidelines
Hi We have https on aspects of the site which users directly interact with, such as login, basket page. But we don't have https across the whole site. In light of Google adding it to their guidelines - is this something we need to put into action? Also same question on the Accessibility point Ensure that your pages are useful for readers with visual impairments, for example, by testing usability with a screen-reader. Are we going to be penalised if these are not added to our site? Thank you
Algorithm Updates | | BeckyKey0 -
Google indexing https sites by default now, where's the Moz blog about it!
Hello and good morning / happy Friday! Last night an article from of all places " Venture Beat " titled " Google Search starts indexing and letting users stream Android apps without matching web content " was sent to me, as I read this I got a bit giddy. Since we had just implemented a full sitewide https cert rather than a cart only ssl. I then quickly searched for other sources to see if this was indeed true, and the writing on the walls seems to indicate so. Google - Google Webmaster Blog! - http://googlewebmastercentral.blogspot.in/2015/12/indexing-https-pages-by-default.html http://www.searchenginejournal.com/google-to-prioritize-the-indexing-of-https-pages/147179/ http://www.tomshardware.com/news/google-indexing-https-by-default,30781.html https://hacked.com/google-will-begin-indexing-httpsencrypted-pages-default/ https://www.seroundtable.com/google-app-indexing-documentation-updated-21345.html I found it a bit ironic to read about this on mostly unsecured sites. I wanted to hear about the 8 keypoint rules that google will factor in when ranking / indexing https pages from now on, and see what you all felt about this. Google will now begin to index HTTPS equivalents of HTTP web pages, even when the former don’t have any links to them. However, Google will only index an HTTPS URL if it follows these conditions: It doesn’t contain insecure dependencies. It isn’t blocked from crawling by robots.txt. It doesn’t redirect users to or through an insecure HTTP page. It doesn’t have a rel="canonical" link to the HTTP page. It doesn’t contain a noindex robots meta tag. It doesn’t have on-host outlinks to HTTP URLs. The sitemaps lists the HTTPS URL, or doesn’t list the HTTP version of the URL. The server has a valid TLS certificate. One rule that confuses me a bit is : **It doesn’t redirect users to or through an insecure HTTP page. ** Does this mean if you just moved over to https from http your site won't pick up the https boost? Since most sites in general have http redirects to https? Thank you!
Algorithm Updates | | Deacyde0 -
Moving to https and back to http, would it it hurt?
We have redirected everything on our blog from http to https. Our blog is in a subfolder so that now it looks like this: https://ourdomain/blog; But everything else i.e. our shop continues to be on http at http://ourdomain We are wondering: 1- Does the domain authority for SEO purposes have different values for the http and the https version of a domain? 2- If yes, is there a way to check the difference in authority between the http and the https version? 3- If we do have a higher authority on our http version (as historically we have been mostly on our http), would it make sense to go back to the http for the blog to enjoy that authority too? 4- Would changing our mind and going back to http after a few months of just having moved to https from http send any negative signals to Google? Would Google care if we do a back and forth essentially? Many thanks!
Algorithm Updates | | TVape0 -
Google Latest Algorithmic Change about Https & Mobile Friendliness
How effective did it prove for anyone with the latest algorithmic change google search engine made for being mobile friendly and using https (valid ssl certificate). I see a good change being made under the ecommerce category for sites being used for online shopping. Let me know if anyone observes a major difference.
Algorithm Updates | | mozexpone0 -
Https slower site Versus Non https faster site??
Hey all, I know that everyone is going on about https as a ranking signal (as far as I read it is not a very important ranking signal, but a low ranking signal) but Site speed is a ranking signal https is now a ranking signal as well https makes sites slower So in view of the above, what's better? An https site that is slower A non https site that is faster Thanks!
Algorithm Updates | | bjs20100