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.

More people now ask AI assistants instead of searching, and those answers cite only a few sources. If AI crawlers cannot reach or read your pages, the answer cites someone else. AEO makes your pages easy to fetch, understand and quote; it cannot guarantee that an AI answer will mention you.

Re-scan a page after you change it, to confirm the fix worked; marking a fix done on the site dashboard shows each page's result before and after. To follow how AI engines answer your buyers' questions over time, turn on weekly monitoring in AI Visibility instead of checking by hand.

Each analyzed page costs 1 credit, whether you select one page or several. Finding the pages on your site is free. An AI Visibility check costs 10 credits. New accounts receive 15 complimentary credits once the email address is confirmed. The free “Can AI read my site?” check uses no credits, and every paid action shows its cost before you start it.

Buy a one-time credit package whenever you need more; there is no subscription. The pricing page reads the active package catalog, so the credit totals and prices shown are the current purchase options. Work already running keeps the credits it reserved.

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.

Our scanner is not the crawler your site serves. When a firewall, CDN or bot challenge refuses our request, or the page times out, we cannot tell what the real crawlers get, so the check says “could not test” and is left out of the score instead of failing. If the real crawlers are refused too, your server or CDN logs will show it.

Yes. A page report downloads as PDF or HTML, and its Raw Data tab holds the data as JSON. The site dashboard exports the site report, and What to do next downloads every fix as Markdown tickets or a CSV spreadsheet. Agencies can download a client summary as PDF and every site as CSV.

Scores, recommendations and reports stay in your account while it is open. The raw page data behind them (fetched content, detailed check output and PageSpeed data) is kept only for the 3 most recent analyses of each page. Deleting your account removes your sites and analyses. The privacy policy lists every retention period.

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.

Yes. Under Profile → Report branding, set your agency name, logo and accent colour and turn on white-label: client summary reports and site reports then carry your branding instead of NIUEXA's.

Auto-Fix uses a script tag. When a visitor loads your page, the script fetches your fix rules from our servers and applies them in the browser, 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, or, if your site runs through Cloudflare, the Cloudflare Worker, which writes the fixes into the HTML for every crawler. 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 turn single fixes on or off at any time.

AI Visibility monitors ChatGPT (OpenAI), Claude (Anthropic), Perplexity, 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 choose the engines and the questions to track (up to 10); questions are never filled in from a generic template when we do not know your industry. Run a check yourself at any time, or turn on weekly monitoring so the tracked questions are asked again every week.

Setting up a brand is free. Each check, whether you start it or a weekly run does, costs 10 credits and is charged only if at least one engine answered. Weekly runs stay inside a monthly budget that you set and agree to first; when it is reached, the month's remaining weekly runs are skipped, never charged. Fact checks, suggested questions and finding content gaps are free.

Yes. Connect ChatGPT or Claude by signing in to your AEO NIUEXA account, or create an API key for coding agents and use the authenticated Streamable HTTP endpoint shown in the MCP guide. 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.

Yes. The interface, the Learn guides and this documentation are available in English and Italian: switch with EN · IT in the menu or the footer. Italian pages are also scanned with Italian wording rules. Emails and the legal pages are in English.