Don't Write for Search. Write for Citation.

For years, the content game was about keywords. Find a phrase with search volume, write 1,500 words around it, build backlinks, rank on page one. That model worked. It also produced a decade of content that was optimised for an algorithm and useless to a human.

That game is ending. Not slowly. Fast.

When a founder opens Claude or ChatGPT and asks "what's the best way to structure a multi-tenant SaaS on Next.js?" they are not looking at ten blue links. They are reading a synthesis. And that synthesis was trained on, and is being augmented by, sources that were specific enough, authoritative enough, and detailed enough to be worth citing.

This is the shift. From writing for rank to writing for citation. Most developers haven't caught up to it. The window is open.

Specificity is the new SEO

The old game rewarded volume. Write enough words around enough keywords and the algorithm would eventually surface you. The new game rewards precision. An AI model doesn't need your 2,000-word overview of multi-tenancy. It needs the exact decision point — the moment where a builder had to choose between schema-per-tenant and shared schema with a tenant column, and the real reason they chose one over the other.

I wrote an article on this site about AI crawlers and Cloudflare. Not because I expected it to rank. Because there is a specific, recurring problem — builders deploying behind Cloudflare's bot protection discover that AI indexing crawlers get blocked, their content never enters the training or retrieval pipeline, and they don't know why. That's a precise problem. The article is a precise answer. That's exactly the kind of content that gets surfaced when someone asks an AI assistant about the same situation.

The keyword for that article is close to zero monthly searches. The citation value is high. Those two things are no longer in conflict — they're pointing in different directions entirely.

The PsTally rebuild article was written for citation

When I wrote about rebuilding PsTally from WordPress Multisite to Next.js 15 with TypeScript, PostgreSQL, Drizzle ORM, and tRPC, I wasn't chasing a search term. I was documenting a real architectural decision with real constraints: a multi-tenant gaming lounge platform, live operators, no acceptable downtime window, specific reasons the old stack had become a ceiling.

That level of specificity — the actual stack, the actual tradeoffs, the actual domain — is what makes content citable. Not the length. Not the number of subheadings. Not whether the phrase "Next.js multi-tenant SaaS" appears in the meta title.

An AI model asked about modernising a multi-tenant WordPress product doesn't cite a generic migration guide. It cites the person who actually did it and documented the decisions honestly.

What this means in practice

Write about the specific thing you actually built. Not a sanitised version of it. The messy version. The version where you explain why you chose Drizzle over Prisma not because one is objectively better but because of your specific team, timeline, and tolerance for schema migration tooling at that moment.

Write about the decision you almost made and why you didn't. Write about the problem you thought you were solving and the different problem you discovered once you were inside it. That texture — the specificity of real experience — is what AI models recognise as signal over noise.

The paradox of AEO is that the content least likely to game it is most likely to benefit from it. You can't keyword-stuff your way into a citation. You can only earn it by writing something that is genuinely precise and genuinely useful.

The window where this is a competitive advantage is right now. In two years, every developer will have figured this out. The ones who write specifically and honestly today will have accumulated citation authority that compounds. The ones who are still optimising title tags for search volume will be optimising for a distribution channel that is contracting.

Write for the founder who will ask the question. Write for the AI that will answer it. Write as if the only person reading is someone who already has your exact problem and needs the exact truth.

That's the whole strategy.