When I rebuilt my video downloader as a plain PHP site, every platform got its own page: TikTok, Instagram, Facebook, YouTube. That made sense, because each one resolves differently and each visitor arrives with one job in mind. But after a few weeks I noticed a problem. People landed on the homepage and had no idea what the site actually did. They saw one link box and one button, and that was it. So I built a tools hub page — one page that explains the whole site — and it turned out to be one of the more useful pages I have added.
The problem was not the tool itself. The downloader worked. The problem was orientation. A visitor who arrives from a search result lands deep inside the site, on a single tool page, with no context. They do not know there are other tools. They do not know the site also handles TikTok photo slideshows, or Instagram stories, or Facebook reels. They see one box, paste one link, and leave, and most of the site stays invisible.
A hub page fixes that in the simplest possible way: it lists everything, in plain words, on one page. Each tool gets a short line saying what it does and a link to its page. No clever copy, no marketing language. The TikTok downloader saves TikTok videos. The Instagram downloader saves reels and photo posts. The Facebook downloader saves reels and videos. That is the whole pitch, and it is honest, because that is genuinely all each tool does.
Building it took an afternoon, and most of that was deciding what to leave out. I kept the layout the same as the rest of the site: the same header, the same blue-and-white theme, the same footer. The page is static HTML, no PHP logic, no API calls. That matters on shared hosting, because a page with no server work behind it loads fast and cannot break when a provider is having a bad afternoon. The only thing it shares with the tool pages is the stylesheet, so one CSS change still fixes every page at once.
The harder decision was what the hub page should not do. It does not run the downloader itself. I thought about putting a link box on it, but that would have made it a second homepage, and a second homepage is exactly the kind of duplicate I had already spent time removing elsewhere on the site. Its job is to point, not to do. A visitor reads it, picks a tool, and clicks through to the page built for that job.
It also solved a problem I had not expected: it gave the site a page I could link to when someone asked what the site was. Before the hub existed, the honest answer was "it is a downloader", and then I had to list the platforms from memory. Now there is one address that answers the question properly. I link to it from the homepage navigation, from the footer, and from the About page, so a visitor can always find their way back to the full list.
There is a search-engine angle too: a hub page gives crawlers one clear map of the site. Each tool page links back to the hub, and the hub links out to every tool page. That is not a trick, just internal linking done the boring way, and it means a new tool page is one link away from a page that already exists instead of floating on its own. When I added the TikTok Slide, Story and Notes pages, they went onto the hub the same day.
The lesson I took from it is a small one, but it keeps coming back: a tool site is not just the tool. The tool does the work, but the visitor still needs to understand what is on offer, and one plain page that says so is worth more than a clever homepage. If you are building a small site with several tools, build the hub page early. It costs an afternoon, it never breaks, and it is the page your visitors actually read when they want to know what you built.
I run the site at ramrom.io, and the hub page is linked from the homepage navigation if you want to see how plain it really is.


