In some cases, Test Entry or a normal PriceFetchWP fetch may return an HTTP status such as:
403 Forbiddenor:
429 Too Many RequestsThese responses usually mean the external website received the request but chose not to return the normal product page.
This guide explains what blocked requests may mean and what you can try.
– What Does a Blocked Request Mean?
PriceFetchWP fetches external product pages from your WordPress server.
A direct fetch generally looks like:
Your WordPress Server → External WebsiteSome websites restrict automated, server-based, or high-frequency requests.
This can happen even when the same product page loads normally in your browser.
The website may be evaluating things such as:
- Anti-bot or security rules
- IP address or IP reputation
- Request headers
- Browser characteristics
- Request frequency
- Cookies or session state
- JavaScript execution
A blocked response does not necessarily mean your price selector is incorrect.
– Common HTTP Status Codes
403 Forbidden
A 403 response means the external server understood the request but refused access.
This can happen when a website blocks requests that do not resemble normal browser traffic, restricts certain server IP ranges, or uses an anti-bot service (such as Cloudflare).
429 Too Many Requests
A 429 response usually means the external website believes too many requests have been made within a certain period.
If you encounter repeated 429 responses:
- Avoid repeatedly running Test Entry within a short period
- Review your PriceFetchWP price caching settings
- Allow time before testing the same site again
- Consider whether a proxy provider is appropriate
Other Access-Related Responses
Some websites may return other status codes such as:
401503while still serving a challenge page, access-denied page, or other content instead of the expected product page.
Because of this, the HTTP status alone does not always tell the full story.
– Use Test Entry First
If a price is not being fetched, run Test Entry for that URL entry.
Check the reported:
- HTTP status
- Fetch mode
- Fetch result
- Selector results
- Proxy result, if applicable
If Test Entry returns a clear 403, 429, or other access-related response before selectors are tested successfully, changing the XPath, ID, Class, or Script selector will normally not solve the problem.
The external page must first be successfully retrieved before PriceFetchWP can detect its price.
– Why Does the Site Work in My Browser?
Your normal web browser and your WordPress site do not make identical requests.
Your browser may have:
- normal consumer or residential internet access
- cookies from previous visits
- JavaScript enabled
- browser-specific headers
- an established session
- other characteristics that make the request appear normal
A direct PriceFetchWP fetch comes from your hosting server and may be treated differently by the external website.
This is why a page can load normally for you while a server-based fetch is restricted.
– Try the Advanced Options
Before using a proxy provider, you can test the per-entry Advanced Options available in PriceFetchWP.
Depending on the website, options such as a custom:
- User-Agent
- Referer header
- Accept header
- Language header
may affect how the external website handles the request.
These settings are not guaranteed to bypass a blocked request. Some websites use much more advanced request filtering.
Use Test Entry after making changes to determine whether the fetch result has changed.
– Try a Proxy Provider
If a Direct Fetch continues to be blocked, a supported proxy provider may help.
With a proxy provider, the request follows a different path:
Your WordPress Server
↓
Proxy Provider
↓
External WebsiteThe proxy provider makes the final request using its own infrastructure. This may help with websites that restrict normal server-based requests, require browser-style fetching, or use more advanced anti-bot protection.
A website that blocks Direct Fetch may therefore work successfully through a proxy.
Proxy providers are optional third-party services and may have their own usage limits, pricing, and configuration options.
Proxy Provider Guides
For provider-specific setup and troubleshooting, see:
Additional provider guides will be added as support becomes available.
– When a Proxy Still Does Not Work
Most of the time a proxy provider will succeed with requests, but it does not guarantee that every external website can be fetched.
Some websites may require:
- specific cookies or session state
- user interaction
- account login
- location-specific access
- dynamically generated pricing
- browser automation beyond a normal page render
- other site-specific behavior
If the proxy successfully retrieves the page but PriceFetchWP still does not find the price, the problem may no longer be a blocked request.
At that point, check the selector and whether the price is present in the returned page content.
⚠️ Blocked Request or Selector Problem?
These are different problems.
Likely a blocked request?
Test Entry returns something such as:
403 Forbiddenor:
429 Too Many Requestsand PriceFetchWP cannot retrieve the expected product page.
Likely a selector problem?
Test Entry successfully retrieves the external page, but reports that the configured price selector did not match a price.
In that case, review:
- Price Selectors
- Also Check (Secondary Checks)
- The external site structure
Price is visible in the browser but not in the fetched page
The price may be inserted or changed by JavaScript after the initial page loads.
See the related guide:
Price Visible in Browser but Not PriceFetchWP
– What PriceFetchWP Can and Cannot Control
PriceFetchWP can provide different fetch methods, request options, selectors, and proxy integrations.
However, PriceFetchWP does not control the external websites being fetched.
Retailers and other websites can change:
- HTML structure
- security rules
- anti-bot services
- request limits
- JavaScript behavior
- pricing systems
at any time.
A configuration that works today may need to be adjusted if the external website changes how its pages are delivered. Luckily, you will only need to change the URL price selectors and some general settings.
Next Steps ───
If you are troubleshooting a blocked or failed fetch, continue with:
