QA for marketing sites — in your build

Catch it in the build.Not in production.

Post your build to Sitetools during CI — or point it at live URLs. It checks SEO, metadata, broken links, OG cards, accessibility, and Core Web Vitals, and hands back a pass/fail result. Ship marketing pages without regressions.

Start freeRead the docs
No credit card required · Runs in any CISee how it works
ci · deploy preview
$ curl -F [email protected] $API/sites/$ID/runs
↑ uploading build … done (0.4s)

One payload in.A full QA report out.

Sitetools inspects the HTML, metadata, links, and assets from your build — the same output you're about to deploy — and reports every regression before it reaches a visitor.

SEO & metadata

Titles, descriptions, canonicals, and indexability — validated against your rules on every build.

Broken links & assets

Every internal link and referenced asset resolved, so nothing 404s after deploy.

OG & social cards

og:image, Twitter cards, and share previews present and correctly sized for every page.

Accessibility

Alt text and markup on every build, plus computed axe violations (contrast, ARIA) in a real browser.

Core Web Vitals

Render each page in real Chromium — mobile and desktop — and fail the build when LCP or CLS blows the budget.

Visual regression

Screenshot every page and diff it against the last run, so an unintended layout change never ships silently.

How it works.From build to verdict in three steps.

  1. 01

    Add Sitetools to CI

    Drop one step into your pipeline that posts the build payload after your site builds.

  2. 02

    Fast checks run

    Sitetools inspects the payload and runs its QA suite in parallel — results in seconds, no crawler warm-up.

  3. 03

    Result returned

    A pass/fail verdict plus a full report. Gate the deploy on failures or post the report to your PR.

Built for your pipeline.One call gates the deploy.

Send the build payload, get back a structured verdict. Non-zero exit fails the job — so a broken sitemap or a missing OG image never makes it to production.

REST APIGitHub ActionsGitLab CIWebhooksJSON report
Read the API docs
# Start a run — a build ZIP or a list of live URLs
POST /api/v1/sites/:siteId/runs
  Authorization: Bearer <api-key>
  -F [email protected] -F label=$GIT_SHA

{ "doc": { "_id": "6a55…", "status": "queued" } }

# Poll for the result
GET /api/v1/sites/:siteId/runs/6a55…
{
  "run": { "status": "completed",
    "summary": { "passed": 11, "failed": 1, "score": 92 } },
  "results": [ { "name": "Social share image",
    "status": "failed", "findingCount": 1 } ]
}

Put your marketing site on a quality gate

Add Sitetools to your build, send the payload, and let the checks guard every release. Your team ships fast — Sitetools keeps it correct.

Connect your first buildTalk to us