Add page metadata and generated SEO sitemap configuration
This commit is contained in:
@@ -47,4 +47,7 @@ User confirmed parent-domain cookies meshkee_customer_access_token and meshkee_c
|
||||
## Backend access rules confirmed (2026-09-05)
|
||||
Profile URL: https://customer.sgemed.com/profile. Website management URL: https://business.sgemed.com/website. The account endpoint treats a user as eligible for the management link only if they are a super-admin (`isSuperAdmin` or `roles` includes `super_admin`) or hold a membership for the resolved SGE tenant (`businessId`/`id` matches tenant ID) with `isOwner: true` or `teamRole` `admin`, `editor`, or `viewer`. This decision is made server-side from the verified `/auth/me` response; it is never inferred from client data.
|
||||
|
||||
## SEO update (2026-09-05)
|
||||
Source brief: https://api.meshkee.com/api/v1/public/ai-prompts/sge-medical-group/seo/700d7980abbb7920d7a95085. Added page-specific titles, descriptions and canonical URLs for home, about, contact and blog; root metadata now includes Persian Open Graph defaults and `metadataBase` for sgemed.com. Blog detail already uses CMS title/content summary and canonical `/blog/{id}/{titleSlug}`. The build-time sitemap generator now publishes `public/meshkee/sitemap-config.json` with change frequencies and priorities for public static routes only. Do not add `robots.txt` or `sitemap.xml`: production nginx proxies Meshkee’s generated versions. After deployment, run Website → Settings → Sync sitemap config in the Meshkee business dashboard to include the static routes.
|
||||
|
||||
Build-generated public/meshkee/sitemap-config.json lists public static pages. Do not ship sitemap.xml or robots.txt because production nginx delegates them to Meshkee. Test commands: node --experimental-strip-types --test tests/contact.test.mjs; node --test tests/backend.test.cjs.
|
||||
|
||||
Reference in New Issue
Block a user