Urgent.News

What's breaking now, across thousands of outlets.

Tech

Google no longer provides direct URLs in search results

Google is transitioning from providing direct URLs in search results to using a redirect system called google.com/goto. When a user clicks on a search result, Google redirects them to the actual page. The destination URL is encoded in a custom format that is not a simple base64 encoding. This change is now visible consistently across searches, even when a user is logged out or browsing in private mode.

Google has used redirect wrappers before, but this is no longer limited to a small portion of search results. The older format, which exposed the destination URL directly in the query string, is still present, but the new format is being rolled out more widely. This shift impacts anyone building a search index from SERP data at scale, as it requires making a request back to Google to learn the destination.

Google's move is part of a broader effort to combat automated SERP harvesting, particularly from AI crawlers and SEO scrapers. By requiring each result to have a separate request to Google, the company aims to slow down and make more noisy the scraping process, while also providing clearer signals when the same client resolves many links in sequence.

Google has updated its API to resolve the google.com/goto links and return the final destination URL in API responses. Developers who use Autom's Google Search endpoints should continue to receive usable destination URLs without making changes to their integration.

Written by urgent.news from Hacker News's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at autom.dev →

More in Tech

The Intelligence Ladder

How much intelligence do we really need? I have been sitting with this question for a long time. The more I fold language models into my daily work as a software developer, the less sure I am about a…

  • Proposes intelligence ladder system to sort AI work into rungs with model and cost estimates.
  • Current AI model answers lead to sunk cost trap, unclear true costs for users.
  • Behavior-based system breaks work into shareable pieces called behaviors, assigned to rungs.

Context engineering is mostly deciding what to leave out

Most advice about context windows is about fitting more in. Bigger windows, more retrieved documents, the whole file instead of the function.

  • Context engineering focuses on removing irrelevant information
  • A smaller, focused context often yields better results
  • Unnecessary context is costly in both money and quality

How I built a Pit Wall with AWS IoT Core (and why this pattern works for any industry)

Hola a todos! Hace unos meses me surgio la idea de empezar a correr en simrace nuevamente, en pandemia me compré el volante y lo usé un rato pero perdi la motivación cuando me di cuenta de lo dificil…

  • Author built a Pit Wall using AWS IoT Core for racing simulation.
  • Captured data from Assetto Corsa simulator and sent to AWS IoT Core.
  • Pattern applies to any device generating data outside infrastructure.

More from Saturday 12 September →