WooCommerce Analyzer — No Login, Emails, Phones & Plugins

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 active record checked on 20 October 2026 charges platform usage separately to the user. The Console's current pricing panel is authoritative.

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.

WooCommerce research for agencies and ecommerce teams

Use the WooCommerce analyzer when your input is a known public store and your question concerns its observed catalogue, contacts or visible technology. The Actor builds a structured report from accessible evidence, then exposes sampling and source limits alongside the result.

Workflow	Useful sections	What to verify before acting
Catalogue pricing research	Products, currency groups and price statistics	Sample size, currency and catalogue completeness
Plugin or integration research	Visible plugins and tech evidence	Public asset signatures do not enumerate every installation
Agency account qualification	Contacts, socials and source layers	Published routes may be general inboxes or stale links
Category and stock review	Observed categories and stock counts	Unknown stock is separate from sold out
Optional website inventory	Sitemaps, public metadata and headers	These are observations, not a security or compliance certification

Sample ten public products with their price context

Start with one store and a small sample. The report can contain fewer than ten products because the catalogue is smaller, access is limited or the request budget stops collection. Inspect coverage before extrapolating.

{
  "storeUrls": [
    "https://woocommerce.com"
  ],
  "maxStores": 1,
  "productSampleSize": 10,
  "pageSize": 10,
  "extractProducts": true,
  "extractCategories": true,
  "extractTechStack": true
}

Focus on observed contacts and technologies

Disable product collection when the current question only concerns public website signals. Keep at least one supported data section enabled. This configuration does not establish complete plugin coverage or access to private WooCommerce administration data.

{
  "storeUrls": [
    "https://woocommerce.com"
  ],
  "maxStores": 1,
  "productSampleSize": 10,
  "extractProducts": false,
  "extractTechStack": true,
  "extractPlugins": true,
  "extractContact": true,
  "extractSocials": true,
  "extractTraffic": false,
  "extractRevenueEstimate": false
}

Inspect public WordPress metadata and blog observations

Optional sections may be absent or unavailable independently of the catalogue. A site-published organization claim is not independent verification, and a public author profile is not proof of an admin role.

{
  "storeUrls": [
    "https://woocommerce.com"
  ],
  "maxStores": 1,
  "productSampleSize": 5,
  "extractWpNamespaces": true,
  "extractSchemaOrg": true,
  "extractBlog": true,
  "extractTraffic": false,
  "extractRevenueEstimate": false
}

Keep a catalogue-first comparison bounded

Use the same sample settings when preparing reports for several stores, then compare currency groups and coverage rather than assuming every sample represents the full catalogue. The single store here keeps the first validation small; expand storeUrls only after reviewing the result.

{
  "storeUrls": [
    "https://woocommerce.com"
  ],
  "maxStores": 1,
  "productSampleSize": 25,
  "pageSize": 10,
  "extractProducts": true,
  "extractCategories": true,
  "extractTraffic": false,
  "extractRevenueEstimate": false,
  "storeTimeoutSecs": 60
}

Understand prices, stock and catalogue coverage

The report separates the number sampled, any source-reported total and whether collection reached the observed end. A full-looking table is not proof that a large store's entire catalogue was collected. Products can repeat, disappear or change while pages are being requested.

Price statistics use published currency minor units. Compare like currencies and inspect price_groups when more than one currency is present. A sample median is not an actual order value. Public stock states do not reveal inventory counts, purchase rates or supplier availability beyond the returned observations.

Creation dates are only counted when published. A modified date is not a new-product launch. Likewise, product image counts can describe visual content but do not identify actual best sellers. Keep those limits in research reports sent to clients or colleagues.

Read plugin and contact evidence as observations

An asset path can reveal a visible plugin slug; a private, removed or server-side plugin may leave no public signal in the inspected pages. Absence from plugins_detected is therefore not proof of absence. Public namespaces and technology signatures are useful integration research, not a complete WordPress administration inventory.

Contact fields contain public routes observed by the collector. They are not a mailbox-deliverability test or a verified decision-maker directory. Open source URLs to confirm account identity and review the service you intend to propose. The optional lead score prioritizes available evidence, not the store's commercial value or readiness to buy.

Price a WooCommerce store report

The active configuration checked on 20 October 2026 is $0.01 per useful delivered store report, $0.00005 per Actor Start memory unit (minimum one unit), and separate user-paid platform usage. At standard memory, one useful report has $0.01005 in event fees; five have $0.05005. These calculations exclude resources and do not guarantee successful access.

A report is the billing unit, not each sampled product or detected plugin. Changing the sample size can increase collection work and resource costs without changing that result-event unit. A useful partial report can be billed when optional sections are unavailable. Failed or non-store inputs produce no paid store result, though a start event and platform costs can still occur.

Export and recover an agency research file

JSON retains nested catalogue and source evidence. CSV/Excel are useful for domain-level comparisons; decide deliberately how to flatten nested arrays instead of assuming they are already one row per product. Keep the original run, dataset and report URLs for reproducibility.

Re-download a completed dataset after a transfer failure rather than starting the same analysis again. New runs are independent and can observe different catalogues; no cross-run change-history database is included. For a repeat comparison, preserve the old report yourself and keep sample settings and interpretation rules consistent.

Frequently asked questions

Is this a WooCommerce sales or revenue API?

It analyzes public observations. It does not expose orders, customers, actual revenue or product sales. Optional revenue output is an explicitly hypothetical scenario with assumptions, not an estimate validated against the store's accounts.

Can I discover every store using WooCommerce?

This Actor takes known store homepages. It does not provide a search index of every WooCommerce business. Use an appropriate website lead-discovery workflow first, then analyze the selected public stores.

Can I use it without a store's API credentials?

The supported workflow uses accessible public store data. It requires no WordPress admin login or store secret key. Hosted API/MCP access still requires Apify authentication and applicable run charges.

Why is a successful report marked PARTIAL?

One or more requested sections can be unavailable while other evidence remains useful. Inspect source_layers, catalogue_coverage and ERRORS. Do not replace a missing optional section with an assumed zero.

n8n and developer integrations

Use this Actor in your automation or application with the existing community integrations below. An Apify account and API token are required; Actor and platform charges follow the current pricing.

• n8n community node: n8n-nodes-apivault-woocommerce-analyzer. Install package name n8n-nodes-apivault-woocommerce-analyzer in a self-hosted n8n instance that permits community packages.
• Python client and examples: GitHub.
• n8n source and usage: GitHub.

These are community packages. Publication on npm does not establish n8n verification or availability in n8n Cloud. Review the linked package README for supported inputs and setup.