Web Design & SEO Leads Database | 3.2M+ Audited Records

Inventory checked 17 October 2026: 3,236,115 stored records with successful audits, including 695,782 with a stored email. The title rounds this down to 3.2M+ audited records. These counts are before domain validation/deduplication; they are not 3.2 million unique domains or verified email addresses. Contact and campaign filters reduce the available audience. The separate unfiltered source inventory also contains unaudited/failed-attempt rows; those are not included in this title.

Find web design leads, SEO leads and website redesign prospects with available contact details. Search a growing database of audited WordPress sites for website issues that your agency or freelance service can help address. Filter by country, technology, company profile and audit findings, then export emails, phones, scores and a suggested pitch angle to CSV, Excel or your CRM workflow.

This is a WordPress website lead database with previously collected audits. Each export searches stored results; audit dates and freshness filters help you select recently checked prospects. Refresh coverage depends on the collection queue; there is no guaranteed update interval.

For web designers, SEO agencies and WordPress consultants, the workflow is simple: find a relevant website issue, review the evidence and contact information, and decide whether the business is a good fit for your service.

Find clients for web design and SEO services

Service you sell	Prospects to search for	Useful controls
Website redesign	WordPress sites with broad or targeted redesign opportunities	Redesign preset, audit scope, country, available email
SEO services	Websites with weak stored SEO scores and relevant findings	SEO preset, SEO threshold, technology, company profile
WordPress speed optimization	Sites with weak performance scores	Performance preset, score threshold, country
WooCommerce development	Audited WooCommerce stores with redesign opportunities	WooCommerce technology filter and redesign preset
Accessibility or maintenance	Sites with recorded accessibility or best-practices issues	Specialist preset, score threshold, available contacts

An audit finding is a starting point for research. Review the website before claiming a current problem or sending a proposal.

Use it to turn technical website signals into a practical prospecting workflow:

1. choose the service you provide, such as SEO, performance or redesign;
2. narrow the audience by location, technology, company profile and severity;
3. review the reason each website may need help;
4. export available email, phone or social contacts;
5. come back later for newly added and newly audited opportunities.

Every result is one successfully audited website. Results can include:

• website and company name;
• emails, phone numbers and social profiles;
• Overall, SEO, Performance, Accessibility and Security/Best Practices scores;
• recommended scope: minor fixes, targeted fixes, targeted redesign or broad redesign;
• specific weak areas and audit confidence;
• website structure: one-page, multi-page, SPA or unknown, with confidence and evidence;
• country, city, industry, employees and estimated revenue;
• ecommerce, CMS, CRM, marketing, payments, hosting and detected AI technologies.
• a ranked Lead Score, primary weakness, recommended service and ready-to-personalize pitch angle.

The Actor searches a growing database of previously audited WordPress websites; it does not run a new live audit during each export. New data is added through the ongoing collection and audit process. Use the freshness filter when your campaign requires recently checked scores, and run the Actor again over time to find newly available prospects.

Web design leads, SEO agency leads and WordPress prospects

• SEO leads for technical SEO, content and search-visibility services;
• website performance investigation prospects;
• website security and best-practices audit leads;
• accessibility remediation opportunities;
• web design and website redesign leads, including one-page sites with recorded issues;
• WooCommerce and WordPress technology-based prospecting;
• email, phone and LinkedIn lead lists by country and company size;
• recent website audit leads for time-sensitive outreach.

Quick start

The default Balanced preset returns websites with an Overall Score of 74 or lower and an available email address, with the weakest opportunities first. Specialist presets target weak SEO, performance, security or redesign opportunities without silently applying an unrelated Overall threshold.

Choose Preview audience size first when planning a campaign. It returns the number of matching stored audit rows without creating lead rows. This is before domain validation and deduplication, so it can exceed the unique export size. Switch to Export leads with the same filters when the audience looks right.

Start with a focused example:

• Find US SEO agency leads with email
• Find one-page WordPress web design leads
• Find WooCommerce website redesign leads

Automation quickstarts:

• Python SDK and website-audit-leads on PyPI;
• n8n community node with a ready-to-import review-queue workflow;
• review-first prospecting guide.

The processed-site counter and the matching-lead counter are intentionally different. A processed site can be unreachable, blocked or missing a complete score, while every delivered row must contain a successful audit. Campaign and contact filters narrow that successful set further. Choose All successful audits and Any contact data to view the largest currently available audience.

{
  "runMode": "export",
  "opportunityPreset": "balanced",
  "contactRequirement": "email",
  "maxItems": 5
}

Target weak website security and best practices:

{
  "opportunityPreset": "security",
  "securityScoreMax": 60,
  "contactRequirement": "email",
  "country": [
    "US",
    "GB"
  ],
  "maxItems": 5000
}

Find WooCommerce website redesign leads

{
  "auditScopes": [
    "targeted_redesign",
    "broad_redesign"
  ],
  "technologies": [
    "WooCommerce"
  ],
  "contactRequirement": "email",
  "sortBy": "Overall Score",
  "sortDesc": false
}

Find web design prospects with one-page WordPress sites

{
  "siteTypes": [
    "one_page"
  ],
  "siteTypeConfidence": [
    "high"
  ],
  "contactRequirement": "email",
  "maxItems": 1000
}

Target established companies that do not already use a competing platform:

{
  "opportunityPreset": "performance",
  "contactRequirement": "email",
  "requireLinkedIn": true,
  "employeesMin": 10,
  "salesRevenueMin": 1000000,
  "excludeTechnologies": [
    "HubSpot"
  ],
  "maxItems": 1000
}

Score meaning

Scores are normalized to 0–100. Lower scores indicate more room for improvement. They are discovery signals for prioritizing outreach, not a warranty, security certification or substitute for a full manual audit.

Best Practices is displayed as Security / Best Practices because it includes web-security and implementation hygiene signals. The AI field lists detected AI technologies. AI Search Readiness is a transparent prioritization heuristic derived from the SEO score and findings such as missing structured data, weak headings, weak titles and thin content. It is not a certification or a measurement of search-engine inclusion.

Lead prioritization

Lead Score combines the size of the audit opportunity with available email, phone, LinkedIn, company and firmographic data. Primary Opportunity, Recommended Service and Pitch Angle translate raw scores into an outreach starting point. They are deterministic suggestions and should be personalized before contacting a prospect.

Billing and count preview

Delivered leads cost $3 per 1,000 on every plan. A standard-memory run also has a $0.00005 start event. Apify platform usage is charged separately to the user. For example, five leads have event fees of $0.01505 on every plan, plus platform usage. The default UI and API limit is five leads when maxItems is omitted.

Use runMode: "preview" to count matching stored audit rows and read COUNT_SUMMARY, COUNTRY_BREAKDOWN and MCP_RESPONSE. Preview creates no lead rows and has no result events; the start event and platform usage still apply. The legacy countOnly input remains supported. With unavailable segments the count is a lower bound (countComplete: false). If every segment fails, the run fails and the matching count is unknown rather than zero.

Empty results, duplicate domains and invalid audit rows are not billed as leads. Only leads actually delivered to the dataset incur result events.

Reliable bulk exports

Results use a global order across available data segments. The Actor reads bounded portions, validates domains and scores, and refills after duplicates. Deduplication by root domain is enabled by default. RUN_SUMMARY reports actual delivered rows, skipped duplicates, budget stops and segment health.

EXPORT_CONTINUATION contains a copy-ready nextInput only when another matching lead exists, all segments were available and the next offset is at most 50,000. Narrow your filters when this pagination limit is reached. Its offset advances by delivered rows, including when a charge limit stops delivery. A partial-source run withholds continuation because the global order is incomplete: retry the original input and deduplicate against your destination. ERRORS contains neutral error codes. If every segment fails, the run fails instead of reporting an empty audience.

For large exports, review a small sample and continue in pages. Dataset exports are available from Apify as JSON, CSV, Excel, XML and RSS. When delivery fails, inspect the dataset before retrying; rows may already have been delivered.

API and AI agents

The Actor declares input, output and dataset schemas. Use runMode: "preview" to size an audience, then export with the same filters. MCP_RESPONSE is the stable machine response: complete, partial or failed, delivered rows, segment health and safe continuation when available.

Connect an MCP client to https://mcp.apify.com with your Apify authentication, add apivault_labs/website-audit-leads, and ask: "Find three US WordPress sites with weak SEO and an email address. Return the dataset and MCP_RESPONSE."

{
  "opportunityPreset": "seo",
  "contactRequirement": "email",
  "country": [
    "US"
  ],
  "maxItems": 3
}

For REST, POST this JSON to https://api.apify.com/v2/acts/apivault_labs~website-audit-leads/runs using an Authorization: Bearer <YOUR_APIFY_TOKEN> header. Poll the returned run ID, then read its default dataset and key-value store. Keep authentication in your client configuration.

Data freshness

This Actor searches stored WordPress audit observations; it does not perform a new live audit of each URL. Audit Checked At identifies the observation time. Use checkedWithinDays to require a recent observation; future dates are excluded. Unknown component scores and derived readiness values stay empty. Zero is a known score, not a missing value. Invalid Overall Scores are excluded.

The data can change between runs. Offset pagination does not create a frozen snapshot: keep the same filters and sort, and deduplicate in your destination.

Frequently asked questions

How can I find businesses with bad websites?

Choose the redesign, SEO or performance preset, select a country and require available email or phone data. Review the stored scores, audit date and findings before deciding which businesses to contact. "Bad website" is a prospecting description, not a guarantee that a business needs or wants to buy your service.

Can I use this as an SEO lead generation tool?

Yes. The SEO preset finds matching audited WordPress sites. Combine it with country, technology and contact filters to build an SEO agency prospect list. Export a small sample first and review it before a larger campaign.

Does it find businesses without a website?

Every result has a website and a successful stored audit. Businesses without websites are outside this database's coverage.

Can I audit my own URL list or search Google Maps?

Inputs select prospects from the stored WordPress audit database. Live URL audits and Google Maps discovery are separate workflows and are not inputs to this Actor.

Are the emails verified and the leads guaranteed to convert?

Contact fields contain available collected data. They are not a guarantee of mailbox deliverability, current ownership or buying intent. Check the business and contact details before outreach.

Responsible use

Use contact data in accordance with applicable privacy, marketing and anti-spam laws. Scores should support relevant, personalized outreach rather than bulk spam.

Review the evidence before outreach

The Audit Leads view includes Audit Checked At, Audit Age Days, Audit Provider, Audit Confidence, stored issue tags, available contact channels and a website Verification URL. Opportunity Evidence is a structured stored audit summary, not a live retest or page-level proof. Unknown dates and providers remain unknown.

When Audit Provider is localfast, scores describe homepage HTML, response and header heuristics. They are not Lighthouse scores or measured Core Web Vitals. For other providers this export does not establish the collection method. Review the linked website before claiming that an issue still exists. Lead Score and AI Search Readiness are calculated prioritization heuristics, not certifications.

Build a review queue for your agency service

The best audience depends on the service you actually deliver. An SEO agency needs a reason to inspect search-related findings; a WordPress developer may prefer redesign scope and company fit; a performance specialist can start with a weak stored performance score. These are research queues, not lists of businesses that have agreed to a sales call.

Service	Start with	Inspect in every useful row
Technical SEO review	SEO preset, country and email	SEO score, issue tags and audit date
WordPress speed investigation	Performance preset	Provider, performance evidence and freshness
Website redesign	Redesign preset or explicit audit scopes	Recommended scope, confidence and site structure
Small-business maintenance	Company-size and contact filters	Company fit, reachable website and current contact route
Accessibility investigation	Accessibility threshold	The recorded finding; a separate manual accessibility review is needed

Preview the same audience you intend to export

This counts stored matching audit rows without creating lead output. Keep the filters unchanged when switching runMode to export. Count preview is not free of start/platform costs, and overlaps can make it larger than the eventual deduplicated export.

{
  "runMode": "preview",
  "opportunityPreset": "seo",
  "country": [
    "US"
  ],
  "contactRequirement": "email",
  "maxItems": 5
}

Export a small performance investigation list

Start without a country restriction if you are first checking coverage. Then add geography and a freshness window appropriate for your campaign. The score belongs to the stored audit; it does not measure the website again.

{
  "runMode": "export",
  "opportunityPreset": "performance",
  "performanceScoreMax": 60,
  "contactRequirement": "email",
  "maxItems": 5
}

Find recent redesign candidates

Requiring a recent observation can substantially reduce the audience. An empty result is an answer about matching stored coverage, not evidence that the country has no businesses needing web design services.

{
  "runMode": "export",
  "opportunityPreset": "redesign",
  "country": [
    "GB"
  ],
  "checkedWithinDays": 30,
  "contactRequirement": "email_or_phone",
  "maxItems": 5
}

Prioritize accessibility findings for manual review

Use the broad successful-audit preset with an explicit component threshold when that is the condition you intend to investigate. This avoids assuming that every low overall score represents the same type of problem.

{
  "runMode": "export",
  "opportunityPreset": "all",
  "accessibilityScoreMax": 60,
  "contactRequirement": "email",
  "maxItems": 5
}

Output fields for a useful SEO or redesign brief

Field group	Use in a review queue	Interpretation boundary
Root Domain, Company, Country	Identify and route the account	Company data may be incomplete
Emails, Telephones, LinkedIn	Choose an available contact channel	Presence is not consent or deliverability
Overall Score and component scores	Sort a limited research queue	Scores depend on the stored provider and method
Audit Checked At, Audit Age Days	Decide whether to recheck	Missing dates remain unknown
Audit Provider, Audit Confidence	Understand the observation	localfast is not Lighthouse or a Core Web Vitals measurement
Primary Opportunity, Recommended Service	Draft a review task	Heuristic suggestions, not a confirmed buying need
Opportunity Evidence, Verification URL	Reopen the relevant website	Stored summary is not fresh page-level proof

Preserve the domain, audit date and provider when copying a row into a CRM. Use your own account key to avoid duplicate outreach across repeat exports. If you need to share a sample, export only the columns relevant to the review and keep your own notes distinct from the original observations.

Recover a partial export without guessing

Read RUN_SUMMARY after every run. When some source segments are unavailable, the useful rows already delivered remain useful, but a count or ordering may be incomplete. Continuation is intentionally withheld for that case. Retry the original input when sources recover and deduplicate against the destination.

For a healthy capped run, use nextInput from EXPORT_CONTINUATION unchanged except for an intentional budget or page-size adjustment. Do not replace it with Website Leads' resumeInput: the two Actors have different continuation contracts. Save completed run and dataset IDs so a download failure can be recovered by reading the existing dataset without another paid lead export.

Frequently asked workflow questions

Can I use this to sell Core Web Vitals improvements?

Use the records to choose websites for investigation. Check the provider and conduct the measurements your proposal requires. A localfast performance score is an HTML/header heuristic, not a field or lab Core Web Vitals result.

Does a low security score prove a vulnerability?

No. Security / Best Practices findings are screening signals. A low score does not establish an exploitable vulnerability, an active compromise or a legal compliance failure. Investigate with the business's authorization.

Can I run an agency workflow through n8n or Python?

Yes. The linked maintained clients call this hosted Actor. Start with Preview, then a five-row export, and send records to a review queue before a CRM or outreach action. Public npm availability does not establish n8n Cloud support. The Actor itself neither sends proposals nor guarantees clients.

n8n and developer integrations

Use this Actor in your automation or application with the existing community integrations below. An Apify account and API token are required; Actor and platform charges follow the current pricing.

• n8n community node: n8n-nodes-apivault-website-audit-leads. Install package name n8n-nodes-apivault-website-audit-leads in a self-hosted n8n instance that permits community packages.
• Python client and examples: GitHub.
• n8n source and usage: GitHub.

These are community packages. Publication on npm does not establish n8n verification or availability in n8n Cloud. Review the linked package README for supported inputs and setup.

Export source and continuation

Fresh exports can use the warmed copies of the audited source tables. Keep the complete nextInput from EXPORT_CONTINUATION; its source session and private 24-hour checkpoint preserve progress. Old offset-only inputs use the standard index. Audit dates are the stored observation dates, not a new live audit. Warm copies are live databases, not immutable snapshots or a guarantee of immediate replication of future audit updates. parallelReaders: "7" enables bounded bulk reads; "1" retains standard concurrency.

Exported source dates

The historical First Detected, Last Found, First Indexed, and Last Indexed fields are omitted from all exported rows and CSV files, including Full output and continuation pages. Existing source-date filters and sorting still operate internally. Other observation dates, such as technology, audit and traffic checks, retain their existing behavior. Source records and stored databases are unchanged.

Legacy date column selections in saved Tasks or API inputs remain accepted for compatibility; those date values are omitted from the resulting rows.