Scheduled updates
CMS, theme, plugin and dependency updates, tested on staging first.
SUPwebsite support & management
Website support and maintenance services that watch your rankings too.
Founcy Solutions' website support and maintenance services give London businesses the usual care: updates, backups, security and fixes. They add what most plans leave out: search-health monitoring. That means indexing errors, Core Web Vitals field data, and alerts when a change drops clicks on the pages that make you money.
- uptime + security + search health
- one ticket queue
- monthly health report
- monitored together: uptime, security, backups, updates, Core Web Vitals and index coverage
- routine work logged from one ticket queue
- caught: a noindex that a theme release added to /services/
search health watchedone ticket queuemonthly report
definition
What are website support and maintenance services?
Website support and maintenance services keep a live website secure, working and improving after launch. Maintenance is scheduled and preventive: updates, backups, security scans and monitoring. Support is reactive and request-driven: fixes, content edits and small features. Most businesses need both under one plan, with clear priorities and a monthly view of what was done. For sites that rely on search traffic, that view should include indexing and Core Web Vitals, not just uptime.
- Maintenance
- Scheduled updates, backups, security and monitoring
- Support
- Fixes, edits and small features through one ticket queue
- Monitored
- Uptime, security and search health, together
- Reported
- A monthly health report with a prioritised fix list
find the right support
Website management services, by situation.
Every plan includes search-health monitoring. Start from where you are today.
SOSwhen: it's broken right now
Emergency website support
Site down, hacked or flagged by Google. Site and search recovery run in parallel.
Get help now → WPMwhen: you run WordPressWordPress maintenance plans
Staged updates, plugin audits and an SEO regression check after every update.
Explore → HSTwhen: the server is the weak pointManaged hosting and maintenance
Hosting, SSL, CDN and backups run by a team that watches your crawl stats.
Explore → MIGwhen: you're changing platform or domainSEO-safe website migration
Redirect maps, crawl comparisons and monitoring, so rankings survive the move.
Explore → ENTwhen: it's a complex platformEnterprise development support
Engineering capacity for large platforms, with SEO regression tests in CI/CD.
Explore →sample monthly report
What you'd see every month.
One page: what we did, what we caught, and what to fix next, ranked by impact. Switch months to see how a site settles in.
// monthly health reportyourbrand.exampleillustration · sample data
uptime99.98%
updates shipped15
issues caught1
lcp · p75 mobile2.1s
// search & site health
- Search Console errors0 new
- Core Web Vitalsgood
- Robots / canonical changesnone
- XML sitemapvalid
- Backup restore testpassed
- Security scanclean
// next month's fix list
- Consolidate three thin tag archivesimpact med · effort low
- Lazy-load the below-fold videoimpact low · effort low
- Retire the legacy slider pluginimpact med · effort med
Month 3: steady state. One canonical change caught and reverted the same day.
sound familiar?
Signs nobody really owns your website.
Tap the ones that apply. We'll carry them into your support brief.
Tap anything that sounds familiar.
Build a support plan around these →what's included
Ongoing website support, covered end to end.
Uptime & expiry alerts
Uptime, SSL and domain-expiry monitoring, with alerts routed to a person.
Tested backups
Off-site backups, restored on a schedule to prove they work.
Security
Hardening, malware scanning and firewall rules kept current.
Search-health monitoring
Indexing errors, Core Web Vitals, and robots or canonical change alerts.
One ticket queue
Content edits and small development requests, prioritised in the open.
Monthly health report
What changed, what we caught, and a fix list ranked by impact.
Quarterly review
Technical debt and SEO opportunities, turned into a short roadmap.
how requests are prioritised
No mystery queue. Four levels, agreed up front.
Priority levels and their response targets are written into your agreement at onboarding. They depend on your coverage hours and plan, and nothing is assumed from a sales page.
P1e.g. 5xx on every page
Site down or compromised
Outage, hack, checkout failure or deindexing. Everything else stops.
P2e.g. leads stop reaching the CRM
Revenue path broken
A form, integration or key template fails while the rest of the site works.
P3e.g. CLS on blog templates
Something's wrong, not urgent
Visual bugs, slow pages and search warnings that need fixing this cycle.
P4e.g. a new landing page
Changes & improvements
Content edits, new sections and small features, scheduled into the queue.
support, seo-aware
Most support plans watch the server. Yours should watch the traffic.
traffic drops spotted: weeks later
MonitoringIs the server responding?Server, security and search health: indexing, Core Web Vitals and clicks on money pages
After a change"Looks fine to me"Robots, canonical and sitemap changes detected and confirmed
RequestsEmails into an inbox, priority unclearOne queue with four agreed priority levels
BackupsTaken, never testedOff-site, and restore-tested on a schedule
ReportingHours used this monthWhat changed, what we caught, and the fix list ranked by impact
PlanningReactive, foreverQuarterly review of technical debt and SEO opportunities
onboarding
How support gets started.
The first weeks are about knowing your site better than whoever built it.
- 01
Onboarding audit
Access, backups and a stack inventory, plus a baseline crawl and Search Console and GA4 benchmarks.
→ risk list + baseline - 02
Agree the model
The support model, priority definitions, response targets and communication channels, in writing.
→ support agreement - 03
Set up monitoring
Uptime, security and search-health monitoring go live, with the update schedule agreed.
→ monitoring live - 04
Run the queue
Ticket work and scheduled maintenance windows, with every change logged.
→ steady cadence - 05
Report & review
A monthly health report and a quarterly roadmap review.
→ health report
tooling
What we monitor and work with.
// search health
Google Search ConsoleGA4CrUXPageSpeed InsightsScreaming Frog
// uptime & errors
UptimeRobotBetter StackSentry
// security
CloudflareWAFMalware scanning2FA
// workflow
GitStagingJiraLinear
what shapes the plan
What does ongoing website support cost?
It comes down to four things. Set them to see which support model fits.
beyond support
When support turns into a project.
AUD
SEO audits
A full technical, content and backlink diagnosis with a prioritised roadmap.
Explore → DEVWebsite development
When patching isn't enough: a rebuild engineered to rank from day one.
Explore → WPWordPress development
Lean custom block themes instead of page-builder bloat.
Explore → CXOCustomer experience optimisation
Turn the traffic you protect into more enquiries and sales.
Explore →faq
Website support questions.
Maintenance is scheduled and preventive: updates, backups and monitoring. Support is reactive and request-driven: fixes, edits and small new features. Most plans combine both under one agreement, so nothing falls between them.
By the priority levels agreed at onboarding, for example a site outage versus a broken form versus a content edit. Coverage hours and plan level change the targets. Get them in writing in your agreement rather than assuming them from a sales page.
It depends on site complexity, the number of sites and environments, the platform, coverage hours and expected request volume. Retainers suit steady demand; ad hoc blocks suit occasional needs. An onboarding audit comes first so the scope can be priced accurately.
Yes, after an onboarding audit of the code, hosting and access. Undocumented custom code and abandoned plugins are flagged as risks up front, along with a plan to reduce them.
Because many traffic losses start as technical changes: an update, a release or a misconfiguration. Monitoring search health alongside uptime catches those regressions while they're still cheap to fix.
It depends on the agreement. Some plans roll hours over for a limited period and others don't. Whatever the terms, you should see exactly how hours are tracked and used in each monthly report.
start with an audit
Give your website an owner.
Send your domain. We'll start with an onboarding audit of updates, backups, security and search health, and show you what's at risk.
friendly, UK-based support · one ticket queue · monthly health report