An audit checks one website against the four Consumer Duty outcomes. The first one takes a few minutes to set up; after that, rerunning it is a single click.
1. Start a new audit
Open Audits and click New audit. The set-up runs through a few steps: Audit details, Audit type, Authentication if the site needs a secure login, then an API step if you chose the friction finder or a URLs step if you chose manual selection, and finally Launch. Steps you have finished show an Edit link, so you can go back and change them.
2. Audit details
Give the audit an Audit name, such as "Claims journey", then enter the Domain - the website's address, for example www.example.com - and choose a Segment: Banking, Credit, Mortgages, Insurance, Investments, Private wealth, Pensions or General. The segment calibrates which Consumer Duty expectations apply.
Tick Include accessibility checks if you want WCAG 2.2 AA checked on every page alongside the four outcomes. It is off by default, and its findings sit in the same list as the rest. Tick Secure login required if the pages you care about sit behind a login, such as an account area, a quote journey or a claims portal; that adds a step for the credentials.
3. Audit type
Choose how the pages are picked: How should we choose the pages? This decides the steps that follow, and it is fixed when the audit starts, so every run covers the same pages and the trend means something:
- Site sample - UXDuty finds the pages that matter for Consumer Duty, in order, and audits as many of them as you ask for.
- Friction finder - ask your analytics where customers are struggling, and audit the journeys they struggle on. It requires a connection to Google Analytics or Microsoft Clarity.
- Manual selection - give us the list, and UXDuty audits exactly those pages and nothing else.
4. Authentication (if a secure login is required)
Add the Sign-in page URL, Username and Password. UXDuty uses them the way a customer would, through the sign-in page in a real browser, and only reaches pages that account can reach. They are encrypted at rest, only used during scanning, and never shown back to you.
5. Launch
Site sample. UXDuty counts the pages on your website first, from the sitemap or by walking the site, at no cost. You then type how many pages to audit in Pages to audit, up to the size of the site. The field opens on 10. The crawl reads claims, complaints, cancellation and support pages first, and also reads linked policy documents such as complaints procedures and terms of business.
Friction finder. On the API step, connect Google Analytics or Microsoft Clarity. The integration guide walks through each connection. After launch you pick the journeys to audit, and the pages on them become the audit.
Manual selection. On the URLs step, paste your URLs one per line, or upload a spreadsheet. Blank lines and duplicates are ignored, and a missing https:// is added.
A UXDuty page scan also follows links a couple of levels deeper, like a customer would, and searches any PDFs it finds. The page shows how many of your monthly pages the audit will use. A web page or a document counts as one page, so a PDF uses one page however long it is. Click Run Audit to start.
6. While it runs
The audit page shows Audit in progress, with a progress bar and the number of pages scanned. Pages are analysed one at a time, typically in 6 to 16 seconds each, so a 100-page audit takes in the region of 10 to 30 minutes. The work runs on our servers, so you can close the tab and come back; the audit shows as in progress on your Audits list.
Abort audit stops the audit and deletes it, with every run and finding. It cannot be undone.
7. Rerun any time
Once an audit has finished, Rerun scan scans the same pages again as a new run. Every run is kept, so you can use it after you ship a fix to see what has changed, and the trend chart on the Overview tab shows progress over time. A rerun analyses the same number of pages as the first audit, so it uses the same number of pages from your allowance.
All documentation