@wix/auto_sdk_events_forms 1.0.104 → 1.0.106

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

@@ -1422,7 +1422,22 @@ interface Tag {
     meta?: Record<string, any> | null;
     /** SEO tag inner content. For example, `<title> inner content </title>`. */
     children?: string;
-    /** Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages). */
+    /**
+     * 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.
+     *
+     * 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
+     * from a page's manually saved SEO title/description override. Don't use this field to verify whether
+     * a live page reflects a manual per-page SEO edit.
+     *
+     * Limitation: when `ResolveStaticPageSeoTags` is called without `seoData`, the per-page SEO data is read
+     * only from the Vibe/Wix-managed-headless override store. That store holds nothing for classic Wix Editor
+     * or Wix Studio pages, so even genuine Advanced/Custom Tags saved on those pages are missing from the
+     * response entirely — there, `false` means this API could not tell, not that no custom tag exists.
+     * Pass `seoData` explicitly to resolve against a known set of tags.
+     */
     custom?: boolean;
     /** Whether the tag is disabled. If the tag is disabled, people can't find your page when searching for this phrase in search engines. */
     disabled?: boolean;