We use your site's WordPress API to pull the content data needed for our reporting and SEO-related tools. In some cases, website security settings block or limit automated requests, which can prevent us from accessing that data consistently.
If that happens, the most common fix is to whitelist our IP address so our system can reach your WordPress API without being blocked by your firewall, security plugin, CDN, or hosting provider.
Disclaimer: Even after whitelisting, due to the way WordPress and its API function, we may not always retrieve data exactly as it appears within WordPress. As a result, minor delays or small discrepancies may occur, and data may not always reflect a perfect 1:1 match.
We continuously work to minimize these differences and ensure the data remains as accurately and as timely as possible.
IP Address to Whitelist
Please whitelist this IP address:
`100.28.194.104`Why This Matters
Our system connects to standard WordPress API endpoints to retrieve content and related site data. If your site security tools see those requests as suspicious or unauthorized, they may block them, rate-limit them, or redirect them.
When that happens, it can lead to:
- missing or incomplete content data
- delayed updates in WordPress reporting
- extraction failures that prevent us from refreshing your data
Where to Add the Whitelist
The correct location depends on how your site is set up. Common places to add the whitelist include:
- your CDN or web application firewall
- your WordPress security plugin settings
- your hosting provider's firewall or security tools
- any custom server-level access rules managed by your developer or hosting team
If you are not sure where this is configured, your web developer, hosting provider, or site administrator should usually know where to make the update.
What to Allow
Please allow our IP address to access your WordPress API so we can retrieve site data successfully. If your setup supports path-level rules, it can be helpful to ensure API access is allowed for standard WordPress REST API routes such as:
`/wp-json/wp/v2/posts``/wp-json/wp/v2/users`
If your security setup does not allow path-specific exceptions, allowlisting the IP at the firewall or security layer is typically the simplest option.
After Whitelisting
Once the IP has been whitelisted, please let us know by submitting a support request. We can then retry the connection and confirm whether data extraction is working as expected.
If Access Is Still Blocked
If issues continue after whitelisting, the cause is usually a separate WordPress or server configuration setting. For example, some security tools restrict API access by default, especially for certain API routes.
In those cases, your developer or hosting team may need to review:
- WordPress security plugin rules
- firewall or bot-protection settings
- API access restrictions
- custom server or application rules affecting WordPress API traffic
Who From My Side Can Help?
If your team is unsure where to make this change, send this document to the person who manages your website hosting, security, or WordPress configuration. They should be able to update the appropriate setting and confirm when access has been allowed.
Reviewing your bot and crawler settings?This guide covers access needed for Raptive’s internal tools. If you’re reviewing your site’s broader bot and crawler settings (especially for ad performance), you may also want to ensure that important advertising and verification bots aren't blocked. |
Need Further Support?
Submit a support request with details on your site and what issues you are having.