{
  "schema_version": 1,
  "lang": "en",
  "page_type": "content-page",
  "source_file": "should-service-page-say-what-is-not-included.html",
  "context_url": "https://hebora.be/contexts/should-service-page-say-what-is-not-included.en.json",
  "url": "https://hebora.be/should-service-page-say-what-is-not-included.html",
  "title": "Should a service page say what is not included? | Hebora",
  "meta_description": "Scope, options and responsibilities: discover how to explain service boundaries without alarming customers or turning the page into a contract.",
  "h1": "Useful boundaries reduce misunderstandings and make the service easier to choose.",
  "lead_paragraph": "A clear exclusion should explain the scope, not attempt to cover every possible risk.",
  "structured_data_types": [
    "WebPage",
    "BreadcrumbList",
    "ListItem"
  ],
  "headings": [
    {
      "level": 2,
      "text": "What you can observe"
    },
    {
      "level": 2,
      "text": "The short answer"
    },
    {
      "level": 2,
      "text": "Name the normal scope"
    },
    {
      "level": 3,
      "text": "Name the normal scope"
    },
    {
      "level": 3,
      "text": "Add common differences"
    },
    {
      "level": 3,
      "text": "Offer an option"
    },
    {
      "level": 2,
      "text": "Do not replace the quote or contract with this page."
    },
    {
      "level": 2,
      "text": "Make the business consistent"
    },
    {
      "level": 2,
      "text": "The question, directly"
    }
  ]
}