WordPress Showcase Scraper - Website Examples

What does WordPress Showcase Scraper do?

This Actor reads the public WordPress.org Showcase archive, search results, filters, and detail pages. It returns showcased site names, canonical Showcase URLs, linked website URLs/domains, descriptions, screenshots, categories, flavors, tags, countries, authors, publication labels, and bounded public design context.

The Actor uses direct HTTPS requests to wordpress.org only. It does not use a WordPress API, log in, crawl the linked websites, download screenshots, or perform mutations. Access failures, empty scopes, malformed responses, and invalid requests are recorded as explicit diagnostics.

Why use WordPress Showcase Scraper?

Use the dataset for public website discovery, WordPress ecosystem research, design and category analysis, editorial research, portfolio benchmarking, and market intelligence. Normal rows retain public Showcase and linked-site metadata with source lineage. The Actor does not infer private contact details or make claims about ownership, technology beyond the public Showcase context, or outreach permission.

How to use WordPress Showcase Scraper

1. Choose archives to browse, search to query, or details for named Showcase slugs.
2. For search mode, provide query; for details mode, provide one or more public Showcase slugs or URLs.
3. Optionally select a category, tag, or flavor filter for archive browsing.
4. Bound the run with page and maxItems; enable includeDetails for linked website and design metadata.
5. Keep requestDelayMs at or above the default for polite serial requests and inspect the OUTPUT run summary with the dataset.

Input

mode accepts archives, search, or details. query applies to search mode. filterType and filterSlug select a public category, tag, or flavor path. page selects a bounded Showcase result page. showcaseSlugs accepts public Showcase slugs or URLs in details mode. maxItems caps records, includeDetails controls detail-page enrichment, maxContentChars bounds stored detail text, and requestDelayMs controls the minimum interval between direct source requests.

{
  "mode": "archives",
  "filterType": "category",
  "filterSlug": "creative",
  "page": 1,
  "maxItems": 10,
  "includeDetails": true,
  "maxContentChars": 30000,
  "requestDelayMs": 500
}

{
  "mode": "search",
  "query": "museum",
  "page": 1,
  "maxItems": 10,
  "includeDetails": true,
  "requestDelayMs": 500
}

{
  "mode": "details",
  "showcaseSlugs": ["physics-world"],
  "maxItems": 1,
  "includeDetails": true,
  "maxContentChars": 12000,
  "requestDelayMs": 500
}

Output

Dataset rows have recordType: "wordpress-showcase-site", stable identity, public Showcase metadata, optional linked website/detail fields, and source timestamps. Run status and detail-request outcomes are kept in the OUTPUT key-value record. Saved site rows produce status: "SUCCEEDED"; later detail or summary-write issues set dataStatus: "PARTIAL". A genuine empty search is SUCCEEDED with dataStatus: "NO_RESULTS"; a source failure before any site row is FAILED with dataStatus: "FAILED" and no diagnostic dataset row.

{
  "recordId": "wordpress_showcase_site_physics-world",
  "recordType": "wordpress-showcase-site",
  "source": "wordpress_showcase_public_html",
  "provenance": "wordpress_org_showcase_html",
  "showcaseSlug": "physics-world",
  "showcaseName": "Physics World",
  "showcaseUrl": "https://wordpress.org/showcase/physics-world/",
  "websiteUrl": "https://physicsworld.com/",
  "websiteDomain": "physicsworld.com",
  "category": "Publication",
  "country": "United Kingdom",
  "scrapedAt": "2026-09-08T00:00:00.000Z"
}

You can download the dataset in various formats such as JSON, HTML, CSV, or Excel.

Data table

Field	Description
recordId, recordType	Stable site identity and row type.
showcaseSlug, showcaseName, showcaseUrl	Public WordPress Showcase identity and canonical detail page.
websiteUrl, websiteDomain	Public linked website and normalized hostname when supplied by the Showcase page.
showcaseDescription, showcaseAuthor, country, published	Public detail-page descriptive and publication metadata.
category, flavor, siteTags	Public detail-page taxonomy labels.
cardCategories, cardTags, cardFlavor, cardText	Public archive-card metadata and normalized card text.
screenshotUrl, detailImageUrls	Public image URLs exposed by WordPress.org; images are not downloaded.
detailText	Bounded public detail context.
source, provenance, sourceUrl, scrapedAt	Extraction lineage and retrieval timestamp.

The OUTPUT key-value record contains serialized JSON with scope, filters, request counts, stored-record counts, detail failures, diagnostics, final status, and generated-by metadata.

Pricing / Cost estimation

Archive and search modes use one bounded listing request. Details mode uses one direct request per selected slug, and includeDetails can add one detail request per discovered card. maxItems, response-size limits, content limits, request delays, and timeouts keep resource use predictable. Your Apify plan determines the final platform cost.

Tips or advanced options

Use details mode for repeatable monitoring of known Showcase slugs. Use search mode for a focused public phrase such as museum. Keep includeDetails disabled when card metadata is enough and speed matters. Keep the default request delay for larger runs. Showcase categories, labels, descriptions, linked sites, and screenshots are source snapshots and can change between runs.

FAQ, disclaimers, and support

Only public WordPress.org Showcase HTML is in scope. The Actor does not crawl or evaluate linked websites, collect private contact information, or verify ownership. You are responsible for lawful use, terms compliance, robots guidance, and appropriate request rates. If the public page shape changes, the Actor emits a diagnostic rather than fabricating values. Use the Issues tab for feedback.

Local verification

npm ci
npm test
npm run lint
apify validate-schema
apify run --purge --input-file test/inputs/default.json
npm run validate