{"product_id":"claude-code-website-operations-maintenance-system","title":"Claude Code Website Operations \u0026 Maintenance System","description":"\u003ch2 id=\"headline\"\u003eYour website is live. Now keep it healthy.\u003c\/h2\u003e\n\n\u003cp class=\"sbs-lede\"\u003eA complete operating system for running a production website with Claude Code — monitoring, security checks, dependency updates, backup verification, performance regression, SEO maintenance, deployment gates, incident diagnosis and monthly reporting. Not a prompt pack: 17 modules, 19 slash commands, 11 working scripts, 9 checklists, 8 report templates and 4 platform guides, with a safety system that never touches production without your say-so.\u003c\/p\u003e\n\n\u003ch2 id=\"problem\"\u003eThe problem\u003c\/h2\u003e\n\n\u003cp\u003eLaunching is the short part. What follows is years of small things going wrong quietly: a certificate that stops auto-renewing, a contact form that has delivered nothing since the mail provider tightened its rules, a plugin two majors behind with a published exploit, a deploy that took the checkout button off mobile, a backup nobody has ever restored, a \u003ccode\u003enoindex\u003c\/code\u003e left on after a migration. None of them announce themselves. Each shows up weeks later as a lost order, a lost ranking, or a Friday-evening outage.\u003c\/p\u003e\n\n\u003cp\u003eAsk a capable model to “fix the site” and you get a confident change on production with no rollback point and no record. Ask it to “check the site” and you get a paragraph of reassurance based on a page that loaded. Neither is operations.\u003c\/p\u003e\n\n\u003ch2 id=\"solution\"\u003eThe solution\u003c\/h2\u003e\n\n\u003cp\u003eOperations is a set of checks with a rhythm, a way of scoring what they find, and a discipline for changing things. This system gives you all three, built to run inside Claude Code:\u003c\/p\u003e\n\n\u003cul\u003e\n  \u003cli\u003e\n\u003cstrong\u003eWorking scripts\u003c\/strong\u003e that measure the site from outside — HTTP, TLS, DNS, headers, exposure, links, redirects, sitemap, endpoints, baseline — and merge into one report with a health score. Standard-library Python; nothing to install.\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003eSlash commands\u003c\/strong\u003e that run the scripts, read the results, add the parts a script cannot see (backups, forms, flows, logs, dependencies), and write the report in a fixed format.\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003eA safety system.\u003c\/strong\u003e Every change follows \u003cstrong\u003eDiscover → Analyze → Backup → Change → Test → Validate → Document\u003c\/strong\u003e. Audit commands change nothing. The two that do propose one change with its rollback point and wait for a yes. Secrets are never printed, logged, committed or reported.\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003eA rhythm\u003c\/strong\u003e: daily, weekly, every deploy, monthly, quarterly — as one-page checklists and as automation samples that run the daily part for you.\u003c\/li\u003e\n\u003c\/ul\u003e\n\n\u003ch2 id=\"included\"\u003eWhat is included\u003c\/h2\u003e\n\n\u003cp\u003e106 files, 17 modules, 19 commands, 11 scripts — about 63,000 words — in one download. Every number here was counted at build time from the bundle, not typed.\u003c\/p\u003e\n\n\u003cdiv class=\"sbs-table\"\u003e\n\u003ctable\u003e\n\u003cthead\u003e\u003ctr\u003e\n\u003cth\u003eModule\u003c\/th\u003e\n\u003cth\u003eCovers\u003c\/th\u003e\n\u003c\/tr\u003e\u003c\/thead\u003e\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u003ccode\u003e01-getting-started\u003c\/code\u003e\u003c\/td\u003e\n\u003ctd\u003eSetup in ten minutes, the safety system, every configuration value explained\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u003ccode\u003e02-website-health\u003c\/code\u003e\u003c\/td\u003e\n\u003ctd\u003eThe daily health check and how to read its score\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u003ccode\u003e03-uptime\u003c\/code\u003e\u003c\/td\u003e\n\u003ctd\u003eThe four layers of “down”; what to monitor and from where\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u003ccode\u003e04-security\u003c\/code\u003e\u003c\/td\u003e\n\u003ctd\u003eTransport, headers, exposure probes, platform checks; dependency vulnerabilities by reachability\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u003ccode\u003e05-dependencies\u003c\/code\u003e\u003c\/td\u003e\n\u003ctd\u003eThe inventory; the update plan in batches with rollback points\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u003ccode\u003e06-backups\u003c\/code\u003e\u003c\/td\u003e\n\u003ctd\u003eCompleteness by platform, the three numbers, the monthly restore test\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u003ccode\u003e07-performance\u003c\/code\u003e\u003c\/td\u003e\n\u003ctd\u003eMeasurement, regression bracketing, the baseline file format\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u003ccode\u003e08-seo-maintenance\u003c\/code\u003e\u003c\/td\u003e\n\u003ctd\u003eSitemap, robots, canonicals, noindex, structured data, Search Console coverage — keeping what ranks from breaking\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u003ccode\u003e09-links-redirects\u003c\/code\u003e\u003c\/td\u003e\n\u003ctd\u003eBudgeted crawling; redirect chains, loops, codes and gone rules\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u003ccode\u003e10-forms-flows\u003c\/code\u003e\u003c\/td\u003e\n\u003ctd\u003eForms end to end including delivery; critical flows with a Playwright shape\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u003ccode\u003e11-deployment\u003c\/code\u003e\u003c\/td\u003e\n\u003ctd\u003eThe nine-question pre-deploy gate; the ten-minute post-deploy check; rollback by provider\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u003ccode\u003e12-diagnostics\u003c\/code\u003e\u003c\/td\u003e\n\u003ctd\u003eLog analysis in a fixed seven-section format, with redaction rules\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u003ccode\u003e13-incidents\u003c\/code\u003e\u003c\/td\u003e\n\u003ctd\u003eSEV-1 to SEV-4, the first ten minutes, ten playbooks\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u003ccode\u003e14-monthly\u003c\/code\u003e\u003c\/td\u003e\n\u003ctd\u003eThe two-hour monthly session; the flagship audit with per-area scoring\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u003ccode\u003e15-reporting\u003c\/code\u003e\u003c\/td\u003e\n\u003ctd\u003eEight report templates, from the daily health report to the executive summary\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u003ccode\u003e16-automation\u003c\/code\u003e\u003c\/td\u003e\n\u003ctd\u003eA check runner, a crontab, two GitHub Actions workflows\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u003ccode\u003e17-platforms\u003c\/code\u003e\u003c\/td\u003e\n\u003ctd\u003eShopify, WordPress, Astro and static hosts, Node.js\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003c\/tbody\u003e\n\u003c\/table\u003e\n\u003c\/div\u003e\n\n\u003cp\u003ePlus \u003ccode\u003ecommands\/\u003c\/code\u003e with 19 slash commands for \u003ccode\u003e.claude\/commands\/\u003c\/code\u003e, \u003ccode\u003escripts\/\u003c\/code\u003e with 11 scripts, \u003ccode\u003etemplates\/\u003c\/code\u003e with the \u003ccode\u003eCLAUDE.md\u003c\/code\u003e site block and operating rules, the config file, the critical-URL list and the baseline format, \u003ccode\u003echecklists\/\u003c\/code\u003e with all nine, and \u003ccode\u003eexamples\/\u003c\/code\u003e with a real operations report from this store and three worked examples.\u003c\/p\u003e\n\n\u003ch2 id=\"commands\"\u003eThe commands\u003c\/h2\u003e\n\n\u003cdiv class=\"sbs-table\"\u003e\n\u003ctable\u003e\n\u003cthead\u003e\u003ctr\u003e\n\u003cth\u003eCommand\u003c\/th\u003e\n\u003cth\u003eWhat it does\u003c\/th\u003e\n\u003c\/tr\u003e\u003c\/thead\u003e\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u003ccode\u003e\/website-health-check\u003c\/code\u003e\u003c\/td\u003e\n\u003ctd\u003eUp, TLS, DNS, headers, sitemap, redirects, link sample, baseline — scored, in five minutes\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u003ccode\u003e\/website-operations-audit\u003c\/code\u003e\u003c\/td\u003e\n\u003ctd\u003e\n\u003cstrong\u003eFlagship.\u003c\/strong\u003e Every area checked and scored; the master report and \u003ccode\u003eoperations-report.json\u003c\/code\u003e\n\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u003ccode\u003e\/security-check\u003c\/code\u003e\u003c\/td\u003e\n\u003ctd\u003eTLS, forced HTTPS, security headers, exposure probes, platform checks\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\n\u003ccode\u003e\/dependency-audit\u003c\/code\u003e → \u003ccode\u003e\/update-plan\u003c\/code\u003e\n\u003c\/td\u003e\n\u003ctd\u003eInventory and advisories ranked by reachability; updates in batches, staging first, rollback named\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u003ccode\u003e\/check-backups\u003c\/code\u003e\u003c\/td\u003e\n\u003ctd\u003eExistence, completeness, age, off-site; the monthly restore test\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\n\u003ccode\u003e\/performance-check\u003c\/code\u003e \/ \u003ccode\u003e\/performance-regression\u003c\/code\u003e\n\u003c\/td\u003e\n\u003ctd\u003eServer and browser measurements against the baseline; bracket a slowdown to the change that caused it\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u003ccode\u003e\/seo-maintenance-check\u003c\/code\u003e\u003c\/td\u003e\n\u003ctd\u003eSitemap, robots, canonicals, noindex, titles, structured data, Search Console\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\n\u003ccode\u003e\/link-check\u003c\/code\u003e \/ \u003ccode\u003e\/redirect-audit\u003c\/code\u003e\n\u003c\/td\u003e\n\u003ctd\u003eEvery broken or bent link with the fix; every redirect one hop, permanent, correct\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\n\u003ccode\u003e\/check-forms\u003c\/code\u003e \/ \u003ccode\u003e\/check-critical-flows\u003c\/code\u003e\n\u003c\/td\u003e\n\u003ctd\u003eEach form through to delivery; each flow on desktop and mobile, in test mode\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\n\u003ccode\u003e\/pre-deploy-check\u003c\/code\u003e → \u003ccode\u003e\/post-deploy-check\u003c\/code\u003e\n\u003c\/td\u003e\n\u003ctd\u003eGO or NO-GO before; KEEP or ROLL BACK after\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u003ccode\u003e\/log-analysis\u003c\/code\u003e\u003c\/td\u003e\n\u003ctd\u003eA log window into Executive Summary, Likely Cause, Immediate Checks, Diagnostic Commands, Remediation, Validation, Rollback\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u003ccode\u003e\/incident-diagnose\u003c\/code\u003e\u003c\/td\u003e\n\u003ctd\u003eConfirm, classify, restore, stabilise, diagnose, report\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\n\u003ccode\u003e\/monthly-maintenance\u003c\/code\u003e → \u003ccode\u003e\/generate-maintenance-report\u003c\/code\u003e\n\u003c\/td\u003e\n\u003ctd\u003eThe monthly session; the report with \u003cem\u003eOverall Health Score: NN\/100\u003c\/em\u003e and the executive summary\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003c\/tbody\u003e\n\u003c\/table\u003e\n\u003c\/div\u003e\n\n\u003ch2 id=\"scripts\"\u003eThe scripts\u003c\/h2\u003e\n\n\u003cp\u003e\u003ccode\u003echeck_http\u003c\/code\u003e, \u003ccode\u003echeck_ssl\u003c\/code\u003e, \u003ccode\u003echeck_dns\u003c\/code\u003e, \u003ccode\u003echeck_headers\u003c\/code\u003e, \u003ccode\u003ecrawl_links\u003c\/code\u003e, \u003ccode\u003eaudit_redirects\u003c\/code\u003e, \u003ccode\u003evalidate_sitemap\u003c\/code\u003e, \u003ccode\u003etest_endpoints\u003c\/code\u003e, \u003ccode\u003ecompare_baseline\u003c\/code\u003e, \u003ccode\u003egenerate_report\u003c\/code\u003e, \u003ccode\u003eread_config\u003c\/code\u003e. Python 3.8 or newer, standard library only. Each has \u003ccode\u003e--help\u003c\/code\u003e and \u003ccode\u003e--json\u003c\/code\u003e, and all use the same exit codes (0 pass, 1 warning, 2 fail, 3 could not run) so a scheduler can read them. One command runs the core set and writes the scored report:\u003c\/p\u003e\n\n\u003cpre\u003e\u003ccode\u003epython3 ops\/scripts\/generate_report.py --run https:\/\/your-site.example\nOverall Health Score: 94\/100 — Healthy\u003c\/code\u003e\u003c\/pre\u003e\n\n\u003cp\u003eThat line is from the sample report in \u003ccode\u003eexamples\/\u003c\/code\u003e, which is a real, unedited run against this store. The warnings in it are real too.\u003c\/p\u003e\n\n\u003ch2 id=\"who\"\u003eWho it is for\u003c\/h2\u003e\n\n\u003cp\u003eAnyone responsible for a website that is already live: developers who built it and now keep it, freelancers and agencies maintaining client sites, founders running their own store, and the person who inherited “the website” with a login and no documentation. It assumes you can run a command and reach the site. It does not assume you have done operations before — the checklists and the safety system are there so that you do it the careful way from the first day.\u003c\/p\u003e\n\n\u003cp\u003eIf the site is not built yet, this is the wrong product; start with the \u003ca href=\"\/products\/claude-code-website-launch-system\"\u003eWebsite Launch System\u003c\/a\u003e. If it is built and nobody is arriving, the \u003ca href=\"\/products\/claude-code-seo-website-audit-toolkit\"\u003eSEO \u0026amp; Website Audit Toolkit\u003c\/a\u003e. If people arrive and do not buy, the \u003ca href=\"\/products\/claude-code-conversion-revenue-optimization-toolkit\"\u003eConversion \u0026amp; Revenue Optimization Toolkit\u003c\/a\u003e. This one is for keeping a live site live.\u003c\/p\u003e\n\n\u003ch2 id=\"platforms\"\u003ePlatforms\u003c\/h2\u003e\n\n\u003cp\u003eFour guides, one per platform, each saying what the platform handles for you, what it does not, where each lever is, and what every check adds on that platform: \u003cstrong\u003eShopify\u003c\/strong\u003e (apps and permissions, theme rollback, what to export because Shopify does not back it up for you), \u003cstrong\u003eWordPress\u003c\/strong\u003e (host-managed versus self-hosted, item by item; plugins, PHP end-of-life, mail delivery, debug logs), \u003cstrong\u003eAstro and static sites\u003c\/strong\u003e (build-time risk, header and redirect files, form services, secrets in the bundle) and \u003cstrong\u003eNode.js applications\u003c\/strong\u003e (the health endpoint, logs, database backups, process restarts, migrations that cannot be rolled back). The scripts and the commands are the same on all four.\u003c\/p\u003e\n\n\u003ch2 id=\"beforeafter\"\u003eBefore and after\u003c\/h2\u003e\n\n\u003cdiv class=\"sbs-table\"\u003e\n\u003ctable\u003e\n\u003cthead\u003e\u003ctr\u003e\n\u003cth\u003eBefore\u003c\/th\u003e\n\u003cth\u003eAfter\u003c\/th\u003e\n\u003c\/tr\u003e\u003c\/thead\u003e\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003eYou find out the site is down from a customer\u003c\/td\u003e\n\u003ctd\u003eThe four-layer check — DNS, TLS, host, application — runs every five minutes and tells you which layer\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e“The contact form works, it loads”\u003c\/td\u003e\n\u003ctd\u003eOne tagged test submission a week, confirmed in the real inbox, with SPF and DKIM checked when it is not\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eDeploy, refresh the homepage, go home\u003c\/td\u003e\n\u003ctd\u003eA nine-question gate before; a ten-minute check after that says KEEP or ROLL BACK\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eBackups exist, probably\u003c\/td\u003e\n\u003ctd\u003eAge, restore time, and the date of the last verified restore — measured monthly\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eTwenty-three outdated packages and no plan\u003c\/td\u003e\n\u003ctd\u003eThree batches, each with a rollback point, applied on staging first\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eA fix on production in the same breath as the discovery\u003c\/td\u003e\n\u003ctd\u003eDiscover → Analyze → Backup → Change → Test → Validate → Document, with a yes before Change\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e“How is the site doing?” — “Fine, I think”\u003c\/td\u003e\n\u003ctd\u003eA monthly report with a score, a trend, and the three things being done next month\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003c\/tbody\u003e\n\u003c\/table\u003e\n\u003c\/div\u003e\n\n\u003ch2 id=\"workflow\"\u003eThe recurring workflow\u003c\/h2\u003e\n\n\u003cdiv class=\"sbs-table\"\u003e\n\u003ctable\u003e\n\u003cthead\u003e\u003ctr\u003e\n\u003cth\u003eWhen\u003c\/th\u003e\n\u003cth\u003eWhat\u003c\/th\u003e\n\u003cth\u003eTime\u003c\/th\u003e\n\u003c\/tr\u003e\u003c\/thead\u003e\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003eDaily\u003c\/td\u003e\n\u003ctd\u003e\n\u003ccode\u003e\/website-health-check\u003c\/code\u003e, or the automated run and a glance at the monitor\u003c\/td\u003e\n\u003ctd\u003e3 minutes\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eWeekly\u003c\/td\u003e\n\u003ctd\u003eSecurity, links, forms, flows, SEO short form, backup existence\u003c\/td\u003e\n\u003ctd\u003e30–45 minutes\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eEvery deploy\u003c\/td\u003e\n\u003ctd\u003e\n\u003ccode\u003e\/pre-deploy-check\u003c\/code\u003e → deploy → \u003ccode\u003e\/post-deploy-check\u003c\/code\u003e\n\u003c\/td\u003e\n\u003ctd\u003e15 minutes\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eMonthly\u003c\/td\u003e\n\u003ctd\u003eThe full audit, the restore test, the dependency plan, the report\u003c\/td\u003e\n\u003ctd\u003e2 hours\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eQuarterly\u003c\/td\u003e\n\u003ctd\u003eAccess, expiry dates, configuration drift, third parties\u003c\/td\u003e\n\u003ctd\u003e1–2 hours\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003c\/tbody\u003e\n\u003c\/table\u003e\n\u003c\/div\u003e\n\n\u003cp\u003eEach is a one-page checklist in \u003ccode\u003echecklists\/\u003c\/code\u003e. The daily and weekly checks can run themselves from cron or GitHub Actions with the samples in \u003ccode\u003e16-automation\/\u003c\/code\u003e; the changes never do.\u003c\/p\u003e\n\n\u003ch2 id=\"honest\"\u003eWhat it will not do\u003c\/h2\u003e\n\n\u003cp\u003e\u003cstrong\u003eIt will not run penetration tests.\u003c\/strong\u003e The security check reads headers and TLS and probes a fixed list of paths that must never be public. It attempts no logins, injection, fuzzing or load, and it says so. Application security testing is a separate engagement with a written scope.\u003c\/p\u003e\n\n\u003cp\u003e\u003cstrong\u003eIt will not automate a change.\u003c\/strong\u003e Checks are scheduled; changes are authorised one at a time with a rollback point named first. That is the design, not a limitation.\u003c\/p\u003e\n\n\u003cp\u003e\u003cstrong\u003eIt will not hide a finding to improve the score.\u003c\/strong\u003e The score is computed from the findings by a script. Accepted findings are listed as accepted, not deleted, and anything that could not be checked is reported as not verified rather than as a pass.\u003c\/p\u003e\n\n\u003ch2 id=\"compare\"\u003eHow it fits with the other three\u003c\/h2\u003e\n\n\u003cdiv class=\"sbs-table\"\u003e\n\u003ctable\u003e\n\u003cthead\u003e\u003ctr\u003e\n\u003cth\u003e\u003c\/th\u003e\n\u003cth\u003eOperations \u0026amp; Maintenance\u003c\/th\u003e\n\u003cth\u003eWebsite Launch System\u003c\/th\u003e\n\u003cth\u003eSEO \u0026amp; Website Audit\u003c\/th\u003e\n\u003cth\u003eConversion \u0026amp; Revenue\u003c\/th\u003e\n\u003c\/tr\u003e\u003c\/thead\u003e\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003ePrice\u003c\/td\u003e\n\u003ctd\u003e$39.99\u003c\/td\u003e\n\u003ctd\u003e$19.99\u003c\/td\u003e\n\u003ctd\u003e$19.99\u003c\/td\u003e\n\u003ctd\u003e$19.99\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eStage\u003c\/td\u003e\n\u003ctd\u003eOperate\u003c\/td\u003e\n\u003ctd\u003eBuild\u003c\/td\u003e\n\u003ctd\u003eRank\u003c\/td\u003e\n\u003ctd\u003eConvert\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eBest for\u003c\/td\u003e\n\u003ctd\u003eA live site you must keep healthy\u003c\/td\u003e\n\u003ctd\u003eA site you are building\u003c\/td\u003e\n\u003ctd\u003eA site that is not ranking\u003c\/td\u003e\n\u003ctd\u003eTraffic that under-converts\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eUptime, incidents, playbooks\u003c\/td\u003e\n\u003ctd\u003eComplete\u003c\/td\u003e\n\u003ctd\u003eNot covered\u003c\/td\u003e\n\u003ctd\u003eNot covered\u003c\/td\u003e\n\u003ctd\u003eNot covered\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eSecurity hygiene and dependency updates\u003c\/td\u003e\n\u003ctd\u003eComplete, recurring\u003c\/td\u003e\n\u003ctd\u003eOne-time audit at launch\u003c\/td\u003e\n\u003ctd\u003eNot covered\u003c\/td\u003e\n\u003ctd\u003eNot covered\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eBackups and restore testing\u003c\/td\u003e\n\u003ctd\u003eComplete\u003c\/td\u003e\n\u003ctd\u003eNot covered\u003c\/td\u003e\n\u003ctd\u003eNot covered\u003c\/td\u003e\n\u003ctd\u003eNot covered\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eDeployment gates\u003c\/td\u003e\n\u003ctd\u003eComplete\u003c\/td\u003e\n\u003ctd\u003eSetup of CI\/CD\u003c\/td\u003e\n\u003ctd\u003eNot covered\u003c\/td\u003e\n\u003ctd\u003eNot covered\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eLog analysis and diagnostics\u003c\/td\u003e\n\u003ctd\u003eComplete\u003c\/td\u003e\n\u003ctd\u003eNot covered\u003c\/td\u003e\n\u003ctd\u003eNot covered\u003c\/td\u003e\n\u003ctd\u003eNot covered\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003ePerformance\u003c\/td\u003e\n\u003ctd\u003eRegression against a baseline\u003c\/td\u003e\n\u003ctd\u003eIncluded at build\u003c\/td\u003e\n\u003ctd\u003eCore Web Vitals in full\u003c\/td\u003e\n\u003ctd\u003eConversion effect only\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eSEO\u003c\/td\u003e\n\u003ctd\u003eMaintenance only\u003c\/td\u003e\n\u003ctd\u003eIncluded at build\u003c\/td\u003e\n\u003ctd\u003eComplete\u003c\/td\u003e\n\u003ctd\u003eNot covered\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eConversion\u003c\/td\u003e\n\u003ctd\u003eForms and flows must work\u003c\/td\u003e\n\u003ctd\u003eOne landing-page workflow\u003c\/td\u003e\n\u003ctd\u003eNot covered\u003c\/td\u003e\n\u003ctd\u003eComplete\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eWorking scripts\u003c\/td\u003e\n\u003ctd\u003e11, standard library\u003c\/td\u003e\n\u003ctd\u003eNot included\u003c\/td\u003e\n\u003ctd\u003eNot included\u003c\/td\u003e\n\u003ctd\u003eNot included\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eMonthly reporting\u003c\/td\u003e\n\u003ctd\u003eComplete\u003c\/td\u003e\n\u003ctd\u003eNot covered\u003c\/td\u003e\n\u003ctd\u003eNot covered\u003c\/td\u003e\n\u003ctd\u003eNot covered\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003c\/tbody\u003e\n\u003c\/table\u003e\n\u003c\/div\u003e\n\n\u003cp\u003eThe three earlier products are also sold together as the \u003ca href=\"\/products\/complete-site-builder-stack\"\u003eComplete Site Builder Stack\u003c\/a\u003e. This one is separate: it starts where they finish, and it is the only one of the four that you will use every week for as long as the site exists. Buying it does not include the others, and there is no automatic upgrade credit.\u003c\/p\u003e\n\n\u003ch2 id=\"delivery\"\u003eDelivery and licence\u003c\/h2\u003e\n\n\u003cp\u003eA single ZIP, delivered by download immediately after purchase. 106 files, about 220 KB — Markdown, Python, YAML and a shell script; nothing to install beyond Python 3, which your machine almost certainly has. A published SHA-256 checksum accompanies the download so you can verify what you received.\u003c\/p\u003e\n\n\u003cp\u003eLicensed to one person for unlimited websites, including client work. You may not redistribute or resell it. Full terms are in \u003ccode\u003eLICENSE.md\u003c\/code\u003e inside the archive.\u003c\/p\u003e\n\n\u003ch2 id=\"notpromised\"\u003eWhat is not promised\u003c\/h2\u003e\n\n\u003cp\u003eNo uptime figure, no security guarantee, no ranking. A passing check covers what the check measured and nothing more, and the reports say what they did not check. What you get is a way to know, every day, whether the site is as healthy as it was yesterday — and a careful, recorded way to change it when it is not.\u003c\/p\u003e\n","brand":"Site Builder Stack","offers":[{"title":"Default Title","offer_id":56264599830820,"sku":"SBS-CCWOMS-V1","price":39.99,"currency_code":"USD","in_stock":true}],"thumbnail_url":"\/\/cdn.shopify.com\/s\/files\/1\/0987\/3925\/7636\/files\/product-ops-system.png?v=1789270528","url":"https:\/\/sitebuilderstack.com\/products\/claude-code-website-operations-maintenance-system","provider":"Site Builder Stack","version":"1.0","type":"link"}