Designed for
Organisations with a live site that needs to stay maintained, monitored and current — without hiring anyone to do it.
Maintenance, monitoring, small improvements
05
Website Care
Ongoing care for a live site: dependency and security updates, monitoring, and measured content and conversion improvements — every change shipped through the same staged pipeline that built the site. It is the routine our client platforms already run on: versioned migrations, automated tests, dev, test and production environments.
Discuss this projectWhat is Website Care?
Website Care is an ongoing monthly service for a live site: dependency and security updates, uptime and error monitoring, Search Console review, accessibility checks and small improvements. Every change ships through the same staged dev, test and production pipeline that built the site.
Choose this if
- A site is live and nobody is currently responsible for keeping it current
- You want security and dependency updates tested before they reach production
- You want Search Console findings acted on rather than accumulating unread
- You would rather not hire someone to do it in-house
Choose something else if
- Website Rebuild — when the site itself is the problem and maintenance will not fix it.
- Platform Build — when you need new application features rather than upkeep.
The problem
Most websites are launched and then left. Dependencies age, forms break silently, Search Console warnings sit unread, content drifts out of date. The cost arrives later, all at once, usually at a bad moment.
The intended outcome
A site that stays current, monitored and steadily improved, with a plain-language record of every change.
Integrated scope
What the engagement can cover.
- 01Dependency and security updates, tested before deployment
- 02Uptime and error monitoring
- 03Search Console monitoring: indexing, coverage, Core Web Vitals
- 04Accessibility checks on every page we touch
- 05Content updates and small feature work
- 06Conversion improvements proposed from evidence, never guaranteed
- 07Every change through dev, test and production
Deliverables
Concrete outputs, agreed before work begins.
- A monthly change log in plain language
- Dependencies kept current, with automated tests passing
- Search Console findings, and what was done about each
- Accessibility findings and fixes on touched pages
- A prioritised backlog, reviewed with you
- Staging previews of anything visible before it ships
Service process
Four stages with one decision trail.
Care runs as a monthly cycle. A site we did not build starts with an audit and a stabilisation period — typically the first month — before the routine settles.
01
Onboard
Access and audit. We read the codebase, hosting, analytics and Search Console before touching anything, and record a baseline so later changes can be judged against it.
02
Stabilise
Overdue updates are applied through staging, the test suite is run — and written where cover is thin — and monitoring is put in place. Usually the first month, and the least glamorous one.
03
Routine
A monthly cycle of updates, content changes and small improvements. AI coding agents keep small changes economical; the staged pipeline and tests keep them safe. This is the discipline that keeps platforms like alberr.org's donation system live — 38 versioned database migrations and counting.
04
Review
Periodically we sit down with what the data actually shows — Search Console, analytics, the change log — and re-prioritise the backlog with you. Decisions come from evidence, not from a sales cycle.
The practice owns
- Ship every change through staging before production
- Keep automated test suites running, and extend them where cover is thin
- Watch monitoring and Search Console, and act on what they surface
- Record every change in language you can read without a developer
- Say clearly when something needs work beyond the plan
You provide
- Access to the repository, hosting, DNS, analytics and Search Console
- A named contact who can approve changes
- Content inputs when an update needs them — prices, dates, text
- Notice when the business changes: hours, offers, locations
- An agreed window for production deployments
Not included by default
- Guaranteed movement in rankings, traffic or revenue — we report what happened, we do not promise what will
- Advertising and campaign management
- Redesigns and new platforms — scoped as separate projects
- Round-the-clock emergency cover, unless agreed in writing
- Emergency work on a site we have never audited
Relevant proof
The proof is live, not promised.
Five live client properties are linked from the work page—open them, click through them and inspect them. El-Sultan Web does not attach invented outcomes or borrowed metrics to any service.
See live client workCommon questions
Website Care, answered directly.
Every answer states a boundary as well as a capability. Broader questions about timelines, ownership and what happens after launch are on the FAQ page.
Do you maintain sites you did not build?
Yes, but it starts with an audit. The codebase, hosting, analytics and Search Console are read and a baseline recorded before anything is touched, followed by a stabilisation period, typically the first month, before the routine settles. Emergency work on a site never audited is not taken on.
What do I actually receive each month?
A change log in plain language, dependencies kept current with automated tests passing, Search Console findings and what was done about each, accessibility findings on touched pages, and a prioritised backlog reviewed with you. Anything visible is previewed on staging before it ships.
Will care improve my traffic or rankings?
No movement in rankings, traffic or revenue is guaranteed. Conversion improvements are proposed from evidence in Search Console and analytics, and what happened is reported. What will happen is never promised.
Is there out-of-hours emergency cover?
Not by default. Round-the-clock emergency cover exists only where it has been agreed in writing. The standard arrangement is a monthly cycle with an agreed window for production deployments.
Project fit
Could Website Care fit the challenge?
Twenty focused minutes: what you need built, in which languages, and what a prototype-first timeline looks like for it. If the project is not a fit for this practice, you will hear that plainly.
Book a project fit callInitial qualification only. Not a free audit or commitment to purchase.