New Unlimited Proxy Controls in the Member Area
We’ve updated Unlimited proxy management in the a-parser.com Member Area.
Separate Subscriptions for Multiple Computers and Servers
Use "Add Subscription" to add multiple Unlimited proxy subscriptions to one account. For each subscription, you can choose the plan, thread count, billing period, and access IP.
Auto-Renewal from Your Account Balance
Auto-renewal can be enabled separately for each subscription. If there are enough funds in your account, A-Parser charges the renewal fee 24 hours before expiration and renews the subscription for the same term.
Expiration Notifications
Each subscription card shows the expiration date and the number of days remaining. A-Parser notifies you before the subscription expires and reminds you to check your balance for auto-renewal.
Balance Top-Up Bonus: Up to 15%
A balance top-up bonus is available in the Member Area:
- Top-up of $500 or more: 10% bonus — your account receives $550.
- Top-up of $1,000 or more: 15% bonus — your account receives $1,150.
Bonus funds can be used toward any A-Parser products and services, including purchasing and renewing Unlimited proxy packages. The promotion applies to all available payment methods and is valid until September 15.
Google's /goto Rollout: What Changed in Search Results and How A-Parser Handles It
1. Introduction: A Major Change to Google Search Result Links
In late August 2026, Google began rolling out a change to its search results pages: direct links to websites started disappearing from some results. Instead of the usual destination URL, users and scrapers began receiving intermediate links of the form:
Code:
https://www.google.com/goto?url=CAES...Organic-result links have long been a core part of the web. Google now places a server-side redirect layer in front of them. This change disrupted data-collection scripts and required SaaS platforms and rank-tracking services to adjust their processing.
In beta version 1.2.3614, /goto bypass was added to the
SE::Google scraper.2. Rollout Timeline: From Early Tests to Global Deployment
- July 2026: Google's first isolated experiments. The new link format began appearing sporadically in search results across a limited sample of search queries and residential IPs.
- First half of August 2026: The
/gotoformat was tested in the background. The share of SERPs containing at least one such redirect was around 5.4%. - August 24–26, 2026: The share spiked to 6%, and on August 26 Google officially confirmed the rollout of the changes to industry media.
- August 27–31, 2026: Broad rollout. In searches run through residential IP pools, the share of SERPs with
/gotoreached nearly 100%. Redirects affected not only standard "blue links" but also SERP features such as AI Overviews, Local Pack (maps/businesses), Featured Snippets, videos, carousels, and Google Lens — a total of 18 SERP feature types. In the first few days, some third-party services and APIs returned unresolved links in rich-result blocks while adapting their parsers.
3. How
/goto WorksAt first glance, the link looks like a standard redirect:
https://www.google.com/goto?url=CAESkAFodHRwczovL2V4YW1wbGUuY29t...The
?url= parameter contains an encoded redirect payload:- Protocol Buffers (Protobuf): Unlike older Google redirects (
/url?q=https://site.com), here the address is not transmitted in plain text. Google packs the navigation metadata into the strictly typed binary Protobuf format. - No Public Schema: The binary stream contains only field numbers, wire types, and values. Field names exist only in a private
.protodefinition on Google's servers. - Base64 Encoding (
CAES...prefix): The binary Protobuf payload is converted into a URL-safe Base64 string. In raw SERP HTML and parser responses, the distinctiveCAES...marker appears instead of the website URL.
4. Why Google May Have Made the Change
A Google spokesperson said:
Industry observers have proposed several business and technical explanations:
1. Impact on AI Search and Grounding Workflows
Some industry observers see the change as an obstacle for companies such as OpenAI and Perplexity, as well as other AI agents that use web search to ground answers in current sources.
Previously, a system could retrieve the top 10 results in one HTTP request. With
/goto, resolving the destination may add a step for each result. On a page with 10 results, this could mean up to 10 additional network requests, higher latency, and higher infrastructure costs.2. Large-Scale Scraping and Legal Pressure
Google has sought to curb automated data collection through technical and legal measures. The new redirect layer may add a technical barrier to how Google delivers search results.
3. The Cost of Resolving Redirects
If a scraper cannot decode or resolve the payload, it may need to use browser automation tools such as Puppeteer or Playwright, or follow every redirect through residential proxies. At high volumes, those extra steps can materially increase collection costs.
5. How the Market Responded
The August
/goto rollout caught much of the industry off guard:- Major analytics platforms and rank trackers: reported data inconsistencies and updated their collection pipelines to preserve reporting accuracy.
- Cloud search API providers: issued fixes as the rollout expanded across SERP features.
- Custom scripts and simple scrapers: could return empty strings or
google.comURLs instead of destination URLs. - Potential click-count distortion: following redirects can increase proxy traffic and, if requests are treated as clicks, distort click-based analytics.
6. A-Parser's Technical Solution
In A-Parser 1.2.3614, we updated the
SE::Google module with native support for Google's new link format.
Code:
A-Parser 1.2.3614:
- Added bypass for Google's new protection: supported bypass of /goto redirects (when Google hides real links from search results)7. What Should an A-Parser User Do Right Now?
Just update to the latest version:
- Open the A-Parser control panel.
- Go to the software update section or download the latest available beta version of A-Parser.
- Restart the parser.
- Your
SE::Googlescraping tasks will continue running normally, outputting direct target website URLs.
Google Update Summary
Google's new
/goto format changes how destination URLs are handled in search results. A-Parser 1.2.3614 includes native support for that format in SE::Google.Update A-Parser to the latest available beta version to use the new
/goto handling in SE::Google.
Last edited: