What should a website maintenance checklist include?
A website maintenance checklist should include checks for security and access, forms and integrations, links and redirects, speed and Core Web Vitals, analytics and tracking, accessibility, and content accuracy. The trick is assigning each to a cadence. Things that break fast get checked weekly. Things that drift get checked monthly or quarterly.
This checklist works for Framer, Webflow, WordPress and Next.js sites, with notes where the stack changes the task. It's the practical companion to our guide on what website maintenance includes, which explains why each area matters. Copy the tasks into your calendar with a named owner, and you'll catch most problems before customers do.
Cadence | Focus | Time it takes |
|---|---|---|
Weekly | Is anything broken right now? | About ten minutes |
Monthly | Is everything still working and secure? | One to two hours |
Quarterly | Is the site still fast, accessible and accurate? | Half a day |
Yearly | Are accounts, licenses and structure in order? | A day |
The time estimates assume a typical marketing site of 10 to 30 pages with a CMS and a handful of integrations. A larger site with a blog, docs or several languages takes longer, mostly in the content review.
What are the weekly website maintenance tasks?
Weekly website maintenance is a quick health check: is the site up, are leads still arriving and is analytics still recording? None of these needs technical skill, and together they catch the failures that cost the most, because they're the ones that hide.
- Check uptime alerts. Confirm your monitoring tool reported no outages, or that any it reported were resolved. Our guide to website uptime monitoring covers setup.
- Glance at lead volume. Compare form submissions or demo requests with the previous week. A sudden drop to zero is almost always technical, not a market shift.
- Sanity-check analytics. Make sure sessions and key events are recording. A flat line on a conversion event usually means a tag broke.
- Scan for anything obviously wrong. Load the homepage and pricing page on your phone. It takes a minute and catches broken banners and layouts.
What are the monthly website maintenance tasks?
Monthly website maintenance makes sure everything still works end to end and that only the right people have access. It's the core of upkeep. Do it on a fixed day, such as the first Monday, so it doesn't slide.
- Submit every important form with a test entry. Confirm the email arrives in the inbox, not spam, and the entry reaches your CRM. See website security basics for spam protection.
- Apply updates. On Next.js or WordPress, update dependencies or plugins in a branch, test on a preview and ship. On Framer or Webflow, review any platform change notes that affect your components.
- Review Search Console. Look for new crawl errors, pages dropping out of the index and manual actions. Check that the sitemap is still being read.
- Fix broken links. Run a crawler or link checker and fix 404s, especially on internal links and calls to action.
- Check redirects. If any URL changed this month, confirm the old one redirects with a single permanent redirect.
- Review access. Remove people who've left and confirm two-factor login is on for the registrar, host, CMS and analytics.
- Check integrations. Confirm scheduling, chat and CRM integrations still connect, and note any API keys that expire soon.
What are the quarterly website maintenance tasks?
Quarterly website maintenance checks the things that drift slowly: speed, accessibility, third-party scripts and content accuracy. They rarely break overnight, but after a few months of small changes, a fast, accessible site can become neither.
Core Web Vitals and speed
Review Core Web Vitals field data in Search Console or PageSpeed Insights for your key templates. Interaction to Next Paint (INP) is the metric most sites fail: Core Web Vitals field data for Q2 2026 shows only about two-thirds of Next.js sites pass it. The usual culprit is third-party scripts, so audit every tag, pixel, chat widget and embed, and remove anything nobody uses.
Accessibility
Run an automated accessibility checker on your main templates, then do a short manual pass: tab through the page with a keyboard, check focus is visible, and confirm images have useful alt text. Automated tools catch only part of the issues. If you find many, our guide to accessibility remediation shows how to fix an existing site in order of impact.
Content and answer-engine readiness
Review your top pages for accuracy: features, pricing, plan names, screenshots and team. Check that each still answers buyer questions directly near the top. Our AI visibility audit explains how to test whether answer engines can read and cite your pages, and how often to update website content gives a review routine.
A quick third-party script audit
Open your tag manager and the page source of your homepage, and list every external script: analytics, ad pixels, heatmaps, chat, A/B testing, scheduling widgets and fonts. For each, write down who asked for it, whether anyone used its data in the last quarter, and whether it loads on every page or only where needed.
Remove anything with no owner. Move anything page-specific, such as a scheduling widget, to only the pages that use it. Delay non-essential scripts until after the page is interactive. This one exercise often fixes more speed problems than any hosting change.
What are the yearly website maintenance tasks?
Yearly website maintenance covers ownership, licenses and the structure of the site as a whole. These tasks are rare but serious: an expired domain or lapsed font license is the kind of problem that takes a site down or creates legal risk.
- Confirm domain renewal and that auto-renew uses a current card. Work through the website ownership checklist at the same time.
- Review licenses for fonts, stock images, icons and paid components, and confirm they're in your company's name.
- Check hosting and plan costs. Platforms change pricing; our hosting cost guide helps you compare.
- Audit the site structure. Look for orphaned pages, outdated sections and pages that should be merged or retired.
- Review the tracking plan. Confirm the events you track still match what the business needs to measure.
- Plan the year ahead. Decide whether the site needs a refresh, a redesign or just steady improvements.
How do you run the checklist on different stacks?
The checklist is the same on every stack, but who does each task changes. On Framer and Webflow, the platform handles server and framework updates, so your team covers forms, content, access and speed. On Next.js and WordPress, someone with development skills also handles updates and anything that touches code.
On a code-based site, run updates in a branch and check them on a preview deployment before merging, so a broken package never reaches the live site. Our guide to Next.js maintenance explains how to keep dependencies current without big, risky upgrades. If a JavaScript-heavy site has crawl or indexing problems in Search Console, moving a React SPA to an SEO-friendly website covers the underlying fix.
How do you make sure the checklist actually gets done?
The checklist gets done when each cadence has an owner, a date and a place to record results. Without those three, maintenance becomes whatever someone remembers during a quiet week, which in a startup means rarely.
Assign an owner per cadence
One person owns the weekly check, even if others help with monthly or quarterly tasks.
Put it in the calendar
Recurring events with the checklist linked, on fixed days, so they survive busy weeks.
Log results
A simple shared doc or sheet: date, what was checked, what was found, what was fixed.
Escalate quickly
Decide in advance who fixes what. A broken form found on Monday shouldn't wait for next month.
If nobody on your team has the time or the skills for the monthly and quarterly tasks, that's a signal to hand them off. Compare the options in who updates your website after launch, or see what different levels of help typically cost in our website maintenance cost guide. On our retainer, this whole checklist is part of the routine, alongside new pages and improvements.
