Why a WooCommerce Store Is Not Detected by a Product Scraper
A WooCommerce product scraper may fail to detect a store when the website does not expose compatible public WooCommerce Store API endpoints, when the active page is not a standard HTTP or HTTPS storefront page, or when the store's security, caching or custom configuration changes the public response. A WordPress website is not automatically a compatible WooCommerce storefront.
Use the troubleshooting checks below only for stores you own, manage or have permission to review. Do not attempt to bypass access controls, rate limits, login requirements or website restrictions.
WordPress and WooCommerce are not the same thing
WordPress is a content-management system. WooCommerce is an ecommerce platform for WordPress. A website may use WordPress without using WooCommerce. It may also use WooCommerce while customizing or restricting the public catalog endpoints that a browser-based exporter expects.
A WooCommerce product scraper needs a compatible public data source. The WooCommerce Store API provides public REST API endpoints for customer-facing product functionality. The Products endpoint provides public product data so it can be rendered on the client side.
The public Store API endpoint to check
For a store that you own or have permission to test, open this URL pattern in a browser:
https://example-store.com/wp-json/wc/store/v1/productsReplace example-store.com with the permitted store domain.
A compatible store may return structured product data. WooCommerce developer documentation explains that only published products are accessible through the Store API. Draft, pending or other non-published products are excluded from the public collection endpoint.
Common reasons a WooCommerce store is not detected
1. The site uses WordPress but not WooCommerce
A WordPress theme, blog or landing page does not prove that the site uses WooCommerce. Check whether the site has public product catalog pages and compatible Store API responses.
2. The WooCommerce Store API is unavailable or customized
The store may disable, restrict or customize the public endpoint. A browser extension should respect that configuration rather than trying to bypass it.
3. The active tab is not a normal storefront page
Open the store homepage, shop page or a public product page using an http:// or https:// URL. Browser-internal pages, local files and extension-management pages are not storefront tabs.
4. Only non-published products exist
The Store API exposes published products. Draft, pending or private catalog records may not appear in a public export.
5. A security layer blocks or alters the public response
Security plugins, firewalls, content-delivery networks and server rules can affect API responses. When you own the store, review the configuration with your hosting or development team. Do not disable security controls on a third-party website.
6. A maintenance page or consent screen replaces the storefront
The browser may be showing a temporary maintenance page, geographic notice or consent interstitial rather than the catalog. Resolve the storefront access issue before exporting.
7. The store uses a custom commerce implementation
Some websites combine WordPress with custom product systems, headless frontends or third-party ecommerce platforms. A WooCommerce-specific extension may not support those implementations.
Store-detection troubleshooting checklist
- Confirm that you are on a public
http://orhttps://storefront URL. - Confirm that the website uses WooCommerce rather than WordPress alone.
- For a permitted store, test the public Products endpoint in the browser.
- Confirm that public product records are published.
- Reload the storefront tab and reopen the extension.
- Check whether a consent screen, maintenance page or login wall is replacing the catalog.
- When you manage the store, review security-plugin, firewall and caching rules with the site administrator.
- Respect website restrictions. Do not attempt to evade access controls or rate limits.
Why variation rows may still be incomplete after detection
Store detection confirms that a compatible public WooCommerce catalog is available. It does not guarantee that every product option is published as a native child variation. WooCommerce developer documentation states that variations are excluded from the default product collection and must be requested explicitly as variations. Third-party add-ons and custom configurator fields may also remain outside the native child-variation model.
Read Native WooCommerce Variations vs Product Add-ons: Why Some Options Are Missing when a product is detected but some selectable options do not appear as variation rows.
WooCommerce scraper not detecting store: diagnostic table
Use this diagnostic table when a WooCommerce scraper is not detecting store data on a website that you own, manage or have permission to test.
| Observation | Likely explanation | Safe next step |
|---|---|---|
| The endpoint returns structured published products | The public Store API is available | Reload the storefront page and reopen the extension. |
| The endpoint returns a 404 response | The endpoint may be disabled, customized or unavailable | When you manage the site, review WooCommerce and server configuration with the administrator. |
| The endpoint returns an access-denied response | A security rule or access control is active | Respect the restriction. Do not try to bypass it. |
| The site shows products but the endpoint is empty | The storefront may use a custom data layer or a different platform | Confirm the actual ecommerce implementation. |
| The endpoint contains products but no variation rows | Variations are not part of the default product collection | Use a scraper designed to retrieve publicly exposed native variation records explicitly. |
| Only some product options are missing | Those options may be add-ons or configurator fields | Document the missing option type and review the variations-vs-add-ons guide. |
How to collect useful support details
When you request help, provide a concise support report. Include the permitted store URL, the page you opened, whether the public Products endpoint returns data, your Chrome version, the extension version and a screenshot of the popup message. Do not share a private password, customer data or a Gumroad license key in a public message.
A good troubleshooting report makes it easier to separate a browser issue from an endpoint issue, a storefront configuration issue or a custom product-options issue.
What the extension should not do
A responsible WooCommerce scraping tool should not evade authentication, rotate proxies to bypass restrictions, solve CAPTCHAs automatically or ignore rate limits. When a website restricts access, the correct action is to respect the restriction and use an authorized export workflow.
Common store-detection questions
Does every WooCommerce website expose the same Store API response?
No. Stores can use different WooCommerce versions, plugins, themes, caching layers and security configurations. The public information available to a browser-based exporter depends on the selected store.
Can the extension scrape products behind a login?
The extension is intended for publicly accessible storefront data. Respect login requirements and access controls.
Can I use the extension on a third-party store?
Use it only when you have the right or permission to collect and use the data. Follow the website's terms and applicable laws.
Where can I get help?
Use the Support page and include the permitted website URL, your Chrome version and a screenshot of the extension popup. Do not post license keys publicly.
Related guides
- How to Export WooCommerce Products to CSV with Product Variations
- Native WooCommerce Variations vs Product Add-ons: Why Some Options Are Missing
- WooCommerce Catalog Migration Checklist for CSV Product Files
Official WooCommerce references
Responsible use: Use catalog-export tools only for lawful workflows. Export data only when you have the right or permission to use it, and follow applicable website terms, privacy requirements, intellectual-property rules and data-use regulations.
