Process
What is included in a 30-day snag period?
Fixing things that do not work as agreed — a broken link, a form that fails on one browser, a layout error on a specific screen size. It is not a window for new requirements, and the distinction should be written down before it starts.
What counts as a snag
- Something that does not work as specified in the agreed scope
- A display error on a supported browser or screen size
- A form, link or button that fails
- A content error introduced during the build
What does not
- New pages, new features or new integrations
- Changes of mind about approved design or copy
- Third-party breakage — a plugin update or an API change after launch
- Content updates that are part of running the site
How to use it properly
Go through the site systematically in the first week rather than reporting things as you notice them over a month. Test on a real phone, complete every form, and check every page — the snag period is most valuable at the start of it.
The longer version
This answer is deliberately short. If you want the full treatment, Website maintenance: the routine that prevents silent failure covers it in about 4 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.