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
-
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 -
Which Sitemap to keep - Http or https (or both)
Hi, Just finished upgrading my site to the ssl version (like so many other webmasters now that it may be a ranking factor). FIxed all links, CDN links are now secure, etc and 301 Redirected all pages from http to https. Changed property in Google Analytics from http to https and added https version in Webmaster Tools. So far, so good. Now the question is should I add the https version of the sitemap in the new HTTPS site in webmasters or retain the existing http one? Ideally switching over completely to https version by adding a new sitemap would make more sense as the http version of the sitemap would anyways now be re-directed to HTTPS. But the last thing i can is to get penalized for duplicate content. Could you please suggest as I am still a rookie in this department. If I should add the https sitemap version in the new site, should i delete the old http one or no harm retaining it.
Technical SEO | | ashishb010 -
Blog RSS behind https
Hi, I'm finding our blog's RSS feed won't be recognized by various websites. The feed is on a https url. Is this the most likely problem? Thanks!
Technical SEO | | OTSEO0 -
Is the If-Modified-Since HTTP Header still relevant?
I'm relatively new to the technical side of SEO and have been trying to brush up my skills by going through Google's online Web-master Academy, which suggests that you need a If-Modified-Since HTTP Header tag on your site. I checked and apparently our web server doesn't support this. I've been told by a good colleague that the If-Modified-Since tag is no longer relevant as the spiders will frequently revisit a site as long as you regularly update and refresh the content (which we do). However our site doesn't seem to of been reindexed for a while as the cached version's are still showing the pages from over a month ago. So two question really - is the If-Modified-Since HTTP Header still relevant and should I make sure this is included? And is there anything else I should be doing to make sure the spiders crawl our pages? (apart from keeping them nice, fresh and useful)
Technical SEO | | annieplaskett0 -
Another http vs https Question?
Is it better to keep the Transaction/ Payment pages on a commercial website as the only secure ones (https) and remainder of website as http? Or is it better to have all the commercial website as secure (https)?
Technical SEO | | sherohass0 -
Mobile Theme Switching
Hi - wondering what one should do with a mobile theme in relationship to Google. We are using wordpress and then a plugin that detects whether or not the user is on a mobile device. Should you no-follow the mobile theme since it is effectively the same content as the main site? Or just leave it be and not worry about it. Thanks!
Technical SEO | | leeg0 -
Will using https across our entire site hurt our external backlinks?
Our site is secured throughout, so it loads sitewide as https. It is canonicalized properly - any attempt to load an existing page as http will force to https. My concern is with backlinks. We've put a lot of effort into social media, so we're getting some nice blog linkage. The problem is that the links are generally to http rather than https (understandable, since that's the default for most web users). The site still loads with no problem, but my concern is that since a redirect doesn't transfer all the link juice across, we're leaking some perfectly good link credit. From the standpoint of backlinkage, are we harming ourselves by making the whole site secure by default? The site presently isn't very big, but I'm looking at adding hundreds of new pages to the site, so if we're going to make the change, now is the time to do so. Let me know what you think!
Technical SEO | | ufmedia0