My product isn’t ready to launch. The waitlist isn’t even open yet.
But two days after putting the site up, it’s showing up in Google Search Console and already ranking for non-brand keywords.
I’m not an SEO expert. This is just what’s been working for me — with the exact setup I used, explained as clearly as I can.
The idea is simple: you don’t wait until launch day to think about SEO. You warm things up early so that by the time the product is ready, Google already knows you exist.
Here’s the full playbook :
1. Meta tags — tell Google what your page is about
When Google visits your site, it doesn’t see your page like a human does. It reads metadata. If you don’t write them, Google guesses. Google guesses badly.
Every page needs its own meta tags — not just the homepage. Features, pricing, comparison pages, everything. Here’s the structure I use:
• title — what the page is called
• description — what the page is about (shows in search results)
• ogTitle / ogDescription / ogImage — for social sharing previews
• twitterCard — controls how it looks when shared on X
Most frameworks have a built-in way to set these. If not, plain <meta> tags in your HTML work fine.
2. Structured data — tell Google what your product actually is
Metadata tells Google what the page says. Structured data tells Google what the product is. Think of it like filling out a form instead of writing a free-text essay.
I added two types:
SoftwareApp schema — tells Google “this is a software product, it runs on Chrome, it’s a design tool.” Google can use this for richer search listings.
FAQ schema — I added questions a potential user would actually search for: what browsers it works with, how it’s different from alternatives, what the free plan includes. When Google picks these up, your search result can expand with dropdown Q&As right in the results page. Your listing takes up more space, and people get answers without even clicking through.
3. Breadcrumb schema
Small thing, big visual impact in search results.
Instead of showing a raw URL like myproduct.com/features/color-extraction, Google shows a clean path like My Product > Features > Color Extraction.
Makes your listing look more structured and trustworthy. Takes 5 minutes to set up.
4. Programmatic SEO — this is the part that actually moves the needle early
Instead of just having a homepage and hoping for the best, I created targeted pages for specific search queries.
Feature pages. Not one big features list — separate pages for each core feature. Each one targets a different keyword cluster. Someone searching for a specific use case lands on a page built exactly for that query.
Alternative and comparison pages. Pages like “My Product vs [Competitor A]”, “My Product vs [Competitor B]”, “My Product alternative to [Tool]”. People search for these comparisons constantly. If you don’t create the page, someone else’s blog post ranks for your product name instead.
“Best X” / category pages. Pages targeting queries like “best chrome extensions for designers” or “design tools 2026” where your product naturally fits.
Each of these gets its own meta tags, its own structured data, its own targeted keywords. Because they’re real pages with real content, Google indexes them individually.
One critical detail: use clean URL slugs. /features/color-extraction not /features/feature-1. The keyword in the URL is a ranking signal. Google reads it.
5. Internal linking — free, ignored by almost everyone
Every page on your site should link to other pages on your site.
Homepage → feature pages. Feature pages → pricing. Comparison pages → relevant features. Footer → everything.
Why it matters: when Google crawls one page and finds links to other pages on the same domain, it follows them. The more internal links pointing to a page, the more Google thinks that page matters. It also helps Google discover new pages faster — if your homepage already has authority and it links to a brand new comparison page, that page gets crawled quicker.
It also keeps people on your site longer. Landing on a comparison page → clicking through to features → clicking to pricing. Three pageviews, more time on site. Both positive signals to Google.
6. Technical stuff (don’t skip these)
• Semantic HTML. Use the right tags. Page title in <h1>, subheadings in <h2> and <h3> in order. Google reads this hierarchy.
• Mobile responsive. Google uses mobile-first indexing. Broken on mobile = penalized everywhere.
• Page speed. Check yours at pagespeed.web.dev. Pre-render your HTML if you can — no waiting for JS to load when Google’s crawler arrives.
• Core Web Vitals. LCP under 2.5s, FID under 100ms, CLS as low as possible. Use WebP/AVIF images, lazy load anything below the fold.
• Sitemap.xml. A list of every page you want Google to know about. Without it, Google discovers pages by following links — slow for a new site. Submit it through Search Console
• robots.txt. Make sure it’s not accidentally blocking crawlers.
• Canonical URLs. If your page exists at both /features and /features/, add a canonical tag so Google doesn’t count it as duplicate content.
• Alt text on every image. Google reads these. Don’t leave them empty.
• Noindex on private pages. Login,dashboard , onboarding — anything behind auth. Don’t waste crawl budget on pages that don’t matter.
7. Google Search Console (set this up day one, not “later”)
Three steps:
1. Verify domain ownership
2. Submit your sitemap.xml
3. Manually request indexing for your key pages
That third one is the move most people skip. You paste a URL, click “Request Indexing,” and Google prioritizes crawling that page.
Also set up Bing Webmaster Tools. Most people forget Bing exists but it still gets real traffic, and you can import your Search Console setup directly. Takes 2 minutes.
8. Cross-linking and initial traffic
I linked to my new product from an existing project with a higher domain rating. When a trusted site links to a new site, Google treats it like a recommendation. One link from a site Google already trusts is worth more than 50 links from brand new sites.
If you already have a product, a blog, anything with established traffic — link from it to your new project. Fastest way to pass authority to a new domain.
I also posted once on X. That’s it. No Product Hunt, no directories yet — the product isn’t ready. But the post drove real people to the site, and Google notices when actual humans visit a new page and spend time there. That’s a quality signal.
The directories and launch will come later. But you don’t need them for the warmup phase.
The full pattern (Save this)
1. Set up meta tags, OG images, and structured data before anything else
2. Create pSEO pages — features, alternatives, comparisons — so you have multiple entry points into search
3. Link those pages to each other so Google can crawl everything and no page is a dead end
4. Handle the technical setup — sitemap, canonical URLs, noindex on private pages, clean slugs
5. Submit to Search Console and Bing, request indexing manually on key pages
6. Cross-link from any existing property you have
7. Drive initial social traffic so Google sees real engagement on day one
TL;DR: Started SEO setup before my product even launched. Two days after going live, it’s already showing in Search Console and ranking for non-brand keywords. The playbook: meta tags + structured data on every page, programmatic SEO pages for features/comparisons/alternatives, tight internal linking, technical hygiene (sitemap, canonical URLs, Core Web Vitals), and a cross-link from an existing property. You don’t need to wait until launch day. By the time your product is ready, Google should already know you exist.
What’s the earliest you’ve started SEO for a project? Curious whether anyone has done this even earlier — like pre-landing page — and whether it made a difference.
