AdPrompt's website checker
AdPromptWebsiteHealth is the website checker behind AdPrompt's website reports. If you found it in your logs or security dashboard, it was checking a website that someone added to AdPrompt, usually the business itself or the agency that runs its marketing.
What it checks
It looks at what decides whether people, search engines and AI answers can find and trust a business online: how its pages show up on Google, whether answer engines and AI search can read them, its Google listing, broken links and forms, contact details, speed on phones, safety and tracking tags. Then it explains what to fix in plain language.
- Free website report
- 80 checks, once, for every new business that adds a website to AdPrompt.
- Website & Search on Growth and Partner
- 51 checks across SEO, AEO and GEO, whenever the business wants. Each run uses 1 analysis.
- AdPrompt 360
- All 111 checks every week, with fixes. AdPrompt 360 is in early access.
What it does on a website
- It reads public pages, the same way a visitor's browser does. The one exception is a sign-in that a website's owner sets up for their own checks.
- It never submits forms, starts chats, places calls or makes bookings, and it never changes a website, its tags or its Google listing.
- It skips account, login, cart and checkout pages unless the website's owner asks for them.
- When a website limits how fast it can visit, it slows down. It never tries to get around security checks and never solves CAPTCHAs.
- Its visits are left out of AdPrompt's own visitor reporting.
How to recognize it
Every request carries AdPromptWebsiteHealth in its user agent, for example:
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/131.0.0.0 Safari/537.36 AdPromptWebsiteHealth/1.0 (+https://adprompt.ai/website-health)
Production checks come from the address 13.72.78.96.
How to let it in
If a website or its security service turns the checker away, some checks can't run and the report says so. To let it in, allow the address 13.72.78.96, or requests whose user agent contains AdPromptWebsiteHealth. Allowing the address is the safer choice, because anyone can copy a user agent.
AdPrompt 360 customers can also turn on Scanner access in Website Health settings. It gives a rule that matches the X-AdPrompt-Scanner header, which only AdPrompt sends to their website.
- Cloudflare
- In Security > WAF > Tools > IP Access Rules, add 13.72.78.96 with the action Allow for this website. On the free plan, Bot Fight Mode can't be skipped by any rule, so turn it off in Security > Bots if it blocks the checker.
- Wordfence (WordPress)
- In Wordfence > Firewall > All Firewall Options, add 13.72.78.96 to the allowlisted IP addresses that bypass all rules. If you block by pattern, remove AdPromptWebsiteHealth from Blocking > Block by pattern.
- Sucuri
- In Firewall (WAF) > Access Control > Whitelist IP Address, add 13.72.78.96.
- Wix and Squarespace
- There is no allow list to edit. Make sure the website is published and public, not password protected. If it is still blocked, contact their support with the user agent token AdPromptWebsiteHealth and the address 13.72.78.96.
- Other hosts and security services
- Ask your web host or security provider to allow requests whose user agent contains AdPromptWebsiteHealth and that come from 13.72.78.96.
Questions
Questions about the checker, or a visit you didn't expect? Email [email protected] with your website address, or use the contact form.