Browser Steps
Monitor pages that require login or user interactions
Browser Steps let you automate interactions before Site Spy captures a snapshot — like logging in, accepting cookie consent, or navigating through a single-page app. This is how you monitor pages that aren't accessible with a simple page load.
Browser Steps require the Pro or Business plan. Dashboard UI for configuring browser steps is coming soon — currently available via the API only.
How it works
Site Spy normally fetches pages with a simple HTTP request. When you configure browser steps, it instead uses a full browser (Playwright) that can:
- Execute your defined steps (click buttons, fill forms, wait for elements)
- Reach the target content
- Capture the snapshot
This runs on every check, so your watch can continuously monitor login-protected or interaction-dependent content.
Current status
Browser steps are fully supported on the backend and can be configured via the API. A visual editor in the dashboard is planned for a future release.
Use cases
- Login-protected pages — Fill in credentials to access dashboard data, account pages, or gated content
- Cookie consent — Click "Accept" on GDPR/cookie banners before capturing content
- Single-page apps — Navigate through JavaScript-rendered pages that require clicks to load content
- Multi-step navigation — Click through menus or tabs to reach the specific content you want to monitor
Fetch backend
For browser steps to work, the watch must use the browser-based fetcher (html_webdriver) instead of the default plain HTTP fetcher. This is set automatically when you configure browser steps or enable screenshot capture.
Limitations
- Browser steps run on every check, which takes longer than simple HTTP fetches
- Complex multi-step flows may occasionally fail if the target site changes its layout
- Two-factor authentication (2FA) requiring dynamic codes cannot be automated