{"section":"known-issues","requestedLocale":"en","requestedSlug":"sitemap-returns-account-not-found-on-public-domains-for-stores-split-between-store-framework-and-faststore","locale":"en","slug":"sitemap-returns-account-not-found-on-public-domains-for-stores-split-between-store-framework-and-faststore","path":"docs/en/known-issues/Store Framework/sitemap-returns-account-not-found-on-public-domains-for-stores-split-between-store-framework-and-faststore.md","branch":"main","content":"## Summary\n\nStores running an active traffic split between VTEX IO and FastStore cannot serve `/sitemap.xml` on their public domains (apex and `www`) — it returns `400 – Account not found`. Internal domains (`{account}.myvtex.com`, `{account}.vtexcommercestable.com.br`) work fine for the same account. Engineering confirmed the current split design is incompatible with sitemap serving for these stores.\n\n## Simulation\n\n- Have a store with an active IO/FastStore traffic split (any percentage).\n- Request `https://{public-custom-domain}/sitemap.xml` (apex and/or `www`).\n- Observe `400 Bad Request`, body `\"Account not found\"`.\n- Compare with the same account on:\n  - `https://{account}.vtexcommercestable.com.br/sitemap.xml` → works (200)\n  - `https://{account}.myvtex.com/sitemap.xml` → works (200)\n\n## Workaround\n\nN/A"}