Search is no longer just Google. I am interested in how people find information today, what of classic SEO still holds, and what AI answers change for a website. No ranking promises, verified sources.
Key questions
Is SEO dead now that AI answers?
I think it's the wrong question. Google's documentation on AI features in Search (last updated 10 December 2025) says there are no additional requirements to appear in AI Overviews or AI Mode, and that SEO best practices remain relevant. A page has to be indexed and eligible to be shown with a snippet. Google counts traffic from these features in the Search Console performance report, under web search. My thinking is in SEO is no longer just Google.
Do I need to do anything special for ChatGPT, Perplexity and Gemini?
First I'd check that I'm not blocking them myself. OpenAI separates OAI-SearchBot (ChatGPT search) from GPTBot (model training); a site that blocks OAI-SearchBot won't be shown in ChatGPT search answers, though it can still appear as a navigational link. Perplexity says PerplexityBot is for search results and is not used to train its models. On this site robots.txt blocks none of these crawlers; checked on 4 October 2026: Googlebot, Bingbot, OAI-SearchBot, GPTBot, PerplexityBot and ClaudeBot all get a 200 response. The checklist is in Is my website ready for AI search?
What does "your website isn't on Google's first page" mean?
Without a query, a language, a location and a device, nothing. Google's own documentation says nobody can guarantee a number one ranking and warns about firms that contact you out of the blue and claim a special relationship with Google (page updated 5 June 2026). How I tell such a message from a real review is in “Your website isn't on Google's first page”.
Do I need FAQ markup, llms.txt or special schema to be cited by AI?
Not as a trick. Google says you need no special text files or new schema for its AI features. Google stopped showing the FAQ result in search on 7 May 2026, so I don't add an FAQ for the search engine's sake, only when it genuinely answers a reader's question. This site has an llms.txt as a descriptive index, but I don't treat it as a ranking factor.
What matters on this topic
A mention in an answer, a citation with a link and a visit are not the same thing, so I decide what I actually want before I measure anything. Different systems also have different rules, which is why I treat claims like "AI search works like this" with care and check each provider's own documentation.
In my practice three steps remain: the technical basics (indexing, sitemap, speed), clarity about who is speaking and about what (author, dates, sources), and text that follows the question: answer first, explanation after. Structured data only makes sense for content that is visible on the page; Google's policies explicitly forbid marking up content visitors can't see (page updated 10 July 2026).
In practice
Sitequiry, a free tool we build at GE-KO, checks technical SEO, speed and readiness for AI answers. Its case study (Slovenian) says the tool never claims to measure actual visibility in AI answers, only readiness signals. I hold the same line in my articles: I can check the conditions, but I won't promise a ranking. If you're curious how GE-KO prepares a site for AI search engines, the approach is on the AI search optimization page (Slovenian).
If AI can answer almost any question, why still write? That's exactly why. Your own site is a source, a context and an archive no algorithm controls. Compared with LinkedIn, social networks, newsletters and AI search.
A half-hour checklist: AI crawler access, answers in the text, structured data, content worth citing, speed and indexing. No promises about getting you into ChatGPT.
I get the e-mails promising Google's first page too. Why that sentence says almost nothing on its own, what I'd ask the sender, and how a review differs from a sales pitch.
AI answers change the path to information, but they don't remove the need for a good website. How I look at visibility, sources and the promises of GEO tricks.
What a website has to tell someone who does not know the business yet, and why that is not mainly a question of design. I write about the decisions that come before the first line of code, about reviewing existing sites, and about when a redesign makes sense and when it does not.
I use AI every day and I do not trust it blindly. Here I note where it genuinely saves work, where the result has to be checked, and which promises do not survive the first enthusiasm. Experiments, not predictions.
How code comes about that can still be maintained a year later. I write about planning, testing, working with AI while developing, and the decisions we forget quickly once something simply works.
When does a new feature improve an application and when does it just complicate it? Drawing on my own products such as Bizko, I write about the path from an everyday problem, like entering the same data twice, to a tool people actually use.
Technology is the beginning; business gives it meaning. I am interested in what a digital solution really brings a company, which processes are worth automating, and when a simple path beats a big system.