Helen Hou-Sandi

The two likely culprits here are either that it’s still being cached (perhaps by Cloudflare?) or that there’s an actual ads.txt file on your server that was separately uploaded. Let me know if you need more help navigating how to find out if either of those situations applies.

Hello – there are a couple of options here. For that length of a list, I think your best bet for the moment is to hook in on a scheduled cron job and grab the JSON and add them to RSA’s options programmatically. Looks like we need to update the readme here on .org but this is an example of adding/removing IPs programmatically: https://github.com/10up/restricted-site-access#how-can-i-programmatically-define-whitelisted-ips

If that’s beyond your technical reach, or if storing that many IPs is an issue (I have not personally tested with that scale of stored options in this plugin so I cannot promise it will work well), let us know and we can take a look at more detailed code or other approaches.

@marcusbae Could you possibly post which editor you are using, your active theme, and any active plugins?

And just to check, since you note you clicked the “hide this update” button, does this mean you are using a language other than US English for your WordPress dashboard?

@onaccs WordPress can be a lot of things to a lot of people as they need! We include multiple bundled themes so you can pick one that fits the kind of site you want to make, on top of all the other themes out there you can use. So sure, it can power a blog, but blog posts are just a form of content, after all.

@chrismenning1990 Do you have an ads.txt file already on your server? And are you able to take a screenshot of the revisions you see for ads.txt in your WordPress dashboard?

Hi everyone – we decided to remove this warning because it seemed to be triggering a lot of false positives and we need to spend some time chasing down the various causes. The error message itself was just a warning and did not affect functionality. If you’re seeing other errors after updating to the latest version of Ads.txt Manager, please start new forum posts so that we can troubleshoot individually. Thank you!

@simshomekitchen Could you open a separate topic for your issue so we can troubleshoot that separately from this thread? Thanks.

Hello everyone – if you’re seeing the expected content at yoursite.com/ads.txt, then don’t worry, you can ignore the message! In the meantime, we are hard at work on a release that will hopefully be smarter about not showing that message if it doesn’t actually apply to your site setup.

Sure thing, you can email [email protected] ??

If you’d like to follow along with what I think the issue is, I’ve opened it here: https://github.com/10up/ads-txt/issues/48

Thought of one thing that might shed some light here if you’re able: could you pull raw access logs for your site and look for any entries for ads.txt? I’d be looking for something like Googlebot, but any entries especially for crawlers you can find would be helpful!

Well, hope springs eternal I suppose ?? You *should* be able to add a file in the root, if it’s on the server most configurations will see that first before WordPress even has a chance to kick in. That said, we’ll see what we can do about setting up a test for this and also at least take a look at the suspected fix, it would be nice to be able to confirm instead of just releasing new versions and hoping though!

Agh, yeah, so I think what’s happening is that when it goes to the detection it’s actually hitting WordPress.com’s own ads.txt file. We’ll take a look at getting that fixed up, and in the meantime you can safely ignore the warning ??

I don’t know for sure what’s happening, I have a suspicion that AdSense is requesting the URL in a way that ends up with a response that the file isn’t actually there, but they’re very opaque so it’s hard to know. Is their support responsive? I could give you something to ask them if so.

In the meantime, the thing I suspect (cachebusting query strings) is something we have on the radar to support better so we may incidentally fix this at some point, but if we can confirm that as the issue we can speed things up a bit.

Sorry to hear that! I wonder if somehow your site is responding to the check in a way that’s the same as if the file were actually there, I actually have a little bit of a suspicion as to what it is but would love to be able to confirm if you can give me a little more info.

Could you possibly share your site’s address as well as the URL you get when you’re on the Ads.txt editing screen? And when you say WordPress.com website, do you mean one that’s on a business plan there so you can install plugins?

In the meantime, if editing and saving still gives you the expected results, you can safely ignore the notice, and hopefully we’ll get a fix out soon so that doesn’t keep bugging you!