Features

QualityGate combines deployed-site checks with release policy and a record of the results. Features below are implemented capabilities; a scanner pass is not a legal or conformance assessment.

Checks and workflows

Feature	Coverage ID	What you can do	Guide
Ten scan bundles	scans	Check accessibility, release quality, performance and search visibility	Bundles
GitHub, GitLab and Bitbucket	integrations	Run in customer CI and publish pull or merge request comments	GitHub, GitLab, Bitbucket
Regression gates	gates	Compare against a matching baseline or apply absolute severity limits	Gates
Local CLI	cli	Run local scans with text or JSON output and automation exit codes	Quickstart
Cloud scans	cloud	Queue a public HTTPS scan and follow it in the app	Cloud scans
Scheduled scans	scheduling	Check a live target on a schedule with a separate allowance	Scheduling
Repository quality checks	quality-suite	Run secret detection, lint, types, tests, builds and PR policy, then aggregate merge readiness	Merge readiness
Account access	accounts	Use email/password or provider sign-in, manage sessions and connected methods	Accounts
Organizations and roles	organizations	Invite teammates, assign roles and switch workspaces	Organizations
Project controls	projects	Configure repositories, allowed hosts, default branches and scoped API keys	Projects
Packages and usage	billing-usage	Review completed and reserved scans, allowances and subscriptions	Packages
Run history and findings	dashboard	Review portfolios, trends and detailed findings	Run history
Reports and client sharing	reports-sharing	Export branded reports and share private client links on paid packages	Reports
Email and Slack notifications	notifications	Receive gate failures, quota alerts and weekly digests	Notifications

Choosing your checks

The bundle groups explain selection, not additional add-ons:

• Accessibility: a11y and ada.
• Release quality: seo, security, links, full and secrets-exposure.
• Performance and search visibility: perf, geo and seo-deep.

full combines accessibility, page SEO, security headers and links for one URL. It does not include performance, GEO, deep SEO or exposed-secret scans. Those bundles run separately. Compare packages for allowances and project limits.

Boundaries and roadmap

GitHub, GitLab and Bitbucket sign-in verifies identity, not repository access. Repository authorization is configured separately under Projects. Cloud scans require public HTTPS targets; private or authenticated targets belong in your own CI environment.

GEO is deterministic readiness analysis. It does not promise rankings or AI citations. AI fix suggestions and vision/content analysis are roadmap items, not available scan features.