Occasionally, I get "Redirect Notice" pages when I click on some Google search results. My website does have a landing page redirect, but no redirect notice shows up when I click on it in Google search. I couldn't find any info about what types of redirects cause Google to display the warning. What exactly are the causes of Google's redirect notices, and what can webmasters do to prevent them from showing up when visitors click on their site in Google?
1I've never seen a redirect notice in Google search before. Can you post a screenshot?– Stephen Ostermiller ♦Aug 5, 2018 at 10:37
Do your URLs have hashes in them? seroundtable.com/archives/022510.html– Stephen Ostermiller ♦Aug 5, 2018 at 10:40
Are you using AMP? salon.com/2017/09/24/…– Stephen Ostermiller ♦Aug 5, 2018 at 10:41
Normal search, or image search?– MaxAug 6, 2018 at 5:58
@Max Normal search– clickbaitAug 6, 2018 at 14:02
I think there may be (or may have been) a few scenarios that can trigger this "redirect notice" from the Google SERPs. Some of these may have been historical "glitches" judging by some of the articles I stumbled across.
I have certainly seen this "redirect notice" several times directly from Google search results in recent times, however, I've not been able to find such a search result whilst researching this question. I have always associated this with a malicious redirect. Although whether this has been truly malicious or just an implementation mishap I don't know.
However, one easily repeatable way to trigger this "redirect notice" is to try to use Google's "internal" redirect service. That is, using the
url - see below) parameter on the
/url URL (this would seem to be how search result URLs used to be constructed - see below). For example:
This instructs Google to redirect to the URL specified in the
q URL parameter. Apparently, according to this article (Feb 2007), Google used to trigger a redirect without prompting. This was naturally open to abuse, so Google introduced the prompt:
When Google constructs such a URL (eg. in the search results), they incorporate a cryptic hash in the URL that validates the target URL, thus avoiding the prompt.
However, Google no longer appears to use the
q parameter in the SERP URLs these days. Instead, they appear to use a
url parameter, together with a cryptic hash. Copying*1 and sharing the entire URL results in the same "redirect notice" (I now realise that this is what @ShayanDavoodi was referring to in his answer! +1), for example:
(As pointed out in @ShayanDavoodi's answer, this probably helps prevent Google SERP CTR being manipulated. Although you don't necessarily need the explicit "redirect notice" for that - it certainly alerts developers not to try.)
However, attempting to modify the value in the
url parameter results in a wholly invalid target URL, but still triggers a "redirect notice". For example:
Sometimes when you share a URL from a single result in SERP with someone that didn't perform the search, the redirect notices appears.
This is for preventing click and CTR manipulation by having fake entrances (clicks that don't actually happen and is generated by an expired Google SERP URL. )
Also it might indicate your site is hacked and is redirecting Google-bot user-agent to another URL.
You can check this using User-agent switcher for Google chrome to check if your pages have suspecious behaviour.
1How exactly are you sharing a URL from the SERPs? And what URL are you sharing specifically? How does this relate to the OPs scenario (and also my experience) where the "redirect notice" occurs when clicking directly on the search result, having just performed a Google search yourself?– MrWhiteSep 2, 2018 at 11:41
1In case you are messing with canonical link of a certain document by putting the canonical link of a page as a URL from Google SERPs (In order to manipulate number of clicks and CTR). This doesn't make any sence but some old-school BH SEOs still use these so-called techniques. Sep 3, 2018 at 9:37
2I see what you're saying now! +1 ;) When I first tried "sharing" the intermediary/tracking Google search URL (which is not "easy" to copy/share) it seemed to work OK, no "redirect notice" when accessing from outside of Google search. However, subsequent tests have resulted in the "redirect notice", so not sure what I did earlier.– MrWhiteSep 4, 2018 at 9:12