Google.com search now refusing to search for FF esr 128 without JavaScript
It just redirects everything to https://www.google.com/httpservice/retry/enablejs?sei=... I guess this is the inevitable end of the era of the web as a collection of hyperlinked documents and the beginning of the web as an application delivery protocol.
In other browsers with JS disabled google search still works but this computational paywall rollout for Firefox esr is a sign of things to come.
89 comments
[ 5.1 ms ] story [ 154 ms ] threadMakes me wonder about Google and AI, with my tin-foil hat on, I cannot help but think Google/AI searches your cache and cookies looking for info.
(Google services' widespread use by 3rd party sites does give them more data, but they have that whether you load google.com with JS or not. And again, unclear how AI changes anything about what data is available to them.)
This is nonsense. Any cached data or cookies that Google’s scripts have access to was saved by those same scripts. If any site’s “AI” (not sure what you mean by that) could search through objects cached by other sites, you’d have bigger problems.
I agree Google is trying to force AI on us, but for a different reason: to demonstrate its value to shareholders.
[0]: https://www.eff.org/deeplinks/2023/09/how-turn-googles-priva...
[1]: https://www.schneier.com/blog/archives/2025/01/google-is-all...
window.addEventListener("load", function() { remover.init(); }, false);
It’s a blank page with one line of text: “Please click here if you are not redirected within a few seconds”.
For the dyed-in-the-wool, lynx https://www.google.com, tab and type in test, tab and enter, Now how can I get lynx to remove the ad?
Startpage search on "Google requires Javascript" replies "Allow JavaScript in your browser - Google AdSense Help" - now isn't that special?
With the caveat that this used to 100% work, but since a couple months, it indeed occasionally redirects to the “Turn on JavaScript to keep searching” page you mention, https://www.google.com/httpservice/retry/enablejs . I'd say the refusal happens 1 / 20 searches. Said differently, I’d prefix your “refusing” with a “sometimes”.
I haven’t investigated the reason for this sometimes-ness. Would love to find an answer here, or ideas/leads (aside switching to another search engine, yes I do know about them, but sometimes Google remains better). Or maybe the sometimes-ness was just A/B testing, and the full switch is happening and this is now a thing of the past.
EDIT you must have posted precisely at the moment of the end of the A/B test: I did several non-JS searches today at $job, and to confirm what I was writing here I did a test one, successfully. But 30min later, I confirm your observation: 100% blocked.
e.g. https://duckduckgo.com/?t=ffab&q=filter+coffee+site%3Areddit...
Edit: maybe you are thinking about the AI deal which is exclusive to Google. That's not the same thing as search engine indexing https://www.cbsnews.com/news/google-reddit-60-million-deal-a...
@mastazi that’s what I’m talking about, and I think your AI vs. indexing nuance is incorrect. I wasn’t sure, so I just did a quick N=1 verification: searching for the name of a random 1week-old popular Reddit post with a precise unique title,
- Insta-found it on Goog as top result
- Didn't find it on DDG, with or without site:reddit.com
Looks like sibling comment from @cpressland (thanks!) is correct: as of today and until other search engines sign licensing agreements with Reddit, “non-Google search engines cannot get new results from Reddit”. See https://www.reddit.com/robots.txt , which links to https://support.reddithelp.com/hc/en-us/articles/26410290525... , section “Reddit may license public content for commercial or non-commercial use”
> a random 1week-old popular Reddit post with a precise unique title
While a week is a long time, is it possible that the other search engines just hadn't got around to indexing it yet?
Kagi I don’t know much about, but quickly reading about it, seems to indeed pay Goog.
> “While a week is a long time, is it possible that the other search engines just hadn't got around to indexing it yet?”
I doubt it, search engines these days are much faster, and this is double-confirmed by 1. articles linked in sibling comments, 2. reading https://www.reddit.com/robots.txt
I found this article by Ars Technica that highlights the consequences of the deal for search engines:
https://arstechnica.com/gadgets/2024/07/non-google-search-en...
so Reddit, the website co created by Aaron Swartz, is now a walled garden.
Wow.
My Google is set to German. Apparently Reddit has autotranslated all their content into German.
If I do a Google search for "ssd zfs pool" the 4th result is "SSD-Pool eine schlechte Idee? : r/Proxmox" and this links to `https://www.reddit.com/r/Proxmox/comments/12a5abh/ssd_pool_a...`.
The Reddit page is in German, but as you may have noticed, the URL has `?tl=de` appended, while it contains `ssd_pool_a_bad_idea` in the path. If I remove the `?tl=de`, I get the original version, in English.
This means that what Google crawled, what it has in its index, was already in German. So Reddit translated the original page into German, then made it accessible for Google to index it.
For me this causes the problem that I am now getting a lot of AI-translated Reddit content, even though I'd really like to have the English version to begin with, because I assume that it won't contain translation errors.
I mean, the translation is very good, you probably wouldn't notice that it is one, but still...
https://www.reddit.com/r/Proxmox/comments/12a5abh/ssd_pool_a...
https://www.reddit.com/r/Proxmox/comments/12a5abh/ssd_pool_a...
Stop using Reddit. Reddit is already following the path toward nothing but SEO spam and malware. Use Hacker News or Fediverse.
EDIT: Figured it out - https://www.reddit.com/r/firefox/comments/1ca4ii3/what_is_fi... - it's "Firefox Extended Support Release" - https://support.mozilla.org/en-US/kb/firefox-esr-release-cyc...
Edit: Reloading doesn't work anymore for me. Unless the sca_esv=xxxxxxxxx param is present it will redirect to the JS wall.
Screen readers are not a type of web browser. They are software which interacts with other software running on the computer, including web browsers. There is nothing which inherently makes JS or CSS incompatible with screen readers.
JS gives the same improvements for screen readers as for everyone else especially with complex apps.
Bad JS of course ruins things as usual, same bad HTML with table layout or whatever. But that's not JS on google.com;)
https://en.m.wikipedia.org/wiki/WAI-ARIA
That said, as ARIA rule #1 says, it's better to not use javascript, as it's always less error prone. That doesn't mean websites shouldn't use javascript when they have reasons to do so, as long as they correctly follow ARIA.
We’re looking in the wrong place if we want an ad company to be the champion of anything but revenue optimization.
Some HN commenters suggest DDG or paid search. Funnily enough, DDG is returning a CAPTCHA at the moment.
Fortunately I have many other free www search engine options that are working fine.
In addition there are countless website search engines that all continue to work. No Javascript required.
I use noscript and refuse to turn on JavaScript for anything but actual Web Applications. I do not turn it on for general browsing of content to be read or search because the the UX abuse that JavaScript enables.
The majority of exploits in the wild are delivered via drive by JavaScript.
That said I'm all for honest Advertising if the UX is not shit.
In fact I think there should be an HTML5 <ad></ad> tag implmented in the browsers sandbox that supports IAB VAST specs so none the that "VAST MACRO" garbage would need to done via huge JavaScript payloads.
You can also click the wrench icon in the Google SERP and choose Send feedback.
In the meantime, use another search engine, such as Brave Search, DDG or Searx.
From five years ago: https://dev.to/ziizium/famous-websites-with-javascript-disab...
And eight years ago: https://www.jakobstoeck.de/2017/websites-which-work-great-wi...
It does seem like JavaScript is required on more sites as time moves forward.
If the statement was "Javascript is used on more sites" then I would agree and it is easy to test for use of Javascript.
But a statement like "Javascript is required on more sites" is difficult to agree with as I have a very different experience..
For example, I am now retrieving Google results from the command line without Javascript using a specific UA string. Arguably, that means no Javascript is "required" to retrieve search results. A specific UA string is now required though. Use the wrong UA string and then Javascript is "required" to retrieve the results.
Rather than focusing on Javascript, a more interesting question might be whether more sites are requiring specific UA strings.
By default I do not use Javascript (I do not use a graphical web browser) nor do I send a User-Agent header. The overwhelming majority of websites "work" for me with no problems. To me, it does not seem that more sites are requring specific UA strings as time moves forward.
Google www search is just one website. The www is vast.
Ask.com: Does not work; does nothing at all.
Ecosia: Blocks me indirectly by cloudflare.
Startpage: Blocks me explicitly, saying "Your connection has been suspended"
Maybe they're doing some weird geofencing or dislike your ISP?
- https://html.duckduckgo.com/html/
- https://searx.be
- https://mojeek.com
- http://frogfind.com
Not affiliated with Kagi btw.
Of course that’s highly subjective, so I think it’s worth trying out their free tier to see if the potential improvement in search result quality is something you notice and find valuable enough to spend money on.
Here is an extended list:
https://searx.space/
https://serpapi.com/blog/google-now-requires-javascript/
https://serpapi.com/blog/google-now-requires-javascript/