The Unlinked Index: How to Archive Your Own Bookmarks as Public Data
We often think of web archiving as a grand, external effort—the Internet Archive's crawlers, national libraries preserving entire domains. But some of the most valuable, specific, and human collections exist not in these vast repositories, but in the humble browser bookmarks bar. It's a personal archive, a curated list of digital artifacts that mattered enough to save from the stream. Yet when a link in that list goes dark, a piece of your intellectual history goes with it. What if we could preserve that curation itself, not just the pages it points to?
I propose a simple technique: exporting and publishing your bookmarks as structured, readable data. This isn't about archiving every page you've ever saved (a monumental task), but about archiving the act of saving itself—the collection, its categories, its descriptive titles. It’s a snapshot of your digital interests at a point in time, independent of the eventual link rot that will inevitably claim many of its targets. The process is straightforward and takes about twenty minutes.
The How-To: From Browser to Public Record
First, export your bookmarks. In Chrome or Edge, it's under Bookmarks > Bookmark Manager > three-dot menu > Export bookmarks. Firefox has a similar option in Library > Bookmarks > Show All Bookmarks > Import and Backup. This gives you an HTML file. Open it. You'll see it's a nested list of links, a structure any web crawler can read but no human would want to. The next step is transformation.
Take that HTML file and run it through a simple converter script (a quick Python script using BeautifulSoup, or a tool like Pandoc) to turn it into a clean Markdown or JSON file. The goal is to strip the browser cruft and leave a plain list: category folders as headings, each bookmark as a line with its title, the URL, and the date you added it if the format retains it. This is your core data. Now, annotate it. Add a preamble explaining the context: "This is my research bookmarks from spring 2024, focusing on municipal open data policies." This turns a raw list into a narrative.
Finally, publish this file. Put it on your personal website, in a GitHub Gist, or in a dedicated repository. The key is to give it a permanent URL and a clear open license, like CC0, declaring it a public dataset. You've now done three things: you've created a backup of your curation logic, you've produced a machine-readable dataset others can analyze (imagine studying the bookmark patterns of a hundred researchers), and you've made a small, concrete contribution to the history of digital attention. The links may die, but the map of what you thought was worth visiting remains.
This act flips the script on personal digital preservation. We’re not just saving content; we’re saving context. Future historians might find the 404 pages less telling than the fact that in 2024, a hundred people in a specific field all bookmarked the same obscure policy document. Your bookmarks, in aggregate with others, become a social sensor network for what the web actually was to its users, not just to its crawlers. It’s a modest practice, but in its modesty lies its power: it starts where the archiving impulse already lives, in the simple click of ‘Bookmark This’.
Notes & further reading
A few pages I came back to while writing this:
- Simi Valley, CA
- The Impermanence Imperative: Why Some Digital Data Should Be Allowed to Die
- Stockton, CA
- The Unseen Architect: How a 19th-Century Librarian Anticipated the Web's Memory
- Sunnyvale, CA
- The Click That Broke the Chain: On Digital Provenance and a Single Broken Link
- Thousand Oaks, CA
- Torrance, CA
- Aurora, CO
- Colorado Springs, CO
- Denver, CO
- Fort Collins, CO
- Lakewood, CO