The NeogencyAudit robot

NeogencyAudit opens your pages the way a visitor does, to check speed, content and what Google and AI assistants see. If your firewall or bot protection refuses it, the audit cannot read your site. Below: how to recognise it and how to let it in.

How to recognise it

User agent

NeogencyAudit/1.0 (+https://neogency.app/robot)

IP address

5.75.161.95

A user agent can be faked, so the safest rule checks both the user agent and the IP. The robot only reads public pages, never sends forms and never logs in.

Vercel

  1. In the project open Firewall and turn off Attack Challenge Mode if it is on. It blocks every robot.
  2. Under Bot Protection, check that automated requests are not set to Challenge or Deny for this site.
  3. Add a custom rule: User Agent contains NeogencyAudit and IP Address equals 5.75.161.95, action Bypass. Publish the change.
  4. If the robot is still refused, the block comes from Vercel's system mitigations. Add a System Bypass Rule for the IP 5.75.161.95 and your production domain (Pro and Enterprise plans).
  5. The audit must point at your production domain. Preview deployments behind Vercel Authentication refuse every robot.

Cloudflare

  1. Open Security, then WAF, then Custom rules, and create a rule.
  2. Condition: User Agent contains NeogencyAudit and IP Source Address equals 5.75.161.95.
  3. Action: Skip, with all remaining custom rules, rate limiting and Super Bot Fight Mode selected.
  4. On the free plan, Bot Fight Mode cannot be skipped by a rule. Turn it off if the robot is still refused.

WordPress

  1. Wordfence: Firewall, then Allowlisted IP addresses, add 5.75.161.95.
  2. In Wordfence rate limiting, do not block crawlers that are not Google.
  3. Other security plugins (Solid Security, All In One WP Security) have a similar IP allowlist. Add the same IP there.
  4. If your host has its own firewall (for example SiteGround or Kinsta), ask them to allow 5.75.161.95.

Your own server

  1. Find the rule that refuses bots: a user agent block in nginx, a SetEnvIfNoCase rule in Apache or a fail2ban filter.
  2. Add an exception for the IP 5.75.161.95, or for the user agent NeogencyAudit.
  3. Reload the server and open your site once from the audit again.
# nginx, before any deny rule
allow 5.75.161.95;

# Apache (.htaccess)
Require ip 5.75.161.95

robots.txt

  1. If the audit says robots.txt blocks it, add these lines at the top of yourdomain.com/robots.txt.
  2. Leave your other rules as they are. This only opens the site to NeogencyAudit.
User-agent: NeogencyAudit
Allow: /

Shopify, Wix, Squarespace

  1. These platforms do not let you set firewall rules and rarely block the robot.
  2. A refusal there usually means the store or site is password protected. Remove the password, or open the site before the next check.

We check again within 24 hours on our own. If the robot is still refused after you changed the settings, write to hello@neogency.app and we will look at it with you.