Website SEO & Broken Link Auditor
Under maintenancePricing
from $5.00 / 1,000 page audit results
Website SEO & Broken Link Auditor
Under maintenanceCrawl websites for SEO issues, broken links, duplicate metadata, image alt gaps and product JSON-LD. Export page findings and a shareable HTML audit report.
Pricing
from $5.00 / 1,000 page audit results
Rating
0.0
(0)
Developer
Lahcen El-Hadi
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
6 days ago
Last modified
Categories
Share
Turn a list of website URLs into a prioritized technical SEO checklist, a broken-link dataset, and a shareable HTML report. Built for marketing agencies, website owners, ecommerce teams, and automation workflows.
What you get
- Same-origin page discovery with explicit page, depth, and link request limits.
- Page titles, meta descriptions, canonical URLs, H1s, image alt coverage, noindex directives, and duplicate metadata within the sampled pages.
- Broken links (HTTP 404/410), server errors, redirect destinations, and separate network-error results.
- JSON-LD syntax checks, schema types, and Product names, SKUs, offer prices, currencies, and availability when present in HTML.
- One dataset item per attempted HTML page, a
SUMMARYJSON record, and an escaped, standaloneREPORTHTML record in the default key-value store. - A recommendation and severity for each finding, with no opaque or invented SEO score.
Quick start
{"startUrls": [{"url": "https://docs.apify.com/"}],"maxPages": 5,"maxDepth": 1,"maxLinkChecks": 15,"checkExternalLinks": false,"requestDelayMs": 300}
Start with a small crawl, inspect SUMMARY for coverage, and increase limits as needed. The total maxPages covers all start URLs together; it is not a per-domain allowance. Only the exact seed origins are eligible for automatic discovery. Add both www and non-www seed origins if needed.
Input
| Field | Default | Meaning |
|---|---|---|
startUrls | required | 1–20 public HTTP(S) URLs, using URL objects or strings. |
maxPages | 10 | Maximum page audit records across all seeds; 1–200. Fetch failures consume this limit. |
maxDepth | 2 | Discovery depth; 0 audits only the supplied URLs, up to 5. |
maxLinkChecks | 30 | Global extra requests to check links; 0–500. Already audited pages are reused. Robots requests and redirects are additional. |
checkExternalLinks | false | Also check links to external origins, within the same global request allowance. |
requestDelayMs | 300 | Minimum delay between requests to the same origin; 100–10,000 ms. |
Outputs and exports
Open Dataset for page results and export JSON, CSV, Excel, or HTML using Apify's standard export tools. Nested objects are most useful in JSON. Open Storage → Key-value store → REPORT for the shareable report, and SUMMARY for issue counts, skipped URLs, request counts, and remaining queued pages.
Each page contains url, requestedUrl, statusCode, title, description, canonical, h1, robots, imagesMissingAlt, schemaTypes, products, checkedLinks, uncheckedLinkCount, and issues. Fetch failures contain an error instead of extracted metadata. Severity is a review priority; a deliberate noindex page can be perfectly correct.
Automation
Run with Apify API, Make, Zapier, or n8n. Use an ACTOR.RUN.SUCCEEDED webhook to trigger your own workflow and read the run's defaultDatasetId or defaultKeyValueStoreId. Scheduling and integrations are configured by the customer; this Actor does not create schedules or send emails.
Pricing
Store price: $5 per 1,000 page audit records ($0.005 per result), plus $0.001 per Actor start at the default 256 MB memory. The start event scales per GB with a minimum of one event. Fetch-error audit records are included because they contain diagnostic results. Skipped robots-disallowed and non-HTML pages do not generate a dataset charge. Check the live Store pricing tab for the active price and platform cost treatment. HTML report and summary do not generate additional result events. The page allowance is reduced automatically when the run's maximum charge budget is lower than the requested crawl size.
Limits and responsible use
This is an HTTP HTML auditor: it does not render JavaScript, bypass logins or CAPTCHAs, perform vulnerability scanning, check Core Web Vitals, or establish full search-engine indexability. JSON-LD checks validate JSON syntax and extract fields; they do not certify rich-result eligibility. Product offers are observed values, not verified stock or checkout prices. Word count and title length are heuristics, not ranking promises.
Only a sample is crawled. Links beyond the configured allowance remain explicitly unchecked. HTTP 403/429 and network failures are not labeled broken links. Response bodies over 3 MB are rejected. Robots rules for WebsiteAuditBot are honored; unavailable robots policies are skipped conservatively, and crawl delays above 10 seconds cause that origin to be skipped. Robots-disallowed URLs, non-HTML responses, and already visited redirect destinations appear in coverage rather than successful page records. Public network targets only; no credentials in URLs or custom authentication headers. Use only on websites you are entitled to audit and follow their terms.
No profit, ranking improvement, complete website coverage, or availability guarantee is made.
Support
Use the Actor's Issues tab with a public sample URL, your input, and run ID. Do not post passwords, tokens, or customer data.