Current public boundary
The existing portal supports controlled HTTP testing of authorized targets. This documentation does not promise hosted browser journeys, screenshots, scheduling, SERP execution or arbitrary URL fetching. Use only capabilities actually exposed for your account in the live portal.
Prepare a safe scenario
Choose an owned or explicitly authorized domain and a read-only path. Specify expected status or text, maximum time and a small request budget. Private networks, loopback, metadata endpoints and redirects to unauthorized targets must not be treated as public test destinations.
Mark the test traffic
Use an explicit synthetic marker such as cc_synthetic=1 on an owned application when supported by its routing, or server-side test metadata. Configure analytics exclusion before the run and verify it. Do not attach a fake public search referrer or create ad/affiliate interactions.
Interpret the evidence
An HTTP response establishes transport and content facts only. It cannot prove visual layout, JavaScript behavior or mobile usability. Browser tests require a separate authorized runner and assertions. Stop on unexpected mutations or redirects and retain only sanitized diagnostics.