Test website availability across 30 locations

Overview

A homepage can behave differently across locations. This Clawbrowser demo checks the public Stake.com homepage from 30 geographic locations using authorized testing endpoints and records the outcomes.

What happens in the video

The task requests 30 isolated regional checks of the public Stake.com homepage. The agent runs sessions sequentially, corrects tab and screenshot handling, and records loading and verification states. A final table shows regional observations, URLs, timings, and screenshot paths, including partial outcomes. This is a test report, not evidence of successful access in all 30 locations.

Before you start

• A public URL and authorized testing endpoints.
• Locations and a definition of a successful load.

Step-by-step guide

Practical steps for adapting the recorded task. The video summary above describes the demonstrated result; these checks guide your own run.

1. 1

   Define the test

   Select the public page and regions. Keep the scope focused on page availability rather than treating it as validation of every service feature.

2. 2

   Run isolated checks

   Run one regional session at a time with a fresh profile for each location, as requested in the recording. Preserve region, final URL, screenshot, and outcome. The agent corrects unexpected tabs and screenshot failures before continuing the batch.

3. 3

   Compare outcomes

   Compile the structured report and preserve failures. A failed observation may reflect network or session conditions as well as a site restriction; retain evidence for diagnosis.

Try this prompt

Results

• A regional observation table for the requested 30-location test, with partial results visible.
• Final URLs, timings, and screenshot references for investigating load outcomes.

Questions about this workflow