A Blogroll for a Personal Website — Curating Paths Through the Open Web

A personal website can easily become a room where only its owner speaks. You publish notes, projects, and opinions, but readers rarely see the wider neighborhood that shaped them. A blogroll changes that by placing a few well-chosen doors in the wall and inviting people to explore beyond your own pages.

At its simplest, a blogroll is a curated list of websites you genuinely read or recommend. It may look old-fashioned beside algorithmic feeds, but that is precisely its strength: every link reflects a human decision rather than an engagement score. In this guide, I will explain why a blogroll still matters, how to design one that remains useful, and how to implement it without turning it into another maintenance burden.

What a Blogroll Is, and What It Is Not

A blogroll is usually a collection of links to independent blogs, personal sites, newsletters, or small publications. Early blogs often placed this list in a sidebar on every page. Today it can live on a dedicated page, inside an About section, or at the end of a reading page. The location matters less than the editorial intention behind it.

It is not a link exchange disguised as friendship, and it does not need to include everyone who links to you. Think of it like the small recommendation shelf in an independent bookstore. The shelf is useful because someone selected those books, not because it contains the entire catalog. A focused list of twelve sites can reveal more personality than a directory containing twelve hundred unreviewed links.

A good blogroll also differs from browser bookmarks. Bookmarks may include private dashboards, temporary research, and tools you use once a year. A public blogroll answers a narrower question: if someone enjoys this website, where might they enjoy going next?

Why Human-Curated Links Still Matter

Search engines are excellent when we know what we want. Social feeds are effective when we want an endless stream. Neither is particularly good at reproducing the quiet recommendation of a person whose judgment we trust. A blogroll creates that recommendation without demanding an account, an app, or a behavioral profile.

It also gives small websites a form of discovery that does not depend on platform popularity. The open web works more like a footpath network than a shopping mall: each useful link creates another route between places. When personal sites link to one another, readers can move through ideas according to curiosity instead of whatever a ranking system wants to maximize.

There is a second benefit for the site owner. Choosing links forces you to articulate your influences. A list of sites about self-hosting, accessible design, thoughtful writing, and digital independence quietly says something about your values. In that sense, a blogroll is both a map and a self-portrait.

Choose a Scope Before Choosing Links

The easiest way to build an unhelpful blogroll is to add every interesting URL you encounter. Define a scope first. You might feature personal websites you read monthly, technical writers who publish practical experiments, local Indonesian creators, or sites that provide an RSS feed. The rule should be broad enough to allow variety but clear enough to guide decisions.

I prefer three simple inclusion tests. First, I have read more than one page on the site. Second, I would recommend it even if the owner never knew I linked to them. Third, the site adds something distinct to the list. These tests prevent reciprocal-link pressure and keep the page anchored in genuine interest.

You can group links into a few meaningful categories, but avoid building an elaborate taxonomy too early. Categories such as “Web Craft,” “Self-Hosting,” and “Essays” are easy to understand. If a site fits several groups, choose the place where a new reader is most likely to appreciate it. A blogroll is a guided walk, not a database normalization exercise.

Add Context, Not Just URLs

A bare domain name tells a reader very little. Add one short sentence explaining what the person writes about and why the site deserves attention. This context is the difference between a pile of addresses and an editorial recommendation.

Keep descriptions concrete. “A great blog about technology” could describe thousands of sites. “Practical notes on running quiet, low-power home servers” gives the reader a reason to click. Write the description in your own words rather than copying a site's metadata; your perspective is the useful part.

The following semantic HTML is enough for a clean blogroll. A heading establishes the category, while each list item contains a visible site name and a concise annotation:

<section aria-labelledby="blogroll-web-craft">
  <h2 id="blogroll-web-craft">Web Craft</h2>
  <ul class="blogroll">
    <li>
      <a href="https://example.com/" rel="external">Example Site</a>
      <p>Careful essays about durable, accessible websites.</p>
    </li>
  </ul>
</section>

Regular HTML links make the page understandable to browsers, screen readers, search engines, and archival tools. JavaScript is unnecessary for the essential experience. If styling fails, the list should still remain readable and navigable.

Design for Reading and Accessibility

A blogroll does not need cards, logos, hover animations, or screenshots from every destination. Those additions can make a short page visually heavy and create more assets to maintain. Clear typography, generous spacing, and recognizable links usually serve readers better.

Do not open every external link in a new tab without warning. Many readers know how to choose that behavior themselves, while forced tabs can be confusing for keyboard and screen-reader users. If you display a site's favicon, treat it as decoration unless it communicates information unavailable in text. The site name must remain visible.

Descriptions should not rely on color to distinguish categories. Use headings and list structure so the organization survives high-contrast mode and custom stylesheets. On narrow screens, prefer a single column. A blogroll is closer to an annotated reading list than a product grid, and its design should feel calm enough to browse.

Keep the List Alive Without Chasing Perfection

Links eventually move, redirect, or disappear. That does not mean you need to inspect the page every morning. A lightweight review every three or six months is usually sufficient. Open each destination, confirm that it still represents what your description says, and update broken URLs when an obvious replacement exists.

A small command can identify obvious HTTP failures, although it cannot judge whether a site has changed purpose:

curl --location --silent --output /dev/null \
  --write-out '%{http_code} %{url_effective}\n' \
  https://example.com/

Do not automatically delete a site after one timeout. Personal websites may run from modest servers, undergo maintenance, or temporarily lose a domain. Check again later. If a valuable site is permanently gone, you can link to a preserved copy in the Internet Archive and label it clearly as archived.

It helps to show a “last reviewed” date near the page introduction. This is not a promise that every link works forever; it is an honest maintenance signal. Add new entries slowly, and remove entries when you can no longer sincerely recommend them. Curation becomes meaningful through restraint.

Optional Enhancements That Respect the Reader

If many listed sites provide RSS or Atom feeds, you can include a small feed icon or a separate feed link beside each entry. That lets readers subscribe directly instead of depending on your page for future discovery. Keep the normal website link primary because not everyone uses a feed reader.

You may also publish the list as OPML, a simple format that feed readers can import. This is useful when the blogroll is explicitly a subscription collection. However, an OPML file should complement the human-readable page rather than replace it; names and descriptions provide context that an import dialog cannot.

Another useful detail is a short invitation for recommendations, with no guarantee of inclusion. A contact link is safer and calmer than an open submission form if you do not want spam. Be transparent that the list is personal and editorial. You owe readers honesty, but you do not owe every submitted site a place.

A Small Page That Strengthens the Open Web

A blogroll will not produce the dramatic metrics promised by growth dashboards. Its value is quieter. It helps one reader find one thoughtful writer, gives an independent site a path that no platform controls, and shows that publishing on the web can be a conversation rather than a performance.

Start with five sites you actually revisit. Add a specific sentence about each, use plain semantic HTML, and schedule a modest review later in the year. That is enough. Like introducing friends around a dinner table, the goal is not to maximize the number of connections but to make a few meaningful ones possible.

If you maintain a blogroll or discover a memorable personal site through one, share your approach in the comments. Your recommendation may become someone else's doorway into a more human corner of the web.