What Happens After Your Website Goes Live?

Submit every form the way a customer would, on your phone and on a computer. Use a normal message, then check the inbox, the notification, or the tool where submissions are supposed to land. Open it and confirm you can reply.

If the form promises that someone will get back to them, name the person who watches that inbox. A form that delivers to an address nobody opens is a dead end. Test again when you change email providers. Delivery breaks more often during those switches than on an ordinary week.

Walk the main routes: navigation, the footer, buttons, PDFs, maps, and any link that leaves your site for ordering, booking, payment, or directions. Look for pages that do not load, links that still point at a draft address, and buttons that open the wrong location.

Do this again when something you depend on moves. If a booking tool changes its address, or a partner replaces a menu PDF, the button on your site will not update itself. A simple brochure site can get by with a pass every few months. If you add pages often, check new links when you publish them.

Call the phone number on the site. Send a message to the published email. Compare the address and hours with the door, your map listing, and your social profiles. If you moved suites or changed a holiday schedule, the website has to change in the same sitting as the sign and the listing.

Prices, menus, and service areas belong in the same habit when you publish them. Visitors treat those as current. If you cannot keep a section accurate, take it down until you can. A missing price does less damage than a wrong one.

Most updates are ordinary: a new staff member, a seasonal offer, a sold-out item, a photo that no longer matches the shop. Decide who is allowed to edit those things and how they ask for a change. If only one person has the login, write down where it lives and who can reach it when that person is away.

A site does not need a blog to be worth maintaining. Add news, a gallery, or regular posts only if someone will actually update them. A quiet site with correct hours is in better shape than a news page whose last entry is from two years ago.

Open the live site on a phone, not only in a narrowed browser window. Read the homepage. Tap the main button. Open the contact page. Text should be readable, buttons should be easy to hit, and you should not have to slide sideways to see a map or a menu.

Repeat this after bigger edits. A new section that looked fine on a laptop can push the phone number below a tall image on a small screen. If most of your customers will visit from a phone, this check matters more than a fresh desktop layout.

The site is not really yours if you cannot get into it. You should be able to reach the domain registrar, the hosting or website platform, the email tied to those accounts, and any form, booking, or payment tool the site depends on.

Keep those accounts in the business's name, with a recovery email the business controls. If a freelancer or a former employee set everything up under a personal login, move it before that relationship is the only key. If you are unsure what you have, confirm these:

• The domain registrar
• Hosting, or the website platform
• The login for the editor
• Where form messages go

A small brochure and a site where customers log in do not need the same routine. Match the effort to what could actually go wrong.

On a hosted builder, the platform applies a lot of the updates for you. Your job is a strong password used only for that account, and two-factor sign-in if it is offered. Do not share the login in a group text.

If the site runs on software you or a developer installed, including many WordPress setups, someone has to update the core software, the theme, and the plugins. Old plugins are a common way small sites get broken into. Agree on who checks, and how often. Monthly is a sensible default for a plugin-heavy site. A site with no plugins and no editor may need almost none of this.

If people create accounts, pay you, or upload documents, treat that as a higher bar. Limit who has an administrator login. Remove accounts when staff leave. Do not collect information you do not need.

Some platforms keep their own backups and will restore a site if you ask. Find out whether that is true, how far back the copies go, and whether you can export one yourself. "The host probably has it" is not a plan until someone has confirmed it.

A custom site, or one that stores orders, form entries, or client records in its own database, needs a backup somewhere other than that same server. Someone should know the restore steps, and those steps should have been tried. A copy that has never been restored is only a guess.

A simple marketing site with no private customer data still benefits from an export of the pages and images. A bad edit or a lost login should not mean rewriting the copy from memory.

Match the routine to the way the site was built:

• Hosted template. Content checks, form tests, link checks, and working account access. The platform handles a lot of the plumbing. A little time each month is enough, with a closer look when you change an offer or a tool.
• Custom theme. Those same checks, plus updates and a backup you trust. That work continues whether you do it or you pay someone to do it.
• Custom site. The content checks, plus hosting, updates, backups, and a way to request changes when the workflow changes. The same applies to a web app the team logs into.

If you are still choosing between a template and a custom build, include this care in the comparison. A lower launch price can cost more later if nobody is watching the software. The line between a marketing site and that kind of tool is in Website or Web App: Which Does Your Business Need?.