New Articles
Windows 11 users have discovered a funny bug that benefits older computers....
It's easy to turn off the transmission — we tell you how to do it....
Such photos have been taken by models and social media users for a long time,...
A famous musician? A schoolteacher? Mom? Tell us about the people you looked up...
Thanks to the instructions of Artyom Kozoriz, you can cope no worse than a...
5 interesting exercises that will help you develop flexibility....
From "Starship Troopers" and "The Matrix" to...
The return of Garfield and Mufasa, the new Transformers and the Lord of the...
About Everything Wiki » Life Hack » How to improve the results page in Google

How to improve the results page in Google

03 May 2023, 19:19, parser
0 comments    0 Show

Search engines are probably the most visited sites. When you are looking for something more or less common and well-known, there is no problem, you can even use the I’m feeling lucky button. However, it is often necessary to view several pages of search results. And here you already start to feel the inconveniences of the current Google interface.

When the desired site is not on the first page of search results, you go to the second, third, etc. Wouldn't it be more convenient if the pages were loaded automatically when scrolling, as in Google Read when reading news? The Redmond competitor does exactly that with regard to image search.

Fortunately, there is a Pagerization script — General Auto Pager for Greasemonkey (an add-on to Mozilla Firefox). It makes Google search look like reading RSS. New search results are automatically loaded when scrolling.

Unlike another similar GoogleAutoPager script, this one supports working with a large number of sites — Google (Search, Image, News, Group, Video), Yahoo, Wikipedia, Hatena, YouTube, del.icio.us , Twitter, Digg and Userscripts.org . It's true that Digg works uncertainly, but I didn't notice any problems with Google services.

Pagerization — General Auto Pager [userscripts.org]

Read also:
14 Jan 2024, 00:01    0    0
To figure it out, you'll have to delve into the history of Apple....
Comments
reload, if the code cannot be seen