I run a small video downloader site with eighteen pages. Every one of them needs a meta description, and I wrote all eighteen by hand. No template, no loop, no string interpolation. Here is why I made that awkward choice.
The temptation to template
My pages share one layout. The same PHP include prints the head section, the same CSS, the same footer. So the obvious move was a template: "Download " . $platform . " videos free — no watermark, no sign-up." One line, eighteen descriptions, done before lunch.
It would have been consistent. It would also have been wrong.
What a page actually promises
The pages look alike, but they do different jobs. The homepage is a general tool. The TikTok page is for someone who typed a very specific thing into Google. The Facebook guide is not a tool at all — it is a long article that explains what works and what does not. A single template cannot describe all three honestly, because they are not the same promise.
So I sat down with the page list and wrote a sentence or two for each, one at a time:
- What does this page do?
- Who is it for?
- What would make them click, and what would they be disappointed to find?
The last question mattered most. A description that over-promises is worse than a dull one. If the page cannot download private videos, the description should not sound like it can. I would rather have fewer clicks from people who stay than more clicks from people who bounce in three seconds.
The practical rules I kept
A few rules made the job manageable:
- Under 155 characters. Google truncates around there on desktop, sooner on mobile. If the sentence does not fit, cut words, not meaning.
- One honest claim per page. The TikTok page says what it does and what it does not. The guides say what you will learn. Nothing says "best" or "fastest" — I cannot prove either.
- Different verbs for different pages. Download, learn, compare, check. If two descriptions start with the same verb, one of them is lying about what the page does.
- No keyword stuffing. The page title already carries the keywords. The description's job is to read like a human wrote it, because one did.
It took an afternoon. Eighteen pages, a text editor, and a character counter. That is the whole tooling.
What I got back
The boring answer is that the site's search results started looking like a real site. Each result in Google says something different, because each page is something different. A visitor deciding between my TikTok page and my Instagram page can tell them apart before clicking. That sounds small. It is the entire job of a description.
The less boring answer is that writing them by hand forced me to look at every page and ask what it was for. Two pages turned out to be doing the same job with different titles. One guide had a title that promised more than the article delivered. I fixed both while I was there.
When templating is fine
I am not against templates. If you have five thousand product pages, write a template and spend your time on the fifty pages that matter. But eighteen pages is not five thousand. At this size, the hand-written version costs an afternoon and buys you something a template cannot: a site where every page can say, in its own words, what it is for.
I build and run ramrom.io, a free video downloader, in plain PHP on shared hosting. No frameworks, no build step — just files, a text editor, and a lot of small decisions like this one.



