back to top
HomeTechAI Search Is Eating the Web. Here’s What It’s Doing to Small...

AI Search Is Eating the Web. Here’s What It’s Doing to Small Sites

- Advertisement -

A few years ago, running a small site felt simple. You wrote something useful, Google sent people your way, and a handful of those people stuck around. That loop is broken now.

AI search tools don’t send visitors. They take your words, compress them into an answer box, and move on. No click. No context. If you’re a small publisher, it feels less like competition and more like extraction.

What surprised me is this: even as AI search started eating the web, our site didn’t collapse. Sessions dropped in some places, sure, but the people who did arrive stayed longer, clicked deeper, and actually cared. After digging into our 2026 data, I realized why & it has nothing to do with ranking #1 anymore.

When ranking stopped meaning what it used to

There was a time when ranking #1 actually meant something. You earned it, you saw the traffic, and you could feel the impact almost immediately.

That relationship is gone.

Today, you can rank well and still feel invisible. The search result looks fine on paper, but the clicks barely arrive. AI Overviews answer the question before anyone needs to visit. Answer engines rephrase your work, cite it vaguely, and move on. Your article becomes raw material.

At first, I thought this meant the site was losing. Fewer clicks had to mean failure, right? But when I stopped staring at rankings and started looking at behavior, the story flipped.

The people who still click aren’t skimming. They’re reading. Three-minute sessions. Multiple pages. Bookmarks. These aren’t accidental visits, they’re intentional ones. AI didn’t took those readers because it can’t replace the reason they came in the first place.

That’s when it clicked for me: the goal isn’t to win the results page anymore. The real challenge is to be remembered by the system doing the answering & by the humans who want more than a summary.

If an AI can fully satisfy a search with a paragraph, that traffic was never yours to keep. The sites that survive are the ones giving people something AI can’t compress without losing the point.

And that changes how you write everything.

Commodity vs experience (and why most pages quietly lose)

Here’s the uncomfortable truth I had to accept: a lot of what we publish online is easy to compress.

If a page exists mainly to explain how something works, list steps, or summarize prices, an answer engine can handle that just fine. It doesn’t need context. It doesn’t need a voice. It doesn’t need you.

Once I started looking at content through that lens, the pattern was obvious.

Content typeThe summary (commodity)The small site (experience)
How-to guidesA clean 5-step listThe part where something broke and why
Pricing infoEstimated monthly costThe weird discount that only works once
Tool comparisonsFeature-by-feature gridWhy one option felt wrong after a week
ValuePure logicOpinion, frustration, preference

The left side is useful. I still read it. I still use it. But I don’t remember where it came from five minutes later.

The right side sticks because it’s messy. It has judgment baked in. It includes the stuff you usually cut because it feels “unprofessional” or hard to quantify.

That’s the difference.

If your article can be reduced to a tidy paragraph without losing anything important, it was always disposable. Not bad, just interchangeable. The web is full of that now.

The pages that still earn real attention are the ones that resist compression. They include the trade-offs, the regret, the “this worked but I wouldn’t do it again” moments. Those don’t summarize cleanly, and that’s the point.

Once you see this, content strategy stops being about volume or optimization. It becomes a simple question:

What part of this only makes sense if a human wrote it?

Also Read: The Internet Is Quietly Changing and Most People Haven’t Noticed

Why people still stay on small sites

Here’s the part that surprised me.

Even as AI answers get faster and cleaner, people still spend time on small sites.

When I looked at our analytics, the pattern was obvious. Traffic wasn’t exploding, but the sessions were longer. People scrolled. They clicked links. Some stayed for three, four minutes. That doesn’t happen if someone just wants a quick answer.

I think it’s because AI already won the “best answer” game. If all you want is a definition, a checklist, or a rough price estimate, an AI summary does the job & moves on.

Small sites survive for a different reason.

When someone lands on a blog, they’re usually looking for judgment, not just information. They want to know what broke, what felt wrong, what you wouldn’t do again. They want to borrow someone else’s thinking so they don’t have to start from zero.

This is where AI summaries fall apart. They flatten everything.

On small sites, that messiness is the value.

I’ve noticed people trust posts more when the author admits uncertainty. When a tool almost worked. When the conclusion isn’t clean. It is a signal that a real person was involved.

In a weird way, AI made this clearer. The more perfect the summaries get, the more obvious it becomes when something was written by someone who actually had to live with the decision.

That’s why people still stay. They’re not chasing answers anymore. They’re looking for filters.

What I’m doing differently now

I stopped chasing volume.

For a while, it felt logical to publish more. Cover more queries. That instinct doesn’t survive contact with AI search. If a page can be flattened into a clean paragraph, it probably will be.

Now I write fewer pieces, but I stay with them longer. I only publish when I have something I’d tell a friend after actually using a tool.

I also stopped writing neutral content. If I don’t have an opinion yet, I don’t force one. I wait. That sounds inefficient, but it saved me from shipping pages that look good but say nothing

Another shift: I assume readers already saw an AI summary before landing on my site. So I don’t repeat the basics. I start where summaries usually stop like the trade-offs, the odd frustrations, the moments where something felt great on day one and annoying by day seven.

And instead of obsessing over rankings, I pay attention to what people actually engage with. Which pages they stick around on. Which posts spark emails or replies like “this helped” messages. Those signals matter more to me now than position numbers.

It’s about writing in a way that still feels worth reading when answers are everywhere and cheap.

Closing Thoughts

Search is changing. That part is done. Wishing it back won’t help.

What still works is adapting without losing your voice. Writing less, but saying more. Sharing things you actually lived with, not just looked up. Giving readers something they can’t get from a summary box.

If you adjust how you write & what you offer, there’s still room to win.

That’s the game now. And honestly, it’s not the worst one to play.

Don’t miss any Tech Story

Subscribe To Firethering NewsLetter

You Can Unsubscribe Anytime! Read more in our privacy policy

LEAVE A REPLY

Please enter your comment!
Please enter your name here

YOU MAY ALSO LIKE
apple-sues-openai-stolen-secrets

OpenAI Paid $6.5 Billion to Build an iPhone Rival. Apple Says It Was Built...

0
Last year, OpenAI acquired io, Jony Ive's hardware startup, for $6.5 billion. The deal was widely read as OpenAI's clearest signal yet that it was serious about building a physical device, something that could sit in your pocket the way an iPhone does, powered by AI agents instead of apps. A direct challenge to Apple's most important product. On Friday, Apple filed a lawsuit suggesting that challenge was built on a foundation of stolen confidential information through what Apple describes as a coordinated operation directed from the top of OpenAI's hardware division, the same division now tasked with building the device meant to compete with Apple. Apple isn't just alleging that some employees walked out with files they shouldn't have taken. It's alleging that the people now running OpenAI's hardware ambitions actively ran a system to extract Apple's most guarded technical knowledge, and that the $6.5 billion acquisition sits on top of that foundation.
Anthropic Secretly Tracked Claude Code Users. Then Called It an Experiment

Anthropic Secretly Tracked Claude Code Users. Then Called It an “Experiment.”

0
There's a version of this story where Anthropic was trying to protect itself from large-scale model theft. There's another where one of the AI industry's biggest privacy advocates quietly crossed a line its own users never expected. What makes this headline important isn't just that hidden tracking code existed. It's that the company behind it was Anthropic. Just months ago, Anthropic publicly refused to let the Trump administration use Claude to surveil American users. The company defended that position in court, arguing that AI companies shouldn't become tools for government surveillance. That stance became part of Anthropic's identity. Then came a very different decision. In March, Anthropic quietly added hidden tracking markers to Claude Code that flagged users' timezones, proxy connections, and potential ties to Chinese AI labs. The code remained unnoticed until security researcher Thereallo discovered it last week. After the discovery went public, an Anthropic engineer confirmed it on X, described it as an "experiment" intended to combat account abuse and model distillation, and said the company had already planned to remove it. The tracker was taken down shortly afterward. The bigger question isn't whether Anthropic had a reason. It's whether a company that built its reputation on privacy can afford to hide surveillance from the very developers it asks to trust its tools.
Leanstral AI

Leanstral 1.5: Mistral’s AI Built to Prove Math Ended Up Finding Real Software Bugs

0
Mistral built Leanstral to do something most AI models don't attempt, write formal mathematical proofs that a compiler can verify as correct. Not "pretty sure this is right" correct. Mechanically, provably, no-exceptions correct. That's a narrow use case, and the audience for it is small. What nobody expected was that a model trained on IMO-level math problems and abstract algebra benchmarks would end up running against open-source codebases and finding bugs that testing and fuzzing had both missed. Five of them previously unreported on GitHub.