[{"data":1,"prerenderedAt":201},["ShallowReactive",2],{"seo-features/business-severity-scoring":3},{"slug":4,"kind":5,"archetype":6,"cluster":7,"navGroup":8,"navLabel":9,"meta":10,"breadcrumbs":15,"hero":23,"sections":65},"features/business-severity-scoring","spoke","capability","features","monitoring","Business Severity Scoring",{"title":11,"description":12,"canonicalPath":13,"twitterCard":14},"Business Severity Scoring — Prioritize Incidents by Page Importance | Sitewatch","Incident severity adjusts based on the business importance of the affected page. A medium issue on a critical checkout page becomes high severity and bypasses quiet hours.","/features/business-severity-scoring","summary_large_image",[16,19,22],{"label":17,"href":18},"Home","/",{"label":20,"href":21},"Features","/features",{"label":9,"href":13},{"eyebrow":24,"headline":25,"intentStatement":26,"bullets":27,"primaryCta":37,"secondaryCta":40,"proofPanel":43},"Business severity","A Broken Checkout Is Not the Same as a Broken Blog Image","Most monitoring tools treat every page the same. Sitewatch adjusts incident severity based on business importance — a medium issue on your client's checkout page (marked \"critical\") becomes high severity and bypasses quiet hours. The same issue on a blog page stays medium. Your team gets woken up for revenue emergencies, not cosmetic issues.",[28,31,34],{"icon":29,"text":30},"heroicons:arrow-trending-up","Severity adjusted by page importance — critical pages escalate automatically",{"icon":32,"text":33},"heroicons:bell-snooze","Critical pages bypass quiet hours so revenue issues never wait until morning",{"icon":35,"text":36},"heroicons:funnel","Reduces alert noise for low-importance pages — fewer interruptions, better focus",{"label":38,"href":39},"Start prioritizing by impact","/#pricing",{"label":41,"href":42},"See critical page monitoring","/features/critical-page-monitoring",{"type":44,"incidentTitle":45,"severity":44,"affectedLabel":46,"detectedLabel":47,"eventLines":48},"incident","Severity escalated — Critical page","/checkout — Business importance: Critical","Medium → High (escalated by business importance)",[49,54,58,60,62],{"icon":50,"text":51,"time":52,"type":53},"heroicons:exclamation-triangle","Issue detected — medium severity","3:12 AM","warning",{"icon":55,"text":56,"time":52,"type":57},"heroicons:star","Page importance checked — Critical","ok",{"icon":29,"text":59,"time":52,"type":44},"Severity escalated to High",{"icon":32,"text":61,"time":52,"type":44},"Quiet hours bypassed — critical page",{"icon":63,"text":64,"time":52,"type":44},"heroicons:bell-alert","Alert sent to 3 channels",[66,94,108,131,155,176],{"id":67,"tocLabel":68,"type":69,"eyebrow":70,"heading":71,"items":72},"benefits","Benefits","benefits-grid","Why business severity scoring","Not every broken page deserves the same response",[73,76,79,82,86,90],{"icon":29,"title":74,"description":75},"Severity adjusted by importance","A medium issue on a critical page becomes high severity. A medium issue on a blog page stays medium. Alerts reflect real business impact.",{"icon":32,"title":77,"description":78},"Critical pages bypass quiet hours","When a critical page has an incident, quiet hours are overridden automatically. Revenue-impacting issues never wait until morning.",{"icon":35,"title":80,"description":81},"Reduces alert noise","Low-importance pages generate lower-priority alerts. Your team focuses on what matters instead of chasing cosmetic issues on blog posts.",{"icon":83,"title":84,"description":85},"heroicons:cog-6-tooth","No configuration per incident","Set the importance level once per page. Sitewatch handles the severity adjustment automatically every time an issue is detected.",{"icon":87,"title":88,"description":89},"heroicons:shield-check","Works with all failure types","Broken links, missing assets, SSL errors, performance regression — severity scoring applies to every detection rule, not just specific issue types.",{"icon":91,"title":92,"description":93},"heroicons:sparkles","Business-aware, not just technical","Most monitoring tools treat every page equally. Sitewatch adjusts incident severity based on the business importance of the affected page — so your response matches the real-world impact.",{"id":95,"tocLabel":96,"type":97,"stats":98},"trust","Trust","trust-strip",[99,102,105],{"value":100,"label":101},"4","Importance levels",{"value":103,"label":104},"Yes","Quiet hour bypass",{"value":106,"label":107},"All","Plans supported",{"id":109,"tocLabel":110,"type":111,"eyebrow":110,"heading":112,"bgVariant":113,"steps":114},"how-it-works","How it works","how-it-works-stepper","From page importance to business-aware severity in four steps","muted",[115,119,123,128],{"number":116,"icon":55,"title":117,"description":118},"01","Set page importance","Tag each monitored page as critical, high, normal, or low. This tells Sitewatch how important that page is to your business.",{"number":120,"icon":50,"title":121,"description":122},"02","Incident detected","Sitewatch detects an issue on one of your monitored pages — a broken asset, SSL error, performance regression, or any other failure.",{"number":124,"icon":125,"title":126,"description":127},"03","heroicons:scale","Severity weighted by importance","The raw severity is adjusted based on the page's business importance. A medium issue on a critical page is escalated to high severity.",{"number":129,"icon":63,"title":77,"description":130},"04","If the affected page is marked critical, quiet hours are overridden. Your team is alerted immediately, even at 3 AM.",{"id":132,"tocLabel":133,"type":134,"eyebrow":135,"heading":136,"withoutLabel":137,"withLabel":24,"rows":138},"comparison","Comparison","comparison-table","The difference","Flat severity vs. business severity","Flat severity",[139,143,147,151],{"label":140,"withoutValue":141,"withValue":142},"How severity is determined","Based on issue type alone — every page treated equally","Issue type weighted by page business importance",{"label":144,"withoutValue":145,"withValue":146},"Quiet hours behavior","All alerts suppressed during quiet hours","Critical pages bypass quiet hours automatically",{"label":148,"withoutValue":149,"withValue":150},"Alert noise","Same urgency for blog and checkout","Low-importance pages generate lower-priority alerts",{"label":152,"withoutValue":153,"withValue":154},"Business context","None — just technical severity","Every alert reflects the business impact of the affected page",{"id":156,"tocLabel":157,"type":158,"eyebrow":157,"heading":159,"items":160},"faq","FAQ","faq-accordion","Frequently asked questions",[161,164,167,170,173],{"question":162,"answer":163},"How does business severity scoring work?","When Sitewatch detects an issue, it checks the business importance level of the affected page. If the page is marked as critical or high, the severity is escalated automatically. A medium issue on a critical page becomes a high-severity incident.",{"question":165,"answer":166},"What are the importance levels?","There are four levels: critical, high, normal, and low. You assign one level per monitored page. Critical is for pages like checkout and login where downtime directly impacts revenue. Low is for pages like blog posts where issues are less urgent.",{"question":168,"answer":169},"Does it affect all alert channels?","Yes. Severity scoring applies before alerts are sent, so every channel — Slack, email, SMS, webhooks — receives the escalated severity. There is no need to configure per-channel rules.",{"question":171,"answer":172},"Is business severity scoring available on all plans?","Yes. Every plan that supports critical page monitoring includes business severity scoring. The number of pages you can monitor depends on your plan (1 on Free, 5 on Starter, 25 on Pro).",{"question":174,"answer":175},"How does it interact with quiet hours?","If an incident affects a page marked as critical, quiet hours are bypassed and the alert is sent immediately. For pages marked high, normal, or low, quiet hours are respected as usual.",{"id":177,"tocLabel":178,"type":179,"eyebrow":180,"heading":181,"links":182},"related","Related","related-links-grid","Explore more","Related monitoring capabilities",[183,186,191,196],{"label":184,"href":42,"description":185,"icon":55},"Critical Page Monitoring","Monitor up to 25 pages per site with business importance levels.",{"label":187,"href":188,"description":189,"icon":190},"Alerts & Notifications","/alerts-notifications","Get notified via Slack, email, SMS, and more.","heroicons:bell",{"label":192,"href":193,"description":194,"icon":195},"Root Cause Analysis","/features/root-cause-analysis","Automatic diagnosis with confidence scoring and evidence.","heroicons:light-bulb",{"label":197,"href":198,"description":199,"icon":200},"For Agencies","/for-agencies","Monitor all client websites from a single dashboard.","heroicons:building-office",1775563111647]