Process
What happens after my website launches?
Thirty days of snag fixes are included — anything that does not work as scoped is corrected at no charge. You receive written handover documentation and every credential. After that, maintenance is optional and monthly, and nothing you paid for stops working if you decline it.
What a snag is, and what it is not
A snag is something that does not work as described in the scope. A change is something new. The distinction is written down before launch rather than argued about after it, which is what makes the warranty meaningful rather than a source of friction.
What handover contains
- Every credential, transferred in writing
- Documentation of hosting, deployment and dependencies
- Repository access with the deploy process written down
- A database backup and restore instructions
- A licence list for fonts, images and any commercial plugins
What to actually watch in the first month
- Search Console coverage — are pages being indexed?
- Enquiries or orders arriving, and confirmation emails reaching inboxes rather than spam
- Core Web Vitals field data, which starts populating after a few weeks
- 404s in your logs, which reveal anything the redirect map missed
The longer version
This answer is deliberately short. If you want the full treatment, E-commerce website development: what the whole build actually involves covers it in about 7 minutes — free, ungated, written from client work.
Who answered this
Anas Bin Masud builds e-commerce sites and does technical SEO for businesses in the UK, Canada and Pakistan — fifteen live client sites, six of them stores taking real payments. These answers come from those projects rather than from a content brief. More about how I work, or ask me something directly.