WooCommerce Store Analyzer

Turn public store homepages into product and technology audit reports. Compare prices, stock coverage, categories, visible plugins, tracking signatures and contact links in one export. Each useful, verified WooCommerce store produces one dataset row.

Useful for ecommerce agencies, integration research and comparing publicly visible store catalogues. No store login or own third-party API key is required.

Start in a minute

1. Enter the store homepage in Store homepages. A bare domain also works; duplicate URLs are removed.
2. Choose Maximum products sampled per store. Start with 25–50.
3. Run the actor. Open Store reports, then check Collection summary & coverage for partial results.

{
  "storeUrls": ["https://woocommerce.com"],
  "productSampleSize": 25,
  "extractProducts": true,
  "extractCategories": true,
  "extractTechStack": true
}

The example is a live public source, not a static demo. Its catalogue and access permissions can change. Use a store homepage, including its WordPress installation subdirectory where applicable. Product links, private network addresses and URLs containing credentials or query strings are rejected before collection.

Understand your report

Field	Meaning
woocommerce_evidence	Public product collection, WooCommerce assets or registered store namespace observed
product_count_sampled	Unique products actually collected
catalogue_coverage.sourceTotal	Count reported by the source, when available
catalogue_coverage.catalogueComplete	Whether this collection reached the observed end of the catalogue
currency, price_min, price_median, price_max	Sample prices, converted using each product's published currency minor units
price_groups	Separate currency groups; mixed currencies are never merged into one median
in_stock_count, out_of_stock_count, unknown_stock_count	Published stock states; missing stock is not counted as out of stock
new_products_7d/30d/90d	Counts among products with known published creation dates; null if none are known
tech_stack, tech_evidence	Visible technology signatures with evidence scope
plugins_detected	Plugin slugs appearing in fetched public assets
source_layers	Availability of each requested section
status	OK or PARTIAL; useful partial reports retain their available evidence

A successful run does not guarantee a full catalogue. The default is 50 products, with up to 2,000 products and 40 product pages per store. The sampling limit, source total, pages fetched and end status are always separate. Source changes or repeated products stop pagination and mark the sample partial.

SUMMARY contains delivered report counts, duplicate removal, requests and store coverage. ERRORS explains invalid inputs, failed stores and unavailable optional sources. These diagnostic records are not paid store results. Export the dataset as JSON, CSV or Excel using the Apify Console.

Optional sections

Expand Optional enrichment only when needed:

• Public REST namespaces, up to 100 categories and catalogue aggregates when exposed.
• Public author profiles, latest 20 blog posts and site-published Schema.org claims.
• Up to 13 sitemap files, declared crawler rules and observed homepage security headers.
• Public DNS/provider hints, archive and certificate observations.
• Third-party traffic estimates and an explicit hypothetical revenue scenario.

These sources may be missing or blocked. Author profiles do not prove administrator roles. Asset paths and namespaces cannot enumerate every installed plugin. Sitemap classification is a URL-path heuristic. Structured data is a claim published by the site; it is not independently verified.

Archive observations do not prove a brand's founding date. Missing headers do not establish a vulnerability. Creation dates absent from public product records remain unknown; modified dates are never used as new-product dates.

For a hypothetical revenue scenario, enable products, traffic and extractRevenueEstimate. The formula is estimated monthly visits × your conversion assumption × an assumed order value of sample median price × 1.5. The result uses the product currency and is explicitly labelled HYPOTHETICAL. Actual order value, sales, revenue, best sellers and dropshipping status cannot be established from these public observations. The legacy avg_order_value, likely_best_sellers, estimated brand age and founding-year fields are unverified and remain null. most_illustrated_products reports image counts without a sales claim.

The optional lead_score measures availability of public contact, technology and product evidence, with the point breakdown included. It is not a commercial quality score.

API and MCP

Use the input above as the JSON body of the actor's Run API. Keep your Apify token in your own secret/environment configuration. Poll the returned run ID, read the default dataset, and inspect SUMMARY and ERRORS in the run's default key-value store. Use a small maxTotalChargeUsd for the first run.

For an MCP client, connect to:

https://mcp.apify.com/?tools=apivault_labs/woocommerce-store-analyzer

Authenticate with your own Apify account. Ask the client to list tools, then call apivault_labs--woocommerce-store-analyzer with the same input and waitSecs: 45. If the response is still running, wait for the returned run ID. Read store rows with get-dataset-items, and read SUMMARY / ERRORS with get-key-value-store-record.

Example instruction: “Analyze https://woocommerce.com using at most 25 products. Return its currency, median price, product coverage and visible technology evidence. Report unavailable sections separately; do not infer actual sales.”

Cost and limits

$0.01 per useful store report ($10 per 1,000), plus $0.00005 per actor start at the minimum 1 GB start event. A 256 MB run uses one start event. The Console's current pricing panel is authoritative; resource billing can depend on the applicable pricing record.

Empty, non-WooCommerce and unreachable inputs produce no paid store rows. A verified store with unavailable optional sections may produce a paid PARTIAL report. Your maximum charge limit can reduce delivery; inspect SUMMARY before assuming every input store was returned. Start fees can still apply to runs with no reports.

Requests and redirects validate public destinations. Collection is bounded by per-request, per-store and run time limits. Collection stops on denied access, rate limits or challenges; access is not guaranteed for every store. There is no login, session rotation or challenge bypass. No cross-run history is accumulated.

Version 1.1 migration

extractBlog and extractSchemaOrg now control their actual sections. Old API aliases extractPosts and extractJsonLd override the default false flags; conflicting nondefault canonical flags are rejected. Prefer the current field names. productSampleSize: 0 is invalid: choose an explicit positive limit. Optional external enrichment defaults to off. Replace image-count “best sellers” with most_illustrated_products and inspect price_groups for mixed currencies.

Questions or reproducible failures: use the actor's Issues tab with the public store URL and run ID. Never post account tokens.