Detect and get rid of unwanted sneaky mobile redirects
Stay organized with collections
Save and categorize content based on your preferences.
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's menu in a navigation drawer
to make mobile browsing easier and more effective. When implemented properly, these user-centric
modifications can be understood very well by Google.
The situation is similar when it comes to mobile-only redirect. Redirecting mobile users to
improve their mobile experience (like redirecting mobile users from example.com/url1
to m.example.com/url1) is often beneficial to them. But redirecting mobile users
sneakily to a different content is bad for user experience and is against
Google's webmaster guidelines.
Who implements these mobile-only sneaky redirects?
There are cases where webmasters knowingly decide to put into place redirection rules for their
mobile users. This is typically a webmaster guidelines violation, and we do take manual action
against it when it harms Google users' experience (see last section of this article).
But we've also observed situations where mobile-only sneaky redirects happen without site owners
being aware of it:
Advertising schemes that redirect mobile users specifically
A script/element installed to display ads and monetize content might be redirecting mobile
users to a completely different site without the webmaster being aware of it.
Mobile redirect as a result of the site being a target of hacking
In other cases, if your website has been hacked, a potential result can be redirects to spammy
domains for mobile users only.
How do I detect if my site is doing sneaky mobile redirects?
Check if you are redirected when you navigate to your site on your smartphone
We recommend you to check the mobile user experience of your site by visiting your pages from
Google search results with a smartphone. When debugging, mobile emulation in desktop browsers is
handy, mostly because you can test for many different devices. You can, for example, do it
straight from your browser in
Chrome,
Firefox
or
Safari
(for the latter, make sure you have enabled the "Show Develop menu in menu bar" feature).
Listen to your users
Your users could see your site in a different way than you do. It's always important to pay
attention to user complaints, so you can hear of any issue related to mobile UX.
Monitor your users in your site's analytics data
Unusual mobile user activity could be detected by looking at some of the data held in your
website's analytics data. For example, looking at the average time spent on your site by your
mobile users could be a good signal to watch: if all of a sudden, your mobile users (and only
them) start spending much less time on your site than they used to, there might be an issue
related to mobile redirections.
To be aware of wide changes in mobile user activity as soon as they happen, you can for
example
set up Google Analytics alerts.
For example, you can set an alert to be warned in case of a sharp drop in average time spent
on your site by mobile users, or a drop in mobile users (always take into account that big
changes in those metrics are not a clear, direct signal that your site is doing mobile sneaky
redirects).
I've detected sneaky redirects for my mobile users, and I did not set it up: what do I do?
Make sure that your site is not hacked.
Check the
Security Issues tool
in the Search Console, if we have noticed any hack, you should get some information there.
Audit third-party scripts/elements on your site
If your site is not hacked, then we recommend you take the time to investigate if third-party
scripts/elements are causing the redirects. You can follow these steps:
Remove one by one the third-party scripts/elements you do not control from the redirecting
page(s).
Check your site on a mobile device or through emulation between each script/element removal,
and see when the redirect stops.
If you think a particular script/element is responsible for the sneaky redirect, consider
removing it from your site, and debugging the issue with the script/element provider.
Last Thoughts on Sneaky Mobile Redirects
It's a violation of the Google Webmaster Guidelines to redirect a user to a page with the intent
of displaying content other than what was made available to the search engine crawler (more
information on
sneaky redirects). To ensure
quality search results for our users, the Google Search Quality team can take action on such
sites, including removal of URLs from our index. When we take manual action, we send a message to
the site owner via Search Console. Therefore, make sure you've
set up a Search Console account.
Be sure to choose advertisers who are transparent on how they handle user traffic, to avoid
unknowingly redirecting your own users. If you are interested in trust-building in the online
advertising space, you may check out industry-wide best practices when participating in ad
networks. For example, the Trustworthy Accountability Group's (Interactive Advertising Bureau)
Inventory Quality Guidelines are a
good place to start. There are many ways to monetize your content with mobile solutions that
provide a high quality user experience, be sure to use them.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],[],[[["\u003cp\u003eDifferent content can be shown on different devices as long as it's user-centric and not deceptive.\u003c/p\u003e\n"],["\u003cp\u003eSneaky mobile-only redirects, which send mobile users to different content than desktop users, violate Google's guidelines and harm user experience.\u003c/p\u003e\n"],["\u003cp\u003eThese redirects can be intentional or unintentional, sometimes caused by advertising schemes or website hacking.\u003c/p\u003e\n"],["\u003cp\u003eWebsite owners can detect sneaky redirects by checking their site on mobile, monitoring user feedback and analytics data, and using tools like Google Search Console.\u003c/p\u003e\n"],["\u003cp\u003eIf redirects are detected, website owners should ensure their site isn't hacked and audit third-party scripts to identify the source.\u003c/p\u003e\n"]]],["Mobile-only redirects can negatively impact user experience and violate Google's guidelines. These redirects can be intentional or unknowingly implemented through advertising scripts or hacking. To detect them, check your site on a mobile device, monitor user feedback and website analytics for unusual mobile user behavior, such as a sudden drop in time spent on the site. If detected and unintended, check for site hacks using the Security Issues tool, and audit third-party scripts. Removal of URLs from Google's index could be the result of the usage of sneaky redirects.\n"],null,["Thursday, October 29, 2015\n\n\nIn many cases, it is OK to show slightly different content on different devices. For example,\noptimizing the smaller space of a smartphone screen can mean that some content, like images, will\nhave to be modified. Or you might want to\n[store your website's menu in a navigation drawer](/web/fundamentals/layouts/navigation-patterns/navigationdrawer)\nto make mobile browsing easier and more effective. When implemented properly, these user-centric\nmodifications can be understood very well by Google.\n\n\nThe situation is similar when it comes to mobile-only redirect. Redirecting mobile users to\nimprove their mobile experience (like redirecting mobile users from `example.com/url1`\nto `m.example.com/url1`) is often beneficial to them. But redirecting mobile users\nsneakily to a different content is bad for user experience and is against\n[Google's webmaster guidelines](/search/docs/essentials).\n\nWho implements these mobile-only sneaky redirects?\n\n\nThere are cases where webmasters knowingly decide to put into place redirection rules for their\nmobile users. This is typically a webmaster guidelines violation, and we do take manual action\nagainst it when it harms Google users' experience (see last section of this article).\n\n\nBut we've also observed situations where mobile-only sneaky redirects happen without site owners\nbeing aware of it:\n\n- **Advertising schemes that redirect mobile users specifically** \n A script/element installed to display ads and monetize content might be redirecting mobile users to a completely different site without the webmaster being aware of it.\n- **Mobile redirect as a result of the site being a target of hacking** \n In other cases, if your website has been hacked, a potential result can be redirects to spammy domains for mobile users only.\n\nHow do I detect if my site is doing sneaky mobile redirects?\n\n1. **Check if you are redirected when you navigate to your site on your smartphone** \n We recommend you to check the mobile user experience of your site by visiting your pages from Google search results with a smartphone. When debugging, mobile emulation in desktop browsers is handy, mostly because you can test for many different devices. You can, for example, do it straight from your browser in [Chrome](https://developer.chrome.com/devtools/docs/device-mode), [Firefox](https://addons.mozilla.org/En-us/firefox/addon/user-agent-overrider/) or [Safari](https://developer.apple.com/library/mac/documentation/AppleApplications/Conceptual/Safari_Developer_Guide/TheDevelopMenu/TheDevelopMenu.html#//apple_ref/doc/uid/TP40007874-CH7-SW5) (for the latter, make sure you have enabled the \"Show Develop menu in menu bar\" feature).\n2. **Listen to your users** \n Your users could see your site in a different way than you do. It's always important to pay attention to user complaints, so you can hear of any issue related to mobile UX.\n3.\n **Monitor your users in your site's analytics data** \n\n Unusual mobile user activity could be detected by looking at some of the data held in your\n website's analytics data. For example, looking at the average time spent on your site by your\n mobile users could be a good signal to watch: if all of a sudden, your mobile users (and only\n them) start spending much less time on your site than they used to, there might be an issue\n related to mobile redirections.\n\n\n To be aware of wide changes in mobile user activity as soon as they happen, you can for\n example\n [set up Google Analytics alerts](https://support.google.com/analytics/answer/1033021h2&vid=1-635769760082728193-812820847#create).\n For example, you can set an alert to be warned in case of a sharp drop in average time spent\n on your site by mobile users, or a drop in mobile users (always take into account that big\n changes in those metrics are not a clear, direct signal that your site is doing mobile sneaky\n redirects).\n\nI've detected sneaky redirects for my mobile users, and I did not set it up: what do I do?\n\n1.\n **Make sure that your site is not hacked.** \n\n Check the\n [Security Issues tool](https://search.google.com/search-console/security-issues)\n in the Search Console, if we have noticed any hack, you should get some information there.\n\n\n Review our additional resources on\n [typical symptoms of hacked sites](/search/blog/2015/08/nohacked-identifying-and-diagnosing#Monitoring),\n and our\n [case studies on hacked sites](/search/blog/2015/02/case-studies-fixing-hacked-sites).\n2.\n **Audit third-party scripts/elements on your site** \n\n If your site is not hacked, then we recommend you take the time to investigate if third-party\n scripts/elements are causing the redirects. You can follow these steps:\n\n 1. Remove one by one the third-party scripts/elements you do not control from the redirecting page(s).\n 2. Check your site on a mobile device or through emulation between each script/element removal, and see when the redirect stops.\n 3. If you think a particular script/element is responsible for the sneaky redirect, consider removing it from your site, and debugging the issue with the script/element provider.\n\nLast Thoughts on Sneaky Mobile Redirects\n\n\nIt's a violation of the Google Webmaster Guidelines to redirect a user to a page with the intent\nof displaying content other than what was made available to the search engine crawler (more\ninformation on\n[sneaky redirects](/search/docs/essentials/spam-policies#sneaky-redirects)). To ensure\nquality search results for our users, the Google Search Quality team can take action on such\nsites, including removal of URLs from our index. When we take manual action, we send a message to\nthe site owner via Search Console. Therefore, make sure you've\n[set up a Search Console account](https://support.google.com/webmasters/answer/6001104).\n\n\nBe sure to choose advertisers who are transparent on how they handle user traffic, to avoid\nunknowingly redirecting your own users. If you are interested in trust-building in the online\nadvertising space, you may check out industry-wide best practices when participating in ad\nnetworks. For example, the Trustworthy Accountability Group's (Interactive Advertising Bureau)\n[Inventory Quality Guidelines](https://www.tagtoday.net/iqg/) are a\ngood place to start. There are many ways to monetize your content with mobile solutions that\nprovide a high quality user experience, be sure to use them.\n\n\nIf you have questions or comments about mobile-only redirects, join us in our\n[Google Webmaster Support forum](https://support.google.com/webmasters/community/).\n\n\nWritten by Vincent Courson and Badr Salmi El Idrissi, Search Quality team"]]