You've just launched your website. The work starts now.

Most websites are treated as finished the day they go live. The invoices are paid, the designer moves on, everyone goes back to work. Which is a strange way to treat the thing, because launch day is the first day the site can actually do anything.

Here is what the first ninety days should look like, whether you handle them yourself or your designer stays on.

Week one: prove it works

Click every link. Submit every form and confirm the enquiry actually lands in an inbox someone reads. Test on a real phone, not just a resized browser window. Check that old URLs redirect to their new homes rather than dying as 404s, because that is where years of accumulated search traffic quietly disappears. Confirm analytics is recording and that Google Search Console can see the site. None of this is glamorous. All of it is the difference between a working asset and an ornament.

Month one: watch what real people do

Analytics gets interesting once real visitors arrive. Where do they come from? Which pages do they actually read? Where do they leave? You are not looking for vanity numbers, you are looking for friction. A services page everyone visits but nobody enquires from is telling you something. So is a mobile bounce rate wildly worse than desktop. Small findings like these are worth more than any amount of launch day excitement, because they tell you what to fix next.

Month three: feed it or watch it stall

A website nobody updates slides backwards. Google notices staleness, and so do return visitors. This does not require a content factory. One well made piece a month, answering a question your customers genuinely ask, will do more than a burst of launch enthusiasm followed by silence. Same for the small maintenance jobs: software updates, new photography when the old work sells, prices that stay current. Websites decay by neglect, never all at once.

The mindset that makes the difference

The businesses that get real returns from their websites treat them like a shopfront rather than a certificate. A shopfront gets swept, restocked and rearranged when something is not selling. A certificate gets framed and ignored.

This is, honestly, why I stopped doing launch and disappear projects. The interesting part of the work, and the part where the numbers move, happens after the site goes live. Whoever built yours, make sure someone is watching what happens next. The launch was the cheapest part.