Choosing routes
Start with the routes most likely to create real user pain when they break:
- home page
- sign-in
- dashboard
- settings
- purchase or onboarding paths
It is better to monitor a small set of important routes than a long list of noisy ones.
Entering routes
You can add routes in a few ways:
- one path per line
- comma-separated
- semicolon-separated
This makes it easy to paste a batch into the project form or the Routes tab on a project page.
What a route result can show
- visible content found
- no visible content detected
- redirect loop detected
- browser console error captured
- screenshot attached to the run report
Managing routes later
Use the Routes tab on a project to paste new paths, add a single route, or remove routes that no longer matter.