Search all pages  ·  Press Esc to close  ·  ↑↓ to navigate
Content Strategy Local SEO GMB Prompts Technical SEO E-E-A-T Guest Post GA4 Analytics
AEO/GEO · AlgoBlueprints · July 2026

Google Confirms llms.txt Does Nothing for Rankings — The Official Clarification That Ends an 18-Month Debate

Add as Preferred Source on Google

Few debates in the AEO and GEO community generated more noise relative to their actual substance than llms.txt. A proposed standard for guiding AI crawlers, llms.txt spawned an entire cottage industry of generators, "AI-readiness audits," and agency service packages built around a file that Google, by its own admission, has never used as a ranking input. On June 15, 2026, Google finally closed the loop with an unambiguous documentation update. The confusion this resolves has cost the industry real time and real client budget — and understanding exactly what Google said, and what it didn't say, matters for every practitioner who has fielded a client question about "AI SEO files" in the past two years.

I manage technical SEO and AI visibility strategy across healthcare, legal services, hospitality, and e-commerce. I've had the llms.txt conversation with nearly every client at least once — usually prompted by a vendor pitch or an industry article claiming it was now essential for AI search visibility. Google's June 15 clarification gives me, for the first time, an unambiguous, citable, official source to close that conversation definitively. This article walks through exactly what changed, the full context of Google's position, and where llms.txt retains legitimate value outside Google Search specifically.


What Google Actually Said — The Exact Language

Google's updated AI optimisation guide states the position directly, and the phrasing matters because it forecloses several common rationalisations practitioners had used to justify llms.txt implementation:

# Google's AI Optimization Guide — Updated June 15, 2026
"You don't need to create new machine readable files,
AI text files, markup, or Markdown to appear in Google
Search (including its generative AI capabilities), as
Google Search itself doesn't use them.

Note that Google may discover, crawl, and index many
kinds of files in addition to HTML on a website: this
doesn't mean that the file is treated in a special way."

Google added the note explicitly "to address questions from the community" — an unusually direct admission that confusion had reached a level warranting formal clarification. The guide continues with an acknowledgement that llms.txt files remain acceptable to maintain for other purposes: "It's completely fine if you decide to create and maintain LLMS.txt files (or other similar files) for other services or systems that use these files."

June 15
2026 — Date Google published the formal llms.txt clarification
Zero
Ranking impact confirmed — neither positive nor negative for Google Search
18 Months
Approximate duration of industry speculation this clarification resolves
2 Platforms
Perplexity and Claude reportedly do use llms.txt-adjacent signals — Google explicitly does not

This Wasn't Sudden — Google Had Been Saying This for Nearly a Year

The June 2026 documentation update formalises a position Google representatives had already stated informally and repeatedly. Gary Illyes, an analyst on the Google Search team, said at Search Central Live in July 2025 that Google does not support llms.txt and is not planning to. John Mueller, Google's Search Advocate, went further — calling the idea speculative and drawing an explicit historical parallel: he compared llms.txt to the old meta keywords tag, the discredited signal that spammers stuffed for years until Google formally announced in 2009 it ignored the tag entirely.

Mueller also addressed a specific source of confusion directly: llms.txt files appeared on some Google properties themselves, which practitioners took as tacit endorsement. Mueller clarified this occurred only because an internal content system had added support for the file format and some internal teams hadn't removed it — not because Google Search consumed or benefited from the file's presence.

The Full llms.txt Timeline — From Proposal to Official Closure
2024 — Proposal Emerges
llms.txt introduced as a proposed standard for AI crawler guidance
The concept spreads quickly through the AEO and GEO community as AI search platforms proliferate. Agencies and tool vendors begin building generators, audits, and service packages around the file format, often implying or directly claiming ranking benefits across major search and AI platforms.
July 2025 — Google's First Informal Rejection
Gary Illyes states at Search Central Live that Google does not support llms.txt
The first clear, on-record Google statement rejecting llms.txt as a ranking or visibility input. Coverage of the statement remains limited relative to the volume of vendor content still promoting the file format.
May 7, 2026 — Lighthouse Adds to the Confusion
Chrome Lighthouse 13.3.0 promotes "Agentic Browsing" audit category to default, including an llms.txt existence check
This inadvertently reinforces the misconception. Anyone running a standard Lighthouse report — and shortly after, PageSpeed Insights and Chrome DevTools — gets an llms.txt check automatically, which many practitioners misread as Google signalling the file's importance for Search specifically, despite Lighthouse's agentic browsing category addressing AI agent compatibility broadly, not Google Search ranking.
June 15, 2026 — Formal Documentation Closure
Google publishes "Clarifying guidance on llms.txt files" in its official AI optimisation guide
The definitive, citable, documentation-level statement: llms.txt does not help or hurt Google Search rankings or AI Overview visibility, because Google Search does not use it in any special way. This closes the debate with Google's most authoritative possible source — official Search Central documentation, not a conference statement or social media comment.

Why Google Bothered to Clarify Something It Already Wasn't Using

Google doesn't typically publish documentation to reject industry speculation about tools it has no relationship with. The clarification fits a broader pattern that TechWyse and other outlets identified in Google's mid-2026 documentation strategy: the company has been spending more time explicitly drawing boundaries around what does and does not matter for AI search visibility, following a similar cadence to its June 5, 2026 statement on third-party SEO tools having no access to internal ranking data.

The Confusion Google Was Responding To
  • 🔴 Vendors and agencies selling llms.txt generation as an "AI SEO" service
  • 🔴 Practitioners spending implementation time on a file with no Google Search benefit
  • 🔴 Confusion between Google's presence of llms.txt on its own properties and endorsement
  • 🔴 Lighthouse's agentic browsing audit reinforcing the misconception unintentionally
  • 🔴 The label "AEO" and "GEO" packaging technical recommendations before platforms endorsed them
What the Clarification Achieves
  • 🟢 A citable, documentation-level source to end client and internal debates definitively
  • 🟢 Explicit confirmation: no positive or negative ranking impact whatsoever
  • 🟢 Clear separation between "acceptable to maintain for other systems" and "helps Google"
  • 🟢 Reinforcement that foundational SEO — not novel AI-specific files — remains the priority
  • 🟢 A template for how Google plans to handle future speculative AEO/GEO tactics
From My Practice — Akif Qureshi

"I had this exact conversation with a legal services client in early 2026 — their previous agency had implemented an llms.txt file and billed it as part of an 'AI visibility package,' alongside a monthly fee to 'maintain AI crawler compatibility.' When I audited the account, the llms.txt file had zero measurable connection to any AI Overview citation change, and Search Console data showed no correlation whatsoever with the file's implementation date. Google's June 15 clarification gave me the exact citation I needed to have that conversation definitively rather than relying on my own analysis alone. I redirected that client's monthly AI visibility budget toward what actually moves the needle: entity schema, content structure for extraction, and Brave Search optimisation for Claude visibility — all confirmed, evidence-backed levers rather than speculative file formats."

Where llms.txt Still Has Legitimate Value — Read This Before Removing Yours

Google's confirmation that llms.txt does nothing for Google Search does not mean the file is universally useless. Google's own guidance explicitly preserves this distinction: "It's completely fine if you decide to create and maintain LLMS.txt files... for other services or systems that use these files."

System Uses llms.txt-Style Signals? Your Action
Google Search / AI Overviews / AI Mode Confirmed — does not use it Remove from any Google-ranking-impact checklist entirely
Perplexity Reportedly references similar signals Low-cost to maintain if you also prioritise Perplexity citation strategy
Claude / Anthropic Some reported use for agentic browsing context Evaluate based on Claude citation priority, not as a blanket requirement
AI coding agents (Cursor, Claude Code, etc.) Genuinely depends on it for codebase context Maintain if you publish developer documentation or open-source projects
Chrome Lighthouse "Agentic Browsing" audit Checks for existence — not a Google Search ranking factor The audit measures agent-readiness broadly, not Search visibility specifically

What Google's Guide Recommends Instead — The Reaffirmed Foundations

The same June 15 documentation update explicitly debunked a cluster of related "AI SEO hacks" alongside llms.txt: content chunking as a separate technical workflow, exact-keyword obsession for AI extraction, and artificial brand mention seeding. Google's summary position, as multiple outlets characterised it: answer engine optimisation and generative engine optimisation are, at bottom, still SEO. The guide redirects site owners toward the same foundational principles that have applied for years — creating unique, valuable content, organising pages clearly for human readers, using high-quality images, and implementing standard technical SEO practices.

The Practical Action Item

Remove llms.txt from any Google-ranking-impact checklist immediately. If you're currently paying an agency for "llms.txt maintenance" as part of an AI visibility package specifically justified by Google Search benefit, request they redirect that budget toward confirmed levers: entity schema, content structure optimised for AI extraction, Brave Search optimisation for Claude, and Bing optimisation for ChatGPT. If your organisation publishes developer-facing content or maintains an open-source project where AI coding agents genuinely reference llms.txt for context, keep the file — but understand precisely why you're keeping it.


Frequently Asked Questions

Should I remove llms.txt from my site now that Google confirmed it does nothing?
Only remove it if your sole reason for maintaining it was Google Search or AI Overview visibility — in which case it was providing zero benefit regardless. If your site serves developer audiences, publishes open-source code, or genuinely benefits from AI coding agent compatibility (Cursor, Claude Code, and similar tools reference llms.txt-style files for codebase context), there's no harm in keeping it for that separate purpose. The file costs almost nothing to maintain; the harm was in believing it delivered Google Search ranking benefit it never provided.
Does this mean AEO and GEO are not real disciplines?
No — Google's clarification targets one specific speculative tactic, not answer engine optimisation or generative engine optimisation broadly. Google's own framing in the same documentation update states that AEO and GEO are, at their foundation, extensions of standard SEO principles rather than requiring entirely separate technical implementations. The confirmed, evidence-backed levers for AI search visibility — entity schema, content structure for extraction, freshness signals, and platform-specific optimisation for Brave (Claude) and Bing (ChatGPT, Copilot, Meta AI) — remain fully valid and increasingly important. llms.txt specifically was never one of those confirmed levers for Google.
Why did Chrome Lighthouse start checking for llms.txt if Google Search doesn't use it?
Lighthouse's "Agentic Browsing" audit category, promoted to default configuration in Chrome Lighthouse 13.3.0 on May 7, 2026, assesses a page's general readiness for AI agent interaction — a broader concept than Google Search ranking specifically. The llms.txt existence check within that category reflects agent-readiness for any AI system that might reference the file, not a Google Search ranking signal. This distinction caused genuine confusion, since many practitioners reasonably assumed a Google-built tool checking for a file implied Google Search valued that file — which Google's June 15 clarification explicitly corrects.

The Bottom Line

Google's June 15, 2026 documentation update ends an eighteen-month debate with unambiguous, citable clarity: llms.txt files do not help or hurt Google Search rankings or AI Overview visibility, because Google Search does not use them in any special way. This followed nearly a year of informal statements from Gary Illyes and John Mueller saying the same thing, and it arrives alongside Google's broader June-July 2026 pattern of explicitly debunking speculative AEO and GEO tactics — content chunking, exact-keyword obsession, and artificial brand mention seeding among them. Remove llms.txt from any Google-ranking-impact checklist today. Redirect the time and budget toward confirmed levers instead: entity schema, extraction-optimised content structure, and platform-specific work on Brave and Bing. If your site genuinely serves AI coding agents or open-source developer audiences, keep the file for that separate, legitimate purpose — just don't mistake it for a Google Search strategy.

Akif Qureshi
Akif Qureshi
Senior SEO Specialist & Marketing Analyst | Content Strategist
5+ yrs experience Google Certified 6 guides

Driven by advanced SEO expertise, deep marketing analytics, high-impact content strategy

With 5+ years of hands-on experience, I specialize in holistic search strategies that don’t just rank—they drive real, measurable business growth. I’ve worked across industries including healthcare, hospitality, legal, e-commerce, and professional services, helping brands dominate their target markets. My approach bridges the gap between raw data and creative execution. Every strategy I build is rooted in rigorous market analysis, structured SEO frameworks, and tailored content ecosystems—no templates, no shortcuts. Whether you’re a single-location brand or scaling across multiple cities, I create data-driven marketing systems designed to compound results and grow with you.

No sponsored content No affiliate links Reader supported

Want Better Visibility in Google & AI Search?

DigitalArka helps businesses improve rankings in Google Search, AI Overviews, ChatGPT, Gemini, Claude, and Perplexity with technical SEO, schema implementation, topical authority, and AI-ready content strategies.

Get Your Free SEO Audit →

© 2026 Algoblueprints. All rights reserved.