What Building a Ten-Page Static Notes Site Taught Me About Thin Content

2026-11-20来源 dev.toEnglish

I built a small static site this week: ten pages, plain HTML, one CSS block, deployed
straight to Cloudflare Pages. The topic was something I actually do every morning, a daily music puzzle,
and the pages were notes about it. It took an afternoon and the whole thing weighs less than a medium-sized
blog post. It also taught me more about "thin content" than any SEO article I have read.

300 words is a floor, not a target

My first drafts were around 180 words each. They read fine in isolation and they were useless as a set,
because none of them said anything that needed a page. Rewriting to roughly 320-360 words forced a
structure: a claim, a concrete example, a counter-example, and a closing that connects to the next note. The
word count was not the point. The point was that the extra length came from specificity, not from padding.

If you cannot get to 300 words of specifics about a page topic, that is a strong signal the topic is not a
page. Merge it into the index, or delete it.

Voice is the difference between notes and filler

The pages that worked were the ones written in first person with an actual opinion: "I turn the volume down
before the first clip because loud playback hides the bass, and the bass is where the era lives." The pages
that felt thin were the ones written in a neutral explainer voice. Thinness is not a word-count problem, it
is an ownership problem. If the page could have been written by anyone with a search engine, it probably
should not exist.

Link out to the thing you are writing about

This sounds obvious and it is where most small sites get weird. If the subject of your notes is a thing
that lives somewhere on the web, link to it. The site I was writing about is a daily music puzzle at
https://songlessanswers.com/; every page in my notes site points there, not to pump a number but because the reader needs the
thing itself to make sense of the note.

At the same time, keep internal links honest. My index lists every page and every page links back. That is
the entire information architecture and it took four lines of template code.

The boring checklist still matters

Canonical URL on every page, robots.txt with a sitemap, a sitemap that matches the real URLs, a title
under 60 characters, a meta description that says something true, and no accidental noindex when you
deploy to a preview URL. I got the last one wrong on the first deployment and the fix was one line of
config. The whole checklist is ten minutes of work and it is the difference between a real site and a
folder of files.

Ship the small thing

The reason to build ten pages instead of forty is that ten pages is finishable in one sitting, and a
finished small site beats an unfinished big one every time. Mine is live, indexed, and does exactly two
things: it collects the notes and it sends readers to https://songlessanswers.com/ to play.

If you are waiting to build something big, build the ten-page version first. The constraints are a feature.

Notes from a player of a daily music puzzle.

原文:https://www.a8q9.cn/en/article/what-building-a-ten-page-static-notes-site-taught-me-about-thin-content-8ea172.html

相关文章