Going up against a calculator site that outranks everyone: 3 weeks in
Three weeks ago I started building a UK salary calculator. The niche is brutal. The top three results have been there for years, one of them ranks for basically every "[salary] after tax" query in the country, and they all do the same thing: type a number, see your take-home.
I didn't want to build the same tool with a different colour scheme. So I picked one thing they all ignore.
Every calculator tells you your take-home pay. None of them tell you what you actually earn per hour once you count the unpaid stuff. If you're on 35k but commute 90 minutes a day and do six hours of unpaid overtime a week, your real hourly rate is a lot lower than the number on your payslip. I built that into the calculator and called it True Wage. You put in your commute and your actual hours, and it works out what you're really earning against what your contract says.
A few things I've learned so far:
The incumbents are beatable on speed. Most of them load a heavy consent popup with 200-plus ad partners before you can touch the tool. Mine is a static site on S3 and CloudFront, no framework, loads in under a second. That alone is a ranking signal and it's the cheapest edge to get.
Programmatic pages are a trap if you're lazy. I generated a page per salary band, but a thousand near-identical pages get you de-indexed fast. Each one needs genuine unique text or Google bins it. I'm still working through that.
Getting the first organic click took six days and felt better than it should have.
The stuff I'm still stuck on:
How do you earn backlinks in a boring niche without buying them? I looked at a competitor with 284 referring domains and every single one was spam, injected blog comments on firmware sites and Romanian forums. Worthless. I'd rather have ten real ones.
If you've built in a saturated niche, how did you find the angle the incumbents missed? True Wage was mine, but I got lucky spotting it.
Tool's here if you want to poke holes in it: https://salarychecker.uk
Happy to answer anything about the static-site setup or the SEO side.
The True Wage angle is the right differentiation. Not a calculator with a different colour scheme but a fundamentally different question: what you actually earn, not what you nominally earn. Most people haven't seen that framing but will immediately get it.
The SEO implication is good too. Queries like 'how much do I actually earn per hour' and 'real hourly rate including commute' have no clean answer anywhere right now. The established sites won't pivot to cover them because it complicates their core tool. That's the gap.
The content play that reinforces this: case studies. 'I thought I earned £35k but my True Wage is £11.20/hr' is the kind of specific, shareable story that drives both backlinks and return visits. Reader submissions or forum threads around True Wage comparisons by industry could compound fast.
Three weeks is almost no time in SEO. Are you seeing any organic impressions at all in Search Console yet?
On outranking them: your edge isn't just speed, it's that you answer questions the incumbents don't have pages for. "Real hourly rate after commute" style queries are long-tail they can't match without copying your feature. Build the page per question, not per salary band: one question per URL, headline answer in the first sentence, the number stated in plain text. That format also gets picked up by AI Overviews and the answer engines, which skip ad-heavy pages and cite whatever states a number cleanly. Your per-city True Wage stats could be that source if each one puts its headline figure high on the page. And agreed on the programmatic trap - five genuinely different pages beat five hundred thin ones.
Boring niches earn links with original numbers, not outreach. You are already sitting on the one dataset none of the incumbents have, what people actually work versus what their contract says, so publish a quarterly True Wage report by city and industry and pitch it to UK money desks, because journalists will link to the source of a statistic and will never link to a calculator. Separate note from the investor seat: decide the revenue model now, since a free tool serving ad-blocked traffic is a hobby with a hosting bill.
I do not have ten real ones. I have 22 views in 7 days, almost all Direct. A comment I leave here will also land as Direct or not at all, because this site strips referrers. So "post in communities" is not a backlink plan. It is a reputation plan.
The one Indie Hackers surface that actually passes a referrer is the product page's website button, not the comments. Directories that drop you without ten upvotes are a rental, not a domain. I would rather keep a listing that does not need a vote threshold than a comment that looks like a link in my own notes and is not one in analytics.
Thanks for the insights and advice really appreciate it
On finding the angle: mine came out of the arithmetic, not intuition. I priced 14 tools, then priced the payment routes - the same $1,000 invoice costs $5.00 to $58.30 to receive. The routes were the bigger half. Did you cost the alternatives before picking True Wage, or spot it first?
Consider accepting salary input with commas, the natural way to enter it is with a comma, especially when your reports show a comma.
Good idea thanks
On backlinks: don't pitch 'please link me' — find pages that already link to the incumbents (money guides, university pages) and give them a reason to swap: an embeddable True Wage widget or a surprising stat from your data. One page linking to a tool their readers actually use beats 284 spam domains.
The True Wage idea is good, and I think it creates one problem worth naming early: search only serves demand that already exists, and nobody searches for a concept they have not heard of. It is an excellent retention and word of mouth differentiator and close to useless for acquisition until the phrase spreads on its own. Worth deciding deliberately which of those two jobs it is doing.
The other thing I would look hard at is whether the after tax queries are worth winning at all. Not mainly because of the incumbents' links, though those are real, but because Google answers that query itself. It is a single number and there is a calculator sitting above every organic result. Even at position one you are competing for whatever clicks survive an answer placed above you, which is a much worse prize than the volume implies. Pull the CTR on those terms in Search Console before spending another month on them, because that number tends to be brutal and it is invisible if you only look at rank.
The demand for your actual idea does already exist, it just is not phrased as true wage. It is phrased as is my commute worth it, should I take a pay cut for a shorter commute, is 35k a good salary uk, is it worth doing overtime. Lower volume, far lower competition, and your tool is the best answer on the internet to every one of them, which is not true of anything you could write about take home pay. Those also have no SERP calculator sitting on top of them, because they are not questions with one number as an answer.
What are you seeing in Search Console right now, impressions with no clicks, or no impressions at all? Those mean completely different things at three weeks and the fix for each is the opposite of the other.
On the programmatic pages: the fix that usually works isn't "add unique text" so much as "give each page a unique computation." A salary-band page that shows a different True Wage breakdown, band-specific thresholds, and where that band actually sits in the distribution is genuinely different content even if the prose template is shared. Pages that only swap a number are the ones that get binned. I'd also prune hard — keep the bands with real search volume, noindex the rest, and let the survivors accumulate signal.
On backlinks in a boring niche: the linkable asset is the dataset, not the tool. "Real hourly rate after commute, by city / by sector, updated each tax year" is something a journalist or a Reddit thread can quote, and quoting requires a citation. One annual data page with a clear methodology and a downloadable CSV will out-earn any outreach campaign, and it's the only kind of link that survives an algorithm update.
Small thing worth checking given your S3/CloudFront setup: make sure the calculator's key output isn't only rendered client-side after interaction. If the differentiating content only exists post-JS, both Google and the AI answer engines can miss the exact thing that makes you different.
Really good distinction, unique computation beats unique prose. My band pages already pre-compute the full breakdown server-side, but you're right that they're too close to each other. I'll add the True Wage breakdown per band, band-specific thresholds and where the band sits in the distribution so each page answers a genuinely different question, then noindex the low-volume bands and let the survivors build signal.
The dataset-as-asset point I hadn't thought about hard enough. "Real hourly rate after commute, by city and sector, updated each tax year" with a methodology and a downloadable CSV is a far better link magnet than a calculator. Adding that to the plan.
And yes, the key output renders in the static HTML, not post-JS, so the differentiator is visible to Google and the answer engines without interaction. Good thing to flag though, easy trap to fall into.
true wage is a decent wedge because it's a different question, not a better ui. on backlinks in a boring niche: the thing that works is publishing the data nobody else bothers to compute - eg real hourly rate by city once commute is counted, updated each tax year. journalists and reddit threads link to numbers they can quote, they never link to a calculator. also worth killing most of the programmatic salary-band pages and keeping only the bands people actually search; a hundred pages with real commentary beats a thousand thin ones.
That 139-site number is grim and useful, cheers for sharing it. Median 8.9s against a 2.5s threshold and 3% clearing it. In a field shaped like that, being the only result that behaves like a tool is the whole point. And you've reframed it correctly for me: the speed isn't doing the ranking work directly, it's doing the second-visit work and making every other signal cheaper to earn. I'd been overcrediting it as a direct ranking lever.
Your CSV story is the bit I'll remember. Publishing the open dataset and a week later the only links being ones you placed yourself, honestly counted, is the correction I need to hear before I do the same and kid myself it's earned.
The thing you said to watch for is the smart one: whether anyone re-uses the True Wage figure inside their own argument. A quote in a forum post isn't a link, but it's what comes before one, and it shows up weeks earlier than anything in a backlink export. That's a better leading indicator than refreshing Ahrefs. Thanks.
The speed point is worth more than it sounds, and I have a number for it. We measured 139 US small business sites pulled from local search results: the median took 8.9 seconds to render its main content against Google's 2.5-second threshold, 3% cleared it, and the median page shipped 1.2 MB of JavaScript before doing anything the visitor asked for. In a field shaped like that, "loads in under a second" isn't a marginal edge — you're the only result that behaves like a tool. I'd temper one thing: I don't think the speed is doing the ranking work directly. It's doing the second-visit work, and it makes every other signal cheaper to earn.
On backlinks in a boring niche I have no answer yet, only a correction I had to make on myself this week. We published the raw dataset as an open CSV — every domain, platform and score — on the theory that data gets cited where a tool doesn't. A week in, the only links that exist are ones I placed myself: a canonical-tagged repost on a dev community. Followed, useful for reach, and I'd be lying to my own tracker if I counted them as earned. Third-party domains citing it: still zero.
The 284 referring domains on the incumbent are worth exactly what you concluded. We pulled the same kind of export on our competitors and the shape was identical — the count isn't the asset, and matching it would mean buying the same garbage. What I'd watch for instead, in your niche: whether anyone re-uses your True Wage figure inside an argument of their own. Someone quoting your number in a forum post is not a link, but it's the thing that precedes one, and it shows up weeks before anything lands in a backlink export.
Agreed on all of it. The pages starting to move are the ones with worked examples and answers to the questions that come after someone sees the result, not the ones with more features bolted on. Three weeks is far too early to be thinking about buying anything, and the True Wage angle is distinct enough to build genuine supporting resources around, which is where I'd rather spend the effort. Appreciate the steer.
That matches what I saw on our own calculator. We put a short FAQ directly under the result, and the questions we picked were the ones people ask once they already have a number in front of them: is this a good price, what is included at each level, why flat rate instead of hourly. Those are the pages pulling traffic now.
One thing worth stealing if you have not already. Open the People Also Ask box on your main query and take a question out of it word for word. We found "is $1000 a good price for a website" sitting there, built a page whose heading is that exact question, and answered it in the first 2 sentences. It works because someone typing that has already seen a number somewhere and is checking whether it was fair. Same visitor you get the moment True Wage hands them a figure they did not expect.
I have found the same thing with calculator sites: a narrower use case can be more valuable than adding more features. Speed helps, but the pages that begin gaining traction usually explain the calculation clearly, include worked examples and answer the questions that arise after someone sees the result.
For links, I would not rush into buying them. Three weeks is still very early. A genuinely useful comparison, dataset or calculation guide gives people a better reason to reference the site naturally. Your True Wage angle is distinct enough to build those supporting resources around.
This is a helpful reminder to me - I have built a retirement calculator and find myself this very moment up at midnight cutting back code/ features to make it more simple. Very good advice.
Digital PR is your best weapon for getting high-authority UK backlinks without buying spam links. Personal finance journalists at UK outlets (MoneySavingExpert, Telegraph, Daily Mail, etc.) love data-backed stories. You can use aggregated 'True Wage' data to pitch stories like 'London commuters lose £X/hr in hidden costs' or 'The real hourly rate of a £35k salary'. They'll link to your calculator as the primary source. Sub-second load times on S3/CloudFront against ad-bloated incumbents is a massive UX edge. How are you handling canonical tags across your programmatic salary band pages?
Competing against established sites in a niche like salary calculators can certainly feel daunting, but there are strategies that can help you carve out your own space. Here are some things I've learned from my own experience in a competitive market:
Long-tail Keywords: Instead of trying to rank for highly competitive terms, focus on long-tail keywords that might have less competition but are still relevant. For instance, phrases like “average salary for software engineers in the UK 2024” or “salary comparison tool for graduates” might not have as many searches, but they can attract users who are ready to engage.
Unique Value Proposition: Think about what you can offer that your competitors don’t. Is it a more user-friendly interface, additional insights such as cost-of-living adjustments, or graphical representations of salary data? Consider creating tools or resources (like benchmark reports) that provide added value.
Content Strategy: Develop content around your calculator that’s informative and targeted. Blog posts discussing salary trends, how-to guides on negotiating salaries, or comparisons with regional averages can attract organic traffic while enhancing your site's authority.
Local SEO: Since you’re built specifically for the UK audience, optimize for local SEO by getting listed in local directories and ensuring your site has UK-specific mentions. Utilize Google My Business if applicable, even if your tool is online-only.
Link Building: Start reaching out to relevant sites for backlink opportunities. This might mean guest blogging, participating in industry forums, or collaborating with influencers in the personal finance space who can point their audience towards your tool.
User Engagement: Build a community around your tool. Encourage user-generated content, like reviews or even forums where users can discuss salary topics. Engagement can increase the time spent on your site, which is a positive signal to search engines.
In my own business, I’ve found that focusing on niche areas and building a community has made a significant difference. With every piece of content and feature enhancement, I monitor analytics and adjust my strategy accordingly. It’s a marathon, not a sprint, so patience is key. Keep iterating on your approach!
This is a distinction I needed spelling out. You're right, a comment here lands as Direct or not at all, so posting in communities is a reputation plan, not a backlink plan, and I shouldn't log a comment as if it were a link. Guilty of exactly that in my own notes.
The point about the product page website button being the one surface that passes a referrer is useful, I'll make sure that's set up properly. And "a directory that drops you without ten upvotes is a rental, not a domain" is going straight into how I think about listings. Cheers.
I think picking one thing to do differently was the right move.In crowded niches, making a slightly better version of the same tool probably isn't enough. The harder part is giving people a reason to remember yours.Also curious to see whether the "actual hours worked" angle ends up being something people specifically search for, or more of a conversion advantage once they land on the site.
True Wage is a more interesting wedge than just making another calculator faster.
The harder question may be whether that difference is strong enough to make people choose and remember it, not just notice that it exists.
Hey aryan_sinh - yes I guess time will tell :-)
Yeah, exactly. It’ll be interesting to see whether that distinction holds once you have more usage behind it.