All posts

Why Bookmarks Are Broken (And What to Do Instead)

The average person has hundreds of bookmarks they never revisit. The problem isn't your discipline. It's that bookmarks were designed in 1993 for a web with 130 websites. In 2026, your saved content should be queryable by AI.

Bookmarks don't work. Not because the technology is flawed. Browser bookmarks do exactly what they promise: save a URL for later. The problem is that "saving a URL for later" doesn't solve the actual problem. You don't need to store links. You need to find information when it matters.

The bookmark graveyard

Open your bookmarks right now. How many are there? Hundreds? Thousands? When's the last time you actually used one that wasn't in your top five?

Your bookmarks bar has the same eight links it's had for two years. Gmail, your company dashboard, maybe Notion. Everything else lives in a folder structure you created with good intentions and abandoned within a week.

Here's what happens, every single time:

  1. You find something valuable on the web
  2. You think "I should save this"
  3. You bookmark it, maybe even put it in a folder
  4. You never look at it again
  5. Six months later, you need that exact information
  6. You can't find the bookmark, so you search Google for 20 minutes
  7. You find it again, and the cycle repeats

Research from browser analytics suggests that over 90% of bookmarks are never clicked after being saved. The average Chrome user has 300-500 bookmarks. Most can't name more than 10 of them.

You're not bad at bookmarks. Bookmarks are bad at being useful.

Why save-and-forget is universal

The bookmark graveyard isn't a discipline problem. It's a cognitive one.

When you save a bookmark, you're making a prediction about the future: "I will need this specific URL at some future moment, and when that moment arrives, I will remember that I saved it, remember where I saved it, and navigate to the right folder to retrieve it."

That's an absurd amount of cognitive work to expect from your future self.

The "save" action provides closure. The moment you bookmark something, your brain marks the task as "handled." The anxiety of losing the information dissipates. You feel a micro-hit of satisfaction. That emotional closure is the point. The retrieval was never the point.

Context disappears immediately. When you saved that article about pricing strategy, you knew exactly why it mattered. Three months later, you see "Pricing in SaaS" in your bookmarks and you have no idea which specific insight made you save it. The URL is preserved. The context is gone.

Folder structures don't scale. You start with three folders. Then ten. Then sub-folders. Then you're spending more time deciding where to put a bookmark than it would take to just Google the thing again later.

The information landscape changes. Half of what you bookmark today will be irrelevant in six months. But bookmarks don't decay. They accumulate. Your collection becomes a geological record of past interests, and the useful stuff is buried under layers of outdated sediment.

People don't fail at bookmarks. The bookmark model fails at how people actually retrieve information.

What "finding later" actually requires

Here's the key insight the entire bookmark paradigm misses: retrieval is a search problem, not a storage problem.

When you need information you've previously encountered, you don't think in URLs or folder names. You think in concepts:

  • "That article about why companies undercharge in the first year"
  • "The blog post comparing rate limiting approaches"
  • "Something I read about GDPR compliance for small startups"

You think in meaning. Bookmarks give you a flat list of URLs organized by folders you named months ago. That's a fundamental mismatch.

What retrieval actually requires:

Search by meaning, not location. "Articles about developer experience" should surface everything relevant, regardless of whether you tagged it "DX," filed it under "Engineering," or forgot to organize it entirely. This is semantic search.

Full content, not just URLs. A bookmark saves a URL. But URLs break. Pages get updated. Paywalls go up. The average half-life of a web page is roughly two years. Useful retrieval requires the actual content to be captured at save time.

Zero-organization input. The best capture system requires no organizational decision at the moment of saving. Every second you spend choosing a folder is friction that makes you less likely to save the next thing.

Contextual retrieval. When you return to a topic months later, the right content should surface based on the concepts you're currently working with, not the folder name you picked when you saved it.

Bookmarks are invisible to your AI tools

Here's where the problem gets worse in 2026: your bookmarks are completely invisible to AI.

You use Claude, ChatGPT, or Cursor daily. These tools are central to how you work. And they have absolutely no idea what you've bookmarked.

Think about what that means. You've spent years curating valuable web content through bookmarks. You've built up a personal library of trusted sources. And none of it is accessible to your AI tools.

When you ask Claude about a topic you've researched deeply, it draws from its training data and whatever you paste into the conversation. It doesn't know about the 47 articles you've bookmarked on that exact topic. It doesn't know which sources you trust.

So it gives you generic answers. Or it cites the SEO-optimized content farm instead of the deeply researched independent analysis you bookmarked six months ago.

Your taste, your curation, your judgment about what's valuable: all trapped in a format that predates the modern web, let alone AI.

The format problem

Bookmarks are, technically, a list of URLs with optional titles and folder paths. That's the entire data model. No content extraction. No full-text indexing. No semantic understanding.

This format was designed in 1993 for Mosaic, one of the first web browsers. The web had roughly 130 websites at the time. Thirty-three years later, the bookmark data model is functionally unchanged. Still URLs in folders. Still invisible to everything except your browser's bookmark manager.

The evolution: from bookmarks to intelligent capture

Stage 1: Bookmarks (1993-2005)

Save a URL. Put it in a folder. Hope you remember it exists.

Stage 2: Social bookmarking (2005-2012)

Delicious, Digg, StumbleUpon. Tags were better than folders. Social discovery was genuinely useful. But still just URLs.

Stage 3: Read-later apps (2008-2025)

Instapaper, Pocket, Omnivore. Save the content, not just the URL. Better reading experience. But built around "reading later," which most people don't do.

Stage 4: AI-native knowledge capture (2025+)

Save content and make it queryable by AI. Semantic search replaces folders. MCP integration connects your saved knowledge to Claude, ChatGPT, Cursor, and every AI tool in your workflow.

The key differences from every previous stage:

  • No organization required. You save content. Semantic search makes it findable.
  • AI can access it. Through MCP and APIs, your saved content becomes available to every AI tool you use.
  • Search by meaning. "That article about why B2B pricing is harder than B2C" finds exactly what you're looking for, even if those words never appeared in the title.
  • Content persists. Full extraction at save time means your knowledge survives link rot, paywalls, and redesigns.
  • Knowledge compounds. Every page you save makes your knowledge layer more valuable. Over months and years, you build a corpus of trusted, curated content that your AI tools can draw from.

What to do instead of bookmarking

Save the content, not the link. Use a tool that captures the full page content, not just the URL. This protects you against link rot and makes the content searchable.

Skip the folder decision. Don't spend ten seconds choosing between "Marketing," "Strategy," and "Business." Just save. Any tool worth using in 2026 should have search good enough to make folders unnecessary.

Connect to your AI tools. Your saved knowledge should be accessible to Claude, ChatGPT, Cursor, and anything else you work with. Look for tools that support MCP, the open standard that lets AI assistants query external data sources.

Trust search over organization. Describe what you're looking for, and semantic search understands meaning, not just keywords. "Articles about engineering team scaling challenges" finds relevant content whether you tagged it "engineering," "management," or forgot to tag it entirely.

Let your knowledge compound. Each save should make your overall knowledge layer more valuable. Over time, you build a personal corpus that no generic internet search can match.


Your bookmarks aren't lazy. They're legacy. The web moved on. Your saving habits should too.

Related reading:

Knowledge that compounds.

Solem is the shared knowledge base for humans and AI agents. Save once. Your AI knows forever.

Frequently Asked Questions

Why don't I ever use my bookmarks?
Because bookmarks require you to remember what you saved, where you saved it, and navigate to the right folder to find it. Studies show over 90% of bookmarks are never revisited after saving. The save action provides psychological closure, making your brain feel the task is handled even though the information isn't truly accessible.
What's wrong with bookmark folders?
Folders require an organizational decision at the moment of saving that rarely matches how you'll search for the information later. They don't scale past a few dozen bookmarks. Semantic search, finding content by meaning rather than location, eliminates this problem entirely.
Can AI tools access my bookmarks?
No. Browser bookmarks are stored in proprietary, browser-specific formats with no standard API. Claude, ChatGPT, Cursor, and other AI tools cannot see, search, or reference your bookmarks. To make saved web content accessible to AI, you need a tool that captures page content and exposes it through protocols like MCP.
What is a knowledge layer?
A personal repository of saved web content that's indexed for semantic search and accessible to AI tools. Unlike bookmarks (which store URLs) or read-later apps (which store articles for human reading), a knowledge layer captures content and makes it queryable by both you and your AI agents.
How is this different from a read-later app like Pocket?
Read-later apps were designed around a premise that doesn't hold: I'll read this later. A knowledge layer flips the model. Instead of saving content to read it again, you save it so you or your AI can query it later.