|(New) Google bug - same page is shown for position 20 -120|
I Recently a found a Google bug - when I'm searching for a special query I'm getting the same URL (same title, same description) for position 20 to 120 in the SERPs when I'm limiting the number of results to one per page.
Of course, only an SEO would ever search with 1 result per page, but this shows that something wrong with the results.
If I change to 10 results per page then identical URLs on any one page are filtered out. However, I still find the same URL at the bottom of many pages - at #20, #30, #40, #50 and so on.
I'm not sure if this kind of bug was already reported.
A possible explanation for the behaviour is that there is number of different URLs in Google's database which are merged to the same page (URL). When searching for some phrase Google considers these URLs as different. In a second step, the internal different URLs are replaced by the merged one. In a third step, identical URLs are filtered out from the SERPs. This would explain the behaviour described above. However, this is just a theory. A reason for merging different URLs is identical content, e.g. from mydomain.com and my-domain.com or using 301 redirects.
I tried to replicate that, but I am not seeing it.
I assume you are adding &num=1 to the end of your search string and then clicking forward until you see them repeat?
Indeed, I added &num=1. But the bug just appear for a few keywords.
Interestingly, when I checked it today, the bug is still there, however, the page given on position 20-120 has changed.
Is it a keyword (content) search, or a domain / url search?
If the latter, I really wouldn't worry, most 'webmaster searches' get obfuscated in one way or another.
It's a (normal) keyword search.
|I still find the same URL at the bottom of many pages - at #20, #30, #40, #50 and so on |
I can confirm that this kind of bug does show up - I also have seen the exact same url show up on several pages in the SERP. In the cases I noticed, the bug went away within a week or so. I always felt like this bug could be a window into how Google generates the SERP, but I never had any insight.