Latest
Anthropic Bans Cruelty Toward Claude: What It Means for WritersWork-for-Hire Contracts: What the Asimov’s Cover Fight Teaches FreelancersGenre Fiction vs Literary Fiction: Don’t Confuse Taste With SkillFlorida Hurricane Prep Rituals: The Grocery Run, the Water Pallet and the Generator in the BoxThe Most Insulting Line of Dialogue Ever Written for the ScreenLoki Through the Ages: From Norse Myth to Marvel, The Mask and Dogma“You Are Utterly Disgusting”: A Book Festival, an AI Cover Ban and a Pile-OnWho Rewrote the Sligachan Legend: AI or the Tour Buses?Why I Don’t Like Reedsy for Ghostwriting: The NDA ProblemLayers: How I Ride Out Florida Power Outages in My ApartmentThe Enshittification of AmazonPublishers Cancel Books Over AI While Using It in SecretI Was Getting 100 Spam Emails a Day. $4.50 a Month Fixed It.World Mental Health Day: Nothing Was Wrong With MeKessler Syndrome: How Space Debris Could Close Earth’s OrbitAmazon Is Blocking Real Readers From Book ReviewsShould a Novella Get a Paperback, or Go Ebook Only?BookFunnel Download Problems: Fixes, Scams and AlternativesSir Sean Connery: A TributeHow to Find Plot Holes in Your Novel (Most Are Character Holes)Reshoring: The Factory Is the Easy PartMost of the Books I Was Forced to Read in High School Were CrapPlot Armor: Signs Your Hero Is Too Safe, and How to Fix ItShould You Sell Lifetime Rights to Your Self-Published Book for a Modest Advance?Shame Doesn’t Stop Artists From Using AI. It Stops Them From Telling You.AI Labels on TikTok and Meta Are Flagging Human WorkAuthor Richard Lowe Completes Peacekeeper, a Four-Book Science Fiction Series He Started at Age 14Sir Sam Neill: A TributeFan Art Copied by AI: Glass Houses, Copyright and the Pile-OnReal Names in a Book: Who Gets Sued, the Author, the Publisher or the Ghostwriter?When Characters Take Over the Plot, Let ThemDoes Human Writing Have a Soul?“You’re Not a Real Author”: The Pile-On Over AI-Assisted BooksDoes AI Have a Soul? Wrong QuestionHumor in Book Marketing: Getting Attention Without BeggingHow Long Should a Chapter Be? Manuscript Habits That Save You LaterThe Business Novel and the Companion Workbook: Two Formats Business Authors OverlookThe Back of the Book: Index, About the Author, Acknowledgments and Back Cover CopyI Build My Own Software Tools With Claude, and Some of Them Bit MeWhat Years of Buying From IT Vendors Taught MeI Write Books for a Living. I Barely Read Them Anymore.Three Management Habits That Waste Good PeopleThe Coach and the Webinar That Sold Me NothingThe Work I’d Cringe At Now, and Why I’m Glad I DoWho Is Your Book For? Build a Reader Avatar Before Chapter OnePreface, Prologue, Foreword or Introduction: What Goes WhereWhy I Won’t Build a Ghostwriting Business That ScalesHow I Hire a Virtual Assistant: Do It, Script It, Hand It OffThe Mail Carrier Who Thought Flipping Houses Was EasyWhat Wedding Photography Taught Me About Pricing Creative Work
The Writing King Your Ethical Ghostwriter. Your Story, Done Right.

The Publishing Series

The Day Your Website Died

Optimizing for AI Search

I got good at ranking websites, then the traffic changed shape

That’s search engine optimization, and like anybody who has done it for years I’ve ridden its ups and downs. You learn the rules, the rules shift, you learn them again. Over time I got fairly good at the whole dance.

Then the traffic started to change. Not all at once, and not in a way that set off alarms, just a shift in the shape of it.

So I did what I always do when something changes. I started reading. About AI, and from there about answer engine optimization, and I found a different world.

I want to set one expectation before you start, because it’s the thing that surprised me most and the thing most likely to throw you. This isn’t like SEO. I went looking for a clear account of how it works, couldn’t find one, and assembled the one I wish somebody had handed me at the start.

What is inside The Day Your Website Died?

Who should read The Day Your Website Died?

Why did I write The Day Your Website Died?

Richard Lowe, the Writing King

Years of getting websites to rank, then watching the traffic change and going looking for an explanation that didn’t exist. Thirty-three years in enterprise IT before that. That’s how I know the difference between a system changing and a system being replaced. Two clients have since found me through exactly the mechanism this book describes.

► Behind the Book: The Day Your Website Died
How this one got written, what went wrong, and what got cut.

► With SEO There’s Eventually a Big Bang. This Doesn’t Work That Way.
One story from behind this book.

What do people ask about The Day Your Website Died?

Is this just SEO advice with the word AI added to it?
No, and there’s a whole chapter on exactly where that claim comes from and why it’s only half right. Google’s position is that this is all just SEO done well, and the shared floor is real: a site that cannot be crawled, cannot be read, or contradicts itself won’t be cited by anything. But ranking no longer predicts citation, the engines disagree with each other and change without warning, and the thing that earns a citation is a confirmable identity instead of a good position. The book maps what carries over, what doesn’t, and where your effort should go.
I’m not technical. Is The Day Your Website Died over my head?
There’s a note at the very front written for that exact worry. Almost everything hard in this book is hard in a technical way, and the technical parts are the parts you delegate. The structured data, the DNS check, the one rendering fix: hand those to whoever builds your site. What cannot be delegated isn’t technical at all. It’s deciding the real, settled facts about your business and saying them clearly, in one voice, everywhere. Read the technical chapters for the shape of the thing, not to become an engineer.
Does The Day Your Website Died’s AI search advice work, or is it another someday promise?
The book opens with the proof instead of the promise. Two paying clients arrived after an AI engine named the author, one through Perplexity and one through ChatGPT, and at the time none of the deliberate work in this book had been done. A sound foundation was already enough. One of them said the author came up as the number two recommendation and chose him anyway, which is the finding: you don’t have to be the single best result, you have to be on the short list. The proof comes first, the method follows.
How fast does AI search optimization work?
Slowly, and the book says so plainly, because that’s the expectation most likely to throw you. SEO has a kind of big bang, a day the traffic shows up. This doesn’t work that way. You get a trickle here and a trickle there, an engine names you in one answer and then another, and before you quite notice it’s happened you’re seeing more of the right people finding you. It builds the way trust builds. There’s also a full chapter on the honest limits: what barely moves the needle, what works more slowly than promised, and the payoff ranking so you spend your time where it counts.

Also in The Publishing Series

An answer has no page two

Which is the whole problem, and the whole opportunity.

BUY FROM INGRAMSPARKAMAZONKOBOREAD THE INTRODUCTIONTABLE OF CONTENTS

Paperback and ebook.

Introduction

The Day Your Website Died

I’ve spent a long time getting websites to rank, and I’ve been good at it. That’s search engine optimization, and like anyone who has done it for years, I’ve ridden its ups and downs. You learn the rules, the rules shift, you learn them again. Over time I got pretty good at the whole dance.

Then the traffic started to change. Not all at once, and not in a way that set off alarms at first, just a shift in the shape of it. So I did what I always do when something changes. I started reading. I started reading about AI, and from there about answer engine optimization, and I found a whole different world.

This book is the compilation of what I learned along the way. It’s been a long and twisty road, and an interesting one, and so far a successful one. I wrote it because I went looking for a clear account of how this works and couldn’t find one, so I assembled the one I wish I had been handed at the start.

I want to set one expectation before you begin, because it’s the thing that surprised me most and the thing most likely to throw you. This isn’t like SEO. With SEO there is, eventually, a kind of big bang. A day arrives when Google decides to rank you, and the traffic shows up. AEO doesn’t work that way. There’s no single moment, no flip of a switch, no morning you wake up ranked.

What happens instead is quieter. You get a trickle here and a trickle there. An engine names you in one answer, then another. And before you quite notice it’s happened, you’re seeing more traffic in certain areas, more of the right people finding you, more conversations that started with a machine recommending your name. It builds the way trust builds, slowly and then suddenly. If you’re used to the big bang, the trickle can feel like nothing is happening, right up until you look back and see how far it carried you.

That slow, twisty, rewarding road is what this book is about. Here’s what I learned walking it.

Parts of this book get technical. There’s a chapter about your domain and DNS, a chapter about code that describes your pages to machines, a chapter about reading your server logs. I’ve worked hard to explain all of it in plain language, and most of it’ll make sense as you go.

But some readers see a word like schema and quietly decide the whole thing is over their heads. If that’s you, I want to catch you before you put the book down, because that conclusion is wrong, and it would cost you the part that matters.

Table of contents

The Day Your Website Died

  • Chapter 1: The Client Who Found Me Through a Machine
  • Chapter 2: Two Kinds of Search
  • Chapter 3: The Cost of Doing Nothing
  • Chapter 4: The Mistake I Made First
  • Chapter 5: What Carries Over and What Doesn’t
  • Chapter 6: Three Moving Targets That Don’t Agree
  • Chapter 7: What the Bots Cost You
  • Chapter 8: The Density Principle
  • Chapter 9: Your Site Is the Center of the Universe
  • Chapter 10: The Plumbing: Your Domain, DNS, and the Bot That Cannot Reach You
  • Chapter 11: The Blank Page: When the Crawler Can’t Read Your Site
  • Chapter 12: The Anchor: One Org, One Author
  • Chapter 13: sameAs: The Equals Sign of the Web
  • Chapter 14: The Rest of the Schema: Facts the Machine Can Read
  • Chapter 15: Wikidata: The Keystone
  • Chapter 16: The Hard Identifiers
  • Chapter 17: FAQ Content: Answers the Machine Can Lift
  • Chapter 18: Building a Page the Machine Can Lift
  • Chapter 19: The Evidence That Earns the Citation
  • Chapter 20: Original Research: The Thing Only You Can Be Cited For
  • Chapter 21: E-E-A-T: The Trust the Machine Checks For
  • Chapter 22: The Pages That Actually Convert
  • Chapter 23: Listings and Reviews: The Off-Site Layer You Control
  • Chapter 24: Local: When the Customer Is Standing Nearby
  • Chapter 25: Social Profiles: More Nodes in the Web
  • Chapter 26: YouTube: The Citation Source Hiding in Plain Sight
  • Chapter 27: GitHub: The Citation Source for Technical Authority
  • Chapter 28: Posting: Marketing, Not Entity-Building
  • Chapter 29: Wikipedia: The One You Earn
  • Chapter 30: Reddit: The One You Cannot Fake
  • Chapter 31: Quora: Expertise With Your Name On It
  • Chapter 32: More Than One Domain: Expanding Without Diluting
  • Chapter 33: How the Machine Actually Learns You
  • Chapter 34: Reading the Crawl: How to Know It’s Working
  • Chapter 35: Freshness: Why the Work Is Never Done
  • Chapter 36: The Engines, One by One
  • Chapter 37: Spoken Answers: Siri, Alexa, and the Voice Surface
  • Chapter 38: The Agents Are Coming: Optimizing for Machines That Act
  • Chapter 39: Poisoning the Well: How Your Entity Can Be Attacked
  • Chapter 40: The Honest Limits
  • Chapter 41: The Through-Line
  • Chapter 42: The Operating Card
0 comments

No comments yet. Yours can be the first.

Was this useful?