{"id":1252,"date":"2025-05-16T11:13:42","date_gmt":"2025-05-16T09:13:42","guid":{"rendered":"https:\/\/keypers.io\/blog\/the-future-of-seo-how-to-get-ai-answers\/"},"modified":"2025-11-05T18:17:27","modified_gmt":"2025-11-05T17:17:27","slug":"the-future-of-seo-how-to-get-ai-answers","status":"publish","type":"post","link":"https:\/\/keypers.io\/en\/blog\/the-future-of-seo-how-to-get-ai-answers\/","title":{"rendered":"The future of SEO: How to get AI answers?"},"content":{"rendered":"\n

AI is coming, but technical SEO remains<\/h2>\n\n

Even with the advent of AI tools, the need to get the basics right in terms of technical SEO<\/strong> doesn't change. Thus, a necessary step for being able to be found in the answers is the very accessibility of the site for<\/strong> both search engine crawlers<\/strong> and AI tools. <\/p>\n\n

JavaScript still as an obstacle<\/h3>\n\n

Until recently, we were dealing with optimizing the non-JS<\/strong> version of the site primarily because of Bing and Seznam. And this topic will be equally important in the future. None of the non-Gemini<\/strong> AI tool crawlers can correctly handle<\/strong> content output by JavaScript. <\/p>\n\n

This is a significant problem for sites built on JavaScript frameworks<\/strong>, which have significant difficulties without further optimization. Fortunately, this issue is solvable, although it often requires significant developer capacity. <\/p>\n\n

Focus on making the main content of the page<\/strong> (without interactive elements) available directly in the underlying HTML code<\/strong>. For JS frameworks, server side rendering (SSR)<\/strong> can help a lot. <\/p>\n\n

Only with such a fine-tuned website can you become a source of answers<\/strong> in Chat GPT, Perplexity, etc.<\/p>\n\n

Watch out for blocks and robots.txt file<\/h3>\n\n

If you want to get into AI answers, you need to let both search engine crawlers and chatbots crawl your site<\/strong>.<\/p>\n\n

Be careful about any leftover settings from the past when you might have blocked certain crawlers<\/strong> (for example, to reduce server load). <\/p>\n\n

If you find that some crawlers are blocked in your robots.txt file, you\u2019ve got a problem in the age of AI. Such rules should be removed if necessary<\/strong>. <\/p>\n\n

Among the most interesting user agent entries you can find in robots.txt are the following identifiers:<\/p>\n\n

    \n
  1. Open AI - GPTBot, OAI-SearchBot and ChatGPT-User<\/li>\n\n\n\n
  2. Anthropic - anthropic-ai, ClaudeBot and claude-web<\/li>\n\n\n\n
  3. Perplexity - PerplexityBot and Perplexity-User<\/li>\n\n\n\n
  4. Google - Google-Extended<\/li>\n<\/ol>\n\t\t\t\t
    \n\t\t\t\t\t\t\t
    \n\t\t
    \n\t\t\t<\/svg>\n\t\t\t
    \n\t\t\t\t

    Interesting fact<\/strong>: GPTBot is the most blocked AI crawler (3.71% of the sites analyzed in the Ahrefs study had some form of blocking set in the robots.txt file).<\/p>\n\n\t\t\t<\/div>\n\t\t<\/div>\n\t<\/div>\n\t\t\t<\/div>\n\n

    Help crawlers get to your site sooner<\/h3>\n\n

    This topic doesn't make much sense for a site with 5 subpages. But for medium and larger sites you can help crawlers with indexing. <\/p>\n\n

    The basic option is a sitemap.xml file<\/strong>, which should contain all the pages of the site that we want to get into the search results<\/strong>. Be sure not to generate URLs in this file that don't work. Don't generate URLs here that have temporary content or are not suitable for indexing (treated with meta robots or canonical). <\/p>\n\t\t\t\t

    \n\t\t\t\t\t\t\t
    \n\t\t

    Are you concerned about the speed of indexing for sites that frequently add new content<\/strong>? Both Seznam and Bing (and therefore Chat GPT) support the Index Now protocol<\/strong>. Where you can use the API to submit newly created URLs. In our experience, this method will ensure faster indexing<\/strong> even with traditional search engines. However, it makes sense to use this option for specific cases of large websites<\/g>. For the others, the sitemap.xml file, which is linked to from the robots.txt file, is fully sufficient. <\/p>\n\n\t<\/div>\n\t\t\t

    \n\t\t\t
    \n\t\t\t\t\t\t\t\t\t\n\t\t\t\t\t\t\t\t\t\t\t\n\t\t\t\t\t\t\"\"\n\t\t\t\t<\/picture>\n\n\t\t\t<\/div>\n\t\t\t\t\t\t
    \n\t\t\t\tMichal Ka\u0161par, CEO\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t<\/blockquote>\n\n

    Are you concerned about the speed of indexing for sites that frequently add new content<\/strong>? Both Seznam and Bing (and therefore Chat GPT) support the Index Now protocol<\/strong>. Where you can use the API to submit newly created URLs. In our experience, this method will ensure faster indexing<\/strong> even with traditional search engines. However, it makes sense to use this option for specific cases of large websites. For the others, the sitemap.xml file, which is linked to from the robots.txt file, is fully sufficient. <\/p>\n\n

    Web speed? Still needed, but primarily for users <\/h3>\n\n

    Don't forget about page speed. If each page on a large site takes forever to respond, you won't please your users or crawlers. They have a certain amount of time (crawl budget<\/strong>) to crawl as many pages as possible. <\/p>\n\n

    Also, from a user perspective, Google defined Core Web Vitals<\/strong> standards some time ago. We recommend that you and your programmer focus on all of these metrics and fine-tune your website. <\/p>\n\n

    It's still about quality content<\/h2>\n\n

    From a content perspective, nothing fundamentally<\/strong> changes in SEO. What works in traditional search engines also works in generative search engines. <\/p>\n\n

    The key remains quality, relevant and well-structured content that matches the user's intent. <\/strong> <\/p>\n\n

    In addition, it should appear credible and expert, for which we have long defined the principles of E-E-A-T<\/strong> from Google (Experience, Expertise, Authoritativeness, Trustworthiness).<\/p>\n\n

    Demonstrate your expertise on the topic<\/h3>\n\n

    Every search engine and AI tool needs content in its answers from verified and trusted sources<\/strong> that bring real value to the user. <\/p>\n\n

    Focus on comprehensive coverage of the topic<\/strong>. Build a series of thematically linked articles<\/strong> into content clusters so that you become a true specialist on the topic<\/strong> in the eyes of search engines. <\/p>\n\n

    Don't be afraid to cite internal and external experts<\/strong> and give their comments on the topic at hand. <\/p>\n\n

    Work with numbers<\/strong>. Give specific figures, refer to relevant studies<\/strong> to support your claims and back up the published information. <\/p>\n\n

    Structured data for content sites has long required information about the author of the article<\/strong>. Have this information on your site as well, including the inclusion of a medallion<\/strong>. <\/p>\n\n

    The list of sources used<\/strong> in the article can also help to substantiate the claims made.<\/p>\n\n

    \"\"<\/figure>\n\n

    Tip: Don't just research, add something extra<\/h3>\n\n

    Do you want to become a source of answers? Then you probably won't be satisfied with just research<\/strong>. The approach where the copywriter goes through the top 5 search results and summarizes them into one text or takes the text itself from Chat GPT and adds nothing extra may not be enough in the future. <\/p>\n\n

    Such texts merely recycle statements that have already been written hundreds of times. AI tools don't need to learn assertions they already have from another source. It is adding your own knowledge, tips and bringing real value to the user<\/strong> that will be critical. <\/p>\n\n

    Focus on structuring the text<\/h3>\n\n

    It's also important for search and AI chatbots whether the content is structured. What is important is clarity, proper formatting and logical hierarchy.<\/strong> <\/p>\n\n

    So for AI, let's use these formatting options:<\/p>\n\n