What Is a Website Auditor?
A website auditor evaluates how a site performs across technical SEO, performance, structured data, accessibility, trust signals, crawlability, and machine-readable systems. WebsiteIQ combines these inspections into one evidence-based report.
Run a Website Audit
Enter a public website. WebsiteIQ consults robots.txt before content, audits one permitted page, and turns the same unlisted token-bearing URL into the finished HTML report. Anyone with the complete link can view it; report and status responses remain noindex and no-store. No account, email, or contact consent is required.
Price the Sitemap Before an Audit Crawl
WebsiteIQ reads robots.txt first, then follows a bounded same-host sitemap tree—including namespaced, WordPress, and Yoast-style sitemap indexes. It counts only robots-permitted page URLs and does not start an audit.
Standard: $0.01 through 10 pages, then $0.001 per additional page. White-label: $0.02 through 10 pages, then $0.002 per additional page. x402 v2 settlement is live through API and MCP; this website remains a free sample and quote interface with no paid checkout.
Website Audit Reports for People and Software Agents
POST /api/intake returns a request id, status URL, access token, and report URL. MCP exposes the same audit as structured tool output, so agents do not need to parse report CSS. Free browser, API, and MCP access is one comprehensive page per requester IP and per target website each day. No account, email, or contact consent is required. The current public sample audits one robots-permitted page and returns the same evidence through human and machine-readable interfaces.
POST /api/estimate reports the bounded, robots-permitted sitemap scope and both deterministic quotes without executing an audit.
POST /api/intake
{
"url": "https://example.com"
}
What the Website Auditor Checks
WebsiteIQ records direct observations first, calculates derived metrics second, and labels interpretive heuristics as heuristics. The report stays dense because a website is simultaneously infrastructure, interface, publication, entity record, and machine-readable surface.
Technical behavior
Status codes, redirect paths, response timing, transfer weight, TLS and DNS evidence, security headers, sitemap coverage, and crawl accessibility.
Document precision
Titles, descriptions, canonical hints, headings, landmarks, image alternatives, link evidence, HTML structure, and page-to-page consistency.
Structured data
JSON-LD types and identifiers, organization evidence, service and offer descriptions, citations, machine discovery, and agreement with visible content.
E-E-A-T and YMYL evidence
Observable authorship, operator identity, credentials, policies, contact paths, sources, and topical risk—mapped through a disclosed WebsiteIQ heuristic, not a fictional Google score.
Performance and accessibility
Page weight, resource inventory, responsive metadata, common accessibility evidence, delivery friction, and issues that deserve browser or human follow-up.
Human and agent surfaces
robots.txt, sitemaps, llms.txt, well-known resources, OKF v0.2 projections, API descriptions, content alignment, query intent, and locality-volume review.
How WebsiteIQ Audits Websites
The public crawler identifies itself as WebsiteIQBot/1.2, consults robots.txt before content, rejects unsafe network targets and redirects, and stops at published request limits. It never pays a target to crawl it.
- ValidateReject private networks, credentials, unsafe ports, unresolved hosts, and mixed public/private DNS answers.
- ConsultSelect the applicable robots group and apply longest-match rules before requesting content.
- ObserveFetch permitted same-host pages sequentially with pacing, body limits, and redirect revalidation.
- ExplainShow observations, calculations, heuristic judgments, limitations, and next actions in the report.
A high score means the current WebsiteIQ rubric found more of the evidence it tests. It does not mean a search engine, customer, regulator, court, accessibility assessor, or security reviewer agrees.
Choosing a Website Audit Approach
Building an internal fetcher can be straightforward. Keeping its network boundaries, robots behavior, parsers, evidence model, report language, interfaces, and tests coherent over time is the expensive part.
Build your own
Best when the audit logic is core intellectual property and your team wants to own crawler identity, SSRF defense, parsing failures, scoring explanations, storage, delivery, and maintenance.
Use a broad SEO suite
Best for rank tracking, keyword programs, large recurring crawls, competitive datasets, and teams that need an established campaign platform rather than a bounded evidence pass.
Use WebsiteIQ
Best as a fast first diagnostic, a reusable client report, a white-label audit layer, or a small machine-callable capability before deeper specialist work.
Website Audit Reports
The human report, API contract, live MCP tools, crawler policy, well-known catalog, and OKF v0.2 bundle describe the same operating boundaries. Machine discovery is useful only when it stays aligned with what the service actually does.
Self-serve audits
Submit a public URL, follow live status, and open the unlisted token-bearing report without creating an account. Anyone with the complete link can view it.
White-label reports
Use WebsiteIQ’s evidence and report craft inside an agency, consulting, launch-QA, or customer-remediation workflow.
Agent access
The production MCP endpoint supports discovery, sitemap scope estimation, free single-page audits, x402-paid whole-site audits, status, and deletion with structured output that follows the same public operating boundaries. The official MCP Registry lists io.github.OsbornVentures/websiteiq version 1.4.0 as active.