Running an Accessibility and SEO Audit Before You Publish
The same accessibility and SEO check that runs live in the editor is now available as an API call, so you can audit a whole site before you publish it.
Piskes Website Builder's editor has always flagged accessibility and SEO problems live as you build a page. That same check is now available as an API call, so you can run it against a whole site — every page, all at once — before you publish, not just one page at a time while you happen to be looking at it.
What it checks
The audit runs the same underlying check the editor's live panel uses, applied to each page's actual stored markup rather than the open canvas. It returns issues per page along with a total error and warning count for the site, covering the kinds of problems that are easy to miss by eye: missing alt text, heading structure, and the SEO fundamentals search engines actually look at.
Where it lives
The audit is reachable two ways: through the public API as GET /api/v1/public/sites/[siteId]/audit using a site API key, or as the audit_site tool if you've connected an AI assistant over MCP. Both return the same structured result — page, issue, severity — rather than a pass/fail summary that hides what's actually wrong.
Why it's worth running before you publish, not after
Catching a heading-structure problem or a missing alt tag in the editor is useful. Catching it as a scriptable check you can run automatically before a deploy — or ask an assistant to run for you — is what turns "we should check this sometime" into something that actually happens every time a site changes.
Available today on every site, no setup required beyond an API key or a connected assistant.