Documentation

Launch Audit Help

Choose the right workflow, prepare the target, and turn automated findings into a clear launch decision.

Quick Start

1

Choose a workflow

Use Standard Audit for technical launch checks or Accessibility for automated WCAG-focused checks.

2

Enter the target

Paste a domain or URL and choose a full-site or selected-page scan. Site setup is detected when you start; sign-in appears only when access may require it.

3

Run, resume, and triage

Start the queued run and keep its resume link. Review blockers first, then copy JSON or download CSV for handoff.

Choose a Workflow

Standard Audit

Technical launch readiness

Crawls the full site or selected pages and checks response status, indexing signals, metadata, security, performance samples, and regressions. A fresh crawl is selected by default.

Accessibility

Automated WCAG-focused review

Runs browser-based checks, groups outcomes by WCAG threshold, and detects common cookie or contrast controls. Automated results support—but never replace—manual accessibility review.

Understand Reports

  • Standard report: Start with the launch decision, then use the score, site overview, search, severity filters, and page details to prioritize work.
  • Critical: HTTP errors, broken pages, or major technical blockers. Resolve these before launch.
  • Warnings: Review SEO, indexing, performance, and configuration issues in context.
  • Accessibility report: Use the visible result filters, then select a check to inspect its pages, instances, and guidance. Scan methodology and exports remain under Scan details.
  • Manual review: Expand a page and choose Review flagged elements to see the saved selector, HTML, and reason automation could not decide. These are review candidates, not confirmed failures.
  • Filters: Result counts update as the outcome, WCAG level, search, or individual check filters change.

Advanced Options

Option Workflow Default When to change it
Page scope Both Full site Choose specific pages to scan only the paths or full URLs entered in the target field.
Crawl strategy Standard Fresh crawl Reuse the newest matching saved report only when its displayed checked time is recent enough for your decision.
WCAG baseline Accessibility WCAG 2.2 Select the WCAG version required by the project or review scope.
Concurrency Both System setting Lower it for a sensitive staging server; raise it only when the target can handle additional parallel requests.
Shared regions Accessibility Off — scan every page Enable the best-effort reuse option only when scan speed matters more than complete page-by-page coverage. Matching markup can still behave differently under page-level styles or context.
HTTP Basic Auth Both Detected automatically Enter both username and password when the target is protected, then choose Check access in Standard Audit or Continue scan in Accessibility.
Setup presets Accessibility Automatic detection Override detected cookie or contrast setup when you know the site needs a different preset.
User agent Standard Built-in audit agent Use a custom value when bot rules, a WAF, or target-specific traffic handling requires one.
Allow / deny paths Standard No path filters Include a site area such as /blog/* or exclude low-value/private routes such as /checkout/*.

Fix Priorities

  1. Resolve launch-blocking HTTP failures and broken pages.
  2. Resolve critical and serious accessibility failures, then verify the fix in context.
  3. Fix indexability problems such as unintended noindex, canonical mismatches, or robots constraints.
  4. Review warnings and all checks marked not auto-verified; complete manual accessibility testing.
  5. Re-run a fresh crawl or scan and confirm the launch decision against the new result.

Exports

  • Copy JSON places the report data on the clipboard for automation, issue templates, or custom pipelines.
  • CSV downloads a spreadsheet-friendly file for triage, QA handoff, and owner assignment.
  • Exports reflect the saved report. Check the displayed source and age before sharing a reused result.

Troubleshooting

  • For a protected site, correct the credentials and choose Continue scan. For other preparation failures, correct the URL if needed and choose Start scan again.
  • If a run is still queued or processing, use its resume URL; the page can be closed safely.
  • If expected pages are missing, verify sitemap discovery, page scope, and allow/deny rules.
  • If results look stale, start a Fresh crawl and compare the checked time shown on the report.
  • If canonical checks look odd, verify redirect chains and final URL scheme.
  • If an accessibility page has no automated results, treat it as unassessed and complete manual review.

Server Appendix

# Brotli/Gzip
<IfModule mod_brotli.c>
  AddOutputFilterByType BROTLI_COMPRESS text/html text/css application/javascript application/json image/svg+xml
</IfModule>
<IfModule mod_deflate.c>
  AddOutputFilterByType DEFLATE text/html text/css application/javascript application/json image/svg+xml
</IfModule>

# Security headers
<IfModule mod_headers.c>
  Header always set X-Content-Type-Options "nosniff"
  Header always set Referrer-Policy "strict-origin-when-cross-origin"
</IfModule>

# Rewrites
<IfModule mod_rewrite.c>
  RewriteEngine On
  RewriteRule ^help/?$ help/index.php [L,QSA]
</IfModule>

FAQ

Usually due to sitemap coverage, allow/deny filters, server max page cap, redirects, or blocked fetches.

No. It means the automated runner recorded no applicable result for that page or baseline. Complete manual review before making a conformance claim.

Choose Specific pages and enter one path or full URL per line. For a broader Standard crawl, allow and deny patterns can further control discovered paths.