WooCommerce feed availability

Stop WooCommerce XML Feed Timeouts

Do not make your store rebuild a large XML file for every Google request. Fetch it on schedule, publish a prepared feed and reduce repeated load on WooCommerce.

Loading verification

Audits up to 10,000 products. No account or credit card required.

✓Scheduled source retrieval✓Published static artifact✓Conditional ETag refreshes
Feed diagnosis

WooCommerce origin

Unavailable

504 Gateway Timeout

Google cannot fetch the feed

!PHP worker exhausted
!XML generated on every request
!Large catalogue response

Feedlinter delivery

A stable published feed URL for advertising channels

Why large WooCommerce feeds time out

A dynamic feed endpoint makes your storefront do expensive work at the worst possible moment.

On shared hosting, exporting thousands of products can consume PHP memory, database connections and CPU for many seconds. If Google requests the URL while the store is busy, the reverse proxy may return a 504 Gateway Timeout before WooCommerce finishes building the XML.

Repeated failures make the feed unreliable and can pause product updates. Increasing PHP limits may only postpone the problem. A more durable approach separates scheduled feed generation from delivery to crawlers.

Feedlinter does not promise to rescue an origin that never responds within the retrieval window. Once the source is reachable, it prevents every downstream fetch from becoming another heavy WooCommerce export.

  1. Retrieve

    Fetch the source on a controlled schedule

    Feedlinter requests the public XML with bounded resources and supports conditional ETag or Last-Modified checks.

    2, 4 or 12 source refreshes daily by plan
  2. Process

    Transform products as a stream

    The worker processes one product item at a time and enforces plan limits without loading the full catalogue into application memory.

    Up to 256 MiB source feeds
  3. Publish

    Serve a prepared feed URL

    Advertising channels receive the latest published XML artifact rather than triggering WooCommerce generation on every request.

    Public cacheable output

Better product data means fewer disapprovals, steadier campaigns and more room to scale.

Built for Google Merchant Center

Pricing

Simple pricing for every catalog.

Pay for processed products across your account. Every plan includes unlimited domains.

1,000 SKU
1 000 SKU250,000 SKU

The prices below include each plan’s base SKU allowance. Additional SKUs are sold in packs of 1,000.

Core

Recommended

$9.99/ month

1,000 SKU total · included

  • 2 source feeds
  • 1,000 SKUs included
  • $2.00 per additional started 1,000 SKUs
  • Unlimited domains
  • 2 daily refreshes per feed
  • Google Merchant Center

Omnichannel

$29.99/ month

10,000 SKU total · included

  • 6 source feeds
  • 10,000 SKUs included
  • $2.00 per additional started 1,000 SKUs
  • Unlimited domains
  • 4 daily refreshes per feed
  • Google Merchant Center
  • Meta / Facebook Catalog
  • OpenAI / ChatGPT

Scale

$59.99/ month

30,000 SKU total · included

  • 20 source feeds
  • 30,000 SKUs included
  • $2.00 per additional started 1,000 SKUs
  • Unlimited domains
  • 12 daily refreshes per feed
  • Google Merchant Center
  • Meta / Facebook Catalog
  • OpenAI / ChatGPT

1 SKU = 1 processed product record in a feed. The same product in two feeds counts twice. When you exceed your allowance, we email you and allow 24 hours to correct it before adding SKU packs to your invoice.

Not ready to subscribe? Run a free instant audit →

Frequently asked questions

The details, without the fine-print fog.

Everything you need to know before running your first product feed audit.

Still have a question? Talk to us

Can Feedlinter fix a WooCommerce endpoint that always returns 504?

The source must respond successfully long enough for the scheduled retrieval to complete. Feedlinter then publishes the processed artifact so channel requests no longer regenerate it.

Does Feedlinter install anything on my hosting?

No. It works from the public XML URL and does not require a WordPress plugin or server configuration change.

How often does Feedlinter retrieve the source?

Core refreshes twice daily, Omnichannel four times per day and Scale twelve times per day. If the source provides ETag or Last-Modified headers, unchanged responses can be recognized conditionally.