Guide
Configure and run website audits
Choose pages, import a sitemap, configure initialization, schedule audits, and review results.
Last reviewed September 12, 2026
Scheduled audits overview
Scheduled Audits run SiteWall checks against a defined set of website pages. Use them to revisit important public or authenticated routes on a repeatable cadence, capture configuration and integrity context, and preserve run history for investigation or evidence review.
Configure audit pages and sitemap import
Configure the smallest page set that represents the website’s important client-side behavior. Include entry pages, high-risk journeys, and routes that load materially different third parties; avoid adding duplicate URLs that produce the same browser state.
Procedure
- 1.
Open the correct project and page
Use the project selector to choose the website you intend to review, then open Audits in the left navigation. Confirm the organization, project, and monitored domain before interpreting a record or changing a control.
- 2.
In Pages to Audit, add a page path
In Pages to Audit, add a page path such as the relevant SiteWall page or an available supported pattern. Use paths that belong to the project’s verified domain.
- 3.
To import from a sitemap, enter its path,
To import from a sitemap, enter its path, load the available URLs, select the intended pages, and confirm the addition. Review the imported list rather than accepting every URL by default.
- 4.
Remove duplicate, administrative, destructive, sign-out, or irrelevant routes
Confirm the approved page list, authentication or initialization requirements, schedule or run state, and resulting records. A configured page is not evidence that every conditional browser state was exercised.
- 5.
Save the configuration and compare the displayed page
Save the configuration and compare the displayed page count with the intended scope before running or scheduling the audit.
Configure an audit initialization script
An initialization script prepares the browser before an audit—for example, by selecting a consent state or signing in to a dedicated test account. Use it only when the target page cannot be reached safely in its default state.
Run, schedule, and review an audit
Run an audit after its page scope and initialization are validated. Use an on-demand run to test a new configuration; schedule repeat runs only after the result is stable and an owner is responsible for reviewing failures and changes.