Marketing Starts Before the First Commit: The SEO Foundation Indie Hackers Skip

Most indie hackers run marketing in the wrong order. You build for three or six months, ship a launch post, get a spike of traffic from Hacker News or Product Hunt, and then start thinking about "doing marketing." The spike fades in 48 hours, and you discover the uncomfortable truth about the cheapest long-term channel you have: SEO compounds on a clock that started the day your domain went live — not the day you decided to care about it. By launching first and marketing second, you didn't save time. You burned a year of ranking runway.

This isn't an argument for marketing instead of building. It's an argument for setting up the foundation of your marketing — especially the technical SEO of your website — before and during the build, when it's nearly free, instead of after, when it's a retrofit.

Marketing-last is the default, and it quietly costs you a year

The instinct is reasonable: there's nothing to market until there's a product, so build the product first. But that logic only holds for channels with instant feedback — ads, launches, outreach. It's exactly backwards for the channel most indie products eventually depend on. Organic search is a slow-compounding asset. Google has to discover your pages, decide your domain is trustworthy, and watch users interact with your results before it ranks you for anything competitive. That process takes months, and the clock doesn't start until your site exists and is crawlable.

So "I'll do SEO after launch" really means "I'll start the months-long clock after launch" — which means your first year of organic traffic is mostly zero, not because your content is bad, but because you started the timer late.

SEO is the one channel you can't cram

You can cram a launch. You can cram a week of cold outreach. You cannot cram domain age, indexation history, or the slow accumulation of search trust. Those only respond to elapsed time with a real site in place. That's what makes the SEO foundation different from every other marketing task: doing it early is not a nice-to-have, it's the only way to have it at all when you launch.

The good news is that the foundation is cheap to lay before you have code, and expensive to lay after you have 200 pages and existing URLs to migrate.

What retrofitting SEO actually costs

Bolt SEO on after launch and you pay for it in concrete ways:

• URL and structure migrations. You picked URLs without thinking, now you have to redirect them — and every redirect leaks a little authority and risks broken links.
• No domain history. A six-month-old domain with real pages and a few backlinks ranks differently than one registered last week. You can't buy back the months.
• No measurement baseline. You never connected Search Console, so you have no idea which queries you were almost ranking for — the exact data that tells you what to write next.
• Content that has to age from zero. The article you publish on launch day won't rank for months. The article you published while building is already aging by the time anyone arrives.

None of this is hard to avoid. It's only hard to fix.

Set up the correct SEO website before you build

Here's the foundation to lay while the product is still a work in progress. None of it requires the product to be finished.

1. Register the domain now and put a real page on it

Buy the domain the day you commit to the idea. Don't leave it parked — put up a single real page that says what you're building and who it's for, with a way to follow along. A parked page does nothing for domain age that matters; an indexed, meaningful page starts accumulating trust immediately.

2. Decide your URL and information architecture early

Choose your URL structure before you have pages to migrate. Flat, readable, lowercase, keyword-bearing slugs. Decide where the blog lives, how categories work, and how product pages are organized. This is a five-minute decision now and a multi-day migration later.

3. Ship a technically sound site from commit one

Search engines reward sites they can crawl and users can load fast. The baseline:

• Server-rendered or statically generated content so crawlers see real HTML, not an empty shell hydrated by JavaScript.
• A valid sitemap.xml and a sane robots.txt from the start.
• Semantic HTML and per-page title + meta description — unique, descriptive, not auto-generated filler.
• Fast Core Web Vitals. Speed is both a ranking input and a conversion input.
• HTTPS and clean canonical URLs so you're not splitting authority across duplicates.

A modern framework gives you most of this for free if you set it up at the start. Retrofitting server rendering onto a client-only app is a rewrite.

4. Connect Google Search Console on day one

This is the highest-leverage five minutes in the whole list. Verify the domain in Search Console as soon as it's live. You won't have data for weeks — that's the point. You're starting the baseline so that, by the time you launch, you already know which queries you're appearing for, which pages get impressions, and where you're stuck on page two. You can't optimize what you never measured, and the measurement has to start early to be worth anything.

5. Publish problem-space content while you build

You don't need the product to write about the problem it solves. While you're building, publish genuinely useful content in your product's problem space — the questions your future users are already searching. Done early, those articles age and start ranking before launch, so your launch lands on a site that already has organic visibility instead of a blank domain. This is also the most honest form of "build in public": teach the problem, not just the product.

6. Start capturing an audience before launch

The foundation isn't only technical. A simple email capture on that first real page means launch day isn't a broadcast to zero. Every person who follows along while you build is someone who shows up — and converts — when you ship.

Reframe: marketing is a system that runs alongside the build

The deeper shift is to stop thinking of marketing as a launch event and start thinking of it as a system that runs in parallel with development. Every feature you ship is a piece of content. Every week of building is a week your foundational articles are aging into rankings. Every search impression is a signal about what to write next. Treated as a system, marketing compounds. Treated as an event, it spikes and dies.

For a solo founder, the problem has never been knowing this — it's that executing it means juggling Search Console, a keyword tool, a publishing workflow, a rank tracker, and a directory list, none of which talk to each other. So the "start early" advice quietly dies under the weight of the tooling.

Where this gets practical

This is exactly the gap 1MarketingTool is built to close. It's a desktop app that runs the whole marketing foundation as connected pipelines from day one: turning shipped features into blog and social content, scoring keyword opportunities straight from your Search Console data, monitoring your rankings, and submitting your product to directories for backlinks — all locally, on your own machine, with your own API keys, and nothing leaving your device. The point isn't another SaaS subscription; it's making "do the marketing foundation early" something a solo developer can actually run alongside the build instead of postponing until it's too late to matter.

The takeaway

You can defer almost every marketing task until after you launch. The one you can't defer is the SEO foundation, because it runs on elapsed time you can't buy back. Register the domain now, put a real page on it, decide your structure, ship a crawlable and fast site, connect Search Console, and start publishing problem-space content while you build. Start the clock early — by the time you launch, you'll have a year of compounding instead of a year of zero.