# Quick Start
> Canonical HTML version: https://rocketvalidator.com/docs/quick-start
> Attribution: Rocket Validator (https://rocketvalidator.com)
> License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/)
To begin validating your sites you just need to create an account. There's a free trial that includes the W3C Validator engine for HTML checks. By subscribing to a plan you unlock all features and engines, including accessibility checking, muting rules, scheduled reports, and more.
Once you have created your account, you'll be prompted to validate your first site by entering a starting URL and clicking on the "Validate" button.
## Options
To validate a site, you can define the following options.
* **Starting URL**. Our validation spider will visit this URL and follow the internal links, validating each internal web page found. Typically, you can enter the main URL of the site to validate, but it can be any URL from your site, or an XML or TXT sitemap.
* **How many pages to validate**. The maximum number of pages to validate. You can include up to 5,000 web pages per report, but you'll typically want to set a much lower limit. If you need to validate more pages than the limit on a report, consider using XML sitemaps to organize pages into sets.
* **Validation speed (requests/second)**. Can be set from 1 to 10 requests per second.
* **Deep Crawling**. When enabled, our crawler will recursively look for more internal web pages following the links found.
* **Prefer Canonical URLs**. When enabled, our crawler will use the canonical URLs for the web pages, if present. This is a useful option to avoid duplicated web pages in your reports.
* **Tags**. A comma-separated list of tags to apply to the generated report.
* **Shared Report**. By default, the report is private and only accessible to you. If you want to share it with others, you can enable this option to get a shareable link.
## Advanced options
When subscribed to a plan, you'll have access to the advanced options that add additional features to your report.
* **Check HTML with W3C Validator**. Each web page found will be checked using [W3C Validator Nu](https://rocketvalidator.com/w3c-validator).
* **Check Accessibility with AccessLint**. Each web page found will be checked using [AccessLint Core](https://rocketvalidator.com/accesslint).
* **Check Accessibility with Axe**. Each web page found will be checked using the [Axe Core](https://rocketvalidator.com/axe-core) engine.
* **Store Manual Review Checks**. Axe Core checks marked as incomplete will be kept for manual review.
* **Dynamic Crawler**. Use the dynamic crawler to validate pages that are loaded via JavaScript. Enable it only if the site is rendered via JavaScript and has no server-side rendering.
* **Initial URLs**. When enabled, it allows you to define a list of URLs to be included as the starting web pages of the report.
* **Exclusions**. When enabled, it lets you to define a list of paths to be excluded from the web pages list by our web crawler.
* **Basic Authentication**. Set the [basic authentication credentials](https://rocketvalidator.com/docs/basic-authentication) to use when validating pages that require authentication.
* **Device Viewport Emulation**. Optionally choose a [device](https://rocketvalidator.com/docs/device-viewport-emulation) to emulate while validating the page for accessibility issues. This will set the viewport's width, height and device scale factor to the ones in the selected device. If none selected, the default 800x600 viewport will be used.
* **Store Screenshots**. Choose whether screenshots of the validated pages are stored with the report.
## Re-checking your pages
Once your site has been processed, you'll see the HTML and accessibility issues for each page found. As you go fixing them, you can re-check the pages quickly with:
* **Re-check this page** button on each page. This will submit an individual page to the validator.
* **Re-run validation** dropdown on the report page, with these options:
* **Re-run on all pages**. This will submit all pages on the site to the validator.
* **Re-run on pages with issues**. This will submit only the pages with errors or warnings to the validator.
* **Re-scrape the site**. This will start a new report, running the scraper again to discover the internal pages of the site and validate each of them. Use it when the structure of your site has changed, when you want to change any parameter (like max pages), or when you want to keep the current report and start a new one.
* **Re-check affected pages** button on each issue page. This will submit all pages affected by that issue to the validator, checking them with the engines selected on the report.