Review the tool details
Compare responses only for locations with available probes. Compare the reported regions for the same page or domain.
Check whether a public URL is reachable from available regions. Compare HTTP responses to help diagnose location-specific access problems.
Use Website Location Tester ↗Enter the required details to explore the available output and report options.
A failed probe does not prove a website is unavailable to all visitors in that country; verify CDN, DNS and firewall behaviour. Review the source evidence before making changes.
Consider http response status, probe availability, regional failures together rather than relying on a single indicator.
A failed probe does not prove a website is unavailable to all visitors in that country; verify CDN, DNS and firewall behaviour. Compare the example workflow with your own actual results.
Prioritise the changes that help your audience, and recheck after deployment. A failed probe does not prove a website is unavailable to all visitors in that country; verify CDN, DNS and firewall behaviour.
Check regional responses when customers report that a website is difficult to access. Compare available country probes and investigate DNS, CDN or firewall settings before concluding that a market is blocked.
Compare responses only for locations with available probes. Compare the reported regions for the same page or domain.
An unavailable probe is not proof of a blocked website. Repeat a failed request before drawing conclusions.
Keep the result alongside the page or domain reviewed, so you can compare the evidence after making changes.
It reports whether an available probe could reach the submitted URL. Inspect the returned status and any error details.
Related check — Does a successful probe mean the page works for users? It confirms the probe reached a response. Test actual interactions and rendered content separately.
Prioritise markets served by the site. Compare a nearby and a distant region when diagnosing a delivery problem.
Related check — How do I test an intermittent outage? Record the URL, region and time of each failure. Compare with monitoring and incident logs to identify the pattern.
Routing, origin capacity or firewall policy may differ. Compare repeat checks and inspect host or CDN logs.
If one region times out while neighbouring probes return a success status, note the time and inspect edge and origin logs for that region. Compare a static resource and the affected page to narrow down whether delivery or application processing is involved.
It confirms the probe reached a response. Test actual interactions and rendered content separately.
Related check — What does reachability from a region mean? It reports whether an available probe could reach the submitted URL. Inspect the returned status and any error details.
Compare selected locations before and after the change. Review timing and cache response headers where available.
Related check — What is the difference between reachability and regional speed? Reachability asks whether a response was received. Speed compares timing under consistent conditions.
Review geo restrictions and firewall rules. Confirm whether the block matches your intended access policy.
Related check — Why does one location time out? If one region times out while neighbouring probes return a success status, note the time and inspect edge and origin logs for that region. Compare a static resource and the affected page to narrow down whether delivery or application processing is involved.
The requested URL may route to another hostname or region. Compare final destinations when investigating differences.
Related check — How should I verify a fix? Repeat the test from affected regions and a control location. Confirm ordinary users can reach the same final page.
Record the URL, region and time of each failure. Compare with monitoring and incident logs to identify the pattern.
Related check — Which regions matter most? Prioritise markets served by the site. Compare a nearby and a distant region when diagnosing a delivery problem.
Reachability asks whether a response was received. Speed compares timing under consistent conditions.
Related check — How can I verify a CDN rollout? Compare selected locations before and after the change. Review timing and cache response headers where available.
Repeat the test from affected regions and a control location. Confirm ordinary users can reach the same final page.
Related check — Can redirect rules affect results? The requested URL may route to another hostname or region. Compare final destinations when investigating differences.
SEO Mentor helps you identify opportunities. SEOKart can help put those findings into action with professional SEO services, technical improvements and ongoing optimisation.
Explore SEOKart SEO Services