Web and site audits

Website audit

Technical and on-page SEO audit of one website, page by page, in a real browser.

Each page comes back with a 0 to 100 score and nine category scores, plus meta tags (title and description with lengths, canonical, robots, Open Graph, Twitter card, viewport, language), heading structure, content signals (word count, readability, keyword density, thin content, search intent), technical checks (HTTPS and certificate, mobile friendliness, sitemap, robots.txt, JSON-LD, microdata and RDFa types, AMP, indexability, whether the page needs JavaScript to render its content, pagination), page timing measured in the browser (time to first byte, first contentful paint, total blocking time, cumulative layout shift, speed index), links (internal and external counts, anchor text quality, broken links and redirect targets with the status code each returned), image alt and size coverage, and basic accessibility (ARIA labels, lang attribute, skip links, contrast). Every issue is classified critical, warning or info and carries an id, a category, a priority, an estimated impact and a fix hint. A final item of type site-summary averages the pages, ranks the issues that repeat across them, and reports crawl coverage.

When to use it

Use when you have a website and need to know what is actually wrong with it: auditing a prospect before pitching, checking a site after a launch or migration, or turning a domain into a concrete fix list. One site per call, so pass a single URL and call again for the next one. Billed per PAGE audited, not per site: leaving maxPages out audits up to 5 pages, and whatever you set is what you pay for, up to 25. It does NOT tell you what a site is built on (no CMS, framework, analytics or hosting detection) and returns nothing about backlinks, keyword rankings or traffic.

Inputs

Website audit takes 16 fields, 1 of them required. Anything you leave out falls back to the tool's own default.

How to call it

Connect once and your agent can reach Website audit the same way it reaches everything else in the catalog. Add Goro as an MCP connector, or paste the setup line into an agent that reads skills.

Or plain HTTP

POST /v1/run

{
  "endpoint": "website.audit",
  "input": {
    "startUrls": [
      "<startUrls>"
    ]
  }
}