Reserved URL Paths for the Astro Integration

On a Wix-managed headless project, the wix() Astro integration registers its own routes into your project as part of the build, at a known set of paths. Those routes live in the same router as the routes you define, so a route you add at one of those paths collides with the one the integration already registered.

Knowing which paths the platform claims helps you:

  • Choose safe URLs for your own HTTP endpoints and custom feeds.
  • Understand a router-collision warning in your build output.

How a collision plays out

Because the integration's routes and your routes share a router, adding a route at a claimed path doesn't cleanly override the platform's route. Astro logs a router-collision warning at build and dev time. For /robots.txt specifically, Astro currently serves your project's route instead of the platform's, so your project stops serving the robots.txt file a Wix user manages in the dashboard. See About SEO Support.

Some claimed paths have a configuration option to turn them off instead. For example, wix({ robots: false }) stops the integration from registering /robots.txt at all, so you can serve your own route there without a collision. The table below notes which paths have a configuration option. If a path isn't noted, avoid the collision by choosing a different path instead.

Paths the platform claims

Path or patternWhat it's for
/_api/*Requests the platform's own viewer components make to Wix. Also includes /_api/mcp, every site's built-in MCP server. See About the Wix Site MCP. Call Wix APIs from your own server code, or use /api/* for your own endpoints, instead of adding routes here.
/api/auth/loginStarts the member login flow. Built in. See Add Member Login with the Astro Integration.
/api/auth/callbackCompletes the member login flow. Built in. Don't link to it directly.
/api/auth/logout and /api/auth/logout-callbackLog the member out. Built in.
/checkout and /__ecom/checkoutWix-hosted checkout.
/_paylink/[id]Payment-link pages.
/_proposal/[id]Proposal pages.
/robots.txtThe robots.txt file a Wix user manages in the dashboard. Turn this off with wix({ robots: false }) if you want to serve your own.
/sitemap.xml and other *-sitemap.xml pathsThe generated sitemap index and its per-vertical sitemaps. See About Sitemaps in the Astro Integration.
/_wix/pages.jsonYour page registry.
/_wix/extensions/*Backoffice, service-plugin, and webhook calls for your project's extensions.
The path set by adminPathnameThe admin redirect. You choose this path yourself with the integration's adminPathname option.

Everything under /_wix/ belongs to the platform. Define your own endpoints under /api/ instead, apart from the built-in /api/auth/* routes above, and check your build output for collision warnings.

Only /sitemap.xml and its *-sitemap.xml siblings relate to the generated sitemap. The other claimed paths in this table, such as /checkout and /api/auth/*, don't relate to sitemap content.

What stays yours

Astro serves the following from your own routes:

  • Your own HTTP endpoints, at /api/<your-endpoint>.
  • Custom feeds at any path the platform doesn't claim, such as /google-merchant-feed.xml.
  • Regular pages, such as /about, /shop, and /product/[handle].

See also

Last updated: 15 September 2026

Did this help?