In the first 30 days after launch, confirm the domain and certificate work everywhere, test every form, check that old addresses redirect, verify the site in Google Search Console, submit the sitemap, and set up monitoring. Then watch search coverage and error reports weekly, and fix what real visitors turn up.
Launch day is the day a site stops being a project and starts being a thing people rely on. It is also the day most projects stop getting attention, which is backwards. The first month is when a new site is most likely to have a problem nobody has noticed yet.
We stay on after launch as a matter of course: hosting, monitoring, fixes, and the next feature. We also run our own products, so we are the ones who hear about it when something turns up that review did not predict.
This is the checklist we work through. It promises nothing about rankings or traffic. It is about making sure the site you paid for is actually reachable, working, and visible to search engines.
What happens on launch day?
On launch day the domain is pointed at the new site, the security certificate is confirmed, and every critical path is tested on the live address. That means loading the site with and without "www", submitting each form, and checking that old addresses redirect to their new homes.
- Point the domain. DNS records are updated to the new host. Changes can take time to reach everyone, so some visitors see the old site for a while. We explain the mechanics in how to point a domain to a website.
- Check the certificate. The site should load over
httpson every variant of the address, and the other variants should redirect to one canonical version. - Submit every form. On the live site, from a phone, and confirm the message arrives where it should.
- Check redirects. Every address that existed on the old site should lead somewhere sensible on the new one.
- Remove the "do not index" setting. Sites under construction are usually hidden from search engines. Forgetting to lift that after launch is a classic mistake.
- Confirm analytics and monitoring are recording. If you plan to measure anything, check it is being measured from day one.
Forms deserve the emphasis. For Vortech AC and Electrical, the quote form reaches the owner directly. A form like that is the point of the whole site. If it fails silently, the site looks fine and produces nothing, and nobody knows until someone asks why the phone has been quiet.
What should you check in the first week?
In the first week, verify the site in Google Search Console, submit the sitemap, set up uptime and error monitoring, and review the site on real devices. This is also the week to collect the small defects that only appear with real visitors and fix them in one pass.
- Verify the site in Search Console. This is how Google tells you what it can and cannot read. Our guide to Google Search Console for business owners covers what to look at.
- Submit the sitemap. A sitemap is a file listing every page you want indexed. Submitting it tells search engines where to start.
- Turn on uptime monitoring. Something should alert a person if the site stops responding.
- Turn on error monitoring for apps. See error monitoring for web apps.
- Test the forms again. Email delivery problems sometimes appear only after a few days.
- Ask a few people to use it. Staff, a friendly customer. Collect what they report.
What should you check in weeks two to four?
In weeks two to four, watch how search engines are processing the site and how real visitors are using it. Check Search Console for pages that could not be indexed, look for addresses returning "not found", and confirm that leads from forms are still arriving.
| When | Check | Why |
|---|---|---|
| Week 2 | Indexing report in Search Console | Shows which pages have been read and which were skipped |
| Week 2 | "Not found" errors | Reveals old addresses that were missed in the redirect list |
| Week 3 | Form submissions against real enquiries | Confirms nothing is being lost or sent to spam |
| Week 3 | Speed on a real phone on mobile data | Office wifi hides slow pages |
| Week 4 | Backups, and that one can be restored | A backup nobody has tested is a hope |
| Week 4 | Content corrections from staff and customers | Wrong hours and old prices surface now |
How quickly search engines pick up a new site varies and is not under anyone's control. If someone promises you a position by a date, ask how they know.
What changes if the launch replaced an older site?
When a launch replaces an older site, redirects become the most important item on the list. Every address the old site had is known to search engines and may be linked from elsewhere. Each one must either stay the same or redirect permanently to its replacement.
The best redirect is the one you do not need. When we moved Homes by Jan, a realtor's site, off WordPress to a static build, every page and article came across at its exact original address. Old addresses redirect where they should. An address that never changes gives a search engine nothing to relearn.
After a replacement launch, add two checks. Keep the full list of old addresses and test all of them, not a sample. And leave the old hosting in place for a short while, so there is something to fall back on. Our walkthrough of migrating off WordPress without losing URLs covers the method.
What is different for a web app?
A web app adds accounts, data, and payments to the launch checklist. Beyond the website checks, confirm that sign-up and sign-in emails arrive, that payments work with a real card, that error reports reach a person, and that the database is backed up on a schedule.
The first real users will do things nobody tested. That is expected. What matters is finding out quickly, which is what error monitoring is for, and having a clear way to release a fix. Changes after launch should go through the same checks as changes before it, as described in how software is tested before launch.
Frequently asked questions
How long does it take for a new site to appear in Google?
It varies, and no developer controls it. Verifying the site in Search Console and submitting a sitemap makes sure search engines know the pages exist. After that, the indexing report shows progress page by page.
Should traffic be expected to dip after a redesign?
Some movement is common while search engines reprocess a changed site. Keeping addresses the same, or redirecting each old one, reduces how much there is to reprocess. Nobody can honestly guarantee the result.
Who should be responsible for the site after launch?
Agree this before launch, in writing: who hosts it, who receives alerts, who applies updates, and how you request a change. A site with no named owner gets attention only when it breaks.
When should the old hosting be cancelled?
Not on launch day. Keep it until the new site has been stable for a few weeks and you have confirmed that email and anything else on the old account has been moved.
Is a new site finished once it launches?
No. Content goes out of date and customers ask new questions. Plan for regular small updates.
If you are about to launch, or launched recently and nobody ran a list like this, get in touch and we will go through it with you.