Skip to main content
Field note · geo case studyPublished February 17, 2026 · 6 min read

What We Changed for AI Search by February 2026 (Dated Note)

A dated note on the changes we made to our own site for AI search between October 2025 and February 2026, and the results claims we withdrew in October 2026.

geo case studygenerative engine optimizationgeoai search optimizationai search resultsllms txt implementation

What Is This Note?

This is a dated note on the changes we made to our own site for AI search between October 2025 and February 2026. It replaces a post called "We Optimized for AI Search. Here's What Changed." The changes were real. The results the original reported were not backed by data, so this note records what we changed and withdraws what we claimed.

What Did We Change, and When?

The dates and commits below come from the git history of this site.

DateCommitChange
28 Sep 20259131e818llms.txt first added
31 Oct 20258ae6b225AI crawler rules added to robots.txt
31 Oct 20256b21b5d7llms.txt restructured to be easier to parse
5 Nov 20255c352eeb12 data and training crawlers blocked
6 Nov 202507ba6857AI referrer tracking added to analytics
15 Feb 202665958ad8Duplicate FAQ markup removed
17 Feb 20264055aaa7Blog series navigation added
30 Mar 2026
when our citation monitor started recording, six weeks after this post, so no before-and-after citation data exists for these changes
Source: Pixelmojo citation monitor records, checked 2 October 2026

What we changed, in order

From the git history

Sep 2025

llms.txt

first added

Oct 2025

Crawler rules

robots.txt

Nov 2025

Blocks

12 crawlers

Nov 2025

Tracking

AI referrers

Feb 2026

Series

blog structure

The dates that matter for this note

From the git history and our citation monitor

28 Sep 2025

llms.txt first added

31 Oct 2025

AI crawler rules added

17 Feb 2026

original post published

30 Mar 2026

citation monitor started

Which Claims From the Original Post Are Withdrawn?

Claim in the February 2026 versionWhat the record showsStatus
Results from implementing the playbookNo baseline was recorded; the citation monitor started 30 March 2026Withdrawn
FAQ schema on every post was something that workedNo major AI engine documents a citation benefit from FAQ markupWithdrawn
llms.txt was created from scratchFirst added 28 September 2025, restructured 31 October 2025Corrected
robots.txt had no AI rules; it now manages 18 crawlers, 10 allowedAI rules from 31 October 2025; the lists have changed several times sinceCorrected
7 May 2026
when Google stopped showing FAQ rich results; as of September 2026 no major AI engine documents a citation benefit from FAQ markup
Source: Radar evidence note on FAQ schema, checked September 2026

What the original claimed, and what the record shows

February 2026 post versus the record checked on 2 October 2026

The February 2026 post
  • Implementing the playbook produced results
  • FAQ schema on every post was something that worked
  • llms.txt was created from scratch
The record
  • No baseline existed; the monitor started 30 March 2026
  • No major AI engine documents a FAQ citation benefit
  • llms.txt existed from 28 September 2025

Our posts still carry an FAQ, because readers use it. Since 2 October 2026 each post's FAQ comes from one list that renders both the visible questions and the markup, so the two can no longer disagree.

Where Are the Practical Steps Now?

They are in Part 3, the GEO Playbook, rewritten on 2 October 2026. It covers crawler access by type, quotable pages, the technical signals that still matter and how to measure without fooling yourself, using our own referral and mention data from 2026. Our dated note on the bot policy covers how our robots.txt changed over the year.

What This Series Covers

This is Part 4 of The AI Search Playbook, now a dated note. Part 3 holds the practical steps.

Our February 2026 Changes: Questions Readers Ask

Common questions about this topic, answered.

What did Pixelmojo change on its own site for AI search?

Between October 2025 and February 2026 we added rules for AI crawlers to robots.txt (31 October 2025), blocked 12 data and training crawlers (5 November 2025), restructured our llms.txt (31 October 2025), added AI referrer tracking (6 November 2025), removed duplicate FAQ markup (15 February 2026) and launched our blog series structure (17 February 2026). The git history records each change.

Did those changes increase AI citations?

We cannot show that they did. The original version of this post presented results without the data behind them, and our citation monitor did not start until 30 March 2026, after these changes. We withdrew the results claims on 2 October 2026.

Did FAQ schema help AI search?

We have no evidence it did. The original post named FAQ schema as something that worked. As of September 2026, no major AI engine documents a citation benefit from FAQPage markup, and Google stopped showing FAQ rich results on 7 May 2026. Our posts still carry an FAQ, now generated from one source so the visible FAQ and the markup always match.

Did Pixelmojo create llms.txt from scratch in February 2026?

No. Our llms.txt was first added on 28 September 2025 and restructured on 31 October 2025. The original post described it as created from scratch during this work. There is still no evidence that llms.txt changes what AI engines say.

What did the original post get wrong about robots.txt?

It described the file as having no AI-specific rules before this work and said it managed 18 crawlers with 10 allowed. The git history shows AI crawler rules from 31 October 2025, and the allow and block lists have changed several times since. Our current policy is described in the GEO Playbook and in our dated note on the bot policy.

Is this post still part of The AI Search Playbook?

Yes, as Part 4, in the form of a dated note. The practical steps now live in Part 3, the GEO Playbook, which was rewritten on 2 October 2026.

How should I measure my own AI search changes?

Record a baseline before you change anything. Track AI referral sessions in analytics and, separately, how often a fixed set of prompts names or links you across engines, with dates and counts. Without a baseline, a later improvement cannot be attributed to the change.

What changed in this post on 2 October 2026?

We cut it down to a dated note. The record of what we changed is kept, with commit dates. The results claims, the claim that FAQ schema worked, the description of llms.txt as new and the robots.txt counts are withdrawn.

Start with the current playbook

Next insightSEO vs AEO vs GEO: From Ranking in Search to Becoming the Recommended Brand
Lloyd Pilapil
About the author
Lloyd PilapilFounder & AI Product Architect · Pixelmojo

Lloyd Pilapil is the founder of Pixelmojo and a senior UI/UX and growth designer with 20+ years of digital product experience and more than 30 years across visual and graphic design. His work includes projects for Salesforce, Parsons, Egis, and other public- and private-sector organizations. He builds production AI systems for B2B companies and writes about agentic AI, multi-agent orchestration, AX (Agentic Experience) design, GEO, and Thread-Based Engineering, focused on shipping AI products that generate revenue, not prototypes.

Agentic AI SystemsMulti-Agent OrchestrationAX DesignGEO & AI SearchThread-Based EngineeringAI Product DevelopmentGrowth MarketingUI/UX Design

Related reading

All field notes
Read enough? Check your own
Does AI get your business?

Run Radar's six free technical checks on your domain, then follow the evidence behind each finding.