{"id":24907,"date":"2015-10-29T00:00:00","date_gmt":"2015-10-29T00:00:00","guid":{"rendered":"https:\/\/alienroad.com\/google-bilgi-bankasi\/detect-and-get-rid-of-unwanted-sneaky-mobile-redirects\/"},"modified":"2015-10-29T00:00:00","modified_gmt":"2015-10-29T00:00:00","slug":"detect-and-get-rid-of-unwanted-sneaky-mobile-redirects","status":"publish","type":"ar_kb","link":"https:\/\/alienroad.com\/google-bilgi-bankasi\/detect-and-get-rid-of-unwanted-sneaky-mobile-redirects\/","title":{"rendered":"Detect and get rid of unwanted sneaky mobile redirects"},"content":{"rendered":"<p class=\"gargardate\">Thursday, October 29, 2015<\/p>\n<p>\n  In many cases, it is OK to show slightly different content on different devices. For example,<br \/>\n  optimizing the smaller space of a smartphone screen can mean that some content, like images, will<br \/>\n  have to be modified. Or you might want to<br \/>\n  <a href=\"https:\/\/developers.google.com\/web\/fundamentals\/layouts\/navigation-patterns\/navigationdrawer\" class=\"external-link\">store your website&#8217;s menu in a navigation drawer<\/a><br \/>\n  to make mobile browsing easier and more effective. When implemented properly, these user-centric<br \/>\n  modifications can be understood very well by Google.\n<\/p>\n<p>\n  The situation is similar when it comes to mobile-only redirect. Redirecting mobile users to<br \/>\n  improve their mobile experience (like redirecting mobile users from <code>example.com\/url1<\/code><br \/>\n  to <code>m.example.com\/url1<\/code>) is often beneficial to them. But redirecting mobile users<br \/>\n  sneakily to a different content is bad for user experience and is against<br \/>\n  <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/search-essentials-overview\/\">Google&#8217;s webmaster guidelines<\/a>.\n<\/p>\n<p><img decoding=\"async\" alt src=\"https:\/\/alienroad.com\/wp-content\/uploads\/kb-gorsel\/g-341981b86dc9.png\" loading=\"lazy\"><\/p>\n<h2 id=\"who-implements-these-mobile-only-sneaky-redirects\" tabindex=\"-1\">Who implements these mobile-only sneaky redirects?<\/h2>\n<p>\n  There are cases where webmasters knowingly decide to put into place redirection rules for their<br \/>\n  mobile users. This is typically a webmaster guidelines violation, and we do take manual action<br \/>\n  against it when it harms Google users&#8217; experience (see last section of this article).\n<\/p>\n<p>\n  But we&#8217;ve also observed situations where mobile-only sneaky redirects happen without site owners<br \/>\n  being aware of it:\n<\/p>\n<ul>\n<li>\n    <b>Advertising schemes that redirect mobile users specifically<\/b><br \/>\n     A script\/element installed to display ads and monetize content might be redirecting mobile<br \/>\n    users to a completely different site without the webmaster being aware of it.\n  <\/li>\n<li>\n    <b>Mobile redirect as a result of the site being a target of hacking<\/b><br \/>\n    In other cases, if your website has been hacked, a potential result can be redirects to spammy<br \/>\n    domains for mobile users only.\n  <\/li>\n<\/ul>\n<h2 id=\"how-do-i-detect-if-my-site-is-doing-sneaky-mobile-redirects\" tabindex=\"-1\">How do I detect if my site is doing sneaky mobile redirects?<\/h2>\n<ol>\n<li>\n    <b>Check if you are redirected when you navigate to your site on your smartphone<\/b><br \/>\n    We recommend you to check the mobile user experience of your site by visiting your pages from<br \/>\n    Google search results with a smartphone. When debugging, mobile emulation in desktop browsers is<br \/>\n    handy, mostly because you can test for many different devices. You can, for example, do it<br \/>\n    straight from your browser in<br \/>\n    <a href=\"https:\/\/developer.chrome.com\/devtools\/docs\/device-mode\" class=\"external-link\">Chrome<\/a>,<br \/>\n    <a href=\"https:\/\/addons.mozilla.org\/En-us\/firefox\/addon\/user-agent-overrider\/\" class=\"external-link\">Firefox<\/a><br \/>\n    o<br \/>\n    <a href=\"https:\/\/developer.apple.com\/library\/mac\/documentation\/AppleApplications\/Conceptual\/Safari_Developer_Guide\/TheDevelopMenu\/TheDevelopMenu.html#\/\/apple_ref\/doc\/uid\/TP40007874-CH7-SW5\" class=\"external-link\">Safari<\/a><br \/>\n    (for the latter, make sure you have enabled the &#8220;Show Develop menu in menu bar&#8221; feature).\n  <\/li>\n<li>\n    <b>Listen to your users<\/b><br \/>\n    Your users could see your site in a different way than you do. It&#8217;s always important to pay<br \/>\n    attention to user complaints, so you can hear of any issue related to mobile UX.\n  <\/li>\n<li>\n<p>\n      <b>Monitor your users in your site&#8217;s analytics data<\/b><br \/>\n      Unusual mobile user activity could be detected by looking at some of the data held in your<br \/>\n      website&#8217;s analytics data. For example, looking at the average time spent on your site by your<br \/>\n      mobile users could be a good signal to watch: if all of a sudden, your mobile users (and only<br \/>\n      them) start spending much less time on your site than they used to, there might be an issue<br \/>\n      related to mobile redirections.\n    <\/p>\n<p>\n      To be aware of wide changes in mobile user activity as soon as they happen, you can for<br \/>\n      example<br \/>\n      <a href=\"https:\/\/support.google.com\/analytics\/answer\/1033021h2&amp;vid=1-635769760082728193-812820847#create\" class=\"external-link\">set up Google Analytics alerts<\/a>.<br \/>\n      For example, you can set an alert to be warned in case of a sharp drop in average time spent<br \/>\n      on your site by mobile users, or a drop in mobile users (always take into account that big<br \/>\n      changes in those metrics are not a clear, direct signal that your site is doing mobile sneaky<br \/>\n      redirects).\n    <\/p>\n<p>    <img decoding=\"async\" alt src=\"https:\/\/alienroad.com\/wp-content\/uploads\/kb-gorsel\/g-38ddbb880c5b.png\" loading=\"lazy\">\n  <\/li>\n<\/ol>\n<h2 id=\"ive-detected-sneaky-redirects-for-my-mobile-users,-and-i-did-not-set-it-up:-what-do-i-do\" tabindex=\"-1\">I&#8217;ve detected sneaky redirects for my mobile users, and I did not set it up: what do I do?<\/h2>\n<ol>\n<li>\n<p>\n      <b>Make sure that your site is not hacked.<\/b><br \/>\n      Check the<br \/>\n      <a href=\"https:\/\/search.google.com\/search-console\/security-issues\" class=\"external-link\">Security Issues tool<\/a><br \/>\n      in the Search Console, if we have noticed any hack, you should get some information there.\n    <\/p>\n<p>\n      Review our additional resources on<br \/>\n      <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/nohacked-identifying-and-diagnosing-injected-gibberish-url-hacking\/#Monitoring\">typical symptoms of hacked sites<\/a>,<br \/>\n      and our<br \/>\n      <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/case-studies-fixing-hacked-sites\/\">case studies on hacked sites<\/a>.\n    <\/p>\n<\/li>\n<li>\n<p>\n      <b>Audit third-party scripts\/elements on your site<\/b><br \/>\n      If your site is not hacked, then we recommend you take the time to investigate if third-party<br \/>\n      scripts\/elements are causing the redirects. You can follow these steps:\n    <\/p>\n<ol>\n<li>\n        Remove one by one the third-party scripts\/elements you do not control from the redirecting<br \/>\n        page(s).\n      <\/li>\n<li>\n        Check your site on a mobile device or through emulation between each script\/element removal,<br \/>\n        and see when the redirect stops.\n      <\/li>\n<li>\n        If you think a particular script\/element is responsible for the sneaky redirect, consider<br \/>\n        removing it from your site, and debugging the issue with the script\/element provider.\n      <\/li>\n<\/ol>\n<\/li>\n<\/ol>\n<h2 id=\"last-thoughts-on-sneaky-mobile-redirects\" tabindex=\"-1\">Last Thoughts on Sneaky Mobile Redirects<\/h2>\n<p>\n  It&#8217;s a violation of the Google Webmaster Guidelines to redirect a user to a page with the intent<br \/>\n  of displaying content other than what was made available to the search engine crawler (more<br \/>\n  information on<br \/>\n  <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/spam-policies\/#sneaky-redirects\">sneaky redirects<\/a>). To ensure<br \/>\n  quality search results for our users, the Google Search Quality team can take action on such<br \/>\n  sites, including removal of URLs from our index.  When we take manual action, we send a message to<br \/>\n  the site owner via Search Console. Therefore, make sure you&#8217;ve<br \/>\n  <a href=\"https:\/\/support.google.com\/webmasters\/answer\/6001104\" class=\"external-link\">set up a Search Console account<\/a>.\n<\/p>\n<p>\n  Be sure to choose advertisers who are transparent on how they handle user traffic, to avoid<br \/>\n  unknowingly redirecting your own users. If you are interested in trust-building in the online<br \/>\n  advertising space, you may check out industry-wide best practices when participating in ad<br \/>\n  networks. For example, the Trustworthy Accountability Group&#8217;s (Interactive Advertising Bureau)<br \/>\n  <a href=\"https:\/\/www.tagtoday.net\/iqg\/\" class=\"external-link\">Inventory Quality Guidelines<\/a> are a<br \/>\n  good place to start. There are many ways to monetize your content with mobile solutions that<br \/>\n  provide a high quality user experience, be sure to use them.\n<\/p>\n<p>\n  If you have questions or comments about mobile-only redirects, join us in our<br \/>\n  <a href=\"https:\/\/support.google.com\/webmasters\/community\/\" class=\"external-link\">Google Webmaster Support forum<\/a>.\n<\/p>\n<p class=\"byline-author\">\n  Written by Vincent Courson and Badr Salmi El Idrissi, Search Quality team<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Thursday, October 29, 2015 In many cases, it is OK to show slightly different content on different devices. For example, optimizing the smaller space of a smartphone screen can mean that some content, like images, will have to be modified. Or you might want to store your website&#8217;s menu in a navigation drawer to make [&hellip;]<\/p>\n","protected":false},"menu_order":83263,"template":"","meta":{"footnotes":""},"ar_kb_kategori":[665],"ar_kb_etiket":[],"class_list":["post-24907","ar_kb","type-ar_kb","status-publish","has-post-thumbnail","hentry","ar_kb_kategori-blog"],"_links":{"self":[{"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/ar_kb\/24907","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/ar_kb"}],"about":[{"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/types\/ar_kb"}],"version-history":[{"count":0,"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/ar_kb\/24907\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/media\/27088"}],"wp:attachment":[{"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/media?parent=24907"}],"wp:term":[{"taxonomy":"ar_kb_kategori","embeddable":true,"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/ar_kb_kategori?post=24907"},{"taxonomy":"ar_kb_etiket","embeddable":true,"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/ar_kb_etiket?post=24907"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}