Business Web Page Data Documentation

1. Quick Start

2. Requirement Legend

3. Core Business Data Contract

Put the machine-readable business metadata in one hidden element: #business-data. The rendering engine reads these values and generates the public page, SEO metadata, LocalBusiness structured data and PWA resources.

<div
  id="business-data"
  hidden

  data-name="Business Name"
  data-short_name="Business"

  data-description="A concise, accurate description of the business."

  data-phone="+8801XXXXXXXXX"
  data-whatsapp="+8801XXXXXXXXX"
  data-email="hello@example.com"

  data-address="Full street address"
  data-city="City"
  data-region="Region"
  data-country="BD"
  data-postal_code="0000"

  data-category="LocalBusiness"

  data-latitude="00.00000"
  data-longitude="00.00000"

  data-theme="#C0202A"
  data-background="#FAFAFA"

  data-seo_title="Business Name | Primary Service | City"
  data-pwa="true"
  data-lang="bn"
></div>

3.1 Required Data Fields

3.2 Strongly Recommended Fields

4. Image Specification

Images should represent the business or the content they are attached to. Use sharp, high-quality files and place images near relevant text. Meaningful alt text should describe the image in context.

Hero / primary image

First meaningful business image on the page. This image is also suitable for the generated social preview and primary business structured-data image.

Location image

Exterior, entrance, building, signboard or other genuine location evidence.

Service image

Show the real service, product, facility or customer-facing experience.

4.1 Image rules

5. SEO Data Contract

https://w.pointit.org/{business-slug}

{Business Name} | {Primary Service} | {City}

{Business} provides {primary services}
in {city}, serving {audience}.

5.1 Additional SEO principles

6. LocalBusiness Structured Data

6.1 Minimum semantic identity

{
  "@context": "https://schema.org",
  "@type": "LocalBusiness",
  "name": "Business Name",
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "Full street address",
    "addressLocality": "City",
    "addressRegion": "Region",
    "postalCode": "Postal code",
    "addressCountry": "BD"
  }
}

6.2 Preferred complete local-business representation

{
  "@context": "https://schema.org",
  "@type": "LocalBusiness",
  "@id": "https://w.pointit.org/business-slug#business",

  "name": "Business Name",
  "url": "https://w.pointit.org/business-slug",

  "description": "Accurate business description.",

  "image": [
    "https://imgur.com/XXX",
    "https://imgur.com/XXX",
    "https://imgur.com/XXX"
  ],

  "telephone": "+8801XXXXXXXXX",

  "address": {
    "@type": "PostalAddress",
    "streetAddress": "Full street address",
    "addressLocality": "City",
    "addressRegion": "Region",
    "postalCode": "0000",
    "addressCountry": "BD"
  },

  "geo": {
    "@type": "GeoCoordinates",
    "latitude": 24.49212,
    "longitude": 91.77446
  },

  "sameAs": [
    "https://www.facebook.com/example",
    "https://www.instagram.com/example"
  ]
}

6.3 LocalBusiness fields

7. Location Data

data-address="Full street address"
data-city="City"
data-country="BD"

data-address="Full street address"
data-city="City"
data-region="Region"
data-postal_code="0000"
data-country="BD"

data-latitude="24.49212"
data-longitude="91.77446"

7.1 Location image

Recommended: storefront, entrance, building frontage, signboard or another authentic visual cue that helps people identify the real-world location.

8. Contact Data

The visible page should also contain usable contact links:

<a href="tel:+8801887799196">
  Call the business
</a>

<a href="https://wa.me/8801887799196">
  WhatsApp
</a>

<a href="mailto:hello@example.com">
  Email
</a>

9. Opening Hours

Opening hours should be published only when they are maintained accurately. For future renderer support, use a structured internal representation rather than placing free-form hours inside unrelated text.

data-opening_hours='[
  {
    "dayOfWeek": ["Monday", "Tuesday", "Wednesday", "Thursday", "Friday"],
    "opens": "09:00",
    "closes": "18:00"
  },
  {
    "dayOfWeek": ["Saturday"],
    "opens": "10:00",
    "closes": "16:00"
  }
]'

This field is part of the target platform contract and may require renderer support in the next index.js revision.

10. Official Identity & Social Profiles

Future renderer versions should support a structured list of official identity URLs. Only include profiles that genuinely represent the same business.

data-same_as='[
  "https://www.facebook.com/example",
  "https://www.instagram.com/example",
  "https://www.linkedin.com/company/example"
]'

11. Visible Page Content Structure

Metadata alone does not create a useful business page. The visible page should clearly explain the business to people first.

12. PWA Specification

Every business page marked with data-pwa="true" should receive a business-specific web app manifest, icons and application metadata.

12.1 Required PWA identity

12.2 Target generated manifest

{
  "id": "/business-slug",
  "name": "Business Name",
  "short_name": "Business",
  "description": "Accurate business description.",
  "start_url": "/business-slug",
  "scope": "/business-slug/",
  "display": "standalone",
  "background_color": "#FAFAFA",
  "theme_color": "#C0202A",

  "icons": [
    {
      "src": "/business-slug/icon-192.png",
      "sizes": "192x192",
      "type": "image/png"
    },
    {
      "src": "/business-slug/icon-512.png",
      "sizes": "512x512",
      "type": "image/png"
    }
  ]
}

12.3 PWA icon requirements

192 × 192

Square PNG. Keep the important logo/mark inside the safe area.

512 × 512

High-resolution square PNG for installation and larger contexts.

12.4 Service worker

The service worker should be lightweight and should never block primary page rendering. Its purpose is to provide appropriate application resilience, controlled caching and offline behavior where implemented.

/business-slug/sw.js

13. Technical HTML Rules

14. Performance Requirements

15. Crawlability & Indexability

Public business pages should be reachable by ordinary links, should not require authentication, and should be allowed to be crawled and indexed unless a deliberate business-owner decision says otherwise.

16. URL & Error Behaviour

A valid business slug should resolve only to its own business page. Invalid, malformed or unknown routes should not accidentally display another business.

/                     → application root
/register             → registration/information page
/error                → public error page
/{business-slug}      → business page
/{business-slug}/manifest.webmanifest
/{business-slug}/sw.js
/{business-slug}/icon-192.png
/{business-slug}/icon-512.png

17. Pre-Publication QA Checklist

18. Google Validation Workflow

19. Renderer Responsibilities

The public business-page renderer should own technical metadata rather than requiring business-page authors to duplicate it.

20. Extended Data Contract — Reserved Fields

These fields are intentionally documented now so the rendering engine can be expanded without changing the page-authoring model later.

21. web-pages.SKILL

The following compact specification is intended to be copied as plaintext and supplied to an AI agent that is generating or editing a business page.

22. Current Implementation vs. Target Specification