Quickstart · 10 minutes
Run your first useful audit.
This guide takes you from a blank workspace to a prioritized set of findings. You only need a public website URL.
In this guide1. Create a project2. Configure and run a crawl3. Review the results4. Choose your next workflow
1Create a project
- From the workspace home, select New project.
- Give the project a name your team will recognize.
- Enter the canonical origin, including
https://. - Select Create project.
✦
You can audit public sites immediately.
Domain verification is only required for ownership-sensitive features. It does not block a standard crawl.
2Configure and run a crawl
Open the project and choose Start crawl. The recommended profile is a good default for most marketing sites and online stores.
| Option | Choose it when… |
|---|---|
| Standard HTML | Pages return meaningful content without browser rendering. |
| JavaScript rendering | The site uses a client-side framework or loads key content dynamically. |
| Sitemap seed | You want Atlas to begin with URLs declared by the site. |
i
Start small when you are learning.
Use a page limit or path scope for the first crawl. You can expand coverage after confirming the configuration.
3Review the results
When the crawl completes, begin in Overview. Use the health summary to understand the shape of the site, then open Audit to review grouped findings.
AStart with critical findingsConfirm they affect indexable, canonical pages.
BCheck affected reachA template problem usually matters more than an isolated URL.
COpen the evidenceReview the observed value before creating work.
DCreate a focused taskKeep the affected URLs and expected outcome attached.
4Choose your next workflow
Your first crawl is a baseline. What you do next depends on the question you need to answer.