GoodFirms Agency Directory Scraper — Rating, Rate & Employees

GoodFirms Agency Directory Scraper — B2B Agency & Service-Provider Leads

Search the GoodFirms B2B agency directory (goodfirms.co) by category — SEO agencies, e-commerce development companies, cloud computing companies, and 100+ other real GoodFirms categories — and get back full agency profiles: rating, review count, hourly rate range, employee headcount, location, and (optionally) contact email/phone/street address and services offered. Built for finding vetted service providers without a rental subscription wall or manual click-through.

What it does

This actor scrapes a GoodFirms category-listing page (e.g. /seo-agencies), which is the full paginated directory for that category (not the curated "Leaders Matrix" summary page), and for each agency card optionally visits its own GoodFirms profile page to enrich the record with contact details and a services list. No login, no API key, no rental subscription.

Use cases

• Building a shortlist of agencies in a given category, filterable by rating/hourly rate/employee count.
• Prospecting service-provider leads (SEO, e-commerce dev, cloud, DevOps, advertising, etc.) for partnership or outreach.
• Competitive/market mapping of an agency category (who's rated highest, typical rate bands).
• An in-house, frictionless alternative to rental-walled competitor directories that require a paid monthly subscription just to see the list.

Input

• categories — one or more GoodFirms category URL slugs, exactly as they appear at goodfirms.co/<slug> (e.g. seo-agencies, ecommerce-development-companies, cloud-computing-companies, devops-companies, advertising-companies). This is not a free-text keyword search — the slug must be a real category URL segment. Browse goodfirms.co and copy the last path segment of a category page's URL to find a valid one (some natural-sounding guesses, e.g. web-design-companies, do not exist as slugs).
• maxItems — max agency records returned per category.
• maxPages — max listing pages fetched per category (~48 agencies/page).
• fetchDetails — if true (recommended, default), visits each agency's own GoodFirms profile page for bonus fields: email, phone, full street address, and services offered. The core fields (name, website, rating, review count, hourly rate, employees, location) are already complete from the category listing alone — turning this off only drops the bonus fields, never a whole record, and makes the run faster.
• proxyConfiguration — Apify RESIDENTIAL (prefilled, recommended for reliable access).

Fields returned

companyName, website, rating, reviewCount, hourlyRate, employees, location, city, country, streetAddress, foundedYear, shortDescription, phone, email, services, profileUrl, category, detailFetched, scrapedAt.

Field fill-rate — verified on a live cloud run (2026-07-20)

Every field listed above filled at 100% on a real Apify cloud run (8 records, category seo-agencies, fetchDetails: true), including all bonus detail-page fields (streetAddress, foundedYear, phone, email, services). This matches or exceeds the champion comparable's declared field set (companyName/website/rating/reviewCount/hourlyRate/employees/location, all 5/5 100% per the tasted reference actor). On broader samples, expect rating/reviewCount/ location to occasionally run slightly under 100% (a small share of listed agencies carry no reviews yet, or omit a headline location) — this is genuine source-data sparsity on GoodFirms' side, not a parser gap; every other listing-page field (name, website, hourly rate, employees) is structurally always present on the card markup.

No personal data (PII)

This actor collects business/company-level data only — agency names, business emails, business phone numbers, business addresses, and aggregate review stats. It does not collect any individual person's name, personal email, personal phone number, or other personal identifier. There is no owner/contact-person field anywhere in the schema.

Input Example

{
  "categories": ["seo-agencies", "ecommerce-development-companies"],
  "maxItems": 20,
  "maxPages": 3,
  "fetchDetails": true,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": ["RESIDENTIAL"]
  }
}

Output

One dataset item per agency. Export to JSON/CSV/Excel or pull via the Apify API/MCP. Charged per delivered agency-record — no monthly rental subscription like the category's walled competitor directories.

🤖 Use with AI agents (MCP)

This actor is agent-ready. Point any MCP client (Claude Desktop, Cursor, n8n AI, LangGraph) at it:

{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com/?actors=bovi/goodfirms-agency-directory",
      "headers": { "Authorization": "Bearer <YOUR_APIFY_TOKEN>" }
    }
  }
}

Usage statistics

This Actor creates a small, content-free summary at the end of each run. It is used only to monitor reliability and improve this Actor. A copy is saved as USAGE_STATS in your own Apify key-value store, so you can see the exact record created for your run.

Set disableUsageStats to true in the input to opt out. Nothing is sent then; your USAGE_STATS record only says that statistics were disabled.

Only these fields are recorded:

• schema version, Actor name and build number;
• UTC start and finish hour (not a precise timestamp);
• run duration, number of results and time to the first result, each as a coarse range;
• whether the result was empty, the end status, and an error type from a fixed list;
• memory setting and counts of charged events;
• names of the input fields you set, never their values;
• the selected option for input fields that offer a fixed list of choices (for example a sort order).

We do not collect input text, search terms, URLs, domains, usernames, email addresses, names, proxy credentials, tokens, scraped records, output items, raw error messages, stack traces, or hashes of any of those values. Records are kept for no longer than 13 months, used only as aggregated operational statistics, and never sold or shared.

Additional fields (Phase 2)

This Actor also records your Apify user ID, whether Apify marks the account as paying, the size range of list inputs, the selected country when the input offers a fixed list of countries, and one category from a fixed Actor taxonomy. We use these fields only for aggregate reliability, repeat-use and cross-Actor analysis; reports suppress any cell with fewer than five distinct users.

The same disableUsageStats: true input flag turns these fields off too. The user ID is removed after 13 months; we do not export, sell, share, or attempt to re-identify this data.

Run-outcome signals (v2)

To learn whether a run did what it was asked to do, the record also holds a few more coarse ranges and yes/no flags. None of them contains content:

• the result limit you asked for (a range, when the input has one) and what share of it was delivered;
• results delivered per input item you listed (a range);
• output quality as ranges: how fully the result fields were filled, the share of rows that look like errors, the share of duplicate rows, and how many different fields appeared. These are counted in memory while results are saved; no result content is kept;
• how the run was started (console, API, schedule, webhook, another Actor);
• how it ended: stopped by you, timed out, reached the requested limit, stopped by the charge limit, and how many times the platform moved the run;
• if this Actor reports it: how many items to process worked or failed (ranges) and one failure reason from a fixed list;
• a short code made from the names of the input fields you set, never their values.

Repeat-run fingerprint (v2)

When your Apify user ID is recorded (see above), the record also holds an 8-character one-way code made from your input (proxy settings left out) and this Actor's name. It only lets us see that the same account ran the same input again soon after an unsatisfying run; we never see the input itself. It is stored only in the database, never published, and reports use it in aggregate with the same five-user minimum. It is the one exception to the statement above that no hashes are collected, and disableUsageStats: true turns it off.