Perplexity retrieves web pages live at query time rather than answering purely from training data, then ranks candidate sources by relevance to the actual question, freshness, and how clearly structured the page's answer is, before citing a handful of survivors in its response. Perplexity has not published its exact ranking formula, so what follows is the pattern independent analysis has consistently observed, not a confirmed algorithm.
This page tracks meaningful changes to Google AI Overviews and related algorithm shifts as they happen, updated as new, confirmed changes occur rather than left static after publication. It's a working reference, not a one-time explainer, check the date at the top before treating any entry here as current.
This is a maintained, living reference of every major AI crawler currently relevant to AI-search visibility, what each one actually does, and whether it's typically a training crawler or a real-time retrieval bot, the distinction that determines whether blocking it actually affects your AI citation eligibility. Bookmark this rather than a static list, since this landscape changes as companies split and rename crawlers.
White label SEO is when an agency sells SEO services to its client under its own brand, while a separate specialist, like me, actually does the work behind the scenes. The client pays the agency. The agency pays me. The client never knows I exist.
Different AI systems use different underlying models, different training data cutoffs, different retrieval mechanisms, and different weighting of signals like entity clarity, schema completeness, and content freshness. That means citation consistency across ChatGPT, Claude, Perplexity, and Gemini isn't guaranteed even for a well-optimized brand, and inconsistency isn't necessarily a sign something's broken, it's often just a reflection of genuinely different systems making genuinely different retrieval decisions.
AI Overviews don't just cite whatever ranks highest organically. A 2026 study tracking 55,393 queries found nearly 30% of cited domains weren't even on page one.
You don't need a large budget to start checking AI-search visibility, a handful of free, genuinely useful tools can tell you a lot before you ever commit to a paid audit or retainer. Here are twelve worth actually using, including several I built and maintain myself specifically for this purpose.
ChatGPT Search doesn't use one single mechanism, it's a layered system. OAI-SearchBot indexes content ahead of time, similar in spirit to a traditional search crawler. At the moment of a real query, ChatGPT breaks your question into sub-queries through fan-out, retrieves passages from indexed and live sources, checks its own internal confidence against what it already knows, and only then decides whether to cite external content at all. Understanding each layer separately is what actually lets you optimize for it, treating it as one black box doesn't.
Organic click-through rates drop meaningfully, somewhere between 34.5% and 61% depending on the study, on queries where an AI Overview appears. At the same time, the traffic that does click through from an AI Overview converts at roughly 14.2%, compared to about 2.8% for standard organic clicks, nearly five times higher. Fewer clicks, but the clicks that remain are worth substantially more, a genuine shift in what a "good" click-through metric even means.
Keyword SEO optimizes for matching specific search strings. Entity SEO optimizes for being clearly understood as a specific, real thing, a person, organization, product, or concept, that search engines and AI systems can identify with confidence and connect to related facts. Keywords haven't disappeared, current data puts them at roughly 55% ranking importance, still real, just no longer dominant. Content relevance and entity signals have overtaken them as the stronger factors.
Schema tooling splits into three real tiers: free generators for basic, single-page markup, paid plugins that automate schema across a whole site with more advanced type coverage, and custom @graph architecture for sites needing genuinely connected, cross-referenced entity schema. Most sites need to know which tier they're actually in, since using the wrong tier either wastes money on unnecessary complexity or leaves real entity-clarity value on the table.
ChatGPT Atlas, OpenAI's browser with ChatGPT built directly into its core, launched in October 2025 and represents a genuinely different kind of shift than the ChatGPT Search feature that preceded it. Search happens inside a chat interface; Atlas puts ChatGPT inside the browser itself, persistent memory, cross-tab context, and the ability to act on a user's behalf while browsing. For SEO and AEO strategy, the practical implication is that citability, being the source an AI system trusts and surfaces, matters more than ranking position in a growing share of research and shopping journeys that may never touch a traditional search results page at all.
A featured snippet pulls one short, direct excerpt from a single page and displays it at the top of results, position zero, sourced from one URL. An AI Overview synthesizes information from multiple sources into a generated summary, citing several pages at once rather than lifting one excerpt verbatim. The content structure that earns each one overlaps significantly, answer-first, clearly structured, but the underlying mechanism, single-source extraction versus multi-source synthesis, is genuinely different, which matters for how you should think about earning either one.
Reddit is currently the single most-cited domain across major AI answer engines, appearing in roughly 40% of citations in one large study spanning ChatGPT, Perplexity, Gemini, and Claude, and as the #1 cited source specifically for Google AI Overviews and Perplexity. This isn't a quirk of the data, it's structural: Reddit's format naturally produces the kind of specific, self-contained, experience-based content AI systems are built to prefer, and most brand pages simply don't.
Googlebot renders JavaScript, eventually, through a multi-step process that queues pages for rendering after an initial crawl. Most [AI crawlers](/blog/ai-crawlers-explained) don't do this reliably, or at all, many fetch raw HTML and never execute the JavaScript that builds the actual visible content on a heavily JS-dependent page. That means a site that ranks fine on Google can still be functionally invisible to ChatGPT, Claude, or Perplexity if its core content only renders client-side.
JSON-LD is the schema format Google explicitly recommends and the one I use on every engagement. It lives in a separate script block, cleanly detached from your page's visible HTML, which makes it far easier to implement, maintain, and audit than microdata, which requires embedding attributes directly inside the HTML elements themselves. Both are technically valid ways to add structured data, but they're not equally practical, and the gap has widened, not narrowed, in recent years.
Pitch the outcome the client already cares about, more qualified leads, protected visibility, a competitive gap closed, never the mechanics of who's doing the work behind the scenes. The pitch itself doesn't change because the delivery is white-labeled. What changes is your own preparation beforehand: knowing your pricing, knowing what you're actually promising, and knowing enough about the process to answer follow-up questions confidently, even though you're not the one executing it.
AI Overviews are the automatic summary box that appears above regular results for select queries, pushed to every searcher without opting in. AI Mode is a separate, dedicated conversational tab a user actively chooses to open, built for longer, multi-step research. They share the same underlying Gemini model family and Google announced in May 2026 they're merging into one continuous experience, but independent research found only about 13.7% overlap in which URLs each one actually cites for the same query, meaning ranking for one doesn't reliably mean visibility in the other.
"Reseller" and "partner" get used interchangeably in casual conversation, but they imply genuinely different levels of involvement. A reseller relationship is typically thinner, closer to buying a standardized product to mark up and resell, with limited strategic input from the provider. A partner relationship implies real, ongoing strategic collaboration, the provider isn't just executing a package, they're helping shape what the client actually needs.
A topical map is an architecture, a structured plan of every entity, subtopic, and question a site needs to cover to establish comprehensive authority on a subject. A content calendar is a schedule, a plan for when pieces get published. Confusing them leads to a real, common failure pattern: a steady stream of content going out on schedule that never actually adds up to comprehensive topical coverage, because nobody planned the coverage itself before planning the publishing dates.
Yes, though voice search has quietly stopped being its own separate discipline and become one specific surface inside the broader AEO practice, rather than a standalone strategy. There are more active voice-enabled devices worldwide than there are people, roughly 8.4 billion, and somewhere between 20% and 50% of search activity now happens by voice depending on how a given study defines and measures it. The content structure that earns voice answers is the same answer-first, direct-response structure that earns AI Overview citations, so if you're already optimizing for AEO properly, you're already most of the way toward voice search too.
AI shopping agents, the kind now built into Google's AI Mode and increasingly into browsers like ChatGPT Atlas, need structured, machine-readable product data to recommend or transact on a customer's behalf. Retailers with thin or missing Product schema, inconsistent pricing data, or unclear availability information are effectively invisible to this emerging purchase path, regardless of how good the actual product page looks to a human visitor.
A one-time GEO project can genuinely fix real, immediate problems, missing schema, blocked crawlers, absent entity signals. What it can't do is hold your position once fixed, because the thing you're optimizing for keeps moving. AI models update, competitors publish new content, citation patterns shift, and content freshness is itself a real, measured factor in whether you stay cited. Treating GEO as a project with an end date means the improvement you paid for quietly erodes, usually without anyone noticing until visibility has already dropped.
Keyword silos organize content around isolated, individually-optimized keyword targets, each page largely self-contained, competing for its own specific phrase. The pillar-cluster model organizes content around one broad topic, a pillar page, supported by multiple connected cluster articles covering related subtopics, all deliberately interlinked. The difference isn't cosmetic, it changes how authority accumulates, siloed pages build authority individually and slowly; a properly linked pillar-cluster structure lets authority compound across the whole cluster.
SEO ranks you in the traditional blue-link results. AEO gets you selected as a direct answer, in a featured snippet, a voice response, or an AI Overview. GEO gets you cited by name inside generative AI answers on ChatGPT, Claude, Perplexity, and Gemini.
Every schema type describes a different kind of "thing," and using the right one, connected to the others correctly, is what turns a page from isolated markup into part of a coherent entity graph. The core types I use on nearly every engagement are Organization, Person, Service, FAQPage, BreadcrumbList, and Article, each doing a distinct, specific job, not interchangeable labels for the same generic content.
Most robots.txt misconfigurations that block AI crawlers aren't deliberate decisions, they're accidents, inherited rules, overly broad security plugin defaults, or copy-pasted configurations nobody has revisited since before AI search existed. Here are the five specific mistakes I find most often, and how to check for each one yourself.
Vet a white-label SEO or AEO/GEO partner on five things specifically: whether their confidentiality is contractual or just implied, whether they can show you real deliverable structure rather than just describe it, whether their process is documented and repeatable or improvised per client, how they handle a genuine mistake, and whether they'll let you start small before committing to a full retainer. I'd apply this exact checklist to myself too, and I'll say plainly where I think I hold up and where you should still verify independently rather than take my word for it.
Automated tools are fast, consistent, and genuinely good at flagging known, well-defined issues at scale, broken links, missing meta tags, basic crawlability errors. They're weaker at catching context-dependent problems that require actual judgment, a robots.txt rule that technically validates but was clearly never intended to block an AI crawler, or a site architecture decision that's individually reasonable but collectively creates a crawl-budget problem no single automated check would flag. The two aren't competing options, they're complementary, and I use both, deliberately, for different reasons.
Most agencies mark up white-labeled SEO retainers two to four times what they pay their fulfillment partner, with the exact multiple depending on how much additional account management and strategic oversight the agency provides on top. A $750/month fulfillment cost commonly becomes a $1,800 to $3,000/month client-facing retainer. I want to walk through the actual reasoning behind that range, not just state it, because pricing this wrong in either direction costs real money.
White label SEO adds monthly recurring revenue because your agency sets the client-facing price, pays a fixed or scoped cost to the fulfillment partner, and keeps the spread every single month the client stays.
There are two fundamentally different categories of AI bot hitting your server right now, training crawlers that scrape content to build future models (GPTBot, Google-Extended), and retrieval bots that fetch content in real time to answer a specific user's question…
A content gap analysis identifies what real, currently-ranking competitors cover that your own content doesn't, then prioritizes closing that gap by actual competitive relevance rather than arbitrary topic brainstorming. The process: identify real competitors, catalog what they cover, compare against your own coverage, prioritize the gap by relevance and impact. It's a specific, repeatable process, not a vague "see what's missing" exercise.
Ranking #1 on Google and still invisible in ChatGPT? That gap has a name: entity debt. Here's how to diagnose and fix it, from 350+ real audits.
How user intent, schema markup, and conversational E-E-A-T signals are replacing traditional keyword density in the generative AI search landscape.
Same audit data, same prompt, two AI models. The quality gap between Claude and ChatGPT reveals exactly where each sits in a professional SEO workflow today.
Why Ilias Sami is shifting from traditional SEO to User Experience Optimization (UXO) and Answer Engine Optimization (AEO) in the age of AI search.
As the web floods with AI-only content, a counter-movement toward human-crafted experiences is emerging. Why the future belongs to hybrid content strategies.
Five years of SEO experience meets the $24 trillion generational wealth transfer — and why the convergence of AI search and generational spending power demands a completely new playbook.
A 5-year SEO veteran's perspective on why AI Overview is evolving — not killing — SEO, and why quality traffic beats volume every time.