Site audit

WebPinch’s site audit crawls your project’s website and produces a report covering broken links, SEO health, and a battery of general checks (robots.txt, sitemap.xml, meta tags, alt text, etc.). Audits run in the background — start one and come back when it’s done.

Prerequisites

The project must have a website URL configured (Project Settings → URL). The audit will start its crawl from there. Without a URL, the Run Audit button is disabled.

Start an audit

Open the project’s audit page

Click the project in the sidebar, then AI Audit. You’ll land on /dashboard/<projectId>/audit.

Click Run Audit

A small config form appears:

Max depth — how many link-hops deep to follow from the root URL. Default 3, capped at 5.
Max pages — total pages to crawl. Default 50, capped at 100.

Higher numbers = more thorough = longer to run. For a first audit on an unfamiliar site, the defaults are usually fine.

Watch progress

A progress bar shows status as it moves through phases:

Status	What’s happening
`queued`	Waiting to start (usually milliseconds)
`crawling`	Fetching pages following links from the root
`analyzing`	Running SEO + link checks against the crawled data
`complete`	Done — report is ready
`failed`	Something blew up — see the error message

Typical run on a 50-page site takes 1–3 minutes depending on the site’s response speed.

One audit at a time per project. Trying to start a second audit while one is running returns a conflict error. Wait for the first to finish (or fail).

The four tabs

Once an audit completes, the report has four tabs.

General

Pass/Warn/Fail checks across the site. Each check has a name, a status icon, a one-line message, and details on hover. Examples:

robots.txt present
sitemap.xml present
HTTPS used everywhere
Meta description on every page
Title length within recommended range
Images with alt text
Canonical tags set

If WebPinch’s AI features are enabled, this tab also shows an aiSummary — a paragraph distilling the findings into a “what’s most important to fix” recommendation.

SEO

Overall score as a gauge
Categories — separate scores for things like meta tags, heading structure, content quality. Each category has its own list of issues.
AI tips — same as the General tab, but focused on SEO improvements.
Per-page scores — drill into specific pages that scored low.

Site Map

A visual graph of how the crawler followed links from the root. Useful for spotting orphaned pages (no inbound links) or unusually deep paths.

Audit history

Every audit you run is kept. The dropdown in the page header lists all audits with their date and status — pick any past audit to load it. The most recent finishes loaded by default.

Reanalyze

Clicked the wrong audit config? WebPinch shipped an analyzer improvement? You can re-run just the analysis on the existing crawl data without re-crawling — saves time and avoids hitting the site again.

Reanalyze button (refresh icon) on a completed audit. Status moves back to analyzing, then complete with updated reports. The crawl data is unchanged.

Delete

Trash icon next to an audit removes it from the project’s history. Irreversible — but you can always run a fresh audit.

Programmatic

Audits are fully exposed via REST and MCP. Useful for:

Triggering an audit from CI after each deploy
Pulling the report into a Markdown summary via the MCP summarize_audit prompt
Tracking SEO score over time by polling /api/v1/projects/{id}/audits

What’s not (yet) here

Audit export — no download/CSV/PDF button for audit reports yet. Use the API if you need audit data outside WebPinch. (Task data is exportable — see Project → Export for JSON, CSV and Excel — but that covers the kanban board, not audits.)
Scheduled audits — you trigger each one manually. Use cron + the REST API to schedule.
Marking issues as “won’t fix” — the report is read-only.
Diffing two audits — compare current vs previous is on the roadmap.