{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreifyhuv3t3ymsvgp7ma3ii3dnq7oppssaopglhve54wp6qdeqbgsly",
    "uri": "at://did:plc:hqad6xwuzg7oqfmwylfkvqfm/app.bsky.feed.post/3mh3xifhrcsz2"
  },
  "path": "/viewtopic.php?t=33244&p=271128#p271128",
  "publishedAt": "2026-03-15T08:09:20.000Z",
  "site": "http://forum.palemoon.org",
  "textContent": "google search problems can stem from a variety of sources, but in this case it sounds like google objects to either Basilisk, your ISP/VPN/Proxy, or the amount of searches you do. Nothing to do with any changes or \"fixes\" in Basilisk.\n\nTo be entirely sure though, please include the support/troubleshooting information requested. F12 console errors and/or about:support.\n\nAlso, like browsers, there are only a handful of actual engines/indexes, but a whole lot of frontends/rebuilds. If you're looking for a google one, try any of these;\n\nStartpage, Presearch, Ask, SearX (not all instances, but most), DogPile, Gibiru, or Kagi.\n\nFor Bing frontends;\n\nDDG, Yahoo, Metager , Oscobo, You, Lilo, Qwant, Ecosia, MonsterCrawler, SwissCows, EntireWeb, Petal, ZapMeta, Ekoru, Lycos, Neeva, SearX (Not all instances, but most), DogPile.\n\nFor non-google/bing, try; Brave search, Mojeek, Wiby, Stract, Greppr, Marginalia, Yep.\n\n* * *",
  "title": "Basilisk • Re: google search not working",
  "updatedAt": "2026-03-15T08:09:20.000Z"
}