{"section":"known-issues","requestedLocale":"en","requestedSlug":"disablesitemapentry-flag-not-respected-by-sitemap-generation","locale":"en","slug":"disablesitemapentry-flag-not-respected-by-sitemap-generation","path":"docs/en/known-issues/Store Framework/disablesitemapentry-flag-not-respected-by-sitemap-generation.md","branch":"main","content":"## Summary\n\n\nSetting disableSitemapEntry: true on internal routes does not prevent those routes from being included in the generated sitemap. Affected merchants see disabled routes still appearing in brand/category/product sitemaps even after attempting to regenerate the sitemap. This impacts storefronts using the unified sitemap pipeline for Store Framework, FastStore, or legacy, especially when trying to de-index specific routes.\n\n\n#### Simulation\n\n\n1) Query an internal route via GraphQL to confirm current properties:\n\\{ internal \\{ get(path: \"/\") \\{ from type declarer id resolveAs origin disableSitemapEntry \\} \\} \\}\n\n2) Save the route with disableSitemapEntry set to true using:\nmutation saveInternal($route: InternalInput!) \\{ internal \\{ save(route: $route) \\{ from declarer type id query endDate binding resolveAs origin disableSitemapEntry \\} \\} \\} with variables including \"disableSitemapEntry\": true (matching the route fields retrieved in step 1).\n\n3) Wait for sitemap generation (note: forcing generateSitemap has no effect in the unified pipeline which runs once per day).\n\n4) Observe that the route still appears in the sitemap XML (e.g., brand-0.xml), despite disableSitemapEntry being set to true earlier\n\n\n#### Workaround\n\n\nOpen a support ticket so we can install and use the HKignore version of the vtex.store-sitemap."}