Skip to content

CanopySEO / Launch Audit

Know what needs fixing. Launch with evidence.

A useful website audit connects the symptoms to the work: what failed, why it matters, who can fix it, and how to verify the result.

Start with a human-reviewed CanopySEO audit. The self-service Launch Audit scanner is planned; this page does not run a scan.

01 / CanopySEO / Launch Audit

Look beyond the headline score.

Use these seven areas to scope your review. We agree the pages, devices and checks before starting; the depth depends on your site.

Metadata

Page titles, descriptions, canonicals, favicons, viewport settings and document language.

Content & structure

Headings, skipped heading levels and image alternatives, with human review of meaning and context.

Technical health

HTTPS, redirects, headers, cookies, compression, robots.txt, sitemaps and crawl directives.

Accessibility

Labels, landmarks, keyboard journeys and touch targets. Automated findings are a starting point for manual testing.

Social & rich results

Open Graph, share-image dimensions, Twitter cards and structured data, including consistency with the visible page.

Links

Broken destinations, placeholder links and redirect chains within an agreed sample or crawl scope.

Runtime & performance

Loading behaviour, layout shifts, blocking work, failed assets and JavaScript errors under recorded test conditions.

02 / Illustrative report · not a live website result

A finding you can act on.

Every useful issue needs evidence and a next step. This is an example of the handoff we aim for.

WarningOwner: site code

The primary mobile action is difficult to tap

Evidence
Example: a contact button measures 120 × 32 CSS pixels at a 390 px viewport.
Why it matters
A small action can be harder to use accurately on a touch screen.
Suggested repair
Increase the usable target area and spacing. Keep the visual treatment consistent with the surrounding form.
Verify the repair
Recheck the rendered dimensions, keyboard focus and nearby controls on mobile and desktop.
Example developer / AI handoff

Review the contact button on the affected page. Increase its usable touch area without overlapping adjacent controls. Preserve the form action and accessible name. Verify at mobile and desktop widths, with keyboard navigation. Report the files changed and the checks actually run. Do not change hosting configuration or third-party scripts.

Transparent scoring. Clear limits.

The illustrative 39-check model gives a pass 1 point, a warning ½ point and an error 0 points. Divide earned points by 39 and round to a percentage: (35 + 4 × 0.5) / 39 × 100 = 95.

Coverage stays visible

Checks that could not run must stay marked unavailable, with the reason. Missing evidence must never silently become a pass.

Severity still matters

A broken contact form can matter more than several metadata warnings. Prioritize visitor impact and business risk alongside the score.

Infrastructure is contextual

A particular CDN or hosting vendor is not a requirement. Separate site-code repairs, infrastructure decisions and third-party failures.

Lab results need context

Record viewport and test conditions. Keep browser measurements separate from field data and avoid claiming that automated checks prove accessibility compliance.

Where Launch Audit is heading.

Planned capabilities for the self-service tool, not features available on this page:

  • Mobile and desktop browser runs with screenshot evidence
  • Deeper accessibility, schema and hreflang checks
  • Route crawling with explicit coverage limits
  • Saved reports, scan comparisons and regression tracking
  • Copyable fix prompts scoped to first-party code
  • Supplemental Lighthouse and field data when available

Turn findings into a focused repair.

Send your website through CanopySEO intake. We can agree an audit scope, prioritize the findings and quote the implementation work. Already know what is broken? Start with website repair.