Skip to main content

Open in AthenaHQ

app.athenahq.ai/bot

​
Purpose

The AthenaHQ Crawler page is a public, unauthenticated reference page designed for IT administrators and security teams. It explains what the AthenaHQ site auditor is, what user-agent strings it uses, and how it behaves when requesting pages. Because IT admins typically discover this page by following the URL found in their server or firewall logs, they do not need an AthenaHQ account to view it. The page provides the technical details they need to safely allowlist AthenaHQ’s crawler so it can successfully audit their organization’s web properties.

​
What’s on the page

Page heading Introduces the crawler’s purpose: AthenaHQ reads public pages to check what AI assistants can see when answering questions about a brand. It checks for JavaScript dependencies, title tags, structured data, and whether AI crawlers are allowed to read the content. How to identify us Shows the exact primary user-agent string the crawler sends (AthenaHQ-Bot/1.0 (+https://app.athenahq.ai/bot)). It explains that the audit also sends a small number of requests mimicking real AI crawlers (like ChatGPT, Claude, and Perplexity) and standard browsers to accurately measure how the site’s firewall treats them. It also notes that AthenaHQ does not publish a list of fixed IP addresses. If your firewall turns us away Shows the fallback browser user-agent string. It explains that if a site’s bot protection blocks the primary AthenaHQ bot, the crawler will retry the request once using a standard browser user agent to ensure the customer’s audit can finish. What we do and do not do A bulleted list clarifying the crawler’s operational boundaries:
  • Audits happen in short bursts of a few dozen requests over a few seconds, not a steady trickle.
  • The crawler reads robots.txt, but it will not stop auditing if the file disallows the AthenaHQ user agent, because the site owner specifically requested the audit.
  • The crawler does not submit forms, sign in, or try to access authentication-gated content.
  • The crawler does not collect personal data.
Contact information Provides a direct email link to AthenaHQ support for anyone with questions about the traffic they are seeing.

​
What you can do here

  • Email support: Click the support@athenahq.ai link at the bottom of the page to open your email client addressed to AthenaHQ support.
  • Copy user agents: IT admins can manually copy the provided user-agent strings to paste into their web application firewall (WAF) or bot-management allowlists.

​
Data shown

This page displays static technical documentation. It does not display any customer-specific data, metrics, or tracked content.

​
Common workflows

Investigating and allowlisting the crawler
  1. An IT or security admin notices a burst of traffic or blocked requests in their firewall logs containing the AthenaHQ-Bot user agent.
  2. The admin copies the URL from the user-agent string and opens this page in their browser.
  3. They read the documentation to verify the crawler’s legitimacy and purpose.
  4. They copy the AthenaHQ-Bot user-agent string and add it to their firewall’s allowlist so future audits requested by their marketing team succeed.

​
Empty, loading, and error states

Because this is a static text page, there are no loading states, empty states, or error states.
  • Linked from: This page is not linked anywhere within the logged-in AthenaHQ application navigation. Users arrive here exclusively by typing or clicking the URL embedded in the crawler’s user-agent string.
  • Links to: The support@athenahq.ai link opens the user’s default email client.

​
Common support questions

Why is this bot ignoring our robots.txt Disallow rule? We do not treat a Disallow for our own user agent as a stop command because the audit runs only when the site’s owner (your organization) explicitly requested it via their AthenaHQ account. If you want to stop the crawler, you can ask the account holder to remove the site, block our user agent at your edge firewall, or contact us. Do you have a list of IP addresses we can allowlist instead of the user agent? No. We do not publish fixed IP addresses. Firewall rules must match the user-agent string. If your organization requires a stronger identity guarantee than a user-agent string, the page advises the AthenaHQ account holder to contact us to arrange an alternative. Why am I seeing requests from AI crawlers coming from your infrastructure? To accurately measure whether your site’s firewall rules admit AI crawlers, we send a small number of probes to your homepage carrying those exact crawlers’ user agents. Those specific probes are the measurement itself, so they cannot announce themselves as AthenaHQ. Why did you retry the request as a normal web browser? If your bot protection turns away the declared AthenaHQ-Bot user agent, we retry the request once as a standard browser. We do this so the customer’s requested audit can still finish. However, we prefer you allowlist our bot so our traffic stays identifiable in your logs.