18 "reason": "Read-only listing (List Sitemap Pages) of the pages in a headless site's sitemap; there is no write method, so nothing can be imported here. A WordPress XML sitemap (Yoast/Rank Math sitemap module) is generated output, not durable data: Wix builds and serves its own sitemap, so the source sitemap is replaced rather than migrated. Both reference pages under this surface returned HTTP 404 when fetched on 2026-08-16.",
27 "reason": "A service plugin (SPI): an extension point where a 3rd-party keyword tool SUPPLIES suggestions to Wix (Extension Config, Get Quota, List Suggested Keywords). An SPI is not an import path. The source-side analogue - a Yoast/Rank Math focus keyphrase stored on a post - is durable data and imports through Item SEO Tags `focusKeywords`, not here.",
36 "reason": "Site-level routing configuration, not per-record data: `shouldFlattenUrlHierarchy` (flat vs hierarchical page URLs) and `shouldUsePartialRouteMatch` (whether an unknown path returns 200 instead of 404). Reconfigure-in-wix. Flagged for URL preservation: flattening changes every subpage URL, so it is a setup decision taken BEFORE the URL ledger is computed, never an import step.",
45 "reason": "ads.txt declares authorised digital ad sellers (IAB Tech Lab standard). It is advertising configuration, not migrated business data, and no WordPress SEO plugin in scope stores it as per-record data.",
54 "reason": "llms.txt is an AI-crawler manifest Wix generates and serves per site (Get / Update / Append / Update Hidden Status). It is generated output about the destination site, with no source-side counterpart to carry across.",
63 "reason": "robots.txt is crawler configuration, not durable data, and it does not transfer literally: a WordPress robots.txt disallows source-only paths (/wp-admin/, /wp-content/, /?s=) that do not exist on Wix, and Wix serves its own default. Reconfigure-in-wix. A writable path does exist if a future step wants it (PUT https://www.wixapis.com/promote-seo-robots-server/v2/robots, SCOPE.PROMOTE.MANAGE-SEO).",
105 "reason": "Read-only resolve endpoints (Resolve Item SEO Tags, Resolve Static Page SEO Tags) that return the tags a page is expected to render with. Migration-relevant as the post-import VERIFICATION path for seo/item-seo-tags, but it has no write method so nothing imports here. Its object page also carries the `custom` caveat recorded as the `custom-flag-is-not-an-override-signal` pitfall on seo/item-seo-tags: ResolveStaticPageSeoTags called without `seoData` reads only the Vibe/managed-headless override store, so on classic Editor/Studio pages `custom: false` means 'could not tell', not 'no custom tag'.",