WooCommerce Marketplace Extensions Scraper

Scrape public WooCommerce.com Marketplace extension listings into a clean Apify dataset.

The actor uses WooCommerce's public WordPress REST API, so it is fast, HTTP-first, and does not need browser automation or a WooCommerce account.

What does WooCommerce Marketplace Extensions Scraper do?

WooCommerce Marketplace Extensions Scraper collects public extension catalog records from woocommerce.com.

It extracts names, product URLs, prices, availability, categories, SEO copy, images, author/vendor metadata, and publish/update dates.

Use it to monitor the WooCommerce extension ecosystem, benchmark competitors, or build an internal catalog of marketplace products.

Who is it for?

• 🧩 WooCommerce plugin vendors tracking competing extensions.
• 🛒 Ecommerce agencies comparing extension options for client stores.
• 📊 Marketplace analysts monitoring category growth and update cadence.
• 🔎 SEO teams studying how WooCommerce extensions position their product pages.
• 🧑‍💻 Developers building dashboards from WooCommerce.com catalog data.

Why use this actor?

The WooCommerce Marketplace changes frequently.

Manual checks are slow when you need hundreds or thousands of extension records.

This actor gives you repeatable output that can be exported as JSON, CSV, Excel, or sent into your own tools through the Apify API.

Data sources

The default source is the public WooCommerce Extensions category.

https://woocommerce.com/product-category/woocommerce-extensions/

The actor reads the public WordPress REST product endpoint behind that marketplace.

https://woocommerce.com/wp-json/wp/v2/product?product_cat=1021

Output data

Each dataset row represents one WooCommerce Marketplace extension product.

Field	Description
productId	WordPress/WooCommerce product ID.
title	Extension name.
slug	Marketplace slug.
url	Public product detail URL.
excerpt	Short marketplace description.
descriptionText	Optional cleaned long product description.
priceText	Visible price text when exposed by the page metadata.
availability	Availability text such as In stock.
categories	Human-readable marketplace categories.
categoryIds	Raw WooCommerce category IDs.
tags	Raw product tags when exposed.
imageUrl	Product/SEO image URL.
seoTitle	SEO title from WooCommerce metadata.
seoDescription	SEO description from WooCommerce metadata.
authorName	Author or vendor metadata where exposed.
datePublished	Product publish date.
dateModified	Last modified date.
sourceApiUrl	API page that produced the record.
scrapedAt	UTC scrape timestamp.

Example output

{
  "productId": 27147,
  "title": "WooCommerce Subscriptions",
  "slug": "woocommerce-subscriptions",
  "url": "https://woocommerce.com/products/woocommerce-subscriptions/",
  "priceText": "$279",
  "availability": "In stock",
  "categories": ["Developed by Woo", "Subscriptions", "WooCommerce extensions"],
  "authorName": "Magnus Jepson",
  "dateModified": "2026-07-10T04:56:39",
  "scrapedAt": "2026-07-10T03:07:24.581Z"
}

How much does it cost to scrape WooCommerce Marketplace extensions?

This actor uses pay-per-event pricing.

There is a small start charge for each run and a per-extension charge for every dataset item saved.

The exact live prices are shown on the Apify Store pricing panel.

You can control spend with maxItems.

For example, set maxItems to 100 for a quick market sample or increase it for a broader catalog export.

Quick start

1. Open the actor on Apify.
2. Keep the default WooCommerce Extensions category.
3. Set maxItems to the number of extension records you need.
4. Optionally add a keyword such as subscriptions, shipping, or analytics.
5. Run the actor.
6. Export the dataset as JSON, CSV, Excel, or via API.

Input reference

Start URLs

Use product URLs, category URLs, or WooCommerce WP REST product API URLs.

If you leave this field empty, the actor scrapes the default public WooCommerce Extensions category.

WooCommerce category IDs

The default category ID is 1021, which represents the public WooCommerce Extensions marketplace category.

Advanced users can add other WooCommerce.com product category IDs.

Search query

Use a keyword to filter the marketplace API.

Examples:

• subscriptions
• shipping
• bookings
• analytics
• checkout

Maximum extensions

maxItems caps the number of records saved.

Keep it small for test runs and increase it for production exports.

Include long descriptions

Enable includeDescription when you need cleaned product-page body text for copy analysis, AI classification, or content comparison.

Disable it for compact monitoring datasets.

Example inputs

Scrape a marketplace sample

{
  "maxItems": 100,
  "categoryIds": [1021]
}

Search shipping extensions

{
  "search": "shipping",
  "maxItems": 50,
  "categoryIds": [1021]
}

Scrape one product URL

{
  "startUrls": [
    { "url": "https://woocommerce.com/products/woocommerce-subscriptions/" }
  ],
  "maxItems": 1
}

Use cases

Competitor monitoring

Track new extensions, changed prices, and recently updated product pages.

Category intelligence

Compare how many extensions appear in WooCommerce categories such as subscriptions, shipping, merchandising, or checkout.

SEO analysis

Export SEO titles and descriptions to understand how marketplace vendors position their plugins.

Vendor research

Use author/vendor metadata where exposed to build shortlists for partnerships, acquisitions, or competitive research.

Product catalog enrichment

Join WooCommerce Marketplace data with your own CRM, BI, or internal product taxonomy.

Tips for better results

• Start with maxItems: 100 to confirm the fields you need.
• Use orderBy: modified to monitor recently changed products.
• Use orderBy: date to discover newly published products.
• Use includeDescription: true only when you need long text.
• Keep exact product URLs in startUrls for targeted lookups.

Integrations

You can connect the dataset to:

• Google Sheets for lightweight tracking.
• Airtable for plugin research boards.
• BigQuery or Snowflake for marketplace analytics.
• Slack alerts for new or modified extensions.
• CRM tools for vendor and partner research.

API usage

Node.js

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('automation-lab/woocommerce-marketplace-extensions-scraper').call({
  maxItems: 100,
  categoryIds: [1021]
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items[0]);

Python

from apify_client import ApifyClient

client = ApifyClient('YOUR_APIFY_TOKEN')
run = client.actor('automation-lab/woocommerce-marketplace-extensions-scraper').call(run_input={
    'maxItems': 100,
    'categoryIds': [1021],
})
items = client.dataset(run['defaultDatasetId']).list_items().items
print(items[0])

cURL

curl -X POST "https://api.apify.com/v2/acts/automation-lab~woocommerce-marketplace-extensions-scraper/runs?token=$APIFY_TOKEN" \
  -H 'Content-Type: application/json' \
  -d '{"maxItems":100,"categoryIds":[1021]}'

MCP access

Use this actor from MCP-compatible tools through Apify MCP.

MCP URL:

https://mcp.apify.com/?tools=automation-lab/woocommerce-marketplace-extensions-scraper

Add the actor to Claude Code:

$claude mcp add apify-woocommerce-extensions https://mcp.apify.com/?tools=automation-lab/woocommerce-marketplace-extensions-scraper

Claude Desktop JSON configuration:

{
  "mcpServers": {
    "apify-woocommerce-extensions": {
      "url": "https://mcp.apify.com/?tools=automation-lab/woocommerce-marketplace-extensions-scraper"
    }
  }
}

Example prompts:

• "Use the WooCommerce Marketplace Extensions Scraper to scrape 100 extensions and summarize pricing patterns."
• "Use Apify MCP to find recently updated WooCommerce shipping extensions."
• "Run the WooCommerce extension scraper and compare SEO descriptions for subscription-related extensions."

Data freshness

The actor reads live public WooCommerce.com REST responses at run time.

Dates and prices reflect what WooCommerce exposes during the run.

Limitations

• The actor only collects public marketplace data.
• It does not log in or access customer-only vendor dashboards.
• Some vendor or rating fields may not be exposed in the public REST response.
• Long descriptions can be large; enable them only when needed.

Troubleshooting

Why did I get fewer items than expected?

Your search query or category filter may match fewer products than maxItems.

Try removing search or using the default category ID 1021.

Why is priceText empty for some rows?

Price text is collected from public metadata. If WooCommerce does not expose it for a product, the field is null.

Why are descriptions missing?

Set includeDescription to true if you need long product content.

Legality

This actor collects publicly available information from WooCommerce.com.

You should use the data responsibly, respect applicable laws, and follow WooCommerce.com's terms and policies.

Do not use the output for spam, harassment, or unauthorized access.

Related scrapers

Explore related automation-lab actors for marketplace and ecommerce intelligence:

• https://apify.com/automation-lab/shopify-store-leads-scraper
• https://apify.com/automation-lab/shopify-store-analyzer
• https://apify.com/automation-lab/bigcommerce-app-marketplace-scraper
• https://apify.com/automation-lab/github-marketplace-scraper
• https://apify.com/automation-lab/salesforce-appexchange-scraper

FAQ

Can I scrape the whole WooCommerce Extensions marketplace?

Yes. Leave categoryIds as [1021] and increase maxItems up to the catalog size you need.

Can I monitor only recently updated extensions?

Yes. Use orderBy: "modified" and run the actor on a schedule.

Does the actor need WooCommerce login credentials?

No. It uses public WooCommerce.com marketplace data only.

Support

If you need a field that is visible on WooCommerce.com but missing from the output, open an Apify issue with an example product URL.

Changelog

See .actor/CHANGELOG.md for release notes.