Skip to content
Browse all guides

Getting started

From signing up to reading your first scan, in about five minutes.

1. Create your workspace

A workspace holds your sites and the people who can see them. You get one when you sign up, and you can create more — one per client or per brand is the usual split.

Rename it under Settings → General. Invite people under Settings → Members: they get an email invitation, and you choose whether they are an admin, a member or a viewer.

2. Add a site

Click Add site and give PixyScan the address you want crawled, including the scheme — https://example.com.

Two things are worth setting before the first scan:

  • Page cap. Defaults to 1,000. The crawler stops there, so on a large site raise it deliberately rather than being surprised by a partial picture.
  • Exclude patterns. Anything you do not want crawled: faceted search, calendars, print views. Excluding these early keeps the page cap for pages that matter.

3. Run the first scan

Press Scan now. PixyScan fetches robots.txt and your sitemaps, then follows internal links from the address you gave it, honouring the rules it found.

A scan of a few hundred pages usually takes under a minute. The site header shows progress; the Scans tab keeps every run.

4. Read the result

The site overview opens on a health score out of 100 and the counts that produced it. Below that, Since the previous scan tells you what is new, resolved or regressed — that panel only has something to say from the second scan onwards.

From there:

  • Issues lists every failing check, worst first, with the number of pages affected.
  • Open a check for what it is, why it matters, how to fix it, and every URL that fails it.
  • Pages groups every crawled URL by path. Open one for its full report.

5. Keep it current

On the Scans tab, create a schedule — daily, weekly or monthly, in your timezone. PixyScan re-crawls on its own and each run is kept in the history, so Since the previous scan stays meaningful.

There is no email or webhook when a scan finds something new. That is not built yet, so check in on the dashboard rather than waiting to be told.