Something new is on the wayWe are updating the site to match the latest extension. Some pages may change while we finish.

A Google check stopped. What next?

Learn about CAPTCHA and 403 errors and how to resume a browser-based check.

Read the run status

Google may show a CAPTCHA or return a 403 response when it restricts search requests. A connection problem or browser interruption can also stop a check. Read the message in Tracker before restarting.

If Google shows a CAPTCHA

Open the Google tab identified by the tracker and follow Google's instructions. Return to Tracker and continue the run if the controls allow. Solving a CAPTCHA does not guarantee that later requests will succeed.

If Google returns a 403 block

Stop repeated retries and wait before trying again. Check if a regular Google search works in the browser. Shared networks, VPNs, and request volume can affect access, but a 403 response does not confirm a specific cause.

ShoSERP cannot guarantee or force removal of a Google restriction. Pro does not bypass blocks.

Why checks take time

The extension waits between requests. The estimated duration shown before a run may vary, and large keyword lists can take hours. Keep the browser available and start with your most important keywords.

Before continuing

Check which keywords have saved results. An interrupted full run may not become the project's completed comparison baseline. Individual keyword checks are labeled separately in Tracker V2.

If the problem continues, contact support with the visible error, approximate time, and what happened before the run stopped. Do not send passwords or session tokens.

Last updated:
When Google blocks a check