How to Capture Screenshots of Pages Behind a Login with PageCrawl.io

PageCrawl.io documents authenticated access as part of website monitoring. To see where a configured login ends up, open Website Logins, add and test the login, and inspect the screenshot returned by Test the login. That screenshot is a diagnostic result of the login test; the documentation does not describe PageCrawl as a general-purpose screenshot API or promise a separate workflow for downloading arbitrary screenshots.

PageCrawl’s login-authentication feature is available on paid plans. The steps below cover the documented form-login setup, how to tell a successful login from a failed one, two-factor authentication, HTTP Basic Authentication, and common failures. See the ScreenshotNeo website screenshot API section for a separate option when you need a screenshot API rather than authenticated monitoring.

1. Add a website login

1. In PageCrawl, open Website Logins and choose Add New.
2. Enter the login page address. PageCrawl attempts to identify the username field, password field, and submit button.
3. If a field was missed, choose Pick the fields on the page and select it directly. Check the selector match result: it should match one element. A selector matching zero elements cannot be used, while one matching multiple elements may select the wrong control.
4. Enter credentials for an account authorized to access the protected page.
5. If the form appears only after an action, add that action in Pre-login steps. For example, accept a cookie notice or open a Sign in link before the login fields are available.
6. Choose Test the login. Review the reported steps and the screenshot of the location reached after sign-in.

The screenshot answers an important diagnostic question: did the test reach the protected destination, or did it stop at a login, error, or intermediate page? A successful-looking HTTP response alone does not prove that authentication worked; a site can render its normal sign-in page after rejecting credentials.

2. Verify that the resulting page is authenticated

Configure a Login check using content that appears only after successful sign-in. Suitable examples include the account name or a Sign out link, if those are actually unique to the signed-in view on your site.

Avoid checks for generic text, such as a page title or navigation label, if it also appears while signed out. The purpose is to distinguish the authenticated page from a login page that loaded normally. PageCrawl says it can report Login verification failed when this check fails, rather than treating the result as an ordinary content change.

3. Add the protected page as a monitor

1. Add the protected destination as a monitor.
2. In Login Authentication, select the matching login configuration.
3. Confirm that the monitor’s login check tests for signed-in-only content.
4. Review the test result and screenshot when the login configuration or site flow changes.

PageCrawl’s documented workflow is for monitoring authenticated pages. The login test screenshot shows where the sign-in attempt ended up; do not treat it as evidence of a permanent screenshot archive or an arbitrary screenshot-download endpoint.

Form login and HTTP Basic Authentication

Authentication type	Where it is configured	How to identify it
Website Login (form-based)	Website Logins, then select the configuration under the monitor’s Login Authentication.	The site presents username/password fields and a submit control in the page.
HTTP Basic Authentication	Enter credentials under the monitored page’s Advanced Settings.	The browser presents a Basic Auth credential prompt instead of an ordinary page login form.

These are separate setup paths. Do not try to fix a Basic Auth prompt by selecting page-form fields; configure the credentials in Advanced Settings as the help instructions describe.

Two-factor authentication

The PageCrawl help article documents two one-time-code paths:

• Authenticator-app TOTP: provide the authenticator secret or an otpauth:// link. The help article says this works on any paid plan, including Standard.
• Emailed codes: forward codes to a PageCrawl-generated address or send them to the account email address configured for that purpose. The help article warns that email delivery can exceed the tighter Standard per-check time budget and recommends Enterprise or Ultimate for emailed-code flows.

PageCrawl documents session reuse: the code step runs during initial sign-in or after the session expires, rather than at every check. The help article says SMS codes and physical security keys are not supported. Verify current plan details with PageCrawl before choosing a plan, because entitlements can change.

Other protected resources

PageCrawl’s help article says a login configuration can also be selected for authenticated PDF, Excel, CSV, and Word files. It also allows multiple login configurations for different sites. Choose the configuration associated with the resource’s site and authorized account.

Common problems and fixes

Symptom	Likely cause	What to try
The test screenshot shows the login page.	Credentials were rejected, the form was not submitted, or another step is required.	Inspect the test steps, confirm the authorized account credentials, re-pick fields if the form changed, and add any necessary pre-login action.
A field selector matches no elements or several.	The page markup changed, the selector is too broad, or the field is hidden until an interaction.	Use Pick the fields on the page again and choose a selector that identifies the intended single control.
The submit button is blocked or the form is absent.	A cookie notice, overlay, or sign-in link must be handled first.	Add the needed click or other interaction under Pre-login steps, then run the test again.
The site asks for a username before revealing the password field.	The login is a multi-step form.	Add a step that submits or advances after the username so the password field is exposed before PageCrawl tries to use it.
The page loads, but the login check fails.	The check text is absent after sign-in, or it also appears on signed-out pages.	Choose stable content that is present only in the authenticated state, such as the account name or a sign-out control.
The test reaches an OTP prompt.	Two-factor authentication is enabled but the code step is not configured.	Set up a supported authenticator-app TOTP or emailed-code flow. The help article does not list SMS or physical keys as supported.
An emailed code arrives too slowly.	Email delivery consumes the available per-check time.	PageCrawl’s help article recommends Enterprise or Ultimate for emailed-code flows; verify current plan limits before upgrading. An authenticator-app TOTP flow may avoid email-delivery delay if the site supports it.
Basic Auth credentials do not work in the form-login setup.	The site uses the browser’s Basic Auth prompt, not a page form.	Enter the credentials under the monitored page’s Advanced Settings.

These fixes reflect PageCrawl’s documented setup guidance. They do not guarantee support for every identity provider, CAPTCHA, or authentication challenge.

Performance, reliability, and cost considerations

• Authentication state: PageCrawl describes reusing a signed-in session between monitoring checks until it expires. A session expiry can trigger a fresh login and, where configured, another OTP step.
• Time budget: extra pre-login interactions and code delivery add time to a check. Email delivery is especially relevant because PageCrawl warns it can exceed the Standard per-check budget.
• Reliability: use a specific signed-in-only check so failed authentication is recognizable as an authentication problem instead of a content change. Re-test after changes to the login page, consent flow, or identity provider.
• Credentials: use an account authorized for monitoring and protect its credentials and OTP setup as you would other service credentials. Avoid using an account whose access should not be automated.
• Cost: authenticated login monitoring is a paid-plan feature. Plan fit can depend on the authentication flow, particularly the documented recommendation for emailed OTP on Enterprise or Ultimate. Confirm current PageCrawl pricing and entitlements directly; the referenced help material does not establish current prices.

Or skip the browser setup

PageCrawl’s documented login flow is for monitoring and testing authentication. If your goal is to capture a public page, or a page your capture environment can access without a login, ScreenshotNeo offers a one-request screenshot API. It does not sign in to protected accounts, so it is not a replacement for the authenticated PageCrawl workflow above.

curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webp

See the ScreenshotNeo API documentation for request options. The same request in Python:

import requests

r = requests.get(
    "https://api.screenshotneo.com/v1/shot",
    params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"},
    timeout=90,
)
open("shot.webp", "wb").write(r.content)

And in Node.js:

const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);
if (!res.ok) throw new Error(`Screenshot request failed: ${res.status}`);
await import('node:fs/promises').then(fs => fs.writeFile('shot.webp', Buffer.from(await res.arrayBuffer())));

ScreenshotNeo removes cookie and consent banners, newsletter popups, and chat widgets before capture. Bot checks, blank pages, failed loads, timeouts, and cache hits are not billed; response headers identify the page verdict and billing status. Its MCP server provides screenshot and page-info tools for Claude, Cursor, and other MCP clients. The free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000 screenshots.

Sign up for ScreenshotNeo’s free 1,000 screenshots a month, with no card required.

FAQ

Does the login-test screenshot show the protected page?

It shows where the sign-in test ended up. Inspect it and use a signed-in-only Login check to determine whether the protected destination was reached.

Can I use PageCrawl as a general screenshot API?

The cited documentation establishes a screenshot as part of testing login configuration for monitoring. It does not document a standalone general-purpose screenshot API or arbitrary screenshot-download workflow.

Can PageCrawl reuse one login for multiple sites?

The help article says multiple login configurations can be created for different sites. Select the matching configuration for each monitor.

Can I use SMS codes or a physical security key?

The referenced PageCrawl help article says SMS codes and physical security keys are not supported. It documents authenticator-app TOTP and emailed codes.

Does ScreenshotNeo capture pages that require my PageCrawl login?

The ScreenshotNeo API example captures a URL, but the supplied product facts do not establish authenticated login support. Use PageCrawl’s documented login-monitoring setup for the protected-page workflow described here.