What Scrapeless provides
Scrapeless builds web-unlocking and structured-data services for developers, AI systems and automation teams.
Deep SerpApi returns current Google results and SERP features as JSON for search grounding, RAG, SEO monitoring and research.
Where the redirect matters
The destination URL is a core output. If Google exposes an opaque /goto token rather than the publisher URL in result markup, the service must follow or otherwise resolve that intermediary before returning the link customers expect. At scale, an extra operation per result can increase latency, failure rates and collection cost even when the public API schema stays the same.
/goto?url=[hash]resolve + attributepublisher URL
What Scrapeless has said
Specific /goto responseScrapeless says it added /goto handling to its Google Search API so customers can continue receiving usable destinations without building their own resolution layer.
The company recommends detecting intermediary links, navigating them through controlled HTTP or a browser, validating the result, and preserving observed, redirect-chain, final and normalised URLs separately. It does not publish request counts, caching or per-surface coverage.
The method is technically plausible and more detailed than a generic unaffected claim. Public endpoint documentation predates the broad rollout and supplies no field-by-field coverage matrix, sample, success rate or audit, so the evidence does not prove every result surface is resolved.
No /goto-specific price, credit or quota change was announced, and no public surcharge was found.
What is known — and what is not
The source record above is the latest attributable evidence located for Scrapeless. Its stated outcome is not treated as an independent accuracy audit: the exposure rating still describes the relevant product’s dependence on resolving live Google result URLs.
What customers should monitor
- Organic link fields containing google.com/goto instead of publisher URLs
- Higher response time, empty results or partial SERPs
- Parser, schema, pricing or quota notices concerning Google results
What should remain outside the change
- Non-Google sources where the redirect is not deployed
- Previously stored results that already contain resolved URLs