Cloudflare
Security, then WAF Rules: create a Skip rule whose expression is (ip.src eq 51.89.174.65) and move it to the top of the list. If Bot Fight Mode is on, that rule must also skip bot management.
Some sites sit behind a firewall that turns away anything other than an ordinary visitor. Our server is one of those: it reads your pages the way a browser would, but from a data centre. Here is how to let it through, in two minutes, without weakening your protection.
Sign in to run a check. Log in
51.89.174.65
AuditCulturelBot/1.0 (+https://nyumba.bnm-consulting.eu/acces; audit@bnm-consulting.eu)
An audit stopped by a block is never charged to you: the audit is credited back to your account automatically.
Send this page to whoever administers your site: everything they need is on it.
Security, then WAF Rules: create a Skip rule whose expression is (ip.src eq 51.89.174.65) and move it to the top of the list. If Bot Fight Mode is on, that rule must also skip bot management.
Wordfence, then Firewall, Blocking, Allowlisted IP Addresses: add 51.89.174.65. Check Rate Limiting too, whose thresholds apply before the allowlist on some versions.
Firewall, Access Control, Whitelist IP Addresses: add 51.89.174.65.
If your site turns robots away through a .htaccess rule, add an exception above it: Require ip 51.89.174.65, or its equivalent in your server's syntax.
Send this page to your host or web provider and ask them to allow read access from 51.89.174.65. It is a routine change with no effect on your security: one specific address allowed opens nothing to anyone else.
A site that turns robots away often turns away, through the same setting, the assistants that now answer your future clients' questions. Here is what your robots.txt file declares.
If the listing sits on a portal or on a site run by someone else, the protection is not yours to change. Audit a page you do control instead, or write to us: depending on the case, we can collect the page another way.