Launch day feels like the finish line. It is the starting gun.
Most client relationships do not break during the build. They crack in the quiet weeks after go-live, when a plugin update breaks the contact form, nobody knows who restores the backup, and a “quick change” turns into an invoice dispute. Focus Digital’s 2026 agency churn report names the first 90 days as the highest-risk window, with project clients churning at 42% a year versus 18% for retainer clients.
The fix is not more effort. It is a written scope. This guide shows exactly what website maintenance after launch should cover in the first 90 days, what it should not, and how to tell if a care plan is worth paying for.
Why the First 90 Days Decide the Relationship
During the build, ownership is obvious. After launch, the build team moves on, the client’s editors start changing pages, and the first update notice arrives with no name attached.
The risk is real. Patchstack recorded 11,334 new WordPress vulnerabilities in 2025, a 42% jump over 2024, and 91% of them sat in plugins. Its 2026 report adds that 46% had no patch at disclosure. A site nobody updates is a site waiting to be exploited.
Most first-month complaints are small: a slow page, a silent form, a broken link. What turns a one-hour fix into a lost client is confusion about who handles it, how fast, and whether it costs extra.
Put These 7 Decisions in Writing Before Go-Live
Settle these before the DNS switch. Any blank line here becomes your first argument.
- Ownership split: the client owns content; the care team owns the platform.
- Defect window: how long bugs in delivered work get fixed free (30 days is common).
- Update window: when core, theme, and plugin updates run, and who can approve a rollback.
- Backup terms: frequency, retention, storage location, and who restores.
- Response target: how fast issues get acknowledged (for example, one business day), kept separate from resolution time and uptime promises.
- Inherited issues: known defects logged at onboarding, so they are never blamed on the care team.
- Access and handover: admin, hosting, DNS, and source files, all owned by the client.
The 90-Day Website Care Checklist
Split the first 90 days into phases. Each one has a different job.
| Window | What happens | What it is not |
| Launch week | Verify backups, SSL, forms, redirects, analytics, and Search Console; submit the sitemap | The end of client involvement |
| Days 1-30 | Fix reported defects; monitor indexing and 404 errors | New features or scope changes |
| Days 31-60 | First monthly cycle: backup, tested updates, form and speed checks, summary | Daily backups or 24/7 monitoring |
| Days 61-90 | Second cycle plus a Core Web Vitals and analytics review | Redesign work |
| Day 90 | Review request patterns; renew, rescope, or hand over | An automatic renewal |
Launch Week: Lock the Foundations
- Store a full backup off the server, following the 3-2-1 rule: three copies, two media, one offsite.
- Test every form end to end, including delivery to the right inbox.
- Check 301 redirects from old URLs. Google advises keeping them for at least a year after a site move.
- Verify GA4 events and Search Console ownership, then submit the XML sitemap.
Days 1-30: Catch What Testing Missed
Real users find bugs QA never did. Log every report, tag it as a defect or a new request, and respond within the agreed window. Watch the Page indexing report too, since new pages can take days to weeks to get crawled.
Picture a dental clinic two weeks after launch. Its booking form works on desktop but fails on one iPhone browser. Under a written scope, that is a defect: logged, fixed, done. Without one, it becomes a debate about who pays.
Days 31-90: Run the Monthly Cycle
Follow the same order every month:
- Take a fresh backup and confirm it restores.
- Apply updates on staging first, then production.
- Re-test forms, checkout, and key landing pages.
- Check Core Web Vitals against Google’s “good” marks: LCP under 2.5 seconds, INP under 200 ms, CLS under 0.1.
- Send a one-page summary: what changed, what was checked, and what fell outside scope.
That last line matters most. It feeds the day-90 review.
Mini template: the monthly care summary
Site: example.com | Period: March 2026
Backup: taken Mar 3, restore tested OK
Updates: WordPress core, 6 plugins, 1 theme
Checks: 4 forms passed, checkout passed, LCP 2.1s
Issues fixed: 1 (contact form routing)
Out of scope: 2 requests (new landing page, menu redesign)
Five lines a client can read in thirty seconds beat a ten-page report nobody opens.
What Website Care Should NOT Cover
A care plan keeps a working site working. It is not a free improvement budget. List these exclusions up front:
- New pages, features, or design changes
- Content writing and SEO campaigns
- Malware cleanup and emergency recovery (priced separately, in advance)
- Paid plugins, licenses, and third-party platform changes
- Guaranteed uptime or fixed resolution times, unless you sell an SLA
- Unused hours rolling over
Saying no in writing feels awkward at signing. It feels far worse during an outage. If a request is not on the list, it gets a quote, not a quiet yes.
Do You Actually Need a Care Plan? A 4-Question Test
- Is the site healthy today? If not, fix inherited defects first.
- Does it change often? If not, and the host patches core, a quarterly check may do.
- Would updates go unowned without outside help? An in-house developer with spare time needs a runbook, not a retainer.
- Are most requests maintenance, not improvements? If not, budget a small project instead.
Yes to all four? A monthly care plan with a written scope is the right call. For budgeting, GoDaddy puts small business maintenance at roughly $50 to $500 a month and ecommerce at $300 to $1,000.
How Post-Launch Care Protects AI Search Visibility
Google AI Overviews, ChatGPT, and Perplexity lean on pages that load fast, stay crawlable, and carry current facts. A neglected site slips on all three. If a crawler hits a 500 error or a page stuck behind a broken plugin, that page simply drops out of the answer, and a competitor’s page gets cited instead. Add these to the monthly cycle:
- Validate schema markup (Organization, Article, FAQPage) after every update.
- Confirm robots.txt does not block Googlebot, OAI-SearchBot, or PerplexityBot.
- Refresh stats and dates on top pages each quarter.
Turn Launch Day Into a Long-Term Partnership
XCEEDBD builds and maintains websites for US businesses and agencies, with care scopes written before launch instead of argued about after it. Need a 90-day care plan, white-label maintenance, or a site health check? Talk to XCEEDBD today.
Frequently Asked Questions
What should a website maintenance plan include?
Backups, tested core, theme, and plugin updates, security checks, form testing, performance monitoring, and a monthly report. New features belong in a separate project.
How long is a typical post-launch warranty?
Most agencies give 30 days to report defects in delivered work. It covers bugs against the agreed spec, not new requests.
How much does website maintenance cost per month?
Roughly $50 to $500 for a small business site and $300 to $1,000 for ecommerce, based on GoDaddy ranges. Enterprise sites often run $2,000 a month or more.
Is a launch warranty the same as a care plan?
No. A warranty fixes faults in delivered work for a fixed window. A care plan is the ongoing monthly cycle of backups, updates, and checks.
How often should a WordPress site be updated?
Review updates weekly and apply them at least monthly. Push critical security patches as soon as they pass staging tests.
What happens at the 90-day review?
Sort past requests into maintenance and improvements, then renew, resize the plan, or hand over with a runbook.
What happens if we cancel website care?
Monitoring stops. A clean exit hands over maintenance records, recent backups, and every client-owned login.
Can an agency white-label website maintenance?
Yes. Many agencies keep the client relationship and outsource routine care to a partner working under their brand.
