Website Audit: SEO, WCAG Accessibility & AI-Readiness

Audit any website in one run and get a clear, prioritised list of what to fix: SEO basics, WCAG 2.2 A/AA accessibility (powered by axe-core), mobile layout, security headers and AI-readiness: whether ChatGPT, Claude, Perplexity and Google's AI crawlers may read the site, plus llms.txt, sitemap and structured data.

You get a dataset you can export (JSON, CSV, Excel) and a ready-to-share HTML report for every website.

What does it check?

Area	Checks
SEO	Title and meta description (presence and length), H1, noindex in meta and X-Robots-Tag, canonical URL, JSON-LD structured data (presence and validity), Open Graph tags, thin content, malformed hreflang
Accessibility	All axe-core rules tagged WCAG 2.0 / 2.1 / 2.2 level A and AA (contrast, alt text, form labels, ARIA, headings, link names…), page language, pinch-zoom disabled, small tap targets (WCAG 2.5.8)
Mobile	Mobile viewport, content wider than the screen (with the offending elements), tap target size
Security	HTTPS, mixed content, HSTS, Content-Security-Policy, X-Content-Type-Options, clickjacking protection, exposed software version
AI-readiness	robots.txt rules for 12 AI crawlers (GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, Claude-SearchBot, PerplexityBot, Google-Extended, Applebot-Extended, CCBot…), llms.txt, XML sitemap, structured data across the site

Every issue comes with severity, evidence (what was found, with example CSS selectors for accessibility issues), the WCAG success criterion where relevant, and how to fix it.

Who is it for?

• Agencies and freelancers: run a pre-sales audit for a prospect in minutes and send them the HTML report.
• Shops and businesses in the EU and UK: the European Accessibility Act applies to many online shops and services since 28 June 2025. Find the obvious accessibility gaps before a customer or regulator does.
• SEO and content teams: monitor many sites on a schedule and catch regressions (noindex left on, missing titles, broken structured data).
• AI search (GEO/AEO): check whether AI assistants are allowed to read your site, and whether you give them a sitemap, llms.txt and structured data.

How to use it

1. Add one or more website URLs under Websites to audit.
2. Choose how many pages per website (default 10). The Actor follows internal links on the same host.
3. Pick Mobile (default) or Desktop.
4. Run. Open the Site summaries tab and click the HTML report link.

Output

Two kinds of records go into the dataset:

Site summary (type: "site"), one per website:

{
  "type": "site",
  "site": "example.com",
  "pagesAudited": 10,
  "scores": { "seo": 88, "accessibility": 64, "mobile": 100, "security": 91, "overall": 86 },
  "aiReadiness": {
    "score": 83, "robotsTxtFound": true, "llmsTxtFound": false, "sitemapFound": true,
    "aiCrawlers": { "GPTBot": "blocked", "ClaudeBot": "allowed", "PerplexityBot": "allowed" }
  },
  "topIssues": [
    { "severity": "serious", "category": "accessibility", "title": "Elements must meet minimum color contrast ratio thresholds", "wcag": ["1.4.3"], "pages": 9, "howToFix": "…" }
  ],
  "reportUrl": "https://api.apify.com/v2/key-value-stores/…/records/report-example.com"
}

Page result (type: "page"), one per audited page, with its scores and the full issue list.

Scores run from 0 to 100 per area. Each issue subtracts points by severity (critical 25, serious 12, moderate 5, minor 2). They are a quick way to compare pages and track progress, not a Google ranking.

Pricing

Pay per event, no subscription:

• Page audited: charged once for each page that is audited.
• Site report: charged once per website for the summary, AI-readiness checks and the HTML report.

Pages that cannot be audited (blocked, unreachable, not HTML) are not charged. You can cap the cost of a run with Apify's maximum-charge setting; the Actor stops cleanly when it is reached.

Good to know

• Automated accessibility testing finds roughly a third to a half of issues. This is not a WCAG conformance certificate; keyboard and screen-reader testing still need a person.
• Security checks are passive. The Actor reads public pages and response headers. It never submits forms, logs in, adds to cart or tries to exploit anything.
• The Actor respects robots.txt and does not visit login, cart, checkout or admin URLs.
• Sites behind a bot challenge (for example a Cloudflare "Just a moment…" page) are reported as not auditable rather than given a wrong score.
• No personal data is collected: the Actor does not extract e-mail addresses, phone numbers or names.

Support

Found a false positive or want a check added? Open an issue on the Actor's Issues tab.

Made by BEK Service Ltd (UK).