SEO Site Audit: Website Crawler and Lighthouse

Crawl any website and get a full technical SEO audit for every page, status codes, titles, meta descriptions, H1s, canonicals, indexability, broken links, duplicate content, page speed, an onpage score and a plain English list of issues, plus a site summary and optional Lighthouse scores.

Who this is for: SEO agencies auditing client sites, site owners and marketers checking their own website, and developers who need crawl data in a pipeline or CI check.

Why this Actor

• From $3.40 per 1,000 audited pages (Gold plan; $6.90 on Free), no monthly fee; Apify platform usage is billed separately, versus $30 (Gold) / $40 (Free) for the most used SEO audit crawler in the Store and $5 (Gold) / $10 (Free) for a 28-field budget crawler. One per page auditor is $0.40 cheaper on Gold ($3 vs $3.40) but finds no broken links, site wide duplicates or Lighthouse scores (see the comparison below).
• 99 fields per page plus 60+ SEO checks (full field reference): onpage score 0 to 100, a priority (high / medium / low) and a fix hint for every issue, word count, readability, links, page size, timings, broken link targets, Core Web Vitals (optional), and site wide checks (sitemap, robots.txt, SSL, HTTPS/www redirects, 404 page, duplicates across the site).
• Lighthouse on demand: performance, accessibility, best practices and SEO scores with LCP, TBT, CLS and failed audits, from $0.007 per URL.
• Crawl exactly what you need: include only and exclude URL patterns (/blog/, *?sort=, *.pdf$), crawl speed from gentle (5 s between requests) to fastest (0.1 s), depth and time limits.
• Free change monitoring: each page is marked new, changed or unchanged versus the previous run, with the changed fields, schedule it weekly and review only what moved. No browser, proxies or API keys to set up.

One example row from a real run, shortened:

{
  "website": "https://example-shop.com",
  "url": "https://example-shop.com/",
  "pageType": "html",
  "statusCode": 200,
  "redirectUrl": null,
  "onpageScore": 97.07,
  "issuesCount": 4,
  "issues": [
    "Links from HTTPS to HTTP pages",
    "Meta keywords not relevant to page content",
    "Low text-to-HTML ratio",
    "Images without alt text"
  ],
  "issueCodes": [
    "httpsToHttpLinks",
    "irrelevantMetaKeywords",
    "lowContentRate",
    "noImageAlt"
  ],
  "issueDetails": [
    {
      "code": "httpsToHttpLinks",
      "priority": "medium",
      "fixHint": "Change links on this HTTPS page that point to http:// URLs to their https:// versions."
    },
    {
      "code": "irrelevantMetaKeywords",
      "priority": "low",
      "fixHint": "Remove the meta keywords tag (search engines ignore it) or make it match the content."
    },
    {
      "code": "lowContentRate",
      "priority": "low",
      "fixHint": "Little visible text compared with HTML code. Add content or reduce inline code, scripts and markup."
    },
    {
      "code": "noImageAlt",
  …
}

One row per crawled page (HTML pages, broken URLs and redirects) in the dataset:

Full field reference, all 99 fields of a page row</b> (generated from the dataset schema)

* always present and never null. Other fields are null (or an empty array) when the value does not apply to the page, e.g. Lighthouse fields on pages without a Lighthouse audit. checks is left out when Include all check results is off.

Issue priorities and fix hints: issueDetails gives every issue code a priority, high (hurts indexing, rankings or visitors directly, e.g. broken pages, notIndexable, duplicate content), medium (worth fixing soon, e.g. missing meta description, slow server) or low (minor, e.g. missing image title attributes), and a one sentence fixHint. They come from a fixed table per issue code, so they are free and consistent between runs; sort by priority to build a to do list.

That is 99 fields per page, all declared in the dataset schema (see the reference above). Plus a site summary per website in the key value store record SITE_SUMMARY: overall onpage score, pages crawled, top issues with page counts, broken links/resources, duplicate titles/descriptions/content, not indexable pages, redirect loops, CMS, server, SSL validity/expiry, sitemap/robots.txt/HTTPS/www redirect/404 checks, and, with change monitoring, new/changed/unchanged page counts and the previous run's onpage score.

You pay per event, through your Apify account. Main price: $6.90 per 1,000 audited pages on the Apify Free plan and $3.40 on Gold, plus $0.002 per website. Every event and plan:

Every run is one HTTP request to the Apify API with your Apify token; the input below is the actor's own example. The synchronous endpoint returns the rows in the response for runs up to 300 seconds; for longer runs start a run and fetch its dataset.

curl -X POST "https://api.apify.com/v2/acts/cheapapi~seo-site-audit/run-sync-get-dataset-items" \
  -H "Authorization: Bearer $APIFY_TOKEN" -H "Content-Type: application/json" \
  -d '{"startUrls":[{"url":"https://books.toscrape.com"}],"maxPagesPerSite":20,"runLighthouse":false,"crawlSpeed":"normal"}'

With the JavaScript client:

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('cheapapi/seo-site-audit').call({
  "startUrls": [
    {
      "url": "https://books.toscrape.com"
    }
  ],
  "maxPagesPerSite": 20,
  "runLighthouse": false,
  "crawlSpeed": "normal"
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();

A typical run: 1,000 pages of one website. Prices are the per page charge × 1,000 on the Free and Gold plans (event fees only). For this Actor, Apify platform usage is billed separately by Apify (at the default 256 MB a small run typically uses about $0.001 to $0.005), on top of the price shown.

The low cost per page auditor costs $1.90 (Free) / $0.40 (Gold) less per 1,000 pages. It checks structured data, social tags and headings of the URLs you give it; this Actor adds broken link targets, duplicate titles/descriptions/content across the site, indexability reasons, Lighthouse, JavaScript rendering, a site summary (sitemap, robots.txt, SSL, redirects) and free change tracking between runs. Our total includes the $0.002 website summary fee. Rival field counts are as listed on their Store pages, not independently verified.

Cheaper still: a very new crawler with about 4 users charges $0.50 per 1,000 pages (plus a small start fee and platform usage) for a basic audit, status, title/description, canonical, headings, word count, links, image alt gaps, indexability and structured data. If that is all you need, it costs less; it does not list broken link targets, site wide duplicates, Lighthouse, JavaScript rendering or change tracking.

Lighthouse only? If you just need Lighthouse / PageSpeed scores for URLs you already know, a PageSpeed API Actor (90 users) is cheaper at about $0.002 per URL versus our $0.007 (Gold) – $0.07 (Free), and a free Lighthouse Actor (200 users) charges only platform usage. Use this Actor when you also need the crawl, issues, broken links and duplicates.

Prices, user counts and feature lists from public Apify Store listings, checked September 2026.

Not included

• Keyword rankings and search volumes, this Actor audits pages, not Google positions. Use Domain SEO Analyzer for the keywords a domain ranks for, or Keyword Research Tool for volumes and ideas.
• Backlinks (who links to the site), only links on the crawled pages are analysed. Use Backlink Checker.
• Real user (field) Core Web Vitals, Lighthouse and full browser rendering measure lab values from one test run, not visitor data.
• Pages behind a login, only publicly reachable pages are crawled.
• Automatic fixes, you get issues and data, not changes to your website.

• Technical SEO audits for clients or your own sites, export the issue list straight into a spreadsheet.
• Pre- and post migration checks: find broken links, redirect chains, lost canonicals and not indexable pages.
• Content quality reviews: thin content, missing or duplicate titles, descriptions and H1s, low readability.
• Scheduled monitoring: run weekly; changeType and changedFields show which pages are new or changed (title, meta description, H1, canonical, status, indexability, issues, score) since the last run.
• Section audits: audit only /blog/ or /products/ with include patterns, and skip faceted or cart URLs with exclude patterns.
• Performance tracking with Lighthouse and Core Web Vitals for your key landing pages.
• Lead generation for agencies: audit prospects' websites and send them the top issues.

• Keyword rankings and search volumes, this Actor audits pages, not Google positions. Use Domain SEO Analyzer for the keywords a domain ranks for, or Keyword Research Tool for volumes and ideas.
• Backlinks (who links to the site), only links on the crawled pages are analysed. Use Backlink Checker.
• Real user (field) Core Web Vitals, Lighthouse and full browser rendering measure lab values from one test run, not visitor data.
• Pages behind a login, only publicly reachable pages are crawled.
• Automatic fixes, you get issues and data, not changes to your website.

• Lighthouse runs only on crawled HTML pages with status 2xx (the start page first); URLs outside the crawl are not tested.
• The crawler identifies itself with its own user agent; sites with aggressive bot protection may block it (try Use extra crawler network or a Custom user agent).
• Core Web Vitals per page (largestContentfulPaintMs, cumulativeLayoutShift, firstInputDelayMs) are measured only with Full browser rendering; otherwise they are null. Lighthouse always measures them.
• Broken link details are listed for up to 5,000 broken links per website (100 per page).
• If the crawl reaches Max crawl time, it is stopped and the pages crawled so far are delivered (site wide duplicate checks may then be incomplete).
• When several websites share a small budget, pages are allocated in input order, so the last websites may be skipped.
• URL patterns match the URL path and query from its start (robots.txt style * and $), not full regular expressions. Pages behind excluded URLs can still be reached if other links point to them through included sections.
• Change monitoring compares with the last run of the same website in the same monitoring store; changing thresholds or skipped checks changes onpage scores and shows up as changes. pagesNotCrawledAgain can include pages that were simply outside this run's page limit. Up to 40,000 URLs per website are remembered.