Published

The build is finished. The pages look right, the photos are in, and somebody is about to click the button that makes it real. That is the moment most of the avoidable problems get made, because launching a website is not one decision. It is about a dozen small ones, and a few of them happen outside the site entirely.
None of this is complicated. It is just easy to skip when you are tired of looking at the project and you want it live. Here is the pass we make before a site goes live for a local business, written so you can run it yourself or hold your builder to it.
Key takeaways
- Every address on the old site needs to point somewhere sensible on the new one. Google asks you to redirect old URLs to their new locations so the pages you already earned do not turn into dead ends.
- Test the contact form from a real phone on cell service, not from the office wifi, and confirm the message actually lands in an inbox somebody reads every day.
- Check that the site is not still blocked from search. A staging site is usually hidden on purpose, and that setting ships to the live site more often than anyone admits.
- Launch day work happens off the site too. Your Google Business Profile link, your social profiles, your email signature and anything printed with the old address all need the new one.
- Pick a launch day you will be around for. The first week is when you find the things no checklist catches, and a Friday afternoon launch means nobody is watching until Monday.
What should you check before a new website goes live?
Check five things: that old page addresses redirect to the new ones, that every form and phone number works from a real phone, that the site is not blocked from search engines, that your hours and contact details are current, and that tracking is in place. Everything else can be fixed after launch.
That short list covers almost every real problem we see. The rest of a launch checklist is nice to have. These five are the ones that quietly cost you customers, because when they fail, nothing looks broken. The site loads. The pages are pretty. The phone just stops ringing as much and nobody connects the two for a month.
It helps to decide up front who is responsible for each item. Some of it is the builder’s job. Some of it only you can do, because it needs a login to your own accounts. Sorting that out before launch day is the difference between a smooth morning and a week of chasing passwords. The same goes for timing: we cover how long a build actually takes separately, but the last week of it should be reserved for this, not for new ideas.
What happens to your old page addresses when the site changes?
If an old address is not pointed at the new page that replaced it, anyone who clicks that link gets an error. Google’s guidance for a site move with URL changes is to redirect each old URL to its new location, so the search history and the links you already earned carry over instead of starting from zero.
This is the single most expensive thing to get wrong, and it is invisible from the homepage. Your old site had addresses. Some of them are on Google right now. Some are in a customer’s bookmarks, in a supplier’s email, on a flyer, or in a review somebody left three years ago. When the new site uses different page names, every one of those links points at nothing unless somebody maps it.
Ask for the map in writing. A simple list of old address on the left, new address on the right, with nothing left blank. If a page is genuinely gone, send it to the closest match rather than the homepage, because dropping someone on the homepage when they asked for your service page is how you lose them. Google is explicit that redirects should go to the matching content, not to a catch-all.
A Harrison shop we talked with had a specials page printed on the back of a menu they had been handing out for two years. The new site had no specials page at all. That link needed somewhere real to go, and it took five minutes to decide where. It would have taken months to notice.
Why do contact forms break on a brand new site?
Because they are usually tested once, from a desk, by the person who built them. A form can submit successfully and still send its message nowhere, or send it to an address nobody checks. Test it from your own phone on cell service, then confirm the message arrived and that someone knows to answer it.
Submit the form the way a customer would. Stand in the parking lot, use your phone, use the keyboard that actually comes up, fill in the fields the way a person in a hurry would fill them. Then go look for the message. Not in the website dashboard. In the inbox where you live.
Two failures are common. The first is the message going to an address that was set up during the build and forgotten, so the leads pile up somewhere nobody opens. The second is spam filtering, where form mail lands in junk because it comes from the website rather than from a person. Both look identical from the customer’s side, which is to say they look fine. The customer thinks they contacted you.
Check the phone number while you are there. Tap it. Make sure it dials, and make sure it dials the line that is actually answered this season rather than the one that rings in an office nobody is sitting in. If you have a text number or a booking link, test those the same way. What happens to a lead after it arrives is its own subject, and it is worth reading up on why good leads fall through the cracks before you turn the new site loose.
Is your new site actually allowed to show up in search?
Not always. Sites in development are normally hidden from search on purpose, and that setting can travel to the live site. Before you celebrate, confirm the site is not carrying a noindex instruction or a blocking rule in its robots file, then submit your sitemap in Search Console.
Hiding a site while it is being built is correct. Google documents two ways to do it, a noindex instruction on the pages themselves and a rule in the site’s robots file, and both exist for exactly this reason. The problem is that neither one announces itself. The live site looks perfect to you, because you are typing the address in directly. Google simply never comes.
So make it an explicit step with a name on it: someone confirms, out loud, that the block is off. Then submit the sitemap through Search Console so Google has a current list of your pages. If the business has a Google Business Profile, that is also the moment to make sure its website link points at the new site and still lands on a working page. Profiles and maps listings have their own quirks, and we wrote about why a business stops showing up on Google Maps if yours goes quiet after a change.
Do not expect anything to happen the same afternoon. A brand new address is unknown to Google for a while, and that is normal rather than a sign of a mistake. What you are checking here is that nothing is standing in the way.
What needs updating everywhere else on launch day?
Your Google Business Profile website link, your social profiles, your email signature, any directory or association listing, and anything printed or recorded with the old address on it. The site changing does not change those, and a customer who reaches a dead link usually does not try twice.
Make a list before launch day, because you will not remember all of it afterward. The usual ones for a local business around here: the Business Profile, Facebook and Instagram, a chamber or association listing, whatever booking or review platforms you are on, your email signature, and the number or address read out in any radio spot or printed on current materials.
If you advertise, this one matters more than it sounds. An ad is a promise to go somewhere. If the page it points to was renamed during the rebuild, that spend lands on an error page for as long as it takes someone to notice. Check every live campaign’s destination the same day the site changes, not the week after.
Hours and contact details deserve their own look, especially for a seasonal business. A Branson operation that runs different hours in March than it does in July should launch with the hours that are true this week, in both places, on the site and on the profile. Those two disagreeing is one of the easiest ways to frustrate someone who is already in the car.
What should you watch in the first week after launch?
Watch the three things a customer touches: did the calls keep coming, did form messages arrive, and does the site work on the phones people actually carry. Everything else can wait. If one of those three goes quiet, something broke, and it is almost always findable in a few minutes.
Pick a launch day you will be around for. Tuesday morning beats Friday afternoon every time, because the first week is when the small stuff surfaces: a page nobody remembered, an image that looks wrong on a phone, a form field that will not accept a local area code. None of that is a disaster if someone is paying attention. All of it is if the site goes live into a weekend.
Ask a few people who are not involved to use it. Not to admire it. To do something, like find your hours or request a quote, and tell you where they hesitated. That is worth more than any report in the first week, and it costs you a phone call.
After that, a site is not a finished object. Plugins update, content goes stale, seasonal details change. Keeping it healthy is ongoing work, which we cover in plain English under website maintenance. And if you are still earlier in the process and deciding what the site needs to contain, start with what a small business website actually needs instead.
Launching a new site soon?
If you want another set of eyes on the launch, or you are weighing a rebuild and want to know what it involves, book a 25 minute Clarity Call. No pressure, no obligation, and you will leave with a straight answer either way.
Frequently asked questions
What should be on a website launch checklist?
At minimum: redirects from every old page address to its new one, a working contact form tested from a real phone, a confirmation that the site is not blocked from search, current hours and contact details, your sitemap submitted in Search Console, and tracking in place. Then update the Business Profile link, social profiles and anything printed with the old address.
Do I need to redirect my old website pages?
Yes, if the page addresses changed. Google’s guidance for a site move with URL changes is to redirect each old address to the page that replaced it, so existing links and search history carry forward. Send each one to the closest matching page rather than dropping everyone on the homepage.
How do I know if my new website is showing up on Google?
Search for your business name and look. Then check Search Console, which will tell you whether your pages have been seen and whether anything is blocking them. If the site was hidden during the build, confirm that block was removed, because that is the most common reason a new site stays invisible.
How long after launch does a new website start getting traffic?
It varies, and anybody who gives you a date before looking at your site and your market is guessing. Pages usually start getting picked up within days to a few weeks, and a rebuilt site with its redirects done properly tends to hold what the old one had. That is what we watch for, not a promise.
Should I keep my old website up after the new one launches?
Not running at the same address, no. Two live versions compete with each other and confuse anyone who lands on the wrong one. Keep a copy of the old content and its page addresses somewhere safe, though. You will want that list when you are setting up redirects or hunting for a page somebody says has gone missing.
A launch is not a finish line. It is the day the site starts doing its job, and the checking you do that morning decides whether it gets to. If you would like help with a build, a rebuild or the launch itself, that is what our website design and hosting work is for.
Sources
- Google Search Central, Site moves with URL changes (redirect each old URL to its new location)
- Google Search Central, Block search indexing with noindex (how pages are hidden from search)
- Google Search Central, Introduction to robots.txt (blocking rules at the site level)
- Google Search Central, Build and submit a sitemap
Photo by Tim Mossholder on Unsplash.
