The first scan is the one that takes a few minutes; everything after it is two clicks. Once the structure is in place you can re-run any scan, schedule them, or hand the project over to someone else.
1. Create a project
A project is a container for everything you want to scan on a single product or website. Most teams have one project per brand, or one per major customer journey. From the dashboard, click New project, give it a name, and choose the home URL. The home URL becomes the default starting point when you add new scans.
2. Define the journey
A journey is the sequence of pages a customer goes through to reach an outcome - for example, "open a savings account" might be five pages from product page to confirmation. You can either:
- Paste a list of URLs in order, one per line. Best when you already know the route customers should take.
- Connect Microsoft Clarity or Google Analytics and let UXDuty surface the routes customers actually take. Best when you want to scan the most-trafficked or highest-friction journeys without guessing.
Each step can be given a friendly name ("Step 3 – Identity check") so the report reads in plain English.
3. Add login details (optional)
If your journey passes through a logged-in area, add a username and password under the project's settings. UXDuty stores these in encrypted form and only uses them to sign in at the start of a scan. They're never displayed back to you.
4. Start the scan
Click Run scan. UXDuty walks the journey one step at a time, takes a screenshot of each page, and runs the checks. Most journeys finish in two to four minutes. You don't need to keep the tab open - you'll get a notification when it's ready.
5. Re-run any time
After the first scan is complete, the journey is saved and can be re-run with a single click. Use this after you ship a fix to confirm the issue is gone, or schedule recurring scans to catch regressions before they reach customers.
All documentation