← Docs

Check live URLs — no build needed

Point Sitetools at deployed pages and run any check against them.

When to use it

A build ZIP is ideal for gating a deploy, but sometimes you just want to check what’s live — a staging URL, a competitor page, or a site you don’t build yourself. Give Sitetools a list of URLs and it fetches those pages and runs your checks against them.

From the dashboard

On the site’s Reports page, click Run checks, leave the ZIP empty, and paste one URL per line into Live URLs. Then run.

From the API

curl -X POST https://app.sitetools.pro/api/v1/sites/$SITE_ID/runs \
  -H "Authorization: Bearer $SITETOOLS_KEY" \
  -F 'urls=https://example.com/
https://example.com/pricing
https://example.com/blog'

urls accepts a newline/comma list or a JSON array. URLs must be public http(s) addresses.

What runs against a URL

For live URLs, Sitetools fetches each page’s HTML plus its same-origin CSS and JS. So these all work fully:

  • SEO & metadata — titles, descriptions, canonical, Open Graph, structured data
  • Content & accessibility markup — headings, alt text, empty elements, lang
  • CSS budgets, unused CSS, web-font formats
  • Browser checks — Core Web Vitals, console errors, accessibility, layout shift
A full build ZIP still gives the richest results for broken links and image file-size checks, because it contains every file and the complete internal link graph. From URLs we fetch pages and same-origin CSS/JS, not every image.

Security

Every URL is resolved and validated before we fetch it — private, loopback, and cloud-metadata addresses are rejected, and redirects are followed manually with the same check on each hop.