01 / 01
Care
The month afterlaunch matters too.
One monthly cycle, run by the same people every time. We read what changed, fix what slipped, build the next improvement and tell you what followed.
Every month
Week one
Read what changed.
Rankings, speed, errors, uptime and enquiries, read at the source. Monitoring for speed, errors, uptime and search runs all month.
- Week one: Read what changed. Rankings, speed, errors, uptime and enquiries, read at the source. Monitoring for speed, errors, uptime and search runs all month.
- Weeks two and three: Fix what slipped. Fixes are made the week they are found, before anyone else notices. Each one is recorded.
- Week four: Build the next improvement. One planned improvement a month, shipped. The same team every month, who know the site.
- Month end: Report, with every number sourced. A plain-words account of what changed and what followed, with the source and date of every number. Then the next month starts.
What followed
- UK tile retailer, server response: Server response time down 98%. Pages answer almost instantly. Source: Server timing, read before and after the fix. August to September 2026.
- Mowers Online, junk traffic from outside the uk: Junk traffic down 84% on the day the new edge rules went live. Source: The site's own analytics, sessions by country. September 2026.
Care in the work
Questions
What does a month look like?
Week one we read the numbers, then we fix what slipped, ship the planned improvement, and report at the end of the month.
Who does the work?
The same people every month. They know your site, your team and your history.
Can we change what we focus on?
Yes. Each month starts with what matters most to you now, read against the numbers.
Start with care.Tell us what should change.
We read every brief the same day and reply with a plan.
Start a project