You have always (well for as long as I can remember) been able to select the number of search results shown by Google.
The default is 10
Then they add in various other things like news, video, images, local results etc.
Those additions are generally known as universal search
Then you might have results included from your social circle – I have quite a large social circle because I follow lots of people on different social networks, so I almost always see them in the search results.
Google 20 Results Per Page
This isn’t unusual in itself, you could select 20 results before, but now even if I go into advanced search and select 10 results, or manually add &num=10 Google is still giving me 20 search results.

Pseudo Site Search 20 Search Results
A couple of weeks ago Google rolled out what I coined pseudo site search. I spent so long trying to gather data, work out exactly why it was happening and come up with a name for it that Malcolm got the drop on me writing about it.

I should point out pseudo site search isn’t brand – there are more prerequisites – there has to be a very specific indication in the search query that the intent might have been to perform a search query for a specific domain, but either the searcher was unaware of syntax or just lazy.
Commercial Reason For Google To Make Change
A week or so back Dan Taylor of Destination 360 mentioned in a comment on the travel technology blog Tnooz that for the search query [bellagio las vegas] he was seeing 7 out of 10 results from Bellagio.com – travel is a competitive even for hotels as a specific destination and Dan happens to have a page that might rank even higher for Bellagio Las Vegas now (thanks for the great example search result)
I was an idiot and didn’t grab a screenshot then… sigh.
So here is a current 20 page result of which bits were being pushed around. It isn’t now showing a pseudo site search.

Everything below the current #5 result for Trip Advisor was being pushed onto the 2nd page of results, and trip advisor itself was at #10 with Vegas.com 8 & 9
Now imagine that everyone was forced to have 20 search results like I currently am for US searches… I still get 10 in the UK & Poland.
Whilst those results for hotel review sites would be pushed down, they would still be on the page, and a reader might be more tempted to scroll down a 20 result page.
Significance
For some search queries I think this would be useful, though it might cost Google revenue as there are no ads at the bottom half of the search results if people did start scrolling.
It may also result in the 2nd page of results being totally worthless, rather than just very low traffic, for all search queries.
This doesn’t mean you should ever be happy with a page #1 search result – the fold line – the part of the page immediately visible when opened gets most clicks, thus unless someone is using a very high resolution monitor anything below result #3 is frequently severely hampered.
Also with personalization and region there are significant variations in what is seen in the results.
You will also tend to have a lot more double search results in Google.
I would assume this is just a test for now, though Google did roll out the pseudo site search to everyone at once.






























How I Kicked Myself Out Of Google Blogsearch For Months or Years
I’m either a total idiot or a raving lunatic or both.
I can’t even pinpoint within my data as to when this foolish or unfortunate incident occured because well… just look at the data.
That is nigh on 5 years of Google Blogsearch referral data, though because of the long time range it is listed as sampled data. There may be some traffic sources I have missed – variations of url depending on how Google were displaying blogsearch pages, but that is referrals from http://blogsearch.google.com
Because of all of these factors I had always assumed that the idea of using noindex on a feed of any kind was to prevent that feed appearing in Google’s primary organic results.
A pretty Feedburner feed isn’t a terrible landing page, but it is possble to do better. I have even written about using my feedburner URL when leaving blog comments in the past, as in some ways it immediately signals you want people to subscribe more so than linking to a blog.
Other RSS search engines were indexing my feed content – Technorati, Blogcatalog, Icerocket – my feeds were being read by my readers, picked up by various Twitter robots etc.
And of course my content remained indexed in Google’s primary organic index.
But then a few days ago I was browsing a little and looking for additional sources for a story followon, and noticed I wasn’t listed for previous coverage. I hadn’t been specific in the title that I was related… but there wasn’t a lot of competition.
Then I discovered this:-
My first thought for 5 minutes was somehow for some crazy reason I had become penalized in Google Blogsearch – then I rationalized it in thinking it must be something to do with noindex settings in Feedburner.
You see I had never equated noindex with a blog search engine – every other blog search engine which sent me traffic was still picking up my content and sending me traffic.
Google Indexing RSS Feeds
There is still a very real need for a way to tell Google…
3 years ago Google were saying they were working to remove RSS feeds from organic search.
3 years later feeds from Feedburner are still appearing in organic search results.
http://feeds.feedburner.com all the results seem to have been removed
http://feeds2.feedburner.com there still seems to be plenty of feeds within the search results
Information About & Help With Feedburner Since Google Acquisition
On a scale of 1 to 10 Google Feedburner Support gets a 2 – it is a free service, Google monetize it providing Adsense for feeds, but don’t expect anyone to answer support queries in the Google groups from Feedburner.
Documentation is sparse – hardly updated in the over 3 years since Google bought Feedburner… but then there haven’t been too many visible changes other than adding Adsense. I am sure there have been changes to help with scaling, especially how it eventually was made easier to integrate with Blogspot, but very little for anyone else.
Feedburner Noindex Controls
So this I believe is the culprit
This is the code that gets added to the RSS feed.
That data is still not transferred to feed items that are shared within Google Reader or feeds such as tags created there – which can get fed to other places and indexed.
The left hand doesn’t know what the right hand is doing
I have explained my whoopsie, but somewhere in the Googleplex they are a little confused over what they are doing as well.
Blogsearch isn’t the only search for my Blog posts
For instance there is Google Buzz
Now remember – Google is treating the noindex on my RSS feed as being an instruction to not include my content in Google BlogSearch…. so you would expect that instruction to be universal for the RSS content.
Those were taken from the PUBLIC timeline of Buzz. That is content that Google isn’t indexing on Blogsearch due to a noindex in the XML.
I also have my full content being fed into Facebook and being indexed and made searchable within Facebook, but at least that is my choice.
The only way to prevent content being shared and indexed is currently to block Google Reader from accessing feeds. I have been trying for over 4 years to get Google to introduce more publisher controls for sharing… as it would be easy to share private content from Google Reader by mistake… with Pubsubhubbub it can be broadcast by mistake to your 1000s of Buzz subscribers instantly.
This is possibly why Google have never introduced support for http authentication.
With their current stance for sharing freedoms, it doesn’t make sense for them to treat the current xml declarations as an instruction not to index the content in Blogsearch, as the content is in Buzz anyway. It should be treated as just a noindex for the page.
Alternatively they should add support for x-header noindex, then noindex in the XML would be for search engines, and it should travel with each content item, even to Buzz, possibly with no way to share the content.