Location-based page previews

On a schedule or when a page is published, the agent requests TestLocally previews from the locations you care about, reads how the page renders in each region, and writes the results to your tracking record. It applies your rules to note pass or fail per location and notify the owner. Regions showing broken layouts, missing content, or blocked access are flagged for a person, since deciding whether the difference is a real defect or an expected regional variation calls for judgment the agent leaves to your team.

Regional screenshot capture

When a check runs, the agent captures screenshots of the target page from each selected location through TestLocally, reads them against your baseline, and stores the images on the related record for comparison. Where a region matches the baseline within your rules, it marks the check clean. Noticeable visual differences are not judged final by the agent: it attaches the before and after and notifies a reviewer, who confirms whether the change is intended, a rendering bug, or a location-specific issue worth a fix and follow-up.

Load and availability checks

Running on your chosen interval, the agent reads TestLocally load and availability results for the monitored pages from each location, applies your thresholds, and updates the status record. When every region responds within limits, it records a healthy result quietly. Locations reporting slow loads, errors, or an unreachable page trigger a notification to the on-call owner with the failing regions and timings listed, so a person decides whether it is a local network blip or a genuine outage that needs a coordinated response from the team.