Free tool · Launch
Website launch plan
A checklist with dates on it. Pick the day you want to be live and every task lands on the day it has to happen — including the ones that are already behind, which is usually the useful part.
Pick a real date. A plan without one is a list.
The build task is nine days out for a reason.
It is the short part once the words and photos exist. On Black Nile the build itself is about a minute — the rest of this plan is the real work.
The short answer: Website launches slip for two reasons and neither is the building. They slip because the photographs were never taken, and because Google Business Profile verification can need a postcard that takes a fortnight. This takes your launch date and counts every task backwards from it, so the photography lands three weeks out and the verification lands six days out rather than both being discovered in launch week. If your date does not leave enough runway, it says so and tells you exactly how many days short you are — which is a thing a static checklist can never do.
This runs entirely in your browser. Nothing you type here is sent to us or to anyone else — there is no server call, no account, and no email required to see your result or take it away with you. Your launch date stays in this tab; the plan is generated locally.
How to build your launch plan
One date, one choice of scope, and the plan falls out.
- Pick the day you want to be live. A real date, not 'soon' — the arithmetic is the whole point.
- Choose what you are launching: a one-page site, a small multi-page site, or a site with a store.
- Read the runway figure. If your date is too soon, the plan says by how many days.
- Work down the list. Anything marked critical blocks launch if it slips.
- Watch for tasks marked as waiting on someone else — those are the ones you cannot rescue by working harder.
- Copy the plan as text and put the first three dates in your calendar.
Two tasks genuinely resist compression whatever you do: taking photographs and Google Business Profile verification. If the plan says you are short, those are the two to start today regardless of everything else.
Why a date changes what a checklist is
The same twenty tasks, in a form you can actually act on.
A website launch checklist is easy to find and easy to nod at. The reason it rarely changes anything is that a list of tasks with no dates has no beginning — everything looks equally urgent and equally postponable, so the whole thing gets postponed together.
Attaching a date to each item makes two things visible. The first is ordering: photography has to happen three weeks out not because it is hard but because everything downstream needs it. The second is collision — the moment where the plan meets your actual date and one of them has to give.
That collision is the finding. Being told on a Tuesday in March that your April launch is eleven days short is information you can act on: you either move the date or you decide, deliberately, which tasks get compressed. Discovering the same thing in launch week is not a decision, it is a scramble.
What actually delays a launch
Almost never the thing people expect.
- Photographs. The single largest cause. Building the site is a short job once you have images; without them everything stalls, and 'I'll take some this week' becomes a month. This is why it sits three weeks out.
- Words. The second largest. Writing a homepage feels harder than it is, mostly because people try to write it in a text box inside a website builder. Draft it somewhere else first.
- Verification. Google Business Profile verification can require a postcard, which takes up to a fortnight and is entirely outside your control. Starting it in launch week means launching without it.
- Waiting on other people. Review replies, a photographer's availability, someone else's approval. The plan marks these separately because working harder does not speed them up.
- Domain access. Frequently a surprise. The domain is on an old account, or with an agency you no longer use, and recovering access takes days. Buying or confirming access is the first task for a reason.
What is not on that list: choosing a template, picking colours, or building the site. Those are the parts that feel like the project, and they are usually the shortest.
The tasks after launch day matter more than the ones before
Launching is the middle of the plan, not the end.
The plan continues past go-live for a reason. A site that is published and then never linked to is invisible, and a large share of "my website did nothing" turns out to be "nobody, including Google, knew it existed".
The day-after tasks are small and they compound: submit the site to Search Console, add the link to your Google Business Profile, and put the address everywhere your business name already appears — email signature, invoices, directories, the van. None of that takes more than an hour in total and it is the cheapest traffic you will ever get.
Then the thirty-day task, which is the one everyone skips: read your analytics and fix the single worst thing. One month in you have enough data to see where people leave. Change one thing, not five, so you can tell what worked.
If your date is fixed and the plan is too long
What to cut, in order.
Sometimes the date is not movable — a season starts, a lease begins, a competitor opened. In that case the question is what gets compressed, and some things compress far better than others.
Safe to compress: the number of pages, the polish, the product catalogue, the second round of copy editing. A one-page site with your real details is a legitimate launch, and adding pages afterwards costs nothing.
Compress with care: photography. Phone photographs of real work taken on the next job genuinely are acceptable and beat stock by a wide margin. What is not acceptable is stock photography, which reads as stock to almost everyone.
Cannot be compressed: verification waits and other people's response times. If Google needs to send a postcard, the postcard takes as long as it takes. Plan around it rather than into it.
Never compress: testing the contact form, and reading the site on a phone. Both take minutes and both catch the failures that are invisible from the outside and expensive for months.
FAQ
Questions, answered
The things owners ask before they trust a number like this.
How long does it take to launch a small business website?
The building takes hours; the project takes weeks. Realistically three weeks for a one-page site if you are also gathering photographs and content, and longer for a store. The gap between those two numbers is almost entirely photographs, words, and waiting on other people. If you already have images and copy ready, a one-page site can genuinely go live the same day.
What should I do before launching my website?
Gather photographs of real work, write down your services in customer language, ask past customers for reviews, buy the domain, and set up business email. Then build. Then, before you publish: submit your own contact form and confirm the email arrives, read every page on your phone with Wi-Fi off, and get one person who does not know your business to read it cold and tell you what you do.
What is the most common reason a website launch gets delayed?
Photographs. Not design, not technical problems — the fact that nobody has taken pictures of the actual work, and 'I'll do it this week' becomes a month. It sits at the front of this plan for that reason. The second most common is copy, which stalls because people try to write it inside a website builder rather than drafting it somewhere comfortable first.
Do I need my Google Business Profile before I launch?
Ideally you should have started verification before launch, because it can take up to a fortnight if a postcard is required, and that is entirely outside your control. You do not need it completed to publish a website — but if you leave the claim until launch week, you will launch without the thing that produces most of your enquiries. This is the single most common sequencing mistake in the plan.
When should I point my domain at the new site?
A few days before launch, not on launch day. DNS changes usually take effect in minutes and occasionally take most of a day, so leaving no margin means your launch day is spent watching a browser. Make the change early in the day, early in the week, and confirm from a phone on mobile data rather than the browser you have been working in, which caches aggressively.
What should I do the day after launching?
Submit the site to Google Search Console and add your sitemap. Add the website link to your Google Business Profile. Then put the address everywhere your business name already appears: email signature, invoices, directories, social profiles, the van. That is an hour of work and it is the cheapest traffic you will ever get, because it reaches people who already know you exist.
Can I launch a website in a week?
Yes, if you already have photographs and know what your services are. The plan's three-week runway is dominated by gathering material, not by building. What you cannot compress into a week is Google Business Profile verification if a postcard is needed, or reviews from other people. Launch anyway and let those complete afterwards — a live site missing its profile beats a perfect plan that has not shipped.
How do I know if my launch date is realistic?
This tool tells you. It compares the runway the plan needs against the days you actually have and names the shortfall in days. If you are short, the honest options are moving the date or deciding which tasks get compressed — and the two that genuinely cannot be are verification waits and other people's response times. Everything else is negotiable.
More free tools
Others that pair with this one
Every one runs in your browser, free, with no sign-up.
Connect a Domain Walkthrough
Point your domain at your site one step at a time, branched by your registrar, with the exact records and the wait times named.
Google Business Profile Setup
Claim and verify your profile step by step, with the specific thing that goes wrong at each step and how to recover from it.
Move Your Website Walkthrough
Move off Wix, Squarespace, WordPress or a Facebook page without losing your rankings, your email, or a day of uptime.
Domain Extension Guide
A searchable reference for 40 domain endings — who trusts them, who can register them, and where the renewal price jumps.
Related
Where to go next
The reading that turns this result into a decision.
The build task is nine days out for a reason.
It is the short part once the words and photos exist. On Black Nile it is about a minute — which leaves the rest of the plan, which is the real work.