@wix/auto_sdk_events_forms 1.0.108 → 1.0.110

package/build/cjs/index.typings.d.ts

@@ -1411,6 +1411,20 @@ interface Tag {
      *
      *
      * Supported values: `title`, `meta`, `script`, `link`.
+     *
+     * Which of these an API actually accepts depends on where the tag is being set: this
+     * list is not a blanket guarantee across every API that reuses this message. Site SEO
+     * Tags in particular accepts only `meta` (see `SiteSeoTags.tags`) and rejects
+     * `title`/`script`/`link` with a validation error even though they appear here —
+     * check the field description of the specific `tags`-typed field you're writing to
+     * for the types it actually supports and the error it returns.
+     *
+     * Limitation: `title` and `script` (e.g. a `script` tag with `props.type`
+     * `"application/ld+json"` carrying structured data) are supported only when
+     * `custom` is unset or `false`. Setting `custom: true` on a `title` or `script`
+     * tag is rejected with `TAG_TYPE_NOT_ALLOWED`, because `custom: true` routes the
+     * write through the site's Advanced/Custom Tags list. To write structured data,
+     * omit `custom` (or set it to `false`).
      */
     type?: string;
     /**
@@ -1426,6 +1440,18 @@ interface Tag {
      * Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages) —
      * i.e. an entry from the site's Advanced/Custom Tags list.
      *
+     * Setting this to `true` on a write restricts which `type` values are accepted
+     * — the same restriction the Advanced/Custom Tags UI enforces. `title` and
+     * `script` tags (including JSON-LD structured data) must be sent with `custom`
+     * omitted or `false`; sending them with `custom: true` is rejected with
+     * `TAG_TYPE_NOT_ALLOWED`.
+     *
+     * Note this is a separate restriction from Site SEO Tags' own type restriction on
+     * `SiteSeoTags.tags`: even with `custom` unset, Site SEO Tags rejects `script` (e.g.
+     * for site-wide structured data) unconditionally. There is currently no way to set
+     * site-wide, every-page structured data through any of these APIs — write a per-page
+     * `script` tag through the Item SEO Tags API instead.
+     *
      * This flag is scoped to that feature only. It is NOT an indicator of whether a standard tag
      * (`title`, `description`, Open Graph, etc.) reflects a manually configured value versus a computed
      * default/pattern — standard tags always resolve with `custom: false`, even when their content comes