A personal changelog is a dated list of what you changed on your homepage and why you changed it. Software teams publish one because it does two jobs at once: returning readers see what moved, and the person writing it gets proof that the work is moving. Personal pages almost never have one, which is strange given how much quiet iteration goes into them.
The usual pattern is that a homepage gets treated as something you finish. You pick a theme, paste five links, publish, and stop. Eight months later the page reads as abandoned, and you cannot remember which version of your intro line worked better. A site changelog fixes both halves of that problem. It gives small changes somewhere to live, and it gives visitors a reason to come back.
## What is worth logging
The threshold should be low. If you are asking whether a change deserves an entry, it probably does.
Three categories cover most of it. Content changes: a new project, a rewritten bio, a removed section. Design changes: a new theme, a different accent colour, tighter spacing, a new portrait. Structural changes: sections reordered, a contact block moved above the portfolio, an updates feed added. Anything you would mention if someone asked what you did to the page this month belongs on the list.
What does not belong: fixing a typo, swapping one link for another, or anything a visitor would never notice. Logging those turns the changelog into noise, and noise gets deleted in the next cleanup.
## How to iterate a personal site without rebuilding it
Full redesigns are where good pages go to die. The version after a redesign is usually worse for two or three weeks, because you changed six things at once and cannot tell which one cost you the enquiries you used to get.
Change one thing per sitting instead. Swap the headline, leave it for a week, and watch whether anyone repeats it back to you. Then move the contact block. Then cut a section. Then decide about the theme. Each step is reversible, and each one teaches you something about the page you actually have rather than the one you imagine.
## Where the changelog goes
Three placements work, and the right one depends on how much space you have.
| Placement | Format | Best for |
|---|---|---|
| Dedicated section at the bottom | Three to five dated lines | Most pages; costs no attention from first time visitors |
| Inside the updates feed | One entry per month, tagged | Pages that already update weekly |
| Separate page linked from the nav | Full archive | People whose page is also their work log |
A short visible section beats a hidden archive. Three recent entries with dates do more for a visitor than a complete history nobody scrolls to.
## A format that takes ten minutes
Keep three fields per entry: date, what changed, and one line on why. The reason line is the one people skip, and it is the one that carries the value. "Moved contact above the portfolio" is a record. "Moved contact above the portfolio because two people said they could not find it" is information you can act on six months later.
Write entries newest first. Cap the visible list at five and move the rest to an archive, or just let them fall off. Nobody is auditing you.
## FAQ
- Do I need a changelog if my page rarely changes? Then the changelog records that it rarely changes, which is itself useful. One entry a quarter is fine.
- Will visitors see my drafts and half finished ideas? No. Log changes you shipped, not plans.
- Does an old changelog make the page look stale? Only when the last entry is from two years ago. If you stop updating, remove the section rather than leave it as evidence.
- Does this matter for search? Slightly. Dated updates signal a maintained page, and a maintained page is easier to justify linking to. The bigger effect is on you, not on rankings.
## Start tonight
Open your page, add a small section at the bottom called Updates, and write three entries from memory for the last three months. Date them roughly. It takes ten minutes and it is the only part you cannot do later, because in another month you will not remember what you changed.
Start from the [homepage](/), and if the wording is the part you keep rewriting, the [copy self-check](/blog/cut-homepage-copy-by-half) gives you a shorter list to argue with. When you want the updates to show up as content rather than a log, the [updates section](/blog/update-personal-site-posts) is where they belong.