SEO Audit Tool (On-Page Checker, Canonical, Alt Text)

Audit the on-page SEO of any public web pages: title, meta description, headings, canonical, indexability, structured data types, image alt text, link counts and social tags, with a list of issues and a 0 to 100 score per page. Optional same-site crawl.

• Pay per result row: the platform usage of the run is included, and a run that finds nothing has no result charges.
• No login, no cookies, no account on the audited sites: public pages only.
• Export to JSON, CSV, Excel, XML or HTML, or read the rows through the Apify API.
• Start it from the Console, on a schedule, through the API, or as a tool for agents over MCP.
• Tested every day on its example input, with the rows checked, and repaired when a check fails.

What you can use it for

• On-page audits for clients: one row per page with a score and a list of issues to fix.
• Pre-launch checks: run a site through the audit before it goes live.
• Monitoring: schedule an audit and catch pages that lost their title, canonical or alt text.
• Competitor comparison: audit rival pages with the same checks as your own.

What you get

Every result is one row in the run's dataset. Download it as JSON, CSV, Excel or HTML, or read it through the Apify API. The main fields:

Field	Meaning
url	Page
statusCode	Status
score	Score
indexable	Indexable
title	Title
titleLength	Title length
metaDescriptionLength	Description length
h1Count	H1 headings
wordCount	Words
imagesMissingAlt	Images without alt
internalLinks	Internal links
externalLinks	External links
canonicalIsSelf	Canonical is this page
issues	Issues

Example row:

{
  "url": "https://www.python.org/",
  "finalUrl": "https://www.python.org/",
  "statusCode": 200,
  "redirected": false,
  "https": true,
  "contentType": "text/html",
  "pageSizeBytes": 51918,
  "score": 86,
  "indexable": true,
  "title": "Welcome to Python.org",
  "titleLength": 21,
  "metaDescription": "The official home of the Python Programming Language",
  "metaDescriptionLength": 52,
  "h1": "Functions Defined",
  "h1Count": 5,
  "h2Count": 9,
  "wordCount": 936,
  "canonical": null,
  "canonicalIsSelf": null,
  "metaRobots": null,
  "xRobotsTag": null,
  "lang": "en",
  "hreflangCount": 0,
  "imagesCount": 1,
  "imagesMissingAlt": 0,
  "internalLinks": 64,
  "externalLinks": 63,
  "nofollowLinks": 0,
  "structuredDataTypes": [
    "WebSite"
  ],
  "openGraph": {
    "title": true,
    "description": true,
    "image": true
  },
  "twitterCard": null,
  "hasViewport": true,
  "robotsTxtFound": true,
  "sitemapListed": false,
  "foundOn": null,
  "issues": [
    {
      "code": "canonical_missing",
      "severity": "warning",
      "message": "The page has no canonical link."
    },
    {
      "code": "title_too_short",
      "severity": "notice",
      "message": "The title is only 21 characters. Titles of 30 to 60 characters usually work best."
    },
    {
      "code": "meta_description_too_short",
      "severity": "notice",
      "message": "The meta description is only 52 characters. 70 to 160 characters usually work best."
    },
    {
      "code": "h1_multiple",
      "severity": "notice",
      "message": "The page has 5 H1 headings. One main heading is the usual practice."
    }
  ]
}

How to use it

1. Open the Input tab (or call the actor through the API, see below).
2. Fill in Page addresses; the form opens with a working example.
3. Set Maximum results to cap the size and the cost of the run.
4. Click Start. Rows appear on the Output tab while the run works.
5. Download the dataset, or connect it to Google Sheets, Make, Zapier, n8n or a webhook.

Input

Field	Type	Required	Description
startUrls	array	yes	Web pages to audit, one address per line, for example https://example.com/pricing. At most 500. Only public web pages on the standard ports are read.
maxPagesPerSite	integer	no	1 audits only the pages you list. A higher number also follows links to other pages of the same site, breadth first, until that many pages of the site are audited (your listed pages are always included). Default: 1.
maxItems	integer	no	The run stops after this many result rows. It also caps what one run can cost. Default: 100.
proxyConfiguration	object	no	Leave as is: the run starts on the cheapest network the site accepts and switches to Apify Proxy automatically when the site blocks it. Pick proxy groups here only to force one specific network.

Example input:

{
  "startUrls": [
    "https://www.python.org/",
    "https://docs.python.org/3/",
    "https://www.joelonsoftware.com/"
  ],
  "maxPagesPerSite": 5,
  "maxItems": 20
}

Pricing

You pay per result row in the dataset (the current price per 1,000 results is on the Pricing tab). A run that finds nothing produces no rows and no result charges. Set Maximum results to cap what a single run can cost.

Limits and notes

• One row per audited page. At most 500 listed addresses, at most 200 pages per site and 5000 pages per run. With Pages per site at 1 only the pages you list are read.
• The page is read as a visitor without JavaScript sees it, so a page that builds its title or links in the browser shows what the server sends. The run does not read sitemaps, images or other sites.
• The score starts at 100 and loses 20 points per error, 8 per warning and 2 per notice, down to 0. A page that answers with an HTTP error or an empty page scores 0, and a page that is not HTML (a PDF or an image) has no score.
• Duplicate title and duplicate description checks compare a page with the pages of the same site audited earlier in the run, so the later page of a pair carries the finding and names the first.
• Addresses of file downloads (archives, installers, video, audio) are refused. PDFs and images are accepted and reported with their status and size only.
• Pages that the site's robots.txt closes to automated access, pages that refuse the request and pages that cannot be reached are skipped and produce no row. If nothing could be audited the run ends with the reason.
• No page text is collected. Only the title, meta description and first H1 heading are returned, with e-mail addresses and phone-like numbers removed.
• Only publicly visible data is collected. No login, no paywalled content, no personal contact details.
• The actor reads only pages that the site's robots.txt leaves open to automated access.
• Sites change their pages from time to time. The actor is checked automatically and repaired when a check fails.
• Each run sends one short usage record to the developer: the Actor and run IDs, the number of results, whether the run succeeded (and if not, the kind of error, such as "blocked" or "input problem"), whether the account is on a paid Apify plan, how the run was started (for example from the Console, the API or a schedule) and a one-way fingerprint of the account (a hash, not the account ID), so that repeat runs of one account count once. It contains nothing from your input or results.

Run it through the API

Python, with the apify-client package:

from apify_client import ApifyClient

client = ApifyClient("<YOUR_APIFY_TOKEN>")
run = client.actor("v0iddo/seo-audit").call(run_input={"startUrls": ["https://www.python.org/", "https://docs.python.org/3/", "https://www.joelonsoftware.com/"], "maxPagesPerSite": 5, "maxItems": 20})
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)

JavaScript, with the apify-client package:

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: '<YOUR_APIFY_TOKEN>' });
const run = await client.actor('v0iddo/seo-audit').call({"startUrls": ["https://www.python.org/", "https://docs.python.org/3/", "https://www.joelonsoftware.com/"], "maxPagesPerSite": 5, "maxItems": 20});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

One HTTP call that waits for the run and returns the rows (for runs that finish within 5 minutes):

curl -X POST "https://api.apify.com/v2/acts/v0iddo~seo-audit/run-sync-get-dataset-items?token=<YOUR_APIFY_TOKEN>" \
  -H "Content-Type: application/json" \
  -d '{"startUrls": ["https://www.python.org/", "https://docs.python.org/3/", "https://www.joelonsoftware.com/"], "maxPagesPerSite": 5, "maxItems": 20}'

Use it from an agent (MCP)

Claude, Cursor, VS Code and other MCP clients can call this actor as a tool through the Apify MCP server. Add it to the client's MCP configuration:

{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com?tools=v0iddo/seo-audit",
      "headers": {
        "Authorization": "Bearer <YOUR_APIFY_TOKEN>"
      }
    }
  }
}

Then ask, for example: "Audit these five pages and tell me the top SEO issues on each."

FAQ

Do I need an account on the audited sites, cookies or an API key?

No. The actor reads only what every visitor of the audited sites can see, without logging in. You only need an Apify account to start it.

How many results can one run return?

Up to 5,000 rows per run. Without a limit it stops at 100. Set Maximum results to the number you need; large jobs can also be split into several runs or scheduled.

How am I charged?

Per result row in the dataset, at the price on the Pricing tab for your Apify plan. The platform usage of the run is included in that price. A run that finds nothing produces no rows and no result charges, and your spending limit for a run is always respected.

Why did my run return no results?

The status message of the run says why: nothing matched the input, the input was not a page the actor understands, the page is closed to automated access by robots.txt, or the site refused every network the actor tried. Check the input against the example above and run it again with a small limit.

Can I run it on a schedule?

Yes. Save your input as a task and add a schedule in the Apify Console (daily, hourly or with a cron expression). Each run gets its own dataset, so you keep a history.

Which formats can I export?

JSON, CSV, Excel, XML, HTML table and RSS from the Output tab or the API. Integrations send the rows to Google Sheets, Slack, Make, Zapier, n8n or a webhook.

Is collecting this data allowed?

The actor collects only what the audited sites publishes to every visitor, without a login, and it reads only pages that robots.txt leaves open. Public data can still be personal data under laws such as the GDPR, and sites have their own terms: make sure your use of the data follows the rules that apply to you.

What happens when the audited sites changes its pages?

Automated tests run the actor every day on the example input and check the rows, not only that the run finished. When a check fails, the actor is repaired and rebuilt; the build history on this page shows each update.

Something is missing or wrong. Where do I report it?

Open an issue on the Issues tab of this actor with the run link. Requests for a new field are welcome too.

Related actors

• Sitemap URL Extractor
• Website Technology Detector