Frequently Asked Questions

AI Engine Optimization (AEO) focuses on optimizing your content for AI systems like ChatGPT, Claude, Perplexity, and Google's AI features. While SEO focuses on ranking in traditional search results, AEO focuses on being cited in AI-generated responses, being understood correctly by AI, and signaling credibility to AI systems.

As more users get answers from AI assistants instead of traditional search, having your content cited by AI becomes crucial for visibility and traffic. Studies show that AI-powered search is growing rapidly, and businesses that optimize for AI visibility now will have a significant advantage.

Re-analyze the pages you changed after publishing a material content or technical update. For ongoing monitoring, choose a cadence that matches how often those pages change and how important they are to your AI visibility goals.

Each page analysis costs 1 credit. Single-page scans use 1 credit, while Smart Scans use 1 credit per analyzed page. New accounts receive 1 complimentary credit. The free “Can AI read my site?” check uses no credits, and every paid action shows its cost before you start it.

You can purchase one-time credit packages whenever you need more analyses. The pricing page reads the active package catalog, so the displayed credit totals and prices are the current purchase options.

Completion time varies with the selected pages and the external services used by the analyzer. The progress page displays server-reported status. You can leave that page while analysis continues in the background and return to the saved results.

Currently, AEO NIUEXA can only analyze publicly accessible pages. This is because our crawlers (and AI crawlers) need direct access to your content. If your page requires authentication, you'll need to temporarily make it public or provide a non-authenticated version.

Yes! You can export results in multiple formats: PDF reports for stakeholder presentations, JSON data for custom integrations, and raw data available in the Raw Data tab. Use the Export buttons in your report or copy data directly from the Raw Data tab.

AEO NIUEXA does not currently publish a tier-specific retention period in the product contract. Export any report or raw data that your organization must retain, and contact support if you need a confirmed retention policy for compliance.

From a report, use Share to generate a public share link or Export a report as PDF or HTML for a stakeholder. The current product does not provide workspace invitations, subscription team roles, or shared account access. Never share login credentials or API keys.

Auto-Fix uses client-side JavaScript injection. When a visitor loads your page, the script fetches your fix rules from our servers and applies them in real-time to the DOM. This means fixes are applied on page load without modifying your source files. Most AI fetchers do not run scripts, so they will not see those changes: use Copy permanent fix on a rule to get the same change as plain HTML to paste into your own template. Use Check installation on the Auto-Fix page to see whether your page loads the script (a script added through a tag manager may not show up in the page source). You can toggle individual fixes on/off from the dashboard at any time.

AI Visibility monitors ChatGPT (OpenAI), Claude (Anthropic), Perplexity, Google Gemini, and Google AI Overviews (read from Google search results). Each engine is labelled with how the answer is obtained, because we call the provider's API, which is not the same as a person using the consumer app. A Google answer counts as an AI Overview mention only when the search results page really shows an AI Overview. You can configure which platforms to monitor and set up your own prompts; prompts are never filled in from a generic template when we do not know your industry. The system tracks sentiment, citations, and share of voice.

Yes. Generate an API key from your account and configure the authenticated Streamable HTTP endpoint shown in Product Features. Compatible clients can then use the registered scan, result, AI Visibility, and content tools. Support still depends on the client's MCP transport implementation.

Judge crawlers by what they are for. Do not block the search crawlers (OAI-SearchBot, PerplexityBot, Claude-SearchBot, Bingbot, Googlebot) or the user-fetch crawlers (ChatGPT-User, Perplexity-User, Claude-User) on pages you want found: they decide whether AI search and assistants can open a page. Training crawlers (GPTBot, ClaudeBot, CCBot, Google-Extended, Applebot-Extended, Bytespider, meta-externalagent) are your policy choice: blocking them does not hide your pages from AI search, and the AI Bot Permissions check never fails you for it. A crawler with no group of its own follows your User-agent: * rules, so you do not need an Allow line for every bot.

llms.txt is an optional, proposed summary file for AI systems: a short description of your site and links to key pages. Google does not use it and no major AI engine is shown to, so you do not need one. AEO NIUEXA shows the check in your report as unproven and does not count it in your score.

Score changes can occur for several reasons: content changes on your page, changes to external factors (like indexation status), a new scoring version, or variations in AI-powered content analysis. When we change the scoring rules, older reports show an earlier-rule-set notice and trends never compare analyses scored under different versions; re-scan to compare like with like. Small fluctuations are normal. Larger changes usually indicate real content or technical changes.