What ValueSERP provides
ValueSERP is a Google search-results API now presented under Traject Data, which has joined ScraperAPI; the former ValueSERP site redirects to the current Traject Data product.
Its responses cover organic listings and rich SERP elements, making the resolved destination link a central field for customers. The ownership change does not itself establish how /goto links are handled.
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 ValueSERP has said
No public /goto response foundNo ValueSERP, Traject Data or ScraperAPI statement specifically addressing /goto was found. ValueSERP’s former site now redirects to Traject Data, which continues to market the API after Traject Data joined ScraperAPI.
Traject Data describes browser rendering, parsing and optional multi-step downloading, capabilities that could support resolution. It does not say that production ValueSERP output uses them for every /goto variant, so the actual method remains undisclosed.
The current product and documentation establish continuity of the API brand, not destination-link correctness. General uptime cannot substitute for a /goto field test, incident record, affected percentage or residual error rate.
No /goto-specific surcharge or quota change was found. Current request-based pricing does not reveal whether the new owner absorbs additional collection cost.
No provider-specific /goto release or attributable statement is linked because none was found in the public review.
What is known — and what is not
The current product and documentation establish continuity of the API brand, not destination-link correctness. General uptime cannot substitute for a /goto field test, incident record, affected percentage or residual error rate.
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