Website SEO Audit & Contact Scraper (Apify)

Audit public pages for SEO gaps, contact details and security-header signals. Export scores and findings to JSON or CSV.

Servidor MCP hospedado

npx add-mcp 'https://mcp.apify.com/?tools=monkey.d.scraping/website-opportunity-auditor'

Instala no Claude Code, Codex, Cursor e outros

Documentação

Website SEO Audit & Contact Scraper (monkey.d.scraping/website-opportunity-auditor) Actor

Audit public pages for SEO gaps, contact details and security-header signals. Export scores and findings to JSON or CSV for agency prospecting. $0.015 per output record; no login or external API key.

Pricing

$15.00 / 1,000 website auditeds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes. In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours, and optionally produces a well-defined JSON output, datasets with results, or files in key-value store. In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects. You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the API section below.

Each client library has reference documentation the quickstart does not restate: JavaScript/TypeScript (npm install apify-client) and Python (pip install apify-client).

README

Website SEO Audit Scraper for Agency Prospecting

Audit public website pages for visible SEO gaps, contact details and security-header signals. Get JSON or CSV for agency prospecting and manual review at $0.015 per output record.

Website Opportunity Auditor is a fast website audit scraper for SEO lead generation, website redesign prospecting, digital agency sales, technical SEO checks, security-header review and competitor website research. It analyzes public websites without login, API keys or external account authentication and returns structured JSON ready for CRM, spreadsheets and automation.

Website Opportunity Auditor turns a list of public websites into a clean, structured dataset for agencies, consultants, SEO teams, sales operations, web designers and market researchers. Discover which websites have visible SEO gaps, missing contact signals, weak security headers, incomplete social sharing setup or clear modernization opportunities.

Run your first website audit

  1. Enter one public URL in Websites, or keep the example.com sample.
  2. Start the Actor. One output record costs $0.015, including a record that reports an error.
  3. Open the dataset and check status before comparing scores. Export JSON to preserve nested fields, or select fields for CSV.
  4. Save the input as an Apify task if you want to repeat the audit. Scheduling and notifications require your own configuration.

Ready-to-run examples

ExampleUse caseWhat you get
Audit competitor landing pages: SEO issues and contactsCompetitor reviewOn-page SEO issues and public emails, phones and social links for the Pipedrive, Zoho CRM and Freshsales landing pages

Browse all ready-to-run examples →

What you get

Successful website records include:

  • opportunity score and high/medium/low tier;
  • issues with severity and a description of the observed signal;
  • page title, meta description, H1, language and word count;
  • public emails, phone numbers and contact-page links when visible;
  • HTTPS, HSTS, CSP and security-header signals;
  • detectable CMS, CDN and server signals;
  • public social profile links;
  • HTTP status, audited URL and timestamp.

Built for practical workflows

Agency prospecting

Audit a short list of prospective client websites. Filter for missing_meta_description, inspect the returned URL and seo.metaDescription, then verify the page before recommending a metadata update. Use opportunityScore to prioritize manual review; it does not measure purchase intent or predict revenue. Export the dataset to CSV or connect it to your CRM.

SEO lead generation

Create a list of sites missing titles, descriptions, canonical URLs, H1 headings or social metadata.

Web design and development sales

Identify websites with missing mobile declarations, outdated signals, weak trust surfaces or no obvious contact path.

Security and maintenance triage

Surface public HTTPS and security-header signals for a first-pass review before a professional assessment.

Competitor and portfolio review

Run the same audit across a portfolio, market segment or competitor list and compare results in spreadsheets or dashboards.

Input

{
  "websites": [
    "https://example.com",
    "example.org"
  ]
}

websites accepts public URLs or domains. The Actor processes at most 500 distinct input strings per run. The audit applies the same checks and scoring to every website. The former focus selector has been removed because it did not change results; legacy API inputs containing focus are still ignored.

Real output excerpt

Reduced record observed in an owner verification run on 20 October 2026. Values are retained from that page observation; nested findings and other fields are omitted for readability.

{
  "url": "https://example.com/",
  "domain": "example.com",
  "status": 200,
  "fetchedUrl": "https://example.com/",
  "opportunityScore": 42,
  "opportunityTier": "medium",
  "issueCount": 7,
  "auditedAt": "2026-10-20T07:45:34.724Z"
}

The score of 42 is the Actor's rule-based prioritization signal for the observed page, not an independently verified SEO grade or evidence of a sales opportunity. status: 200 is the HTTP outcome, not proof that all information was found. Seven detected issues do not establish seven business-critical defects. Inspect the full findings and evidence before acting; later page changes may produce different results.

Integrations

Use the Apify API, webhooks, schedules, n8n, Make, Zapier, Google Sheets, Airtable or your own CRM. The dataset contains nested objects and arrays; select fields or flatten them for spreadsheet workflows. It is suitable for CSV, JSON, Excel and automated enrichment workflows.

Important notes

The Actor fetches the supplied page and follows redirects; it does not crawl an entire site or execute browser JavaScript. Header flags indicate presence, not a security assessment. Missing analytics or contact signals are not proof of absence. HTTP errors and failed requests produce error records with fewer fields and no opportunity score; inspect status and error before using a record as an audit. The Actor only reports signals visible in the fetched HTML. A missing signal is an opportunity for review, not proof that a business has no capability or service. Always validate findings before contacting a business and comply with applicable privacy, marketing and website-access laws.

Pricing

The current tariff is $0.015 per dataset record, with platform usage included. Ten records cost $0.15 and 100 cost $1.50. The implementation also writes a dataset record for an invalid URL or a failed request; these records fall under the configured dataset-item event, so do not assume failures are free. No separate startup event is configured. Run a small sample first, then scale to hundreds of domains in one run. Your Apify subscription may still apply to normal post-run storage operations.

Why agencies use it

Instead of manually opening websites one by one, sales and delivery teams can create a prioritized list of companies that may benefit from SEO, redesign, analytics setup, maintenance or security improvements. The output is factual and traceable: every opportunity is linked to a visible website signal.

Example tasks

  • Find SEO prospects with missing metadata.
  • Find local businesses that may need a website redesign.
  • Review a portfolio of client websites before a quarterly meeting.
  • Compare technical website signals across competitors.
  • Create a recurring website quality snapshot with Apify Schedules and webhooks.

Frequently asked questions

Does it audit my entire website?

No. SEO checks cover each supplied page. Optional Contact-page enrichment can inspect up to two linked Contact pages on the same site for missing emails or phones; it is not a whole-site crawl. JavaScript is not executed.

What does the opportunity score mean?

Higher values mean more missing signals among the checks performed: critical issues add 25, high 14, medium 8 and low 3, capped at 100. Tiers are high at 55+, medium at 25–54 and low below 25. It is a triage heuristic, not a search ranking, security rating or prediction of sales.

Does it measure visibility in ChatGPT or other AI search engines?

No. It checks public page signals, not AI answers, citations or search rankings. Use its output as evidence for manual review; it does not guarantee SEO or GEO improvements.

Why is the score null?

The request failed or returned an HTTP error. Check status and error; do not interpret an unavailable score as a healthy page. Error records are still dataset records under the current tariff.

Can I monitor changes automatically?

Save the input as a task and configure a schedule. Each run produces a separate dataset; comparison, deduplication and alerts belong in your downstream workflow.

How do I report a problem?

Open the Actor's Issues tab with the run ID, a public example URL and the expected result. Exclude credentials and private information.

Related workflow

Affiliate Program Finder can research published partnership terms for a shortlist of company websites. Use it when qualifying affiliate partners; Website Auditor covers the page’s visible SEO and contact signals.

Contact extraction limits

Emails are read from visible text and mailto links and deduplicated without regard to letter case. Phone candidates come from tel links, international prefixes, or explicit telephone labels; unlabelled national numbers may be omitted to reduce false positives. These are published contact signals, not verified ownership, deliverability or valid telephone lines. Contact-page links are restricted to the same host (www variants accepted); these pages are fetched only when Contact-page enrichment is enabled and an email or phone is missing. The combined contact output retains at most 10 emails and 10 phones per website; each source entry records its own extracted values.

Find email and phone contacts beyond the starting page

Enable Look for missing contacts on Contact pages (followContactPages: true) to inspect up to two linked Contact pages when the starting page lacks an email or phone. Only the same hostname, allowing www equivalence, is eligible. Each page can follow up to three same-site redirects: at most eight additional HTTP requests per website. Requests have a ten-second timeout and HTML responses are capped at two million bytes. The scan stops once both an email and phone are available; it does not crawl links found on the extra pages.

contact.sources records the inspected page URLs and their extracted emails and phones. contactScan reports pages attempted/read, HTTP requests, errors and the stop reason. A failed Contact page does not erase the initial audit. Missing-contact findings mean no value was detected in inspected content, not proof that no public contact exists.

SEO, security and technology checks still refer to the starting page. Contact findings and the opportunity score are updated when an extra page supplies a missing email or phone. This remains one output record per website; the current per-record tariff applies, with no separate Contact-page event. The feature is off by default and can increase runtime. Contacts are published signals, not verified ownership, deliverability or permission to contact someone.

{
  "websites": ["https://creativecommons.org"],
  "followContactPages": true
}

Labelled contacts and contact-page selection

Explicitly labelled email addresses are prioritized before the ten-address cap. Labelled national phone numbers may include parentheses; unlabelled digit groups are excluded to reduce false positives. Long product descriptions mentioning contacts are not treated as Contact links unless their URL identifies a contact path. These are published contact signals, not verified leads: department, deliverability and ownership are not inferred. Source URLs remain available in contact.sources.

Actor input Schema

websites (type: array):

Public page URLs or domains, one per line. Start with one page ($0.015 per output record, including errors). Up to 500 pages; no whole-site crawl.

followContactPages (type: boolean):

If the starting page lacks an email or phone, inspect up to two linked Contact pages on the same site. Stops when both are found. Adds source URLs and scan diagnostics; no additional output rows. SEO checks still describe the starting page. May increase runtime.

Actor input object example

{
  "websites": [
    "https://example.com"
  ],
  "followContactPages": false
}

Actor output Schema

overview (type: string):

No description

API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

JavaScript example

import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "websites": [
        "https://example.com"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("monkey.d.scraping/website-opportunity-auditor").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

Python example

from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "websites": ["https://example.com"] }

# Run the Actor and wait for it to finish
run = client.actor("monkey.d.scraping/website-opportunity-auditor").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

CLI example

echo '{
  "websites": [
    "https://example.com"
  ]
}' |
apify call monkey.d.scraping/website-opportunity-auditor --silent --output-dataset

MCP server setup

{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,monkey.d.scraping/website-opportunity-auditor"
        }
    }
}

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an Authorization: Bearer <APIFY_API_TOKEN> header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/xj4bEIaa35QdrNCNV/builds/cV5TjZ2ipHa2J8cRa/openapi.json