Use cases
Why some people write an apology as a private webpage
3 September 2026 · 2 min read
A sorry page probably doesn't fix anything by itself. But a long message sometimes turns into ten half-written drafts before the actual point gets lost entirely, and a small private page gives an apology the room a text thread doesn't: what happened, what you understood, what you'll do differently, and why the person matters.
Why a message doesn't always work
A text has a way of turning into an editing loop: type it, delete it, start again, send something shorter than you meant because the app is staring back at you. A page you write once, away from the pressure of a blinking cursor in an open conversation, tends to end up saying the thing more clearly.
What actually goes on the page
What happened, as plainly as you can put it. What you understood about the effect it had. What you'll do differently. And why the person matters to you. That's the substance of it, in that order, before anything else gets added.
Keep it honest, not a performance
Add a photo or a specific memory if it genuinely belongs there, but don't turn the page into a production. An apology that reads like a performance undercuts itself. The point is honesty, not staging.
Write it, sleep on it, cut the excuses
Write it, then read it again the next morning before sending anything. Excuses have a way of sneaking into a first draft disguised as context. Cut the lines that are really just explaining why it wasn't your fault, and keep the ones that actually say sorry.
This is exactly what a microsite is for
A page like this is personal, sometimes meant for exactly one person, and it has no business showing up in a search result. A MakeMySiteLive microsite is a single HTML page, published in minutes, and never indexed by search engines by default. That keeps it out of search, but it isn't the same as access control: anyone who has the exact link can still open it, the same as any other website. For most apologies that's fine, since you're only ever sending the link to one person anyway. If you want an actual password gate, that needs a Pro full site instead, password protection isn't something a microsite supports.
Key takeaways
- ✓Writing it as a page, away from an open chat thread, tends to produce something clearer than a live text conversation does.
- ✓Cover four things: what happened, what you understood, what you'll do differently, and why the person matters.
- ✓Keep it honest rather than staged, one photo or memory only if it genuinely belongs.
- ✓Sleep on the first draft and cut anything that reads as an excuse rather than an apology.
- ✓A microsite fits this well: quick to publish, and not indexed by search engines by default. That's not the same as password-protected, though, anyone with the exact link can open it; a real password gate needs a Pro full site.
Frequently asked questions
Will a sorry page actually fix things?
Not by itself, and it shouldn't be expected to. It can't ask someone to forgive you. What it can do is help you say the thing properly, without the pressure of an open chat thread.
Will this show up if someone searches for me?
No. A microsite isn't indexed by search engines by default, which matters for something this personal. That only keeps it out of search results though, the link itself still works for anyone who has it.
Can I make sure only one specific person can open it?
Password protection isn't available on a microsite, only on a Pro full site. For something this size it's usually simpler to just keep the link itself private and only share it directly. If you do want an actual password gate, convert the page to a full site first and turn it on there.
What shouldn't go on the page?
Anything that reads as an excuse rather than an apology. Read the draft again the next morning and cut those lines before sending it.