SEO Page Audit: on-page checks for any URL list
Pricing
from $3.00 / 1,000 page auditeds
SEO Page Audit: on-page checks for any URL list
Fast HTTP-only on-page SEO audit: title, meta, headings, canonical, Open Graph, structured data, security headers, issues list and score per URL.
Pricing
from $3.00 / 1,000 page auditeds
Rating
0.0
(0)
Developer
asaf meizner
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
25 days ago
Last modified
Categories
Features
Share
SEO Page Audit: on-page checks for any list of URLs
Give it a list of public page URLs and get one structured audit row per page: HTTP status, redirects, response time, title and meta description (with lengths), canonical, robots meta, headings, link and image counts, Open Graph and Twitter tags, JSON-LD types and structured-data diagnostics, hreflang, security headers, a plain-language issues list and a 0-100 score.
It checks robots.txt for each origin and fetches each supplied page with plain HTTP, following permitted redirects. No browser or recursive crawling is used. Use it for authorized client-site checks, sitemap exports, or monitoring pages after a deploy. Submit only public URLs whose terms permit automated access.
Input
Start with two public test pages:
{"urls": ["https://www.python.org/", "https://example.com/"],"delaySeconds": 1}
| Field | Default | Meaning |
|---|---|---|
urls | Required | Up to 500 distinct public HTTP or HTTPS URLs. Missing schemes become HTTPS. Invalid URLs are skipped and duplicates are removed. |
delaySeconds | 1 | Pause after each supplied URL. The actor enforces at least one second even if you enter a smaller value; robots crawl-delay may add more waiting. |
Only the supplied pages are audited. Links found on those pages are counted, not followed. To monitor changes, schedule this actor in Apify and compare each URL's results between runs in your own workflow.
Output (one row per URL)
Illustrative excerpt from an HTML audit. Values are examples, not a current measurement of example.com; actual rows include additional fields. The score uses the complete issues list.
{"url": "https://example.com/","finalUrl": "https://example.com/","status": 200,"redirects": 0,"responseMs": 180,"title": "Example Domain","titleLength": 14,"metaDescription": null,"canonical": null,"h1": ["Example Domain"],"internalLinks": 0,"externalLinks": 1,"openGraph": {},"structuredDataTypes": [],"structuredDataBlocks": 0,"structuredDataErrors": [],"securityHeaders": {"strict-transport-security": false, "content-security-policy": false},"wordCount": 28,"issues": ["Title very short (14 chars)", "Missing meta description", "No canonical link", "No viewport meta (not mobile friendly)", "No lang attribute on <html>", "Incomplete Open Graph tags (og:title / og:image)", "Thin content (28 words)"],"score": 44}
Checks include: missing/too long/too short title, missing or long meta description, missing or multiple h1, missing canonical, noindex, missing viewport or lang, images without alt, incomplete Open Graph, malformed or incomplete JSON-LD (@graph traversal, syntax errors, missing @type, and missing recommended fields for common Schema.org types like Article, Product, JobPosting, Event, FAQPage, Organization, LocalBusiness, WebSite), non-HTTPS, thin content, and HTTP errors.
Pricing (pay per event)
page-audit: 0.003 USD per URL audited (including URLs that return an error status or non-HTML content). URLs that cannot be reached at all are listed with anerrorfield and are not charged.
Notes
Page requests use an identifying User-Agent and at least one second between supplied URLs. robots.txt is cached per origin and checked before each page and redirect; disallowed URLs or unverifiable robots policies produce an uncharged error row. Robots redirects are conservatively treated as unverifiable. Robots crawl-delay is honored when present. Robots permission does not replace reviewing the site's terms.
Pages that need JavaScript are audited as served in the initial HTML. The score is a heuristic (100 minus 8 per issue), meant for triage, not a ranking prediction. Response time includes robots checks and any required wait, and is not a browser performance metric.
Local validation on 2026-10-19: eight automated tests passed, and an SDK local-mode run against https://www.python.org/ returned HTTP 200, title "Welcome to Python.org", one WebSite JSON-LD block (structuredDataErrors: missing recommended name), five h1 elements and score 76. These are observed test results, not guaranteed future values.
Passive security-header checks
Every fetched response includes securityHeaderValues and securityFindings. Checks cover HTTPS HSTS max-age, enforcing CSP, script wildcard/unsafe-eval/unsafe-inline without a nonce or hash, framing restrictions, nosniff and referrer policy. CSP frame-ancestors is accepted instead of X-Frame-Options. Permissions-Policy is reported without a blanket requirement.
These are final-response configuration hints, not a vulnerability assessment, full CSP parser, browser enforcement test or TLS scan. Findings remain separate from the SEO score. No extra requests or charges are added; page-audit remains $0.003.