Pre-Launch Marketing Strategy When You Have No Audience
A pre-launch marketing strategy is mostly a scheduling problem. The channels that will carry your launch publish their rules, and those rules decide what you are allowed to do and when, often weeks before you feel ready. Read them first and most of the calendar writes itself.
Every guide on this subject tells you to build hype, collect emails and tease the product. Almost none of them quote the platforms. So this article does the opposite. It reads what Product Hunt, Hacker News and Google publish about launches, quotes it directly, and builds the plan backwards from those constraints. All four documents were read on 26 September 2026. Where a document is silent, we say it is silent.
TL;DR
- Product Hunt lets you schedule a launch up to 1 month in advance, and a brand new account has to wait a week before it can post a product at all.
- Hacker News rules out a Show HN for a landing page or a sign-up page: "Those can't be tried out, so can't be Show HNs."
- Neither platform lets you ask for votes, and both describe the penalty in writing.
- Google's documentation says crawling "can take anywhere from a few days to a few weeks", and that a crawl request does not guarantee inclusion "instantly or even at all". Search is not a launch-day channel.
- To be shown in AI Overviews or AI Mode, a page needs no special file and no special markup. It needs to be indexed and eligible for a snippet.
Table of contents
- Most pre-launch advice assumes an audience you do not have
- The three rulebooks you can read today
- Product Hunt decides your calendar before you do
- Hacker News will not take a landing page
- Google's clock is the one you cannot move
- Being quoted in AI answers needs no special file
- The pre-launch marketing strategy that follows from the documents
- What you cannot buy, in the platforms' own words
- What to measure before launch day
- FAQ
- Where this leaves you
Most pre-launch advice assumes an audience you do not have
Read five articles on pre-launch marketing and you will find the same list: grow an email list, tease the product, line up influencers, build a waitlist, create urgency. Every item on that list works better when people are already listening. On a first launch, nobody is.
So it helps to separate what you control from what you do not. You control the product, the pages you publish, the accounts you create and the words you choose. You do not control votes, the moment Google decides to crawl you, or whether an answer engine quotes you. A plan that spends its energy on the first list and respects the deadlines imposed by the second is the only kind that survives launch week.
That reframing has a practical consequence. Before writing any content, go and read the rules of the two or three places where you intend to show up. They are short, public, and they contain dates and waiting periods that no amount of enthusiasm shortens.
The three rulebooks you can read today
| Channel | Document read | What it decides for you |
|---|---|---|
| Product Hunt | The official Launch Guide and the community guidelines | Who may post, how far ahead you can schedule, what you may ask people for |
| Hacker News | The Show HN rules, the guidelines and the FAQ | Whether your product qualifies at all before it works |
| Google Search | Search Central documentation | When your pages can be found, and whether being found is guaranteed |
Three documents, maybe forty minutes of reading. That is the cheapest research in a launch plan, and it is the part almost everyone skips.
Product Hunt decides your calendar before you do
The first constraint is the age of your account. The Launch Guide states it plainly: "Newly created accounts will even need to wait 1 week before posting a product". It then adds that this is a floor, not a target: "One week is just a minimum, too;" and the guide recommends "joining the platform well ahead of your launch (three months or more)".
The second constraint is who may post. Product Hunt does not accept brand accounts: "We don't allow company or brand accounts to post products or comment." The community guidelines, written by Jake Crump and dated April 11, 2025, say the same thing about profiles: "we require that profiles appear human and represent an individual, not a company, service, brand, or organization". So the account that launches your product is a person, with a real name and a photo, and that person needs to exist on the platform before launch week.
The third constraint is the clock. "You can schedule your launch up to 1 month in advance", and the guide explains why the hour matters: "The homepage runs on a 24-hour cycle based on Pacific Standard Time." Hence the default advice, "a rule of thumb is to schedule your launch for 12:01am PST", so that "Posting at 12:01am PST gives people a full 24 hours to view your product."
Scheduling is also the only sanctioned way to tease a launch on the platform itself. The guide describes it as exactly that: "You can now schedule your launch up to 1 month in advance so that you can tease it," and continues, "drive traffic, and collect followers well before your big day (which we highly suggest!)."
Two of the guide's own figures change what a sensible plan looks like. On who should post: "79% of featured posts were by makers who self-hunted" and "60% of #1 Product of the Day winners were self-hunted", which is why the guide says "You can be the hunter of your own product, and we actively encourage this to give you more control over your launch." On the launch page itself: "70% of products who achieved Product of the Day, Week, or Month had a first comment by the maker." A first comment is a piece of writing you can finish two weeks early, not something to improvise at midnight.
The rest is asset preparation, and the limits are published: a tagline of at most 60 characters, a description of at most 500 characters, up to 3 launch tags, and a gallery that needs two images before it becomes viewable. None of that requires an audience. All of it requires a morning of work before the week of the launch.
One more line matters after the day itself: "You can promote your Launch Page for two weeks after launch day." A launch is a fortnight, not a day, which is a useful thing to know before you plan your own availability.
Hacker News will not take a landing page
Hacker News is where most first-time founders expect to go, and it is the channel where the pre-launch plan most often breaks. The Show HN page defines the format in one sentence: "Show HN is for something you've made that other people can play with."
Then it lists what does not qualify: "Off topic: blog posts, sign-up pages, newsletters, lists, and other reading material." The reason follows immediately: "Those can't be tried out, so can't be Show HNs. Make a regular submission instead." And in case the point was missed: "If your work isn't ready for users to try out, please don't do a Show HN." followed by "Don't post landing pages or fundraisers."
If your pre-launch asset is a waitlist page, that page is explicitly out of scope. The same page also sets a bar that a gated product fails: "Please make it easy for users to try your thing out, ideally without barriers such as signups or emails." A product that can only be joined, not tried, is not a Show HN yet.
The site guidelines add two constraints that apply to the whole pre-launch period, not just to a submission. On promotion: "Please don't use HN primarily for promotion." On votes: "Don't solicit upvotes, comments, or submissions." There is also a line worth reading twice if you were planning to generate your launch copy: "Don't post generated text or AI-edited text. HN is for conversation between humans."
Finally, the FAQ removes the idea of a launch hour: "The basic algorithm divides points by a power of the time since a story was submitted." There is no scheduling, no queue and no reserved slot. The practical conclusion is that Hacker News belongs in the post-launch column of your plan, on the day the thing actually works, and that a regular submission (an article that stands on its own) is the honest pre-launch option.
We have written the same kind of read for another community channel: what Reddit's own rules allow a company to do follows exactly this method, and reaches a similar conclusion about paid shortcuts.
Google's clock is the one you cannot move
This is the part of a pre-launch marketing strategy that cannot be compressed, and Google says so in its own documentation.
On a brand new site: "It can take a few weeks for Google to notice a new site, or any changes in your existing site." The same page offers the only real accelerant, and it is not a button: "Wait a while, and try to get linked from other sites."
On individual pages, the documentation on asking Google to recrawl is equally direct: "Crawling can take anywhere from a few days to a few weeks." And crawling is not indexing: "Requesting a crawl does not guarantee that inclusion in search results will happen instantly or even at all." Both pages carry the same footer, "Last updated 2025-12-10 UTC".
If your instinct is to submit the URL again every morning, the same page closes that door: "Keep in mind that there's a quota for submitting individual URLs and requesting a recrawl multiple times for the same URL won't get it crawled any faster." For volume, the instruction is a sitemap: "If you have large numbers of URLs, submit a sitemap."
The consequence for the plan is blunt. Anything you want to be findable in search during launch week has to be published weeks earlier, because the crawl calendar belongs to Google. Pages that sit in the waiting room have a name and a diagnosis of their own, which we covered in what to do about Discovered, currently not indexed.
Being quoted in AI answers needs no special file
The pre-launch market is full of offers to make your product visible to answer engines. Google's documentation on AI features is unusually short with that idea, in bold on the page: "There are no additional requirements to appear in AI Overviews or AI Mode, nor other special optimizations necessary."
The technical bar is stated as a single condition. To be shown as a supporting link in AI Overviews or AI Mode, "a page must be indexed and eligible to be shown in Google Search with a snippet", and then: "There are no additional technical requirements."
The same page rules out the files being sold for this purpose: "You don't need to create new machine readable files, AI text files, or markup to appear in these features." And there is no schema trick either: "There's also no special schema.org structured data that you need to add."
Two sentences on that page belong in your calendar rather than your to-do list. First, the honest caveat: "Indexing and serving isn't guaranteed." Second, the delay, which is wider than for classic search: "Remember that crawling can take anywhere from several days to several months".
There is, however, a way to disqualify yourself, and it is easy to do by accident. Eligibility runs through the snippet, and the controls that suppress a snippet are the same ones documented on the snippets page: nosnippet, data-nosnippet, max-snippet and noindex. A launch page that blocks previews, or a robots file that blocks crawlers, removes the page from the very surface you were hoping to reach. We unpacked that trade-off in what blocking AI crawlers actually costs you, and the wider mechanics in our guide to generative engine optimization.
The pre-launch marketing strategy that follows from the documents
Put the four documents side by side and the calendar is no longer a matter of taste. It is arithmetic.
| When | What the documents impose | What you do |
|---|---|---|
| 3 months out | Product Hunt recommends "joining the platform well ahead of your launch (three months or more)" | Create a personal account with a real name and photo, and start participating |
| 6 to 8 weeks out | "It can take a few weeks for Google to notice a new site" | Publish the pages you want found during launch week, submit a sitemap |
| 4 weeks out | "You can schedule your launch up to 1 month in advance" | Schedule the launch, and use the scheduled page to collect followers |
| 2 weeks out | Tagline, description, tags and two gallery images are required | Write the assets and the maker's first comment, in full |
| Launch day | "The homepage runs on a 24-hour cycle based on Pacific Standard Time" | Go live at 12:01am PST unless a constraint says otherwise, and answer every comment |
| The fortnight after | "You can promote your Launch Page for two weeks after launch day" | Keep promoting, and post to Hacker News only when the product can be tried without a sign-up |
Two things are worth noticing about that table. Nothing in it requires an audience, and nothing in it can be bought. The only scarce resource is lead time, which is exactly what a founder in a hurry spends first.
The content column is the one most people leave empty. If search needs weeks of lead time, then the articles, the comparison pages and the documentation that answer your buyers' questions have to exist before the launch, not after it. That is also what makes the same work pay twice across channels, which is the argument we make in our guide to one campaign across every channel, and in the more tactical nine social formats from one blog post.
Writing that content column weeks ahead of the launch, in two languages and for three channels, is exactly the work distrify is being built to take off your hands. Join the waitlist
What you cannot buy, in the platforms' own words
Every launch channel sells a shortcut to someone. All three documents close it explicitly, which is worth quoting because the quotes are your defence when an agency offers you the opposite.
Product Hunt, on votes: "Don't ask for upvotes." and "Asking specifically for upvotes is against our policies so we may ask you to stop and remove any social posts, etc." On incentives: "Don't run contests that require upvotes or reward people for upvotes." On paid help: "Please do not pay anyone to hunt or send traffic to your product", with the consequence spelled out, "Spammers will also be permanently removed from the site."
Hacker News, on the same question, in its FAQ: "We penalize or ban submissions, accounts, and sites that break this rule, so please don't." It also explains why soliciting comments backfires: "HN readers are sensitive to this and will detect it, flag it, and use unkind words like 'spam'."
Google, on paying for speed: there is nothing to buy. The quota sentence quoted above is the whole answer, and the only lever offered anywhere in the documentation is being linked from other sites.
What is allowed is narrower and more useful than it looks. Product Hunt states it in one line: "The only real rule here is that you cannot ask people directly to upvote your product." followed by "Instead, ask them to visit and comment." So telling your list that you are live is fine. Telling them what to click is not.
What to measure before launch day
Launch week is the worst possible moment to discover that your pages are not indexed. Two checks a week, from the moment you publish, are enough.
First, indexing: does the URL Inspection tool in Search Console report the page as indexed, and does the sitemap show as read. Second, impressions, not clicks. A new page usually collects impressions on odd, long queries before it collects a single click, and that is the signal that the page exists in the index at all. We described that early phase in the signs that search is working before the first click.
Third, and this is the only number that matters commercially before launch: how many waitlist signups each source sends you. A launch plan with three channels and no source attribution teaches you nothing for the second launch. Once the articles are live, the follow-up work is the same as for any post, which we listed in what to do after publishing.
What not to measure: rankings, in launch week. The documentation quoted above makes that expectation unreasonable, and chasing it is how founders conclude that content does not work after eleven days.
FAQ
How early should a pre-launch marketing strategy start? Take the longest delay in the documents and work back from it. Product Hunt recommends joining "three months or more" ahead of a launch, and Google says a new site can take a few weeks to be noticed. Three months of lead time is not a best practice invented by a marketer, it is the sum of two published constraints.
Can I launch on Product Hunt before the product is usable? The guide does not forbid it, but it lets you schedule ahead specifically so you can "tease it, drive traffic, and collect followers well before your big day". Hacker News is stricter and says the opposite in plain language: "If your work isn't ready for users to try out, please don't do a Show HN."
Is it against the rules to email my list on launch day? Not at all, as long as you ask for the right thing. Product Hunt's own wording is "you cannot ask people directly to upvote your product" and "Instead, ask them to visit and comment." Hacker News asks you not to solicit votes, comments or submissions at all.
Will a launch help the product rank in Google? Indirectly and slowly. The only accelerant named in Google's own documentation is "try to get linked from other sites", and a launch does produce links. But the same documentation says a crawl request does not guarantee inclusion "instantly or even at all", so treat ranking as a consequence of the months after the launch, not of the day itself.
Do I need special markup so that AI answers mention my launch? No. Google's documentation says "You don't need to create new machine readable files, AI text files, or markup to appear in these features", and that the requirement is to be indexed and eligible for a snippet. Anything sold to you as an AI visibility file is not described in that documentation. Our walkthrough of how to appear in Google's AI overviews goes through the rest.
Where this leaves you
A pre-launch marketing strategy built from published rules is less exciting than one built from tactics, and it has one advantage: none of it can be taken away from you on launch morning. The account is old enough, the launch is scheduled, the assets are written, the pages have been crawled, and nobody has been asked to vote for anything.
It also tells you where the real work sits. Waiting periods and crawl delays mean the content has to exist early, and being present on three channels at once means writing the same campaign three ways. That is the problem distrify is being built to take off your hands: one campaign, aligned on the same keywords, published on the blog and distributed to social and to answer engines. The product is not open yet, so the only thing to do today is put your name down.
Read next: our guide to generative engine optimization for the search side, and one campaign across every channel for the distribution side. Or join the waitlist and we will tell you when it opens.