Treat website meta tags as label + full HTML snippets.

Public business-info now exposes metaTags as { html }, matching how admins paste complete <meta> tags in Tags & Badges.

Co-authored-by: Cursor <cursoragent@cursor.com>
This commit is contained in:
Alireza Hassani
2026-10-03 18:39:19 +03:30
co-authored by Cursor
parent 63ae9b22b9
commit e0cd2327eb
7 changed files with 88 additions and 36 deletions
+3 -3
View File
@@ -336,13 +336,13 @@ These are **required on every crawlable page** (home, listing, product/blog/port
Business admins configure this under **Website → Tags & Badges**.
1. `GET /tenants/{domain}/website/business-info`
2. For each item in `metaTags` (array of `{ name, content }`), emit once in the root layout `<head>`:
2. For each item in `metaTags` (array of `{ html }`), emit the full HTML once in the root layout `<head>`.
```html
<meta name="{name}" content="{content}">
{html}
```
In Next.js App Router, map them into `generateMetadata()` → `other: { [name]: content }`. Verification metas (eNamad, Google, etc.) belong here as custom name/value rows.
Example `html` value: `<meta name="google-site-verification" content="…">` (also supports `property`, `http-equiv`, etc.). Parse attributes into a `<meta />` element, or inject the sanitized string into `<head>`. Do **not** wrap it again as `name`/`content` — `html` is already the whole tag. The dashboard “Name” field is an admin label only and is **not** in this public payload.
3. For each item in `trustBadges` (array of `{ kind, embedHtml }`), render `embedHtml` in the site footer (e.g. `dangerouslySetInnerHTML`). These are HTML widgets only (not meta). Scripts are stripped by the API — still treat the HTML as CMS-controlled content.