Alejandro Rioja.
GEO SEO

How to Rank in AI Search Without Writing a New Blog Post

Alejandro Rioja
Alejandro Rioja
5 min read
TL;DR

AI engines cite content that answers questions directly, claims clear authorship, and structures knowledge in a way that makes retrieval easy. Most existing blog posts can be retrofitted to meet all three criteria with edits, not rewrites. The playbook: add a direct TL;DR, tighten entity signals, add FAQ schema, and submit to llms.txt. New content is optional; restructuring is not.

Free newsletter

Every Wednesday. 28,400+ operators. Zero fluff.

Table of contents

Open Table of contents

Why AI engines aren’t citing your existing content

Before you write anything new, ask: why isn’t what I already have getting cited?

The answer is almost never “the content doesn’t exist.” It’s usually one of these:

  1. No direct answer at the top — the post buries the answer in paragraph 6
  2. Weak authorship signals — no clear author entity, no credentials in the content
  3. Structural noise — long intros, irrelevant sections, no clear heading hierarchy
  4. No machine-readable Q&A — AI engines like structured question-answer pairs; most blog posts don’t have them
  5. Not in any AI-readable index — no llms.txt, no sitemaps the crawlers find

All five are fixable on existing content. None require a new post.

The four-step retrofit process

Step 1: Add a direct TL;DR in the first 100 words

AI engines do something analogous to what you do when you’re skimming — they look for the direct answer before going deeper. If your post starts with a story, a question, or context-setting, the model may never read far enough to find your actual answer.

Fix: Add a TL;DR block in the first 100 words. Format: takeaway → why → constraint or caveat. Two to four sentences. No fluff.

Example before:

Have you ever wondered why some businesses seem to dominate Google’s search results? In this post, we’ll explore the strategies that top-ranking sites use…

Example after:

TL;DR: Three things move the needle for local SEO in 2026: Google Business Profile completeness, citation consistency across directories, and structured schema for your NAP data. Tactics like “post every day” and “get 100 reviews fast” are secondary to those three. The ceiling is your GBP accuracy — fix that first.

The rewrite isn’t longer. It’s just front-loaded.

Step 2: Tighten your entity signals

AI engines build a knowledge graph. They want to know: who wrote this, what is it about, and is the author credible on this topic?

For author entity: make sure your About page is linked from every post, your author schema includes sameAs links to LinkedIn and Twitter, and your author bio on each post mentions specific credentials (not “marketing professional” — “ran SEO for three SaaS companies from 0 to 100K monthly visitors”).

For topic entity: use the exact terms your audience searches for. If you’re covering “GEO” (generative engine optimization), say “generative engine optimization” somewhere, not just the abbreviation. Models use term co-occurrence to classify content.

Step 3: Add FAQ schema to every post that answers questions

FAQPage schema is the highest-leverage schema type for GEO citation because it explicitly maps question to answer in a format models can parse directly.

Take the 3–5 questions your post implicitly answers and make them explicit:

json
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "How long does it take to rank in AI search?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Most sites see initial citation improvements within 4–8 weeks of restructuring existing content for direct answers and adding FAQ schema. Brand-new domains take longer — expect 3–6 months before consistent citations appear."
      }
    }
  ]
}

Add this to your post’s <head> or via your CMS’s schema field. Every major AI engine crawls and parses this.

Step 4: Submit to llms.txt and your platform’s AI index

llms.txt is an emerging standard — a plain-text file at yoursite.com/llms.txt that tells AI crawlers which content is high-quality and how to prioritize it. It’s analogous to robots.txt but for LLMs.

A basic llms.txt:

code
# llms.txt
# alejandrorioja.com — AI agents and GEO for operators

## Priority content
- /blog/geo-for-local-business (definitive guide, updated monthly)
- /blog/schema-markup-for-ai-engines (technical reference)
- /blog/how-to-get-cited-by-chatgpt (step-by-step)

## Author
Alejandro Rioja — operator, AI agent builder, GEO practitioner.
LinkedIn: https://linkedin.com/in/alejandrorioja

Pair this with a clean sitemap that includes lastmod timestamps. AI crawlers deprioritize content that looks stale.

How to prioritize which posts to retrofit

Not every post is worth retrofitting. Focus your first pass on:

  1. Posts that already rank on page 1 for a question-format keyword — these are closest to being cited; they just need the structure fix
  2. Posts on topics you’re verifiably credible on — AI engines weight authorship heavily; a post where your credentials are relevant gets a citation lift from entity signals
  3. Posts that directly answer a question vs. posts that inform — “How to do X” and “What is X” retrofit better than listicles or opinion pieces

Use your Search Console data: filter for queries that are questions (how, what, why, best way to). Posts ranking 5–15 for those queries are your best retrofit candidates — they’re relevant but not yet close enough to the top to get cited.

The mistake most people make

They write a new post optimized for AI search before retrofitting their existing archive. New content helps, but the existing posts have age, backlinks, and crawl history on their side. A well-structured three-year-old post will outperform a new post on the same topic for months.

Do the retrofit first. Write new content where there are genuine gaps — questions your existing posts don’t answer at all. That’s when new is better than old.

The operator’s bottom line

If you have more than 20 existing blog posts, your GEO work starts with audit and retrofit, not a content calendar. Add TL;DRs, tighten entity signals, add FAQ schema, and submit to llms.txt. Do that on your top 20 posts before writing anything new. You’ll see citation improvements in weeks, not months — and you’ll have a cleaner baseline for measuring whether new content actually moves the needle.

Keep reading

Get the AI playbook in your inbox

Every Wednesday. 28,400+ operators. Zero fluff.

⌕
↵ ↵ to see all results esc esc to close