What a blog post needs in 2026
A date and some words used to be enough. Here's everything else I think a blog post should have now, with this blog as the example.
A few days ago I wrote about what a website needs in 2026. This is the same idea one level down: not the site, but the page you're reading right now.
A blog post used to be a title, a date and some words. It still is, and the words are still what matters. But a lot has changed around them: people arrive from a search, a shared link or an AI tool, often on a phone, and often years after you wrote it. A good post helps all of them.
Every item below is something this blog does, with a link so you can see it working. Most of it was built with an AI coding agent, which is exactly why I'm writing it down: it won't add any of this unless you ask.
Knowing where you are
The first thing a reader needs is context: what is this, when was it written, and how long will it take.
- A real date. Not "3 days ago", which is wrong the moment the page is cached, but the actual date, in a
<time>element so machines can read it too. Look at the top of this post. - Reading time, next to the date. It's a small thing, but it tells you whether to read now or later.
- A warning on old posts. This blog goes back to 2004, and a lot of what I wrote then is wrong now. Posts five or more years old get a note saying so, like this one from 2005. The links, the prices and the advice may have aged badly, and the reader deserves to know before they follow any of it.
- Breadcrumbs, categories and tags. Above the title you can go back to the blog or to the post's category, and the tags below it filter the blog to everything else on that subject.
- The right language. About half my posts are in Spanish. Each one says so in its
langattribute, so screen readers pronounce it properly and browsers offer to translate the right thing.
Finding your way around
Long posts need a map, and every post needs a way out that isn't the back button.
- A table of contents, but only for posts long enough to need one: five headings or more, like this one. On a wide screen it sits beside the post and follows you down. On a phone it's a bar under the header that opens into a list. Either way, it highlights the section you're reading, and on a phone it scrolls the list to that section when you open it.
- Links to every heading. Every heading has an
id, and a#link appears when you hover over it, so you can share a link to one section instead of the whole post. - A reading progress bar at the top of the window, done with a scroll-driven animation in CSS alone. It's hidden for anyone who prefers reduced motion.
- Older, newer and random. At the end of every post: the one before, the one after, and a random one. The random link is the one I use most; after more than twenty years, I don't remember half of what's in here.
- Series. Posts that belong together say so. This is the second part of one: the box at the top gives your place in it, part 2 of 2, and links to the other parts, in order. A post joins a series with one line in its frontmatter.
- Related posts, scored by shared tags and categories, in the post's own language first. Someone reading an English post wants English posts, even if a Spanish one is a slightly closer match.
- Keyboard shortcuts. J and K go to the older and newer post, and R then P picks a random one. Press ? to see them all.
- On this day. The blog's front page shows what I wrote on this date in earlier years, or that week if there's nothing for the day itself.
Being understood by machines
A post is read by search engines, social networks, feed readers and AI tools long before most people see it.
- Structured data. Each post has a schema.org
BlogPostingin JSON-LD: its title, dates, author, language, keywords and image. ABreadcrumbListgives search results the same path the breadcrumbs show, and the blog's front page describes the wholeBlog. Posts in a series are also part of aCreativeWorkSeries, with their place in it. Google's Rich Results Test will show you what it finds. - A share image for every post, generated from its title, summary, date and reading time. Here's the one for this post. Nobody has to design an image for each post, and every link still looks right wherever it's pasted.
- The usual tags: a canonical URL, a description, Open Graph's
article:published_timeandarticle:tag. - An RSS feed, with each post's title, date and summary. Feed readers are still the best way to follow a blog, and the people who use them are the readers you most want to keep.
Sharing and talking about it
A post should be easy to pass on, and easy to reply to.
- A share button (next to the tags) that copies the link, shares it to Bluesky, X or LinkedIn, or opens your phone's own share sheet through the Web Share API.
- Comments from Bluesky. A post can point to a Bluesky thread, and the replies show up underneath, like they do on the website post. No comment system to run, no spam to moderate, and the conversation happens where people already are.
Content that holds up
The words are the point, but the things around them need to work too.
- Code you can copy. Code blocks are highlighted when the site is built, not in your browser, label their language, and have a copy button.
- Footnotes that link down to the note and back up to where you were.1
- Tables that scroll sideways on a phone instead of breaking the page.
- Images that fail quietly. Some of my old posts link to images on sites that died years ago. Rather than a broken-image icon, they just disappear.
- Embeds that load lazily and run in a sandbox, so a YouTube video or a map can't slow the page down or reach into it.
- A kitchen sink. One hidden post uses every one of these things at once, so when I change a style I can see everything it affects on a single page.
So, if you're writing a blog in 2026
Most of this is invisible, and most readers will never notice any of it. That's fine: it's there for the one who arrives from a search in 2035, on a phone, reading a post from 2005 in a language their browser has to translate.
- Show the real date, and say when a post is old.
- Help people find their way, in the post and out of it.
- Tell machines what the page is.
- Make it easy to share and to reply.
- And then, write something worth all that.