Hello, I'm Wajido

Answer engine optimisation (AEO), also called generative engine optimisation (GEO), is the work of making sure AI assistants such as ChatGPT, Gemini and Google's AI Overviews mention your company and cite your website when people ask about your market. It builds on SEO rather than replacing it: Google's own guidance treats optimising for its AI features as SEO. What changes is what you measure: being named and cited inside an answer, not a position in a list of links.

Yes. Google's AI Overviews and AI Mode draw on Google's search index, and Microsoft Copilot is grounded in Bing, so a page that can't be crawled and indexed is unlikely to be used in an answer. SEO is the foundation; AEO adds measurement and work on the sources AI engines rely on.

In two ways: from what the model learned in training, which changes slowly, and from live web searches it runs while answering, which can change quickly. Answers lean heavily on third-party sources such as review sites, directories, news, forums and videos, not just your own website. Studies find that brands mentioned widely across the web tend to be more visible in AI answers.

Answers are generated afresh each time, so the companies named and their order change between runs, even for the same question, and your own history and location shape what you see. One study found two runs rarely produced the same list. That's why Wajido asks every question several times on every engine and reports how often you're named and your average position, with a range, rather than relying on one screenshot.

Make sure AI crawlers can reach your site and that search engines index it. Publish clear, factual pages about your services, locations and prices, with answers to the questions customers ask. Then earn genuine mentions on the sites AI engines cite: reviews, directories, press and industry publications. Wajido shows which of those sources mention your competitors but not you.

Neither is a shortcut. Google says structured data isn't required for its generative AI features, and a large Ahrefs study found no meaningful lift in AI citations after pages added schema. A study of around 300,000 domains found no link between llms.txt and citations, and Google Search doesn't use the file. Schema still helps with rich results, so keep it, but put access, content and third-party mentions first.

To appear in answers, allow the search crawlers: OAI-SearchBot (ChatGPT search), Claude-SearchBot, PerplexityBot, Googlebot and Bingbot. Training crawlers such as GPTBot, ClaudeBot and Google-Extended are a separate choice: OpenAI and Google both say blocking them doesn't remove you from their search answers. The free check at the top of this page tells you which of these your site blocks.

Often not. Research by Vercel found that the crawlers behind ChatGPT, Claude and Perplexity fetch JavaScript files but don't run them, so content that only appears after scripts run can be invisible to them. Google's crawler does render JavaScript. Serve your key content as HTML.

Arabic and English behave like separate markets. One analysis of billions of AI citations found that the language of a question changes which sources answers cite more than the country does. Customers in Bahrain search in both languages, so Wajido measures Arabic and English separately and never blends them.

It depends on the engine and the change. Engines that search the web live can reflect a fix within weeks; what a model learned in training changes only when the model is updated. Anyone promising a fixed timeline or guaranteed positions is overpromising. What you can do is measure consistently and see what moves.

No. AI answers are probabilistic, and neither Google nor OpenAI guarantees that any page will appear. Wajido measures where you stand and shows what's in your control: whether engines can read your site, and which sources they rely on.

There's no way to edit an AI answer directly. Find where the wrong information comes from, such as an outdated directory listing, an old press release or a page on your own site, and correct it there. Then keep measuring to check the error stops appearing.