If an external price is not appearing on your WordPress page, post, or WooCommerce product, there are several things to check before changing your configuration.
A missing price does not always mean the external website is blocked or unavailable. The issue may be related to the URL Entry, selector, cache, page content, or fetch method.
This guide will help you narrow down where the problem is occurring.
– Start With Test Entry
The first step should usually be Testing a URL Entry.
Open the URL Entry associated with the external website and run a test using the product URL you are trying to fetch.
Test Entry can help determine whether:
- the external page was successfully fetched
- the request was blocked
- the configured selector matched
- a regular or sale price was detected
- a proxy provider was used
- a connection or server error occurred
If Test Entry finds the expected price successfully, the issue may be with how the price is being displayed or connected to your WordPress content.
If Test Entry cannot find the price, continue through the sections below.
– Check the URL Entry
Make sure the external website is connected to the correct URL Entry.
The domain configured in PriceFetchWP should match the domain of the product URL being fetched.
For example:
example.comshould match a product URL such as:
https://example.com/products/example-productAlso confirm that the URL Entry is not currently paused.
– Check the Price Selector
If the page fetch succeeds but no price is detected, review your configured selector.
PriceFetchWP supports:
- XPath
- ID
- Class
- Script
External websites can change their HTML or scripts at any time.
A selector that previously worked may stop matching if the external website changes its page structure.
Use your browser’s developer tools to confirm that the selector still targets the expected price.
If needed, see: Finding Price Selectors
– Price Is Visible in My Browser
A price being visible in your browser does not always mean that the same price is immediately available to PriceFetchWP.
There are several ways a website may provide pricing.
Price is in the normal page HTML
This is the most straightforward situation.
An XPath, ID, Class, or Script selector can usually target the price directly.
Price is stored inside a script
Some websites include product pricing inside embedded JavaScript or other script data.
In this case, a Script selector may be able to retrieve the price without requiring JavaScript rendering.
For example:
#viewed_product::PricePrice is added after the page loads
Some websites use JavaScript, AJAX, coupon scripts, or other dynamic behavior to insert or modify a price after the initial page has loaded.
A normal Direct Fetch does not execute page JavaScript.
In these situations, a supported proxy provider with browser rendering may be required.
Even browser rendering does not guarantee that every dynamically generated or personalized price will be available.
– Check for a Blocked Request
If Test Entry reports an HTTP status such as:
403 Forbiddenor:
429 Too Many Requeststhe external website may be restricting the request.
Changing the price selector will not normally fix a request that is being blocked before the expected product page is returned.
See: Blocked Requests
– Try a Proxy Provider
If Direct Fetch cannot retrieve the expected page, a supported proxy provider may help.
Proxy providers can be enabled individually for URL Entries that require them.
If Direct Fetch already retrieves the correct page and price, a proxy is generally not necessary.
For more information, see:
Additional provider guides may be added as support becomes available.
– Check Advanced Options
Some external websites may respond differently depending on the request configuration.
The per-entry Advanced Options allow you to adjust settings such as:
- User-Agent
- Referer
- Accept header
- Language header
- cURL timeout
- SSL Verification
- Proxy provider
These options are intended for websites that require something different from the normal PriceFetchWP defaults.
After changing an Advanced Option, run Test Entry again to see whether the result changes.
– Check the Cache
PriceFetchWP uses caching to avoid unnecessarily fetching the same external price on every page load.
If you recently changed:
- a selector
- a URL
- an external product price
- a fetch configuration
you may temporarily see a previously cached result.
Review your Price Cache settings and clear or refresh the applicable cache when testing configuration changes.
– WooCommerce Price Not Showing
If Test Entry successfully finds a price but it does not appear on a WooCommerce product, check that:
- the product is configured correctly for your PriceFetchWP setup
- the PriceFetchWP custom field exists on the product
- the custom field name matches the global WooCommerce setting
- the custom field value contains the correct original external product URL
- the URL domain matches a configured URL Entry
- your settings have been saved
If you are using an affiliate link for the WooCommerce Product URL, remember that the PriceFetchWP custom field should contain the original external product page URL used for fetching.
– Page or Post Price Not Showing
For normal WordPress pages and posts, verify that:
- the PriceFetchWP shortcode is present
- the shortcode URL is correct
- the URL domain matches a configured URL Entry
- the URL Entry is not paused
- Test Entry successfully detects the external price
If Test Entry finds the correct price but the shortcode displays nothing, review your Page/Post Settings and shortcode configuration.
⚠️ Still Not Finding the Price?
A successful page fetch does not guarantee that every price can be detected.
The external website may:
- have changed its HTML
- store the price inside a script
- generate the price with JavaScript
- return different content to server-based requests
- use anti-bot protection
- require cookies or session information
- personalize pricing by location or visitor
- require interaction before displaying the final price
PriceFetchWP can provide several fetch methods and selector types, but external websites are outside of PriceFetchWP’s control and may change at any time.
