Need clean destination URLs without the hassle of Google’s intermediate redirect (“goto”) links? We’ve got a solution! Introducing resolve_goto_urls, a new Google SERP API parameter that handles redirect resolution on our side, so you can work directly with final URLs in your JSON results.
The parameter is available for the Google Organic, News, Local Finder, and Search By Image SERP API endpoints.
What’s new
- Final destination URLs in JSON results. When Google returns redirect links instead of direct result URLs, our system follows those redirects and replaces the corresponding
urlfield values with the final destination URLs. - Automatic resolution for Standard Normal-priority tasks. Goto URLs are now resolved automatically for Standard tasks with the default Normal execution priority.
- Optional resolution for Live and High-priority tasks. Enable the feature by setting
resolve_goto_urlstotrue. - Resolution through Task Get. Resolve redirect URLs when retrieving results for previously processed tasks.
How it works
You can enable the resolution of Google’s redirects when submitting a task or when retrieving its results, depending on the request type.
Live requests
Set resolve_goto_urls to true in your request payload:
{
"resolve_goto_urls": true
}
By default, the parameter is disabled for Live requests.
Standard tasks
URL resolution depends on the task’s execution priority:
| Task priority | Default behavior |
Normal ("priority": 1 or omitted) |
Redirect resolution is enabled automatically. No changes to existing requests are required. |
High ("priority": 2) |
Redirect resolution is disabled by default. Set resolve_goto_urls to true to enable it. |
Task Get requests
You can also enable “goto” resolution when retrieving results through Task Get by appending ?resolve_goto_urls=true to the request URL:
/v3/serp/google/organic/task_get/advanced/11091412-0696-0066-0000-5d21fa5fdcf6?resolve_goto_urls=true
The first GET request with this parameter resolves the redirect URLs and stores the results with the task. Subsequent requests return the stored URLs without repeating the resolution process.
Important notes
- Redirect resolution requires additional processing time and thus adds at least 40 seconds to Live and High-priority request turnaround time, while total request processing time never exceeds 260 seconds.
- If a redirect cannot be resolved, the original URL is returned unchanged.
- The
resolve_goto_urlsparameter affects JSON results only (Regular and Advanced). The raw HTML of the SERP remains unchanged, exactly as it was captured.
Why it matters
The resolve_goto_urls parameter simplifies working with Google SERP data by eliminating the need to handle intermediate redirect URLs in your own applications.
With final destination URLs available directly in JSON results, you can streamline data processing, improve URL consistency across rank tracking and competitor analysis workflows, and reduce development effort by relying on DataForSEO to handle redirect resolution.
Get started
Ready to try it? For Live and High-priority tasks, add "resolve_goto_urls": true to your next Google SERP API request. For Normal-priority Standard tasks, URL resolution is already enabled by default.
Explore the endpoint documentation for more details on the new parameter:
You can also explore the DataForSEO SERP API documentation to discover more available features.