AI SEO Ranking Factors: Separating Documented Signals From Folklore (Retrieval-First Playbook)

Context: The UK SaaS Page Cited in an AI Overview That Moved Nothing

A hypothetical but familiar scene: a UK-based B2B SaaS marketing lead notices their pricing-comparison article is being quoted inside an AI Overview for a high-intent query. Visibility has arrived. Branded search has not moved. Demo requests are flat. They ask the obvious question - which AI SEO ranking factors earned this citation, and how do we get more of them?

The honest answer is two answers. Something made the page retrievable and quotable, and something else stopped the citation converting into a click and a pipeline event. Those are different problems with different levers. Most published 'AI SEO ranking factor' lists collapse them into one, which is why teams spend quarters on schema for AI and see no revenue change.

What People Actually Mean by 'AI SEO Ranking Factors' (and Why the Term Isn't Official)

Search the phrase and you will find dozens of scorecards - llms.txt checklists, 'answer-shaped copy', 'AI-only schema', 'entity density'. Useful leads, weak evidence. The term itself is not Google's. Google's own guidance on succeeding in AI Search describes no separate AI ranking system; the same fundamentals - crawlable, indexable, snippet-eligible, helpful content - apply. Its AI features documentation repeats that no special optimisation is required to appear in AI Overviews.

That does not mean nothing matters. It means the signals are ordinary SEO signals, filtered through a retrieval step you do not directly control. The productive framing: not 'how do I rank in AI', but 'how do I remain retrievable, quotable and attributable inside an answer that already exists'.

The Four-Stage Funnel Inside AI Search: Crawl → Retrieval → Grounding → Citation and Click

Classic ranking is one decision - position on a SERP. AI answer engines run a longer chain, and a page fails or succeeds at each link.

Note the mismatch: most 'AI SEO ranking factor' claims sit at stage 3 or 4 and get called ranking factors. Only stages 1-2 are true gates - if you are not crawlable and retrievable, nothing downstream exists.

# Quick retrieval sanity check for a single URL
curl -A "Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)" \
     -I https://example.co.za/pricing-comparison

# Confirm: 200, no rogue canonical, no noindex in the header,
# and the HTML contains the answer passage in the source, not only after JS runs.

Documented Signals Versus Folklore: A Claim-Evidence Table You Can Fill In

Before any budget is spent, classify each candidate signal. The table below is a starter - tailor it to your CMS and stack. 'Documented' means Google states it in its own documentation; 'Third-party claim' means it appears in vendor lists without Google confirmation.

Signals That Gate Inclusion: Crawlability, Indexability and Snippet Eligibility

There is no AI-visibility conversation worth having until these are zero-cost, permanent conditions. Google's Search Essentials covers the same technical baseline for AI experiences because they run on the same index.

• Robots.txt and metas do not block Googlebot or the Google-Extended / AI-related user agents you intend to allow.
• Rendering is not JS-only where the answer passage needs to be visible to a bot.
• Each URL returns 200 with a self-referential canonical; no accidental noindex from staging.
• Search Console confirms indexing; query-driven pages are discoverable via internal links.
• Snippet-eligibility settings do not suppress the text you want quoted.

noindex and googlebot rules are the highest-leverage fixes on any site because they gate every downstream stage. Fix once, stop thinking about them until the next deploy.

Signals That Aid Retrieval and Quotation: Page Structure, Explicit Statements and Entity Clarity

Once the page is in the index, the questions become: is it clearly about the query, and does it contain a passage a retrieval system can lift as an answer? Neither is a 'ranking factor' in the official sense, but both change which pages get selected as sources.

• Topical clarity. The H1 and opening passage state the topic unambiguously. If a reader needs three paragraphs to infer the subject, so does a retrieval step.
• Extractable statements. Short declarative sentences a system can quote without distortion; definitions, ranges and conditions stated explicitly.
• Structured passages. Tables, lists and H2/H3 sections that map to specific sub-questions - the same structure that helps a reader skimming for an answer.
• Entity clarity. Consistent product, brand and author names across the page, About page and schema.
• Evidence density. Claims with sources are more attributable, and attribution is the currency of generative answers.

None of this contradicts Google's people-first content guidance. The same writing that makes a page quotable for an AI Overview makes it quotable for a human. That is the entire argument for treating the two as one discipline, which is how the team at Prebo Digital's SEO and AI SEO practice frames it: revenue over traffic, retrieval over theatre.

Where llms.txt, 'Answer-Shaped Copy' and 'AI-Only Schema' Fit - and Where They Don't

Three recurring vendor claims deserve separate treatment, because each is a plausible lead rather than a documented factor.

llms.txt. A proposed plain-text file that summarises a site for language models. There is no evidence Google's AI experiences require it, and Google has not listed it as a signal. It is cheap to ship - a few hours of engineering - so treat it as a low-cost experiment, not a prerequisite. If you publish one, measure whether retrieval or citation share changes; do not rebuild a content strategy around it.

Answer-shaped copy. The idea that content should be written as short question-and-answer fragments. Partly useful, partly harmful. Useful: explicit statements, tables and clear headings help a reader and a retriever. Harmful: pages reduced to staccato Q&A lose the reasoning, nuance and evidence that make a source quotable in the first place. Aim for structured clarity, not fragmented copy.

Structured data. Google documents schema for rich results - products, articles, breadcrumbs, reviews - in its structured data introduction. It does not list AI Overviews as a schema requirement. FAQ and HowTo rich results have also been scaled back in Search. Pragmatic rule: ship schema that improves classic SERP presentation and entity clarity (Product, Article, OrganiSation), skip 'AI-only' schema unless you can show an effect.

A 30/60/90 Rollout for a Mid-Market Site: Ordering Signals by Leverage

For a mid-market site (Shopify, WooCommerce or a headless build), the sensible ordering below reflects both evidence and effort. It assumes a team that already has Search Console, GA4 and a functioning CMS.

No item on that list requires an AI tool. Several require a working data pipeline, which is why custom reporting aligned to platform signals matters more than another plugin.

POPIA and UK/EU GDPR Guardrails When You Log Prompts for AI Visibility

If you monitor AI answers by logging brand or category prompts, you are likely processing personal data somewhere - not least if you tie a prompt to a user or account. Under POPIA (South Africa) and UK/EU GDPR, the practical safeguards are the same shape:

• Establish a lawful basis for any prompt logging that touches personal data; do not rely on 'research' as a blanket justification.
• Minimise - log only the prompt text and answer, not IP addresses, user IDs or account names.
• Retain briefly. Set a retention window matched to your review cycle, then delete.
• Document the data sources used to choose prompts so a reviewer can reproduce the observation.

These are process requirements, not legal advice. Prebo Digital's strategy consulting team treats prompt logging as part of a wider analytics programme rather than a separate marketing channel.

Measuring AI Visibility Without Click Data: Search Console, Citation Share and Assisted Conversion

AI answer interactions are mostly zero-click or dark, so you measure the pieces you can actually observe and triangulate. Where possible, run changes against a control group of untouched pages.

• Search Console AI impressions. Where Google surfaces AI-feature impressions in reports for your property, treat the trend as a directional indicator, not a revenue scoreboard.
• Citation share. Log the top prompts in your category, run them on a schedule and record whether your domain appears in the cited sources. Compare before and after any structural change.
• Branded search lift. Track branded queries over time as a proxy for recognition, with the caveat that many things move branded search.
• Assisted conversion. GA4 plus server-side tracking should mark AI-referred sessions where possible and, more importantly, measure assisted paths - sessions that touch AI-observed pages before an eventual purchase or demo.

Illustrative budget for a 90-day monitoring cycle at a mid-market site: roughly ZAR 25,000-60,000 of internal time for prompt logging, dashboard work and review - an estimate, not a quote, and largely dependent on existing analytics maturity.

How the Signals Rank Against Each Other: What to Fix First, Second and Third

Ordering signals is more useful than listing them. The table below captures Prebo Digital's working view - high effort, high leverage and high evidence-status items first.

Priority 1 and 8 are the two you should never skip. The first tells you whether the funnel exists; the second tells you whether you are moving. Everything between them is a hypothesis worth testing, not a doctrine to adopt.

Sources

• Google Search Central Blog - Top ways to ensure your content performs well in Google's AI experiences
• Google Search Central - AI features and your website
• Google Search Central - Search Essentials
• Google Search Central - Creating helpful, reliable, people-first content
• Google Search Central - Introduction to structured data