Desktop in http and mobile in https
-
Any experience or advice you can share of having a mix set of pages/urls in one site/domain https and http
e.g. mobile in https and desktop in http ,
(desktop version) http://mydomain/product1
(mobile version)https://m.mydomain.com/product1
att the same time some mobile pages still in http://m.mydomain.com/sectionA/
thanks
-
Unfortunately not, due to issues with data integrity and seasonal variations in traffic. What I can say is that it did not have a catastrophic impact on our traffic. Google still indexed both versions of the webpages if it found them, and chose to display one or the other. Since we don't have a constant to compare it with, it's difficult to ascertain the exact impact it's having. I can say that the less competitive terms with lower traffic we're ranking for just fine, but we're on page five for the most competitive term (with the most volume) we're attempting to rank for, and both an http and https page are vying for position. That's in part the structure being an issue, and also in part the content on the page is thinner than I'd like it to be.
If you run into this issue on specific pages, try adding a rel canonical tag to the page you want Google to rank. If you use this strategy only when you check your rank tracking tools to see which pages are in the SERP and having issues, you can cut down on the maintenance, and quickly determine whether or not it's the duplicate content that's preventing you from ranking or if you need to focus on other on-site or off-site signals.
-
Hi Brett,
Thanks for your insights, this basically reinforce my concerns since I might be potentially deal with this landscape, would you able to share any percentile figures in terms of traffic impact by having this mixed URLs in the sitemap?thanks again
/Arnoldo
-
Hi CleverPHdthanks for your reply, yes agree and one of the reasons for this question is actually the upcoming mobile first update and how Google will behave once is live.
-
This can create some real headaches. If you're going to secure a part of the site, you may as well secure the whole thing. Leaving part of the site unsecured and just securing a few pages that are transactional or used to collect customer data like physical addresses is something other sites have done, but should be considered a temporary solution while securing the rest of the site.
While I'm not sure that this implementation would create dark traffic in your Google Analytics reports, you're still leaving yourself open to MIM attacks and other SEO issues with a partial implementation, such as creating duplicate content. I'm dealing with this issue right now with a couple clients and I can share one of the headaches we're experiencing.
Mixed sitemap URLs! Some URLs are in https and others are in http, because they've managed to confuse the CMS (don't ask, I'm not sure what they did yet). On top of that, duplicate content is created with every new page, because the CMS now creates a page in http and a page in https. The dynamic XML sitemap then picks one and adds it. It gets worse, but I'll end it there.
You can avoid all this by securing everything, and you'll have the optional benefit of upgrading the site to HTTP/2 if you secure the whole thing first.
-
Hello!
If you want to do this. You need to setup your rel alternate and canonical links
https://developers.google.com/webmasters/mobile-sites/mobile-seo/separate-urls
I am not sure if the https vs http designation is that big of a deal as you are already setting up a separate set of URLs with the www. and the m.
What is interesting here is that with the new mobile first update occurring, I am not sure that this page will eventually be updated to have the canonicals point to the mobile version vs the desktop version as mentioned in the link above. Likewise, the https is favored for ranking so there may be another reason to canonical that direction, but you would need to test and see. You may find that due to the mobile first initiative and Googles preference for https that your m. pages might do better.
Generally, I would find a way to move away from the m. setup and simply run a responsive site on https://www - that is going to get you the best bang for your buck.
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
-
Old pages not mobile friendly - new pages in process but don't want to upset current traffic.
Working with a new client. They have what I would describe as two virtual websites. Same domain but different coding, navigation and structure. Old virtual website pages fail mobile friendly, they were not designed to be responsive ( there really is no way to fix them) but they are ranking and getting traffic. New virtual website pages pass mobile friendly but are not SEO optimized yet and are not ranking and not getting organic traffic. My understanding is NOT mobile friendly is a "site" designation and although the offending pages are listed it is not a "page" designation. Is this correct? If my understanding is true what would be the best way to hold onto the rankings and traffic generated by old virtual website pages and resolve the "NOT mobile friendly" problem until the new virtual website pages have surpassed the old pages in ranking and traffic? A proposal was made to redirect any mobile traffic on the old virtual website pages to mobile friendly pages. What will happen to SEO if this is done? The pages would pass mobile friendly because they would go to mobile friendly pages, I assume, but what about link equity? Would they see a drop in traffic ? Any thoughts? Thanks, Toni
Technical SEO | | Toni70 -
Www or https only
All pages are secure on my website now. Some of my pages listed on Google are now https://domain.com and some are https://www.domain.com Which format should I use and why? (with www or without?) I want to give Google a new site map URL in the Google search console? Yes I know both URLs go to the same page.
Technical SEO | | Audio-Bible1 -
Google Bot is seeing the desktop version in cache for Mobile website too.
Hi, I have an e-commerce website that is dynamic(not responsive) in nature. when i check the cached version of mobile website it shows the desktop version in cache. Will it create any problem . How can i tell google bot to see my mobile cached version instead of desktop one.
Technical SEO | | dhananjay.kumar10 -
For responsive site what should be lowest Screen Resolution for Desktop?
Hello Guys, Can you please share in details screen resolution I have to define for my responsive site for desktop, tablet & mobile. Your inputs are very valuable to me. Thanks! Micey
Technical SEO | | micey1230 -
New site - http or https?
Hi. We are currently in the process of creating a new website. We will be using our old domain name. However, the current website is currently live on both http and https protocols, with no re-directs in place. When we launch the new website, we would like to redirect everything to one or the other. Would the preference be to use https as the preferred protocol?
Technical SEO | | Lexica0 -
Multi Domain SSL Certs re HTTPS migration
Hi How important is it that when migrating sites to HTTPS they have their own SSL certificates as opposed to choosing the much cheaper multi domain certificate options such as: https://www.namecheap.com/security/ssl-certificates/comodo/ev-multi-domain.aspx I have been told really should have 1 certificate per domain and people generally unsure about multi domain certsificates ? All Best Dan
Technical SEO | | Dan-Lawrence0 -
Disallowing https URLs
It there a problem disallowing all https URLs to be indexed in order to avoid duplication? This is the article recommending this practice - http://blog.leonardchallis.com/seo/serve-a-different-robots-txt-for-https/ Thanks!
Technical SEO | | theLotter0 -
Mobile site: robots.txt best practices
If there are canonical tags pointing to the web version of each mobile page, what should a robots.txt file for a mobile site have?
Technical SEO | | bonnierSEO0