@wix/auto_sdk_blog_draft-posts 1.0.95 → 1.0.97

package/build/internal/cjs/schemas.js

@@ -63,7 +63,7 @@ module.exports = __toCommonJS(schemas_exports);
 
 // src/blog-v3-draft-draft-posts.schemas.ts
 var z = __toESM(require("zod"));
-var CreateDraftPostRequest = z.object({
+var CreateDraftPostRequest = /* @__PURE__ */ z.object({
   draftPost: z.object({
     _id: z.string().describe("Draft post ID.").max(38).optional(),
     title: z.string().describe("Draft post title.").max(200),
@@ -134,7 +134,7 @@ var CreateDraftPostRequest = z.object({
       tags: z.array(
         z.object({
           type: z.string().describe(
-            "SEO tag type.\n\n\nSupported values: `title`, `meta`, `script`, `link`."
+            "SEO tag type.\n\n\nSupported values: `title`, `meta`, `script`, `link`.\n\nWhich of these an API actually accepts depends on where the tag is being set: this\nlist is not a blanket guarantee across every API that reuses this message. Site SEO\nTags in particular accepts only `meta` (see `SiteSeoTags.tags`) and rejects\n`title`/`script`/`link` with a validation error even though they appear here \u2014\ncheck the field description of the specific `tags`-typed field you're writing to\nfor the types it actually supports and the error it returns."
           ).optional(),
           props: z.record(z.string(), z.any()).describe(
             'A `{"key": "value"}` pair object where each SEO tag property (`"name"`, `"content"`, `"rel"`, `"href"`) contains a value.\nFor example: `{"name": "description", "content": "the description itself"}`.'
@@ -146,7 +146,7 @@ var CreateDraftPostRequest = z.object({
             "SEO tag inner content. For example, `<title> inner content </title>`."
           ).optional(),
           custom: z.boolean().describe(
-            "Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages) \u2014\ni.e. an entry from the site's Advanced/Custom Tags list.\n\nThis flag is scoped to that feature only. It is NOT an indicator of whether a standard tag\n(`title`, `description`, Open Graph, etc.) reflects a manually configured value versus a computed\ndefault/pattern \u2014 standard tags always resolve with `custom: false`, even when their content comes\nfrom a page's manually saved SEO title/description override. Don't use this field to verify whether\na live page reflects a manual per-page SEO edit.\n\nLimitation: when `ResolveStaticPageSeoTags` is called without `seoData`, the per-page SEO data is read\nonly from the Vibe/Wix-managed-headless override store. That store holds nothing for classic Wix Editor\nor Wix Studio pages, so even genuine Advanced/Custom Tags saved on those pages are missing from the\nresponse entirely \u2014 there, `false` means this API could not tell, not that no custom tag exists.\nPass `seoData` explicitly to resolve against a known set of tags."
+            "Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages) \u2014\ni.e. an entry from the site's Advanced/Custom Tags list.\n\nNote this is a separate restriction from Site SEO Tags' own type restriction on\n`SiteSeoTags.tags`: even with `custom` unset, Site SEO Tags rejects `script` (e.g.\nfor site-wide structured data) unconditionally. There is currently no way to set\nsite-wide, every-page structured data through any of these APIs \u2014 write a per-page\n`script` tag through the Item SEO Tags API instead.\n\nThis flag is scoped to that feature only. It is NOT an indicator of whether a standard tag\n(`title`, `description`, Open Graph, etc.) reflects a manually configured value versus a computed\ndefault/pattern \u2014 standard tags always resolve with `custom: false`, even when their content comes\nfrom a page's manually saved SEO title/description override. Don't use this field to verify whether\na live page reflects a manual per-page SEO edit.\n\nLimitation: when `ResolveStaticPageSeoTags` is called without `seoData`, the per-page SEO data is read\nonly from the Vibe/Wix-managed-headless override store. That store holds nothing for classic Wix Editor\nor Wix Studio pages, so even genuine Advanced/Custom Tags saved on those pages are missing from the\nresponse entirely \u2014 there, `false` means this API could not tell, not that no custom tag exists.\nPass `seoData` explicitly to resolve against a known set of tags."
           ).optional(),
           disabled: z.boolean().describe(
             "Whether the tag is disabled. If the tag is disabled, people can't find your page when searching for this phrase in search engines."
@@ -231,7 +231,7 @@ var CreateDraftPostRequest = z.object({
     ).max(10).optional()
   }).describe("Options for creating a draft post.").optional()
 });
-var CreateDraftPostResponse = z.object({
+var CreateDraftPostResponse = /* @__PURE__ */ z.object({
   draftPost: z.object({
     _id: z.string().describe("Draft post ID.").max(38).optional(),
     title: z.string().describe("Draft post title.").max(200).optional(),
@@ -304,7 +304,7 @@ var CreateDraftPostResponse = z.object({
       tags: z.array(
         z.object({
           type: z.string().describe(
-            "SEO tag type.\n\n\nSupported values: `title`, `meta`, `script`, `link`."
+            "SEO tag type.\n\n\nSupported values: `title`, `meta`, `script`, `link`.\n\nWhich of these an API actually accepts depends on where the tag is being set: this\nlist is not a blanket guarantee across every API that reuses this message. Site SEO\nTags in particular accepts only `meta` (see `SiteSeoTags.tags`) and rejects\n`title`/`script`/`link` with a validation error even though they appear here \u2014\ncheck the field description of the specific `tags`-typed field you're writing to\nfor the types it actually supports and the error it returns."
           ).optional(),
           props: z.record(z.string(), z.any()).describe(
             'A `{"key": "value"}` pair object where each SEO tag property (`"name"`, `"content"`, `"rel"`, `"href"`) contains a value.\nFor example: `{"name": "description", "content": "the description itself"}`.'
@@ -316,7 +316,7 @@ var CreateDraftPostResponse = z.object({
             "SEO tag inner content. For example, `<title> inner content </title>`."
           ).optional(),
           custom: z.boolean().describe(
-            "Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages) \u2014\ni.e. an entry from the site's Advanced/Custom Tags list.\n\nThis flag is scoped to that feature only. It is NOT an indicator of whether a standard tag\n(`title`, `description`, Open Graph, etc.) reflects a manually configured value versus a computed\ndefault/pattern \u2014 standard tags always resolve with `custom: false`, even when their content comes\nfrom a page's manually saved SEO title/description override. Don't use this field to verify whether\na live page reflects a manual per-page SEO edit.\n\nLimitation: when `ResolveStaticPageSeoTags` is called without `seoData`, the per-page SEO data is read\nonly from the Vibe/Wix-managed-headless override store. That store holds nothing for classic Wix Editor\nor Wix Studio pages, so even genuine Advanced/Custom Tags saved on those pages are missing from the\nresponse entirely \u2014 there, `false` means this API could not tell, not that no custom tag exists.\nPass `seoData` explicitly to resolve against a known set of tags."
+            "Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages) \u2014\ni.e. an entry from the site's Advanced/Custom Tags list.\n\nNote this is a separate restriction from Site SEO Tags' own type restriction on\n`SiteSeoTags.tags`: even with `custom` unset, Site SEO Tags rejects `script` (e.g.\nfor site-wide structured data) unconditionally. There is currently no way to set\nsite-wide, every-page structured data through any of these APIs \u2014 write a per-page\n`script` tag through the Item SEO Tags API instead.\n\nThis flag is scoped to that feature only. It is NOT an indicator of whether a standard tag\n(`title`, `description`, Open Graph, etc.) reflects a manually configured value versus a computed\ndefault/pattern \u2014 standard tags always resolve with `custom: false`, even when their content comes\nfrom a page's manually saved SEO title/description override. Don't use this field to verify whether\na live page reflects a manual per-page SEO edit.\n\nLimitation: when `ResolveStaticPageSeoTags` is called without `seoData`, the per-page SEO data is read\nonly from the Vibe/Wix-managed-headless override store. That store holds nothing for classic Wix Editor\nor Wix Studio pages, so even genuine Advanced/Custom Tags saved on those pages are missing from the\nresponse entirely \u2014 there, `false` means this API could not tell, not that no custom tag exists.\nPass `seoData` explicitly to resolve against a known set of tags."
           ).optional(),
           disabled: z.boolean().describe(
             "Whether the tag is disabled. If the tag is disabled, people can't find your page when searching for this phrase in search engines."
@@ -387,7 +387,7 @@ var CreateDraftPostResponse = z.object({
     ).min(0).optional().nullable()
   }).describe("Created draft post info.").optional()
 });
-var BulkCreateDraftPostsRequest = z.object({
+var BulkCreateDraftPostsRequest = /* @__PURE__ */ z.object({
   draftPosts: z.array(
     z.object({
       _id: z.string().describe("Draft post ID.").max(38).optional(),
@@ -459,7 +459,7 @@ var BulkCreateDraftPostsRequest = z.object({
         tags: z.array(
           z.object({
             type: z.string().describe(
-              "SEO tag type.\n\n\nSupported values: `title`, `meta`, `script`, `link`."
+              "SEO tag type.\n\n\nSupported values: `title`, `meta`, `script`, `link`.\n\nWhich of these an API actually accepts depends on where the tag is being set: this\nlist is not a blanket guarantee across every API that reuses this message. Site SEO\nTags in particular accepts only `meta` (see `SiteSeoTags.tags`) and rejects\n`title`/`script`/`link` with a validation error even though they appear here \u2014\ncheck the field description of the specific `tags`-typed field you're writing to\nfor the types it actually supports and the error it returns."
             ).optional(),
             props: z.record(z.string(), z.any()).describe(
               'A `{"key": "value"}` pair object where each SEO tag property (`"name"`, `"content"`, `"rel"`, `"href"`) contains a value.\nFor example: `{"name": "description", "content": "the description itself"}`.'
@@ -471,7 +471,7 @@ var BulkCreateDraftPostsRequest = z.object({
               "SEO tag inner content. For example, `<title> inner content </title>`."
             ).optional(),
             custom: z.boolean().describe(
-              "Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages) \u2014\ni.e. an entry from the site's Advanced/Custom Tags list.\n\nThis flag is scoped to that feature only. It is NOT an indicator of whether a standard tag\n(`title`, `description`, Open Graph, etc.) reflects a manually configured value versus a computed\ndefault/pattern \u2014 standard tags always resolve with `custom: false`, even when their content comes\nfrom a page's manually saved SEO title/description override. Don't use this field to verify whether\na live page reflects a manual per-page SEO edit.\n\nLimitation: when `ResolveStaticPageSeoTags` is called without `seoData`, the per-page SEO data is read\nonly from the Vibe/Wix-managed-headless override store. That store holds nothing for classic Wix Editor\nor Wix Studio pages, so even genuine Advanced/Custom Tags saved on those pages are missing from the\nresponse entirely \u2014 there, `false` means this API could not tell, not that no custom tag exists.\nPass `seoData` explicitly to resolve against a known set of tags."
+              "Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages) \u2014\ni.e. an entry from the site's Advanced/Custom Tags list.\n\nNote this is a separate restriction from Site SEO Tags' own type restriction on\n`SiteSeoTags.tags`: even with `custom` unset, Site SEO Tags rejects `script` (e.g.\nfor site-wide structured data) unconditionally. There is currently no way to set\nsite-wide, every-page structured data through any of these APIs \u2014 write a per-page\n`script` tag through the Item SEO Tags API instead.\n\nThis flag is scoped to that feature only. It is NOT an indicator of whether a standard tag\n(`title`, `description`, Open Graph, etc.) reflects a manually configured value versus a computed\ndefault/pattern \u2014 standard tags always resolve with `custom: false`, even when their content comes\nfrom a page's manually saved SEO title/description override. Don't use this field to verify whether\na live page reflects a manual per-page SEO edit.\n\nLimitation: when `ResolveStaticPageSeoTags` is called without `seoData`, the per-page SEO data is read\nonly from the Vibe/Wix-managed-headless override store. That store holds nothing for classic Wix Editor\nor Wix Studio pages, so even genuine Advanced/Custom Tags saved on those pages are missing from the\nresponse entirely \u2014 there, `false` means this API could not tell, not that no custom tag exists.\nPass `seoData` explicitly to resolve against a known set of tags."
             ).optional(),
             disabled: z.boolean().describe(
               "Whether the tag is disabled. If the tag is disabled, people can't find your page when searching for this phrase in search engines."
@@ -558,7 +558,7 @@ var BulkCreateDraftPostsRequest = z.object({
     ).max(10).optional()
   }).describe("Options for creating multiple draft posts.").optional()
 });
-var BulkCreateDraftPostsResponse = z.object({
+var BulkCreateDraftPostsResponse = /* @__PURE__ */ z.object({
   results: z.array(
     z.object({
       itemMetadata: z.object({
@@ -649,7 +649,7 @@ var BulkCreateDraftPostsResponse = z.object({
           tags: z.array(
             z.object({
               type: z.string().describe(
-                "SEO tag type.\n\n\nSupported values: `title`, `meta`, `script`, `link`."
+                "SEO tag type.\n\n\nSupported values: `title`, `meta`, `script`, `link`.\n\nWhich of these an API actually accepts depends on where the tag is being set: this\nlist is not a blanket guarantee across every API that reuses this message. Site SEO\nTags in particular accepts only `meta` (see `SiteSeoTags.tags`) and rejects\n`title`/`script`/`link` with a validation error even though they appear here \u2014\ncheck the field description of the specific `tags`-typed field you're writing to\nfor the types it actually supports and the error it returns."
               ).optional(),
               props: z.record(z.string(), z.any()).describe(
                 'A `{"key": "value"}` pair object where each SEO tag property (`"name"`, `"content"`, `"rel"`, `"href"`) contains a value.\nFor example: `{"name": "description", "content": "the description itself"}`.'
@@ -661,7 +661,7 @@ var BulkCreateDraftPostsResponse = z.object({
                 "SEO tag inner content. For example, `<title> inner content </title>`."
               ).optional(),
               custom: z.boolean().describe(
-                "Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages) \u2014\ni.e. an entry from the site's Advanced/Custom Tags list.\n\nThis flag is scoped to that feature only. It is NOT an indicator of whether a standard tag\n(`title`, `description`, Open Graph, etc.) reflects a manually configured value versus a computed\ndefault/pattern \u2014 standard tags always resolve with `custom: false`, even when their content comes\nfrom a page's manually saved SEO title/description override. Don't use this field to verify whether\na live page reflects a manual per-page SEO edit.\n\nLimitation: when `ResolveStaticPageSeoTags` is called without `seoData`, the per-page SEO data is read\nonly from the Vibe/Wix-managed-headless override store. That store holds nothing for classic Wix Editor\nor Wix Studio pages, so even genuine Advanced/Custom Tags saved on those pages are missing from the\nresponse entirely \u2014 there, `false` means this API could not tell, not that no custom tag exists.\nPass `seoData` explicitly to resolve against a known set of tags."
+                "Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages) \u2014\ni.e. an entry from the site's Advanced/Custom Tags list.\n\nNote this is a separate restriction from Site SEO Tags' own type restriction on\n`SiteSeoTags.tags`: even with `custom` unset, Site SEO Tags rejects `script` (e.g.\nfor site-wide structured data) unconditionally. There is currently no way to set\nsite-wide, every-page structured data through any of these APIs \u2014 write a per-page\n`script` tag through the Item SEO Tags API instead.\n\nThis flag is scoped to that feature only. It is NOT an indicator of whether a standard tag\n(`title`, `description`, Open Graph, etc.) reflects a manually configured value versus a computed\ndefault/pattern \u2014 standard tags always resolve with `custom: false`, even when their content comes\nfrom a page's manually saved SEO title/description override. Don't use this field to verify whether\na live page reflects a manual per-page SEO edit.\n\nLimitation: when `ResolveStaticPageSeoTags` is called without `seoData`, the per-page SEO data is read\nonly from the Vibe/Wix-managed-headless override store. That store holds nothing for classic Wix Editor\nor Wix Studio pages, so even genuine Advanced/Custom Tags saved on those pages are missing from the\nresponse entirely \u2014 there, `false` means this API could not tell, not that no custom tag exists.\nPass `seoData` explicitly to resolve against a known set of tags."
               ).optional(),
               disabled: z.boolean().describe(
                 "Whether the tag is disabled. If the tag is disabled, people can't find your page when searching for this phrase in search engines."
@@ -741,7 +741,7 @@ var BulkCreateDraftPostsResponse = z.object({
     ).optional()
   }).describe("Bulk action metadata.").optional()
 });
-var BulkUpdateDraftPostsRequest = z.object({
+var BulkUpdateDraftPostsRequest = /* @__PURE__ */ z.object({
   options: z.object({
     draftPosts: z.array(
       z.object({
@@ -815,7 +815,7 @@ var BulkUpdateDraftPostsRequest = z.object({
             tags: z.array(
               z.object({
                 type: z.string().describe(
-                  "SEO tag type.\n\n\nSupported values: `title`, `meta`, `script`, `link`."
+                  "SEO tag type.\n\n\nSupported values: `title`, `meta`, `script`, `link`.\n\nWhich of these an API actually accepts depends on where the tag is being set: this\nlist is not a blanket guarantee across every API that reuses this message. Site SEO\nTags in particular accepts only `meta` (see `SiteSeoTags.tags`) and rejects\n`title`/`script`/`link` with a validation error even though they appear here \u2014\ncheck the field description of the specific `tags`-typed field you're writing to\nfor the types it actually supports and the error it returns."
                 ).optional(),
                 props: z.record(z.string(), z.any()).describe(
                   'A `{"key": "value"}` pair object where each SEO tag property (`"name"`, `"content"`, `"rel"`, `"href"`) contains a value.\nFor example: `{"name": "description", "content": "the description itself"}`.'
@@ -827,7 +827,7 @@ var BulkUpdateDraftPostsRequest = z.object({
                   "SEO tag inner content. For example, `<title> inner content </title>`."
                 ).optional(),
                 custom: z.boolean().describe(
-                  "Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages) \u2014\ni.e. an entry from the site's Advanced/Custom Tags list.\n\nThis flag is scoped to that feature only. It is NOT an indicator of whether a standard tag\n(`title`, `description`, Open Graph, etc.) reflects a manually configured value versus a computed\ndefault/pattern \u2014 standard tags always resolve with `custom: false`, even when their content comes\nfrom a page's manually saved SEO title/description override. Don't use this field to verify whether\na live page reflects a manual per-page SEO edit.\n\nLimitation: when `ResolveStaticPageSeoTags` is called without `seoData`, the per-page SEO data is read\nonly from the Vibe/Wix-managed-headless override store. That store holds nothing for classic Wix Editor\nor Wix Studio pages, so even genuine Advanced/Custom Tags saved on those pages are missing from the\nresponse entirely \u2014 there, `false` means this API could not tell, not that no custom tag exists.\nPass `seoData` explicitly to resolve against a known set of tags."
+                  "Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages) \u2014\ni.e. an entry from the site's Advanced/Custom Tags list.\n\nNote this is a separate restriction from Site SEO Tags' own type restriction on\n`SiteSeoTags.tags`: even with `custom` unset, Site SEO Tags rejects `script` (e.g.\nfor site-wide structured data) unconditionally. There is currently no way to set\nsite-wide, every-page structured data through any of these APIs \u2014 write a per-page\n`script` tag through the Item SEO Tags API instead.\n\nThis flag is scoped to that feature only. It is NOT an indicator of whether a standard tag\n(`title`, `description`, Open Graph, etc.) reflects a manually configured value versus a computed\ndefault/pattern \u2014 standard tags always resolve with `custom: false`, even when their content comes\nfrom a page's manually saved SEO title/description override. Don't use this field to verify whether\na live page reflects a manual per-page SEO edit.\n\nLimitation: when `ResolveStaticPageSeoTags` is called without `seoData`, the per-page SEO data is read\nonly from the Vibe/Wix-managed-headless override store. That store holds nothing for classic Wix Editor\nor Wix Studio pages, so even genuine Advanced/Custom Tags saved on those pages are missing from the\nresponse entirely \u2014 there, `false` means this API could not tell, not that no custom tag exists.\nPass `seoData` explicitly to resolve against a known set of tags."
                 ).optional(),
                 disabled: z.boolean().describe(
                   "Whether the tag is disabled. If the tag is disabled, people can't find your page when searching for this phrase in search engines."
@@ -926,7 +926,7 @@ var BulkUpdateDraftPostsRequest = z.object({
     ).max(10).optional()
   }).describe("Options for updating multiple draft posts.").optional()
 });
-var BulkUpdateDraftPostsResponse = z.object({
+var BulkUpdateDraftPostsResponse = /* @__PURE__ */ z.object({
   results: z.array(
     z.object({
       itemMetadata: z.object({
@@ -1017,7 +1017,7 @@ var BulkUpdateDraftPostsResponse = z.object({
           tags: z.array(
             z.object({
               type: z.string().describe(
-                "SEO tag type.\n\n\nSupported values: `title`, `meta`, `script`, `link`."
+                "SEO tag type.\n\n\nSupported values: `title`, `meta`, `script`, `link`.\n\nWhich of these an API actually accepts depends on where the tag is being set: this\nlist is not a blanket guarantee across every API that reuses this message. Site SEO\nTags in particular accepts only `meta` (see `SiteSeoTags.tags`) and rejects\n`title`/`script`/`link` with a validation error even though they appear here \u2014\ncheck the field description of the specific `tags`-typed field you're writing to\nfor the types it actually supports and the error it returns."
               ).optional(),
               props: z.record(z.string(), z.any()).describe(
                 'A `{"key": "value"}` pair object where each SEO tag property (`"name"`, `"content"`, `"rel"`, `"href"`) contains a value.\nFor example: `{"name": "description", "content": "the description itself"}`.'
@@ -1029,7 +1029,7 @@ var BulkUpdateDraftPostsResponse = z.object({
                 "SEO tag inner content. For example, `<title> inner content </title>`."
               ).optional(),
               custom: z.boolean().describe(
-                "Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages) \u2014\ni.e. an entry from the site's Advanced/Custom Tags list.\n\nThis flag is scoped to that feature only. It is NOT an indicator of whether a standard tag\n(`title`, `description`, Open Graph, etc.) reflects a manually configured value versus a computed\ndefault/pattern \u2014 standard tags always resolve with `custom: false`, even when their content comes\nfrom a page's manually saved SEO title/description override. Don't use this field to verify whether\na live page reflects a manual per-page SEO edit.\n\nLimitation: when `ResolveStaticPageSeoTags` is called without `seoData`, the per-page SEO data is read\nonly from the Vibe/Wix-managed-headless override store. That store holds nothing for classic Wix Editor\nor Wix Studio pages, so even genuine Advanced/Custom Tags saved on those pages are missing from the\nresponse entirely \u2014 there, `false` means this API could not tell, not that no custom tag exists.\nPass `seoData` explicitly to resolve against a known set of tags."
+                "Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages) \u2014\ni.e. an entry from the site's Advanced/Custom Tags list.\n\nNote this is a separate restriction from Site SEO Tags' own type restriction on\n`SiteSeoTags.tags`: even with `custom` unset, Site SEO Tags rejects `script` (e.g.\nfor site-wide structured data) unconditionally. There is currently no way to set\nsite-wide, every-page structured data through any of these APIs \u2014 write a per-page\n`script` tag through the Item SEO Tags API instead.\n\nThis flag is scoped to that feature only. It is NOT an indicator of whether a standard tag\n(`title`, `description`, Open Graph, etc.) reflects a manually configured value versus a computed\ndefault/pattern \u2014 standard tags always resolve with `custom: false`, even when their content comes\nfrom a page's manually saved SEO title/description override. Don't use this field to verify whether\na live page reflects a manual per-page SEO edit.\n\nLimitation: when `ResolveStaticPageSeoTags` is called without `seoData`, the per-page SEO data is read\nonly from the Vibe/Wix-managed-headless override store. That store holds nothing for classic Wix Editor\nor Wix Studio pages, so even genuine Advanced/Custom Tags saved on those pages are missing from the\nresponse entirely \u2014 there, `false` means this API could not tell, not that no custom tag exists.\nPass `seoData` explicitly to resolve against a known set of tags."
               ).optional(),
               disabled: z.boolean().describe(
                 "Whether the tag is disabled. If the tag is disabled, people can't find your page when searching for this phrase in search engines."
@@ -1109,7 +1109,7 @@ var BulkUpdateDraftPostsResponse = z.object({
     ).optional()
   }).describe("Bulk action metadata.").optional()
 });
-var ListDeletedDraftPostsRequest = z.object({
+var ListDeletedDraftPostsRequest = /* @__PURE__ */ z.object({
   options: z.object({
     language: z.string().describe(
       "Language filter.\n\n2-or-4-letter language code in [IETF BCP 47 language tag](https://en.wikipedia.org/wiki/IETF_language_tag) format.\nIf omitted, deleted draft posts in all languages are returned."
@@ -1136,7 +1136,7 @@ var ListDeletedDraftPostsRequest = z.object({
     draftPostIds: z.array(z.string()).max(100).optional()
   }).describe("Options for listing deleted draft posts.").optional()
 });
-var ListDeletedDraftPostsResponse = z.object({
+var ListDeletedDraftPostsResponse = /* @__PURE__ */ z.object({
   draftPosts: z.array(
     z.object({
       _id: z.string().describe("Draft post ID.").max(38).optional(),
@@ -1210,7 +1210,7 @@ var ListDeletedDraftPostsResponse = z.object({
         tags: z.array(
           z.object({
             type: z.string().describe(
-              "SEO tag type.\n\n\nSupported values: `title`, `meta`, `script`, `link`."
+              "SEO tag type.\n\n\nSupported values: `title`, `meta`, `script`, `link`.\n\nWhich of these an API actually accepts depends on where the tag is being set: this\nlist is not a blanket guarantee across every API that reuses this message. Site SEO\nTags in particular accepts only `meta` (see `SiteSeoTags.tags`) and rejects\n`title`/`script`/`link` with a validation error even though they appear here \u2014\ncheck the field description of the specific `tags`-typed field you're writing to\nfor the types it actually supports and the error it returns."
             ).optional(),
             props: z.record(z.string(), z.any()).describe(
               'A `{"key": "value"}` pair object where each SEO tag property (`"name"`, `"content"`, `"rel"`, `"href"`) contains a value.\nFor example: `{"name": "description", "content": "the description itself"}`.'
@@ -1222,7 +1222,7 @@ var ListDeletedDraftPostsResponse = z.object({
               "SEO tag inner content. For example, `<title> inner content </title>`."
             ).optional(),
             custom: z.boolean().describe(
-              "Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages) \u2014\ni.e. an entry from the site's Advanced/Custom Tags list.\n\nThis flag is scoped to that feature only. It is NOT an indicator of whether a standard tag\n(`title`, `description`, Open Graph, etc.) reflects a manually configured value versus a computed\ndefault/pattern \u2014 standard tags always resolve with `custom: false`, even when their content comes\nfrom a page's manually saved SEO title/description override. Don't use this field to verify whether\na live page reflects a manual per-page SEO edit.\n\nLimitation: when `ResolveStaticPageSeoTags` is called without `seoData`, the per-page SEO data is read\nonly from the Vibe/Wix-managed-headless override store. That store holds nothing for classic Wix Editor\nor Wix Studio pages, so even genuine Advanced/Custom Tags saved on those pages are missing from the\nresponse entirely \u2014 there, `false` means this API could not tell, not that no custom tag exists.\nPass `seoData` explicitly to resolve against a known set of tags."
+              "Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages) \u2014\ni.e. an entry from the site's Advanced/Custom Tags list.\n\nNote this is a separate restriction from Site SEO Tags' own type restriction on\n`SiteSeoTags.tags`: even with `custom` unset, Site SEO Tags rejects `script` (e.g.\nfor site-wide structured data) unconditionally. There is currently no way to set\nsite-wide, every-page structured data through any of these APIs \u2014 write a per-page\n`script` tag through the Item SEO Tags API instead.\n\nThis flag is scoped to that feature only. It is NOT an indicator of whether a standard tag\n(`title`, `description`, Open Graph, etc.) reflects a manually configured value versus a computed\ndefault/pattern \u2014 standard tags always resolve with `custom: false`, even when their content comes\nfrom a page's manually saved SEO title/description override. Don't use this field to verify whether\na live page reflects a manual per-page SEO edit.\n\nLimitation: when `ResolveStaticPageSeoTags` is called without `seoData`, the per-page SEO data is read\nonly from the Vibe/Wix-managed-headless override store. That store holds nothing for classic Wix Editor\nor Wix Studio pages, so even genuine Advanced/Custom Tags saved on those pages are missing from the\nresponse entirely \u2014 there, `false` means this API could not tell, not that no custom tag exists.\nPass `seoData` explicitly to resolve against a known set of tags."
             ).optional(),
             disabled: z.boolean().describe(
               "Whether the tag is disabled. If the tag is disabled, people can't find your page when searching for this phrase in search engines."
@@ -1312,7 +1312,7 @@ var ListDeletedDraftPostsResponse = z.object({
     ).optional()
   }).describe("Details on the paged set of results returned.").optional()
 });
-var GetDraftPostRequest = z.object({
+var GetDraftPostRequest = /* @__PURE__ */ z.object({
   draftPostId: z.string().describe("Draft post ID.").max(38),
   options: z.object({
     fieldsets: z.array(
@@ -1326,7 +1326,7 @@ var GetDraftPostRequest = z.object({
     ).max(10).optional()
   }).describe("Options for getting a draft post.").optional()
 });
-var GetDraftPostResponse = z.object({
+var GetDraftPostResponse = /* @__PURE__ */ z.object({
   draftPost: z.object({
     _id: z.string().describe("Draft post ID.").max(38).optional(),
     title: z.string().describe("Draft post title.").max(200).optional(),
@@ -1399,7 +1399,7 @@ var GetDraftPostResponse = z.object({
       tags: z.array(
         z.object({
           type: z.string().describe(
-            "SEO tag type.\n\n\nSupported values: `title`, `meta`, `script`, `link`."
+            "SEO tag type.\n\n\nSupported values: `title`, `meta`, `script`, `link`.\n\nWhich of these an API actually accepts depends on where the tag is being set: this\nlist is not a blanket guarantee across every API that reuses this message. Site SEO\nTags in particular accepts only `meta` (see `SiteSeoTags.tags`) and rejects\n`title`/`script`/`link` with a validation error even though they appear here \u2014\ncheck the field description of the specific `tags`-typed field you're writing to\nfor the types it actually supports and the error it returns."
           ).optional(),
           props: z.record(z.string(), z.any()).describe(
             'A `{"key": "value"}` pair object where each SEO tag property (`"name"`, `"content"`, `"rel"`, `"href"`) contains a value.\nFor example: `{"name": "description", "content": "the description itself"}`.'
@@ -1411,7 +1411,7 @@ var GetDraftPostResponse = z.object({
             "SEO tag inner content. For example, `<title> inner content </title>`."
           ).optional(),
           custom: z.boolean().describe(
-            "Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages) \u2014\ni.e. an entry from the site's Advanced/Custom Tags list.\n\nThis flag is scoped to that feature only. It is NOT an indicator of whether a standard tag\n(`title`, `description`, Open Graph, etc.) reflects a manually configured value versus a computed\ndefault/pattern \u2014 standard tags always resolve with `custom: false`, even when their content comes\nfrom a page's manually saved SEO title/description override. Don't use this field to verify whether\na live page reflects a manual per-page SEO edit.\n\nLimitation: when `ResolveStaticPageSeoTags` is called without `seoData`, the per-page SEO data is read\nonly from the Vibe/Wix-managed-headless override store. That store holds nothing for classic Wix Editor\nor Wix Studio pages, so even genuine Advanced/Custom Tags saved on those pages are missing from the\nresponse entirely \u2014 there, `false` means this API could not tell, not that no custom tag exists.\nPass `seoData` explicitly to resolve against a known set of tags."
+            "Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages) \u2014\ni.e. an entry from the site's Advanced/Custom Tags list.\n\nNote this is a separate restriction from Site SEO Tags' own type restriction on\n`SiteSeoTags.tags`: even with `custom` unset, Site SEO Tags rejects `script` (e.g.\nfor site-wide structured data) unconditionally. There is currently no way to set\nsite-wide, every-page structured data through any of these APIs \u2014 write a per-page\n`script` tag through the Item SEO Tags API instead.\n\nThis flag is scoped to that feature only. It is NOT an indicator of whether a standard tag\n(`title`, `description`, Open Graph, etc.) reflects a manually configured value versus a computed\ndefault/pattern \u2014 standard tags always resolve with `custom: false`, even when their content comes\nfrom a page's manually saved SEO title/description override. Don't use this field to verify whether\na live page reflects a manual per-page SEO edit.\n\nLimitation: when `ResolveStaticPageSeoTags` is called without `seoData`, the per-page SEO data is read\nonly from the Vibe/Wix-managed-headless override store. That store holds nothing for classic Wix Editor\nor Wix Studio pages, so even genuine Advanced/Custom Tags saved on those pages are missing from the\nresponse entirely \u2014 there, `false` means this API could not tell, not that no custom tag exists.\nPass `seoData` explicitly to resolve against a known set of tags."
           ).optional(),
           disabled: z.boolean().describe(
             "Whether the tag is disabled. If the tag is disabled, people can't find your page when searching for this phrase in search engines."
@@ -1482,7 +1482,7 @@ var GetDraftPostResponse = z.object({
     ).min(0).optional().nullable()
   }).describe("Draft post info.").optional()
 });
-var UpdateDraftPostRequest = z.object({
+var UpdateDraftPostRequest = /* @__PURE__ */ z.object({
   _id: z.string().describe("Draft post ID.").max(38),
   draftPost: z.object({
     _id: z.string().describe("Draft post ID.").max(38).optional(),
@@ -1554,7 +1554,7 @@ var UpdateDraftPostRequest = z.object({
       tags: z.array(
         z.object({
           type: z.string().describe(
-            "SEO tag type.\n\n\nSupported values: `title`, `meta`, `script`, `link`."
+            "SEO tag type.\n\n\nSupported values: `title`, `meta`, `script`, `link`.\n\nWhich of these an API actually accepts depends on where the tag is being set: this\nlist is not a blanket guarantee across every API that reuses this message. Site SEO\nTags in particular accepts only `meta` (see `SiteSeoTags.tags`) and rejects\n`title`/`script`/`link` with a validation error even though they appear here \u2014\ncheck the field description of the specific `tags`-typed field you're writing to\nfor the types it actually supports and the error it returns."
           ).optional(),
           props: z.record(z.string(), z.any()).describe(
             'A `{"key": "value"}` pair object where each SEO tag property (`"name"`, `"content"`, `"rel"`, `"href"`) contains a value.\nFor example: `{"name": "description", "content": "the description itself"}`.'
@@ -1566,7 +1566,7 @@ var UpdateDraftPostRequest = z.object({
             "SEO tag inner content. For example, `<title> inner content </title>`."
           ).optional(),
           custom: z.boolean().describe(
-            "Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages) \u2014\ni.e. an entry from the site's Advanced/Custom Tags list.\n\nThis flag is scoped to that feature only. It is NOT an indicator of whether a standard tag\n(`title`, `description`, Open Graph, etc.) reflects a manually configured value versus a computed\ndefault/pattern \u2014 standard tags always resolve with `custom: false`, even when their content comes\nfrom a page's manually saved SEO title/description override. Don't use this field to verify whether\na live page reflects a manual per-page SEO edit.\n\nLimitation: when `ResolveStaticPageSeoTags` is called without `seoData`, the per-page SEO data is read\nonly from the Vibe/Wix-managed-headless override store. That store holds nothing for classic Wix Editor\nor Wix Studio pages, so even genuine Advanced/Custom Tags saved on those pages are missing from the\nresponse entirely \u2014 there, `false` means this API could not tell, not that no custom tag exists.\nPass `seoData` explicitly to resolve against a known set of tags."
+            "Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages) \u2014\ni.e. an entry from the site's Advanced/Custom Tags list.\n\nNote this is a separate restriction from Site SEO Tags' own type restriction on\n`SiteSeoTags.tags`: even with `custom` unset, Site SEO Tags rejects `script` (e.g.\nfor site-wide structured data) unconditionally. There is currently no way to set\nsite-wide, every-page structured data through any of these APIs \u2014 write a per-page\n`script` tag through the Item SEO Tags API instead.\n\nThis flag is scoped to that feature only. It is NOT an indicator of whether a standard tag\n(`title`, `description`, Open Graph, etc.) reflects a manually configured value versus a computed\ndefault/pattern \u2014 standard tags always resolve with `custom: false`, even when their content comes\nfrom a page's manually saved SEO title/description override. Don't use this field to verify whether\na live page reflects a manual per-page SEO edit.\n\nLimitation: when `ResolveStaticPageSeoTags` is called without `seoData`, the per-page SEO data is read\nonly from the Vibe/Wix-managed-headless override store. That store holds nothing for classic Wix Editor\nor Wix Studio pages, so even genuine Advanced/Custom Tags saved on those pages are missing from the\nresponse entirely \u2014 there, `false` means this API could not tell, not that no custom tag exists.\nPass `seoData` explicitly to resolve against a known set of tags."
           ).optional(),
           disabled: z.boolean().describe(
             "Whether the tag is disabled. If the tag is disabled, people can't find your page when searching for this phrase in search engines."
@@ -1660,7 +1660,7 @@ var UpdateDraftPostRequest = z.object({
     ).max(10).optional()
   }).describe("Options for updating a draft post.").optional()
 });
-var UpdateDraftPostResponse = z.object({
+var UpdateDraftPostResponse = /* @__PURE__ */ z.object({
   draftPost: z.object({
     _id: z.string().describe("Draft post ID.").max(38).optional(),
     title: z.string().describe("Draft post title.").max(200).optional(),
@@ -1733,7 +1733,7 @@ var UpdateDraftPostResponse = z.object({
       tags: z.array(
         z.object({
           type: z.string().describe(
-            "SEO tag type.\n\n\nSupported values: `title`, `meta`, `script`, `link`."
+            "SEO tag type.\n\n\nSupported values: `title`, `meta`, `script`, `link`.\n\nWhich of these an API actually accepts depends on where the tag is being set: this\nlist is not a blanket guarantee across every API that reuses this message. Site SEO\nTags in particular accepts only `meta` (see `SiteSeoTags.tags`) and rejects\n`title`/`script`/`link` with a validation error even though they appear here \u2014\ncheck the field description of the specific `tags`-typed field you're writing to\nfor the types it actually supports and the error it returns."
           ).optional(),
           props: z.record(z.string(), z.any()).describe(
             'A `{"key": "value"}` pair object where each SEO tag property (`"name"`, `"content"`, `"rel"`, `"href"`) contains a value.\nFor example: `{"name": "description", "content": "the description itself"}`.'
@@ -1745,7 +1745,7 @@ var UpdateDraftPostResponse = z.object({
             "SEO tag inner content. For example, `<title> inner content </title>`."
           ).optional(),
           custom: z.boolean().describe(
-            "Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages) \u2014\ni.e. an entry from the site's Advanced/Custom Tags list.\n\nThis flag is scoped to that feature only. It is NOT an indicator of whether a standard tag\n(`title`, `description`, Open Graph, etc.) reflects a manually configured value versus a computed\ndefault/pattern \u2014 standard tags always resolve with `custom: false`, even when their content comes\nfrom a page's manually saved SEO title/description override. Don't use this field to verify whether\na live page reflects a manual per-page SEO edit.\n\nLimitation: when `ResolveStaticPageSeoTags` is called without `seoData`, the per-page SEO data is read\nonly from the Vibe/Wix-managed-headless override store. That store holds nothing for classic Wix Editor\nor Wix Studio pages, so even genuine Advanced/Custom Tags saved on those pages are missing from the\nresponse entirely \u2014 there, `false` means this API could not tell, not that no custom tag exists.\nPass `seoData` explicitly to resolve against a known set of tags."
+            "Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages) \u2014\ni.e. an entry from the site's Advanced/Custom Tags list.\n\nNote this is a separate restriction from Site SEO Tags' own type restriction on\n`SiteSeoTags.tags`: even with `custom` unset, Site SEO Tags rejects `script` (e.g.\nfor site-wide structured data) unconditionally. There is currently no way to set\nsite-wide, every-page structured data through any of these APIs \u2014 write a per-page\n`script` tag through the Item SEO Tags API instead.\n\nThis flag is scoped to that feature only. It is NOT an indicator of whether a standard tag\n(`title`, `description`, Open Graph, etc.) reflects a manually configured value versus a computed\ndefault/pattern \u2014 standard tags always resolve with `custom: false`, even when their content comes\nfrom a page's manually saved SEO title/description override. Don't use this field to verify whether\na live page reflects a manual per-page SEO edit.\n\nLimitation: when `ResolveStaticPageSeoTags` is called without `seoData`, the per-page SEO data is read\nonly from the Vibe/Wix-managed-headless override store. That store holds nothing for classic Wix Editor\nor Wix Studio pages, so even genuine Advanced/Custom Tags saved on those pages are missing from the\nresponse entirely \u2014 there, `false` means this API could not tell, not that no custom tag exists.\nPass `seoData` explicitly to resolve against a known set of tags."
           ).optional(),
           disabled: z.boolean().describe(
             "Whether the tag is disabled. If the tag is disabled, people can't find your page when searching for this phrase in search engines."
@@ -1816,7 +1816,7 @@ var UpdateDraftPostResponse = z.object({
     ).min(0).optional().nullable()
   }).describe("Updated draft post info.").optional()
 });
-var DeleteDraftPostRequest = z.object({
+var DeleteDraftPostRequest = /* @__PURE__ */ z.object({
   draftPostId: z.string().describe("Draft post ID.").max(38),
   options: z.object({
     permanent: z.boolean().describe(
@@ -1824,18 +1824,18 @@ var DeleteDraftPostRequest = z.object({
     ).optional()
   }).describe("Options for deleting a draft post.").optional()
 });
-var DeleteDraftPostResponse = z.object({});
-var RemoveFromTrashBinRequest = z.object({
+var DeleteDraftPostResponse = /* @__PURE__ */ z.object({});
+var RemoveFromTrashBinRequest = /* @__PURE__ */ z.object({
   draftPostId: z.string().describe("Draft post ID.").max(38)
 });
-var RemoveFromTrashBinResponse = z.object({});
-var BulkDeleteDraftPostsRequest = z.object({
+var RemoveFromTrashBinResponse = /* @__PURE__ */ z.object({});
+var BulkDeleteDraftPostsRequest = /* @__PURE__ */ z.object({
   postIds: z.array(z.string()).min(1).max(100),
   options: z.object({
     permanent: z.boolean().describe("Should delete bypassing the trash-bin.").optional()
   }).describe("Options for deleting multiple draft posts.").optional()
 });
-var BulkDeleteDraftPostsResponse = z.object({
+var BulkDeleteDraftPostsResponse = /* @__PURE__ */ z.object({
   results: z.array(
     z.object({
       itemMetadata: z.object({
@@ -1926,7 +1926,7 @@ var BulkDeleteDraftPostsResponse = z.object({
           tags: z.array(
             z.object({
               type: z.string().describe(
-                "SEO tag type.\n\n\nSupported values: `title`, `meta`, `script`, `link`."
+                "SEO tag type.\n\n\nSupported values: `title`, `meta`, `script`, `link`.\n\nWhich of these an API actually accepts depends on where the tag is being set: this\nlist is not a blanket guarantee across every API that reuses this message. Site SEO\nTags in particular accepts only `meta` (see `SiteSeoTags.tags`) and rejects\n`title`/`script`/`link` with a validation error even though they appear here \u2014\ncheck the field description of the specific `tags`-typed field you're writing to\nfor the types it actually supports and the error it returns."
               ).optional(),
               props: z.record(z.string(), z.any()).describe(
                 'A `{"key": "value"}` pair object where each SEO tag property (`"name"`, `"content"`, `"rel"`, `"href"`) contains a value.\nFor example: `{"name": "description", "content": "the description itself"}`.'
@@ -1938,7 +1938,7 @@ var BulkDeleteDraftPostsResponse = z.object({
                 "SEO tag inner content. For example, `<title> inner content </title>`."
               ).optional(),
               custom: z.boolean().describe(
-                "Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages) \u2014\ni.e. an entry from the site's Advanced/Custom Tags list.\n\nThis flag is scoped to that feature only. It is NOT an indicator of whether a standard tag\n(`title`, `description`, Open Graph, etc.) reflects a manually configured value versus a computed\ndefault/pattern \u2014 standard tags always resolve with `custom: false`, even when their content comes\nfrom a page's manually saved SEO title/description override. Don't use this field to verify whether\na live page reflects a manual per-page SEO edit.\n\nLimitation: when `ResolveStaticPageSeoTags` is called without `seoData`, the per-page SEO data is read\nonly from the Vibe/Wix-managed-headless override store. That store holds nothing for classic Wix Editor\nor Wix Studio pages, so even genuine Advanced/Custom Tags saved on those pages are missing from the\nresponse entirely \u2014 there, `false` means this API could not tell, not that no custom tag exists.\nPass `seoData` explicitly to resolve against a known set of tags."
+                "Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages) \u2014\ni.e. an entry from the site's Advanced/Custom Tags list.\n\nNote this is a separate restriction from Site SEO Tags' own type restriction on\n`SiteSeoTags.tags`: even with `custom` unset, Site SEO Tags rejects `script` (e.g.\nfor site-wide structured data) unconditionally. There is currently no way to set\nsite-wide, every-page structured data through any of these APIs \u2014 write a per-page\n`script` tag through the Item SEO Tags API instead.\n\nThis flag is scoped to that feature only. It is NOT an indicator of whether a standard tag\n(`title`, `description`, Open Graph, etc.) reflects a manually configured value versus a computed\ndefault/pattern \u2014 standard tags always resolve with `custom: false`, even when their content comes\nfrom a page's manually saved SEO title/description override. Don't use this field to verify whether\na live page reflects a manual per-page SEO edit.\n\nLimitation: when `ResolveStaticPageSeoTags` is called without `seoData`, the per-page SEO data is read\nonly from the Vibe/Wix-managed-headless override store. That store holds nothing for classic Wix Editor\nor Wix Studio pages, so even genuine Advanced/Custom Tags saved on those pages are missing from the\nresponse entirely \u2014 there, `false` means this API could not tell, not that no custom tag exists.\nPass `seoData` explicitly to resolve against a known set of tags."
               ).optional(),
               disabled: z.boolean().describe(
                 "Whether the tag is disabled. If the tag is disabled, people can't find your page when searching for this phrase in search engines."
@@ -2018,7 +2018,7 @@ var BulkDeleteDraftPostsResponse = z.object({
     ).optional()
   }).describe("Bulk action metadata.").optional()
 });
-var ListDraftPostsRequest = z.object({
+var ListDraftPostsRequest = /* @__PURE__ */ z.object({
   options: z.object({
     status: z.enum([
       "UNKNOWN",
@@ -2052,7 +2052,7 @@ var ListDraftPostsRequest = z.object({
     ).max(10).optional()
   }).describe("Options for listing multiple draft posts.").optional()
 });
-var ListDraftPostsResponse = z.object({
+var ListDraftPostsResponse = /* @__PURE__ */ z.object({
   draftPosts: z.array(
     z.object({
       _id: z.string().describe("Draft post ID.").max(38).optional(),
@@ -2126,7 +2126,7 @@ var ListDraftPostsResponse = z.object({
         tags: z.array(
           z.object({
             type: z.string().describe(
-              "SEO tag type.\n\n\nSupported values: `title`, `meta`, `script`, `link`."
+              "SEO tag type.\n\n\nSupported values: `title`, `meta`, `script`, `link`.\n\nWhich of these an API actually accepts depends on where the tag is being set: this\nlist is not a blanket guarantee across every API that reuses this message. Site SEO\nTags in particular accepts only `meta` (see `SiteSeoTags.tags`) and rejects\n`title`/`script`/`link` with a validation error even though they appear here \u2014\ncheck the field description of the specific `tags`-typed field you're writing to\nfor the types it actually supports and the error it returns."
             ).optional(),
             props: z.record(z.string(), z.any()).describe(
               'A `{"key": "value"}` pair object where each SEO tag property (`"name"`, `"content"`, `"rel"`, `"href"`) contains a value.\nFor example: `{"name": "description", "content": "the description itself"}`.'
@@ -2138,7 +2138,7 @@ var ListDraftPostsResponse = z.object({
               "SEO tag inner content. For example, `<title> inner content </title>`."
             ).optional(),
             custom: z.boolean().describe(
-              "Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages) \u2014\ni.e. an entry from the site's Advanced/Custom Tags list.\n\nThis flag is scoped to that feature only. It is NOT an indicator of whether a standard tag\n(`title`, `description`, Open Graph, etc.) reflects a manually configured value versus a computed\ndefault/pattern \u2014 standard tags always resolve with `custom: false`, even when their content comes\nfrom a page's manually saved SEO title/description override. Don't use this field to verify whether\na live page reflects a manual per-page SEO edit.\n\nLimitation: when `ResolveStaticPageSeoTags` is called without `seoData`, the per-page SEO data is read\nonly from the Vibe/Wix-managed-headless override store. That store holds nothing for classic Wix Editor\nor Wix Studio pages, so even genuine Advanced/Custom Tags saved on those pages are missing from the\nresponse entirely \u2014 there, `false` means this API could not tell, not that no custom tag exists.\nPass `seoData` explicitly to resolve against a known set of tags."
+              "Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages) \u2014\ni.e. an entry from the site's Advanced/Custom Tags list.\n\nNote this is a separate restriction from Site SEO Tags' own type restriction on\n`SiteSeoTags.tags`: even with `custom` unset, Site SEO Tags rejects `script` (e.g.\nfor site-wide structured data) unconditionally. There is currently no way to set\nsite-wide, every-page structured data through any of these APIs \u2014 write a per-page\n`script` tag through the Item SEO Tags API instead.\n\nThis flag is scoped to that feature only. It is NOT an indicator of whether a standard tag\n(`title`, `description`, Open Graph, etc.) reflects a manually configured value versus a computed\ndefault/pattern \u2014 standard tags always resolve with `custom: false`, even when their content comes\nfrom a page's manually saved SEO title/description override. Don't use this field to verify whether\na live page reflects a manual per-page SEO edit.\n\nLimitation: when `ResolveStaticPageSeoTags` is called without `seoData`, the per-page SEO data is read\nonly from the Vibe/Wix-managed-headless override store. That store holds nothing for classic Wix Editor\nor Wix Studio pages, so even genuine Advanced/Custom Tags saved on those pages are missing from the\nresponse entirely \u2014 there, `false` means this API could not tell, not that no custom tag exists.\nPass `seoData` explicitly to resolve against a known set of tags."
             ).optional(),
             disabled: z.boolean().describe(
               "Whether the tag is disabled. If the tag is disabled, people can't find your page when searching for this phrase in search engines."
@@ -2218,10 +2218,10 @@ var ListDraftPostsResponse = z.object({
     ).max(2e3).optional().nullable()
   }).describe("Details on the paged set of results returned.").optional()
 });
-var GetDeletedDraftPostRequest = z.object({
+var GetDeletedDraftPostRequest = /* @__PURE__ */ z.object({
   draftPostId: z.string().describe("Draft post ID.").max(38)
 });
-var GetDeletedDraftPostResponse = z.object({
+var GetDeletedDraftPostResponse = /* @__PURE__ */ z.object({
   draftPost: z.object({
     _id: z.string().describe("Draft post ID.").max(38).optional(),
     title: z.string().describe("Draft post title.").max(200).optional(),
@@ -2294,7 +2294,7 @@ var GetDeletedDraftPostResponse = z.object({
       tags: z.array(
         z.object({
           type: z.string().describe(
-            "SEO tag type.\n\n\nSupported values: `title`, `meta`, `script`, `link`."
+            "SEO tag type.\n\n\nSupported values: `title`, `meta`, `script`, `link`.\n\nWhich of these an API actually accepts depends on where the tag is being set: this\nlist is not a blanket guarantee across every API that reuses this message. Site SEO\nTags in particular accepts only `meta` (see `SiteSeoTags.tags`) and rejects\n`title`/`script`/`link` with a validation error even though they appear here \u2014\ncheck the field description of the specific `tags`-typed field you're writing to\nfor the types it actually supports and the error it returns."
           ).optional(),
           props: z.record(z.string(), z.any()).describe(
             'A `{"key": "value"}` pair object where each SEO tag property (`"name"`, `"content"`, `"rel"`, `"href"`) contains a value.\nFor example: `{"name": "description", "content": "the description itself"}`.'
@@ -2306,7 +2306,7 @@ var GetDeletedDraftPostResponse = z.object({
             "SEO tag inner content. For example, `<title> inner content </title>`."
           ).optional(),
           custom: z.boolean().describe(
-            "Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages) \u2014\ni.e. an entry from the site's Advanced/Custom Tags list.\n\nThis flag is scoped to that feature only. It is NOT an indicator of whether a standard tag\n(`title`, `description`, Open Graph, etc.) reflects a manually configured value versus a computed\ndefault/pattern \u2014 standard tags always resolve with `custom: false`, even when their content comes\nfrom a page's manually saved SEO title/description override. Don't use this field to verify whether\na live page reflects a manual per-page SEO edit.\n\nLimitation: when `ResolveStaticPageSeoTags` is called without `seoData`, the per-page SEO data is read\nonly from the Vibe/Wix-managed-headless override store. That store holds nothing for classic Wix Editor\nor Wix Studio pages, so even genuine Advanced/Custom Tags saved on those pages are missing from the\nresponse entirely \u2014 there, `false` means this API could not tell, not that no custom tag exists.\nPass `seoData` explicitly to resolve against a known set of tags."
+            "Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages) \u2014\ni.e. an entry from the site's Advanced/Custom Tags list.\n\nNote this is a separate restriction from Site SEO Tags' own type restriction on\n`SiteSeoTags.tags`: even with `custom` unset, Site SEO Tags rejects `script` (e.g.\nfor site-wide structured data) unconditionally. There is currently no way to set\nsite-wide, every-page structured data through any of these APIs \u2014 write a per-page\n`script` tag through the Item SEO Tags API instead.\n\nThis flag is scoped to that feature only. It is NOT an indicator of whether a standard tag\n(`title`, `description`, Open Graph, etc.) reflects a manually configured value versus a computed\ndefault/pattern \u2014 standard tags always resolve with `custom: false`, even when their content comes\nfrom a page's manually saved SEO title/description override. Don't use this field to verify whether\na live page reflects a manual per-page SEO edit.\n\nLimitation: when `ResolveStaticPageSeoTags` is called without `seoData`, the per-page SEO data is read\nonly from the Vibe/Wix-managed-headless override store. That store holds nothing for classic Wix Editor\nor Wix Studio pages, so even genuine Advanced/Custom Tags saved on those pages are missing from the\nresponse entirely \u2014 there, `false` means this API could not tell, not that no custom tag exists.\nPass `seoData` explicitly to resolve against a known set of tags."
           ).optional(),
           disabled: z.boolean().describe(
             "Whether the tag is disabled. If the tag is disabled, people can't find your page when searching for this phrase in search engines."
@@ -2377,10 +2377,10 @@ var GetDeletedDraftPostResponse = z.object({
     ).min(0).optional().nullable()
   }).describe("Draft post info.").optional()
 });
-var RestoreFromTrashBinRequest = z.object({
+var RestoreFromTrashBinRequest = /* @__PURE__ */ z.object({
   draftPostId: z.string().describe("Draft post ID.").max(38)
 });
-var RestoreFromTrashBinResponse = z.object({
+var RestoreFromTrashBinResponse = /* @__PURE__ */ z.object({
   draftPost: z.object({
     _id: z.string().describe("Draft post ID.").max(38).optional(),
     title: z.string().describe("Draft post title.").max(200).optional(),
@@ -2453,7 +2453,7 @@ var RestoreFromTrashBinResponse = z.object({
       tags: z.array(
         z.object({
           type: z.string().describe(
-            "SEO tag type.\n\n\nSupported values: `title`, `meta`, `script`, `link`."
+            "SEO tag type.\n\n\nSupported values: `title`, `meta`, `script`, `link`.\n\nWhich of these an API actually accepts depends on where the tag is being set: this\nlist is not a blanket guarantee across every API that reuses this message. Site SEO\nTags in particular accepts only `meta` (see `SiteSeoTags.tags`) and rejects\n`title`/`script`/`link` with a validation error even though they appear here \u2014\ncheck the field description of the specific `tags`-typed field you're writing to\nfor the types it actually supports and the error it returns."
           ).optional(),
           props: z.record(z.string(), z.any()).describe(
             'A `{"key": "value"}` pair object where each SEO tag property (`"name"`, `"content"`, `"rel"`, `"href"`) contains a value.\nFor example: `{"name": "description", "content": "the description itself"}`.'
@@ -2465,7 +2465,7 @@ var RestoreFromTrashBinResponse = z.object({
             "SEO tag inner content. For example, `<title> inner content </title>`."
           ).optional(),
           custom: z.boolean().describe(
-            "Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages) \u2014\ni.e. an entry from the site's Advanced/Custom Tags list.\n\nThis flag is scoped to that feature only. It is NOT an indicator of whether a standard tag\n(`title`, `description`, Open Graph, etc.) reflects a manually configured value versus a computed\ndefault/pattern \u2014 standard tags always resolve with `custom: false`, even when their content comes\nfrom a page's manually saved SEO title/description override. Don't use this field to verify whether\na live page reflects a manual per-page SEO edit.\n\nLimitation: when `ResolveStaticPageSeoTags` is called without `seoData`, the per-page SEO data is read\nonly from the Vibe/Wix-managed-headless override store. That store holds nothing for classic Wix Editor\nor Wix Studio pages, so even genuine Advanced/Custom Tags saved on those pages are missing from the\nresponse entirely \u2014 there, `false` means this API could not tell, not that no custom tag exists.\nPass `seoData` explicitly to resolve against a known set of tags."
+            "Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages) \u2014\ni.e. an entry from the site's Advanced/Custom Tags list.\n\nNote this is a separate restriction from Site SEO Tags' own type restriction on\n`SiteSeoTags.tags`: even with `custom` unset, Site SEO Tags rejects `script` (e.g.\nfor site-wide structured data) unconditionally. There is currently no way to set\nsite-wide, every-page structured data through any of these APIs \u2014 write a per-page\n`script` tag through the Item SEO Tags API instead.\n\nThis flag is scoped to that feature only. It is NOT an indicator of whether a standard tag\n(`title`, `description`, Open Graph, etc.) reflects a manually configured value versus a computed\ndefault/pattern \u2014 standard tags always resolve with `custom: false`, even when their content comes\nfrom a page's manually saved SEO title/description override. Don't use this field to verify whether\na live page reflects a manual per-page SEO edit.\n\nLimitation: when `ResolveStaticPageSeoTags` is called without `seoData`, the per-page SEO data is read\nonly from the Vibe/Wix-managed-headless override store. That store holds nothing for classic Wix Editor\nor Wix Studio pages, so even genuine Advanced/Custom Tags saved on those pages are missing from the\nresponse entirely \u2014 there, `false` means this API could not tell, not that no custom tag exists.\nPass `seoData` explicitly to resolve against a known set of tags."
           ).optional(),
           disabled: z.boolean().describe(
             "Whether the tag is disabled. If the tag is disabled, people can't find your page when searching for this phrase in search engines."
@@ -2536,7 +2536,7 @@ var RestoreFromTrashBinResponse = z.object({
     ).min(0).optional().nullable()
   }).describe("Restored draft post info.").optional()
 });
-var QueryDraftPostsRequest = z.object({
+var QueryDraftPostsRequest = /* @__PURE__ */ z.object({
   query: z.object({
     filter: z.object({
       _id: z.object({
@@ -2667,7 +2667,7 @@ var QueryDraftPostsRequest = z.object({
     ).max(10).optional()
   }).describe("Options for querying draft posts.").optional()
 });
-var QueryDraftPostsResponse = z.object({
+var QueryDraftPostsResponse = /* @__PURE__ */ z.object({
   draftPosts: z.array(
     z.object({
       _id: z.string().describe("Draft post ID.").max(38).optional(),
@@ -2741,7 +2741,7 @@ var QueryDraftPostsResponse = z.object({
         tags: z.array(
           z.object({
             type: z.string().describe(
-              "SEO tag type.\n\n\nSupported values: `title`, `meta`, `script`, `link`."
+              "SEO tag type.\n\n\nSupported values: `title`, `meta`, `script`, `link`.\n\nWhich of these an API actually accepts depends on where the tag is being set: this\nlist is not a blanket guarantee across every API that reuses this message. Site SEO\nTags in particular accepts only `meta` (see `SiteSeoTags.tags`) and rejects\n`title`/`script`/`link` with a validation error even though they appear here \u2014\ncheck the field description of the specific `tags`-typed field you're writing to\nfor the types it actually supports and the error it returns."
             ).optional(),
             props: z.record(z.string(), z.any()).describe(
               'A `{"key": "value"}` pair object where each SEO tag property (`"name"`, `"content"`, `"rel"`, `"href"`) contains a value.\nFor example: `{"name": "description", "content": "the description itself"}`.'
@@ -2753,7 +2753,7 @@ var QueryDraftPostsResponse = z.object({
               "SEO tag inner content. For example, `<title> inner content </title>`."
             ).optional(),
             custom: z.boolean().describe(
-              "Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages) \u2014\ni.e. an entry from the site's Advanced/Custom Tags list.\n\nThis flag is scoped to that feature only. It is NOT an indicator of whether a standard tag\n(`title`, `description`, Open Graph, etc.) reflects a manually configured value versus a computed\ndefault/pattern \u2014 standard tags always resolve with `custom: false`, even when their content comes\nfrom a page's manually saved SEO title/description override. Don't use this field to verify whether\na live page reflects a manual per-page SEO edit.\n\nLimitation: when `ResolveStaticPageSeoTags` is called without `seoData`, the per-page SEO data is read\nonly from the Vibe/Wix-managed-headless override store. That store holds nothing for classic Wix Editor\nor Wix Studio pages, so even genuine Advanced/Custom Tags saved on those pages are missing from the\nresponse entirely \u2014 there, `false` means this API could not tell, not that no custom tag exists.\nPass `seoData` explicitly to resolve against a known set of tags."
+              "Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages) \u2014\ni.e. an entry from the site's Advanced/Custom Tags list.\n\nNote this is a separate restriction from Site SEO Tags' own type restriction on\n`SiteSeoTags.tags`: even with `custom` unset, Site SEO Tags rejects `script` (e.g.\nfor site-wide structured data) unconditionally. There is currently no way to set\nsite-wide, every-page structured data through any of these APIs \u2014 write a per-page\n`script` tag through the Item SEO Tags API instead.\n\nThis flag is scoped to that feature only. It is NOT an indicator of whether a standard tag\n(`title`, `description`, Open Graph, etc.) reflects a manually configured value versus a computed\ndefault/pattern \u2014 standard tags always resolve with `custom: false`, even when their content comes\nfrom a page's manually saved SEO title/description override. Don't use this field to verify whether\na live page reflects a manual per-page SEO edit.\n\nLimitation: when `ResolveStaticPageSeoTags` is called without `seoData`, the per-page SEO data is read\nonly from the Vibe/Wix-managed-headless override store. That store holds nothing for classic Wix Editor\nor Wix Studio pages, so even genuine Advanced/Custom Tags saved on those pages are missing from the\nresponse entirely \u2014 there, `false` means this API could not tell, not that no custom tag exists.\nPass `seoData` explicitly to resolve against a known set of tags."
             ).optional(),
             disabled: z.boolean().describe(
               "Whether the tag is disabled. If the tag is disabled, people can't find your page when searching for this phrase in search engines."
@@ -2843,10 +2843,10 @@ var QueryDraftPostsResponse = z.object({
     ).optional()
   }).describe("Details on the paged set of results returned.").optional()
 });
-var PublishDraftPostRequest = z.object({
+var PublishDraftPostRequest = /* @__PURE__ */ z.object({
   draftPostId: z.string().describe("Draft post ID.").max(38)
 });
-var PublishDraftPostResponse = z.object({
+var PublishDraftPostResponse = /* @__PURE__ */ z.object({
   postId: z.string().describe("Published post ID.").regex(
     /^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$/,
     "Must be a valid GUID"