Cost to scrape Generic WordPress or static site at 10K, 100K, and 1M

Access fact, checked 2026-07-26: There is no single terms document for independent WordPress and static sites; the dataset records each operator’s terms and machine-readable crawling instructions as unverified until the site is named.

Cost to scrape Generic WordPress or static site at 10K, 100K, and 1M table

The comparison uses 10,000, 100,000, and 1,000,000 billable target calls or delivered results per month, calculated on 2026-07-26. It does not claim those calls all become useful rows. Credit, request, result, and search meters are passed through the dataset quote model, which selects the least expensive published self-service offer that covers each volume. A starting USD rate is shown as a lower bound because an unpublished minimum, tier, or contract can raise the invoice. Retries, pagination, duplicate outputs, taxes, and data licensing are outside these figures.

The published price answer

The record contains 10 published target-rate lines across 10 vendors. Those are the only rows allowed to produce a target-specific dollar result. Different light, normal, HTML, rendered, protected, or dedicated modes stay separate because collapsing them would hide the unit change that drives the bill. A plan name in a cell is the offer selected from that vendor record, not a recommendation.

A normal request with no premium features costs 1 credit. docs.scraperapi.com. Classic HTML requests without JavaScript cost 1 credit. help.scrapingbee.com. A normal datacenter request to an untargeted domain costs 1 credit. scrape.do. Basic public pages are the 1x pricing baseline. docs.zenrows.com. A basic datacenter request costs 1 credit. scrapfly.io. Zyte publishes an HTTP request price starting at $0.00013. zyte.com. Bright Data publishes Web Unlocker pricing starting at $0.0015 per request. brightdata.com. Oxylabs publishes a Web Scraper API price starting at $0.00115 per result for other websites. oxylabs.io. A Web Scraping API request consumes one result from the plan. help.decodo.com. A standard Crawling API request consumes one request. crawlbase.com.

A basic HTTP path may be enough

This record classifies Generic WordPress or static site as easy and records no material protection observed in the reviewed record. JavaScript rendering is not required in the recorded profile, so the table does not add a rendering multiplier unless a published target mode already includes one. Residential routing is not recorded as necessary, which keeps an unsupported premium-proxy assumption out of the calculation.

The requested fields, authentication state, response format, and rendering path must be fixed before a published unit rate becomes a usable estimate.

The official route is a separate product decision

WordPress REST API, when the target runs WordPress is recorded as available. Public WordPress content may be readable without authentication; writes and private content require site-issued credentials. Static sites have no universal API. No separate WordPress REST API fee; the site owner controls hosting and access. The reviewed record does not establish field-for-field equivalence with the rendered site, so required entities and fields must be checked before treating it as a substitute. Source and access status checked 2026-07-26.

What the dataset does not establish

No dedicated vendor endpoint or template is recorded for Generic WordPress or static site. That does not prove generic scraping products cannot reach it. It means the current evidence cannot support a target-specific support or cost claim. A buyer should require a sample response schema and a written meter before projecting volume from a generic pricing page.

What volume means for a static site

One useful unit is one document or content record at a stated refresh date. A whole-site job normally discovers URLs through a sitemap, archive, or content API, then fetches each selected document; archive pagination and document retrieval are separate work unless the archive already contains every required field (WordPress REST API, retrieved 2026-07-27).

There is no universal pagination shape for static sites. For WordPress sites that expose the REST API, collection endpoints use page and per_page, allow up to 100 records per request, and return X-WP-Total and X-WP-TotalPages headers. Other generators and custom sites require their own sitemap or archive audit (WordPress REST API pagination, retrieved 2026-07-27).

The vendors in this record provide generic request products rather than a dedicated “static site” endpoint. A site’s own content API can answer the same document question when it exposes all required public fields, but it will not reproduce theme markup and may omit custom fields or non-content pages (WordPress REST API, retrieved 2026-07-27).

Evidence to check before buying

• ScraperAPI, ScrapingBee, and Scrape.do each publish a 1-credit baseline for ordinary HTML requests scrape.do.
• ZenRows defines basic public pages such as articles, product listings, and blogs as its 1x pricing baseline docs.zenrows.com.
• Scrapfly, Decodo, and Crawlbase each publish a one-unit basic request path scrapfly.io.
• WordPress exposes a first-party REST API when enabled by the site developer.wordpress.org.
• Confirm the exact entity and output unit, whether a page, search, result, record, or API object. Then multiply by pagination and refresh frequency before selecting a plan.