I used to treat customer acquisition as the work that came after building a product. That left the hardest questions until launch: who needs this, how will they find it, and why would they choose it?
Now I’d plan product scope, search pages, and distribution together. I’d start with the customer’s problem, build a focused tool, and reach potential users while development is still underway.
Building the product was the predictable part
Building the product was the most honest of the three jobs. Not easy, but the feedback loop is direct: you ship something, it works or it doesn’t, and you can tell which within minutes.
The discipline was deciding what not to build. Every resume tool eventually drifts toward becoming an HR suite (cover letters, interview prep, job trackers) because every competitor page suggests it. I kept the surface small on purpose: one job, one output, one file done well.
That job belonged to one user type: a person staring at a blank page before an application deadline, who wants a clean, readable, machine-parseable resume without handing over their email first. Every feature debate came back to one question, does this help that person finish tonight?
I expected the roadmap to come from my plans. It came from questions instead, and the pattern was consistent: people didn’t want more features, they wanted fewer ways for the file to break. Formatting, export quirks, whether a parser could read the thing cleanly. That’s the MVP lesson I’d underline for anyone building a SaaS product on a budget, the code is cheap, but scope is expensive. Let usage argue for the roadmap, not your competitor’s feature page.
I picked one of the hardest SERPs on purpose
I knew going in that “resume builder” is one of the most contested commercial searches in existence. What I underestimated wasn’t the competition. It was the clock.
The data is blunt. An Ahrefs study from May 2025 tracked a million randomly published pages and found only 1.74% reached Google’s top 10 for any keyword within a year, down from 5.7% in their original 2017 study. Roughly 73% of pages sitting in the top 10 today are more than three years old, and the average page at position one is about five years old. Ranking fast is the exception that usually belongs to big, established domains.
Semrush ran its own version of this experiment with 28,000 brand-new domains, published in March 2023. About 41% of the domains that survived the year touched the top 10 at some point, but only 19% got there and stayed. And 92% of the domains that held top-100 positions for all 13 months had at least one backlink. New domains don’t mostly fail at getting indexed. They fail at holding ground, because they have nothing holding them up.
Even the boring first step takes longer than you’d guess. Google’s own SEO Starter Guide says some changes show up in hours while others take months, and that there’s no guarantee a new page gets indexed at all. John Mueller put it concretely in a Search Relations video covered by Search Engine Land in June 2021: indexing alone can take “several hours to several weeks,” and being indexed says nothing about how prominently you’ll be shown.
The practical takeaway for a fresh domain is humbling. Head terms like “resume builder” and “free resume templates” are gated by domain age and link profiles you don’t have yet, no matter how good the page is. The realistic entry points are the long-tail patterns, the format-and-role combinations people type when the deadline is real. “Resume format for career change,” not “resume.” That’s not a consolation prize. For a new site, it’s the whole strategy.
Template pages are the logic that fits a resume tool
A resume tool almost begs for template pages (one per job title, format, and situation) because that’s literally how people search for this stuff. Programmatic SEO is the practice of publishing keyword-targeted pages in bulk from a repeatable template, one page per search pattern. Done right, it’s the most natural growth motion a tool site has.
The resume niche even has a textbook example. Canva’s template and feature landing pages (around 310 ranking pages pulling an estimated 13 million monthly organic visits, per Ahrefs’ September 2026 programmatic SEO guide) show how far the model scales. Notion’s template category pages work the same way: hundreds of pages, each mapped to one intent.
But that same guide quotes John Mueller’s warning that programmatic SEO is “often a fancy banner for spam,” and notes that Lily Ray tracked more than 70 companies hit by Google’s early-2026 updates after scaling thin content at speed. Bulk publishing is a multiplier, not a strategy. A template page earns its place only if it’s the best answer for that query, a real example, actual content suggestions, formatting notes that apply to a real application. Not five sentences above a download button.
So my rule became: the template is the shape of the page, not the substance. Where I could add something unique (role-specific bullet examples, formatting guidance, an editable version of the example) the page justified itself. Where I couldn’t, I left it unpublished. Thin pages don’t just fail to rank. Enough of them can drag the rest of the domain down with them.
AI cut the clicks and rewrote the category
On the product side, the machine-reading layer is now universal at big employers. Jobscan’s August 2026 report detected an applicant tracking system at 97.4% of Fortune 500 companies. Formatting for parsing isn’t a niche anxiety; it’s table stakes. And with AI helpers now standard on both sides of the application, the bar for a resume tool moved too, the value shifted from “generate text for me” toward helping someone sound like themselves and get the formatting right, because recruiters are drowning in near-identical generated applications.
On the discovery side, the click math changed. AI Overviews are Google’s AI-generated answers shown above the traditional results. Ahrefs’ April 2025 study of 300,000 keywords found the top-ranking page got 34.5% fewer clicks when an AI Overview appeared above it. Their February 2026 follow-up put the drop at 58% for position one, easing to about 19% at position ten. Ahrefs’ own conclusion: search is becoming zero-click.
For a tool site, that reframes the content plan entirely. Informational posts like “how to write a resume summary” are exactly the queries AI Overviews answer for free. You can rank and still get nothing. Tool pages and template pages are where intent survives, because at some point the person needs to actually use something. I’d weight a new site toward pages that lead to the tool rather than pages that compete with the AI’s answer.
Distribution is a habit, not an event
I treated launch as the moment distribution would start. Backwards. Everything that compounds (community familiarity, directory listings, inbound links) only works if it already exists on the day you need it.
Launch spikes are real, but they’re one-day events. One Indie Hackers post nails the metaphor: a launch is a store’s grand opening, not the business itself. The author watched traffic fall from over a thousand visitors on launch day to a few hundred a day within the week, and argues that’s normal, the baseline is the real business, not the spike.
What I’d start before launch next time, in roughly this order. First, showing up in the communities where the target user already hangs out, answering resume-formatting questions without dropping a link. Second, getting listed in product directories and free-tool roundups while the site is still in beta, so the listings are live on launch day. Third, building one useful free asset (a template, a checklist) that gives people a reason to link to a domain that has no authority yet. Free tools are bait, and the fish need time to find the bait.
Why do distribution plans die after launch? Because launch has a date and a checklist, and distribution after that is amorphous. The fix is to make it scheduled work, a standing weekly block for communities, outreach, and pages. A solo founder will always pick the build queue otherwise, because shipping code feels like progress and posting in a subreddit doesn’t. Both are the job.
What I assumed vs. what actually happened
| What I assumed | What actually happened |
|---|---|
| A better product would rank on quality | Rankings ran on age and links; product quality helped retention, not positions |
| I’d write the blog after shipping the tool | Content needs months before it can rank; the blog should have been first |
| ”Resume builder” was the keyword to win | Head terms stayed out of reach; role-and-format long-tail pages were the realistic lane |
| Launch day would kick-start growth | The spike lasted about a day; baseline traffic returned within the week |
| AI Overviews were a passing shake-up | Click loss deepened from about 34.5% in April 2025 to 58% by February 2026 |
| Users would ask for the features I’d planned | They asked for fewer broken exports and cleaner formatting instead |
The order I’d repeat next time
- Start with search patterns, not the feature list. Look at how people actually describe the problem (formats, roles, situations) and let that shape both the product and the page map.
- Build the narrowest tool that’s useful. One user type, one output, done well. Every extra feature delays launch and dilutes the message.
- Publish the first template pages before launch. They need months to rank anyway, so the beta site can carry them while the tool settles.
- Work communities and directories during the build. Familiarity, feedback, and listings should exist before the day you ask for attention.
- Ship one free, linkable asset with the product. Something worth citing gives a fresh domain its first legitimate links.
- Prune after the first few months. Kill or rewrite the pages that got impressions but no clicks, and double down on the patterns that moved. Scale only what proved itself.
FAQ
What did building a SaaS product teach you about SEO?
Patience and page selection. Ahrefs’ May 2025 study found only 1.74% of newly published pages crack the top 10 within a year, so plan in seasons, not weeks. The controllable part is picking pages a fresh domain can actually win (specific, long-tail, useful ones) and not burning months on head terms you can’t hold.
How do indie founders handle distribution without a team?
With small, recurring blocks of work instead of big pushes. Communities, product directories, free tools, and honest build-in-public updates cover most of a solo founder’s early distribution. The key is starting while you build, so the launch day has an audience to reach and listings that already exist.
What matters more: product or distribution?
Neither wins alone, but they fail differently. A great product nobody finds earns nothing, and a well-distributed product that breaks on first use earns refunds. If I had to rank them for a solo founder: distribution is the one most systematically postponed, so give it the earlier slot in the calendar.
How do you SEO a brand-new tool?
Target long-tail, tool-adjacent pages (templates, examples, role-specific patterns) where intent ends at your product. Publish few pages with real substance rather than hundreds of thin ones. Get your first links with a useful free asset. Then give it months; Google’s guidance on timing runs from hours to months, and rankings lag indexing further.
Is a crowded niche worth entering?
Crowded means demand is proven and the paths are mapped. You pay for that with a slower climb, so you need an actual angle, for me it was privacy: a builder that keeps your draft on your device and works without an account. The entry point isn’t the head term; it’s the long tail plus the one thing incumbents won’t copy quickly.
How long before a new site gets meaningful search traffic?
Measure in quarters. Semrush’s tracking of 28,000 new domains found about 41% touched the top 10 within six months, but only 19% got there and held it. Between indexing, ranking, and AI Overviews absorbing clicks, allow six to twelve months, which is exactly why the SEO and distribution work has to start before the build is finished.
Sources
- Patrick Stox, “How Long Does It Take to Rank in Google? [New Study]”, Ahrefs, May 2025
- “AI Overviews Reduce Clicks”, Ahrefs, April 2025; update by Ryan Law, “AI Overviews Reduce Clicks [Update for 2026]”, Ahrefs, February 2026
- Olga Andrienko, “How Long Does It Take to Rank Higher on Google”, Semrush, March 2023
- Louise Linehan, “Programmatic SEO”, Ahrefs, updated September 2026
- “SEO Starter Guide: The Basics”, Google Search Central
- Barry Schwartz, “Google on how long it takes for pages to be indexed and ranked”, Search Engine Land, June 2021
- “Fortune 500 ATS Usage Report”, Jobscan, August 2026
- “Product Hunt is a Grand Opening, not a Savior”, Indie Hackers
