Webscan Documentation

Lesson 3 · Add your first website

Phase 1 · Foundations — Lesson 3 of 21 · All lessons

Objective: add a website to scan, understand projects, and choose the right environment and page limit.

Before you start: an account and organisation from Lesson 2.

Two ways to add a website

The fast path (onboarding). On the Welcome to Webscan screen — or any time you visit Get started — you can Add your first website directly. Webscan quietly sets up a default organisation and project for you and queues your first scan the moment you save. If you're brand new and just want to see webscan work, use this path and skip to Lesson 4.

The deliberate path (recommended once you're past day one). Create the project yourself so your work is organised the way you want. That's what the rest of this lesson walks through.

Step 1 · Create a project

A project groups the websites for one product or client.

1. On the Dashboard, open your organisation and choose to add a new project (from the organisation's page).
2. Give it a name (e.g. "Marketing site" or a client name) and an optional description.
3. Save. You land on the project page, which will list this project's websites.

Step 2 · Add the website

From the project page, choose to add a website. You'll fill in a short form:

Save, and the website appears with its own website page — the hub you'll launch everything from.

Choosing the environment (this matters)

The environment isn't cosmetic. It sets webscan's blast radius — how freely it may interact with the site:

• Development / test and Staging — webscan can explore and click freely. Best for learning and for thorough audits.
• Production — webscan holds back from actions that might change real data unless you explicitly allow them, protecting your live site and real users.

For these lessons, choose Development / test or Staging, or point at a site you own and don't mind being crawled.

Choosing the page limit

• Start small (10) while you learn — scans finish faster and results are easier to read.
• Raise it later for fuller coverage (up to 100). Bigger sites cost more scan time.
• The limit is per scan; the scanner stops once it has covered that many pages.

The website page: your launch hub

Once the website exists, its page is where every scanning feature lives. You'll see actions including:

• Start scan — run an automated scan (next lesson).
• Edit — change the URL, environment, or page limit.
• Scan profiles, User journeys, Agentic exploration, Recordings, Monitoring, Manual audit — the advanced sources of findings, each covered in later phases.
• A Scan history list, where you can View or Delete past scans.

You don't need any of the advanced actions yet — for now, just know they all start from here.

Tips & pitfalls

• Use the base URL you actually want crawled. If you point at a login page or a redirect, the scan may only see that one page. For sites behind a login, you'll set up authenticated scanning in Phase 3 — don't fight it here.
• Don't scan production while learning. Pick development/staging so you can be bold without worrying about real data.
• Keep the page limit low at first. You can always rescan with a higher limit once you know the results look right.

Recap

• A project groups websites; a website has a base URL, environment, and page limit.
• Onboarding is the fast path (auto-creates a workspace and queues a scan); creating a project yourself is the tidy path.
• Environment controls blast radius — learn on development/staging.
• The website page is the hub every scanning feature launches from.

Try it yourself

Add one website on a development or staging URL with a page limit of 10. Open its website page and find the Start scan button — you'll use it in the next lesson.

Previous: ← Lesson 2 · Set up your account & team Next: Lesson 4 · Run your first scan →