See the outcome
See which plan is enough and how to read a change record.
Product documentation
Set up. Monitor. Prove it.
Short, direct, actionable guides for every role using Crawlens, from the first URL to the notification flow.
Start with your role.
Pick the shortest path for your responsibility; details are in the topic map below when you need them.
Explain the change
Review the evidence, share it and keep the decision in the same event record.
Set up the signal
Configure scan conditions, notification channels and post-deploy triggers.
Topic map.
Open a heading and read the steps directly.
Putting your first client site under monitoring takes a few minutes after you sign up. The moment you add a URL the first scan starts on its own; you never have to look for a “Scan” button.
- Open a project for the client
- Add the first URLs
- Wait for the baseline
- Choose a scan frequency
- Review and close the first change
Crawlens answers one question: when something changes on a site you monitor, do you find out before the person who notices it? Below are the everyday shapes of that question.
- robots.txt and indexing accidents
- Theme, plugin or third-party update
- Pricing and campaign pages
- A page becoming unreachable
- Proving the work you did
Every scan takes a full-height mobile screenshot of the page and compares it to the baseline. Instead of a single “what percentage changed” number it looks region by region, then verifies with a second scan whether the change is real.
- What a baseline is
- Region-based scoring
- A height difference is not a change
- The verification scan
- Ignored regions
- Change states
Scans run automatically at the frequency you chose. Changes are grouped in a 10-minute window and sent as one notification; critical ones do not wait.
- Choose the frequency
- Grouped notifications
- Critical notifications do not wait
- AI answer engines are monitored separately
- Certificate and domain expiry
- Consecutive-failure policy
- Channels
After a deploy you can start the scan yourself, push notifications into your own systems and share evidence through a link that expires.
- Create a trigger token
- Narrow the scope
- Call it after the deploy
- Pre/post release check
- Revoke the token
- Outbound webhook and sharing
The unit you buy is the site: a registered domain, including subdomains. You are buying four things: how many sites are monitored, how many pages per site are monitored with evidence, how often they are scanned, and how many days of history are kept. No credits, tokens or overage charges.
- Two monitoring depths
- Free — $0
- Pro — $49/month
- Agency — $149/month
- Why two evidence limits
- Trial
- Downgrading
Crawlens keeps an archive of your clients’ sites. This page writes down who can reach that archive and where our limits are.
- Organization isolation
- Access to evidence files
- Roles
- Share links
- Trigger tokens
- Scan target restrictions
Four situations cover most of what goes wrong: no baseline is formed, no notification arrives, too many notifications arrive, and the same change repeats.
- No baseline is formed
- No notification arrives
- Too many notifications
- The same change repeats
- Still not solved?
The questions asked most before the trial, with honest answers. If your question is not here, write to us and we will add it to this list.
- What exactly does Crawlens do?
- What does it not do?
- How long does setup take?
- Is the desktop view monitored?
- Is a card asked for during the trial?
- If I downgrade, is my data deleted?
No topic matches this search. Try a shorter or different phrase.
Didn't find the answer?
Share your question and the situation you ran into; we'll find the right starting point together.
Get support ↗