# Domain checklist — read before going live on a new domain

Everything in this package currently points at `btmsecurity.co.ke`. I didn't
guess at a replacement since I don't know your new domain — search for
`btmsecurity.co.ke` across both folders and update per the notes below.

## website/ (the public marketing site)

**SEO canonical tags — update to your new domain, one per page:**
- `index.html` line 11 — `<link rel="canonical" href="https://btmsecurity.co.ke/">`
- `about.html`, `services.html`, `coverage.html`, `contact.html` — same tag, one each

**Structured data (index.html, lines ~18–23)** — the `SecurityService` JSON-LD
block has `"image"`, `"url"`, and `"email"` fields pointing at the old domain.
Update `image` and `url`; see the email note below for `"email"`.

**"Client sign in" links — resolved.** All 11 places (index, about, services,
coverage, contact, thank-you — each has a desktop button + a mobile-menu
duplicate) now point to:
```
https://portal.btmsecurity.co.ke
```
Point that subdomain's document root at the `system/` folder from this
package on cPanel, and this is already correct — nothing left to do here.

**Email addresses** — `info@btmsecurity.co.ke` appears as a `mailto:` link on
every page (footer + contact page) and in the JSON-LD block. Decide first
whether your email is moving with the domain or staying as-is; only replace
if it's actually changing.

**send-message.php** (the contact-form handler) — three references:
- `BTMS_TO_EMAIL` constant (line 16) — where quote requests get emailed
- The `From:` and `Reply-To:` headers (lines 58–59) — currently
  `no-reply@btmsecurity.co.ke`; if your new domain doesn't have mail hosting
  set up yet, `mail()` may fail to send until it does.

## system/ (login, admin, portal)

- `config.example.php` line 10 — `BTMS_SUPPORT_EMAIL` constant, shown to
  users on the login screen and portal ("Contact BTMS support").
- `install.php` line 16 — the **demo** admin seed account uses
  `admin@btmsecurity.co.ke`. This only matters if you run the installer
  fresh; if you already have a live database, this line never executes
  again and is safe to ignore.

## What I did NOT change

I left every reference exactly as-is rather than guess at your new domain —
a wrong guess would silently break links (especially the cross-domain
sign-in button) in a way that's easy to miss until a client complains.
A simple approach once you know the new domain: search for
`btmsecurity.co.ke` in your editor/File Manager across both folders and
review each hit against the notes above.