Writing a comparison page that says 'not affiliated': honest competitor mentions for SEO
I needed a page that would rank for a search term people actually type: the name of a big, well-known downloader. My own site is small and new, and nobody searches for its name yet. People do search for the big names, th
I needed a page that would rank for a search term people actually type: the name of a big, well-known downloader. My own site is small and new, and nobody searches for its name yet. People do search for the big names, though, and for alternatives to them. So I built a comparison page that names the competitor, explains what my tool does differently, and carries the words "not affiliated" in plain sight.
The idea sounds like a trick. It should not be one. The page only works if it is honest, because a comparison page that lies about a competitor is the fastest way to lose a visitor's trust. Here is how I approached it.
Name the competitor, then stop selling
The first decision is which name to target. I picked the biggest tool in my niche, the one whose name people type when they want to download a TikTok video. The page title and H1 carry that name next to the word "alternative", which is what people search for when the big tool is down, slow, or full of pop-ups.
Then I made a rule for myself: the page may mention the competitor, but it may not claim anything about them I cannot verify. No "they sell your data". No "they are unsafe". No invented weakness. If I cannot prove it, I do not write it. What I can say, truthfully, is what my tool does: no sign-up, no watermark games, the formats labelled honestly. That is the comparison. My tool against a standard, not my tool against a straw man.
The "not affiliated" line is not decoration
Every comparison page I wrote carries a short line near the top: we are not affiliated with, endorsed by, or connected to the named service. I put it there for two reasons.
The first is legal common sense. Using another brand's name to describe what your own product does is nominative use β the same way a repair shop can say "we fix iPhones" β but that only holds while you are genuinely describing, not pretending to be them. The disclaimer makes the relationship clear to a visitor in one glance.
The second reason is trust. A visitor who lands on a page that names a famous tool wants to know immediately whether they are on the real site or a copy. The honest answer β no, this is a different tool, here is what it does β is the only answer that keeps them reading. If they feel tricked, they leave.
The table has to be true
The middle of the page is a simple comparison table: feature, them, us. I keep the rows to things I can check in a minute. Does it need an account? Does it work on a phone browser? Does it label audio honestly instead of promising an MP3 that does not exist? Each row is a fact, not an opinion, and I leave out any row where I would have to guess.
I also wrote the limits of my own tool into the same page. If a format tops out at 360p with sound, the page says so. If a platform's links sometimes fail, the page says that too. That sounds like bad marketing, but it is the reason visitors stay: the page reads like it was written by someone who actually built the thing, because it was.
Why this helps search at all
Search engines do not reward the word "alternative" on its own. They reward pages that answer the question behind the search. Someone typing a big brand's name plus "alternative" is asking: is there something simpler, and can I trust it? A page that names the brand honestly, disclaims the connection, shows a true table, and admits its own limits answers that question in full.
That is the whole technique. There is no cleverness to it, which is the point. A comparison page is a trust exercise dressed up as SEO, and the SEO only works if the trust part is real.
I built the page on ramrom.io, where the TikTok downloader it describes actually runs, so anyone reading it can try the tool in the same visit and judge for themselves whether the comparison was fair. That is the test I keep coming back to: if the page cannot survive the visitor trying the thing, the page is not finished yet.
Originally published by Dev.to WebDev. Aggregated on AIWithGhost for educational purposes β full credit and traffic to the original publisher.