Test Authenticated Pages
If part of your site is behind a login, Sitepager can authenticate before scanning so those pages are included in your pre-publish check. Common examples include member areas, course libraries, customer portals, and password-protected staging environments.
Where to find it
Section titled “Where to find it”The Enable Login toggle is in the Advanced Settings section when creating or editing a scan. It is disabled by default.
Setting it up
Section titled “Setting it up”- Click New Scan from the Dashboard
- Enter your Website URL
- Open Advanced Settings and enable Enable Login
- Fill in your login details (see fields below)
- Click Run Scan
Login fields:
| Field | What to enter |
|---|---|
| Login URL | The URL of your login page (e.g. https://example.com/login) |
| Click to show login form | Enable if your login form only appears after clicking a button or link (e.g. a “Sign in” button that reveals the form) |
| Username | The username or email for the account |
| Password | The corresponding password |
| Username Field Selector | The CSS selector for the username or email input field |
| Password Field Selector | The CSS selector for the password input field |
| Submit Button Selector | The CSS selector for the login form submit button |
| Login Success Selector | A selector or text Sitepager uses to confirm the login was successful |
| Login Wait Time | How long Sitepager waits for the login to complete, in seconds (0-30) |
Use a dedicated test account
Section titled “Use a dedicated test account”Do not use personal credentials or an account with access to sensitive data. Create a dedicated test account for Sitepager and use those credentials here. If your authentication structure changes, update the login details in your scan settings to keep the scan working.
How it fits into the release process
Section titled “How it fits into the release process”Enable login on any scan that includes authenticated pages. It runs as part of your standard pre-publish check alongside visual, SEO, and broken link checks. If your login flow or authenticated content changes, re-run the scan to confirm everything looks right before publishing.
Test your selectors before running a full scan. If the login fails, Sitepager cannot capture authenticated pages. Confirm your selectors match the current login form fields before running across your full site.
Update login details when your authentication changes. A redesigned login page or new form structure will break the login flow. Check your scan settings after any authentication update.
Use Include and Exclude patterns to scope authenticated scans. If only part of your site is behind a login, scope the scan to those pages to keep runs focused. See Include & Exclude Pages for how to set this up.