{"section":"troubleshooting","requestedLocale":"en","requestedSlug":"my-product-or-category-page-shows-page-not-found","locale":"en","slug":"my-product-or-category-page-shows-page-not-found","path":"docs/en/troubleshooting/merchandising-and-search/my-product-or-category-page-shows-page-not-found.md","branch":"main","content":"Keywords: Loading error | Sync issue\n\nMy product, category, or subcategory page returns `404` or behaves as if the page doesn't exist (**PAGE NOT FOUND** message). This can happen after catalog updates, such as changes to product content, images, slugs, category hierarchy, or workspace publication.\n\nIn some cases, the issue seems to be a rendering or product visibility issue, but the storefront symptom remains the same: the route can't be resolved correctly. Depending on the root cause, the fix may require action from you, VTEX, or both.\n\nThe most common causes for this behavior are:\n\n- [The URL or slug changed](#check-the-url-and-slug)\n- [The product or category isn't available in the storefront](#confirm-storefront-availability)\n- [The product or category wasn't indexed correctly](#reindex-the-affected-item)\n- [The route wasn't updated in the rewriter](#refresh-route-generation)\n- [The category hierarchy or breadcrumb path is incorrect](#check-the-category-hierarchy-and-breadcrumb-path)\n- [Workspace changes weren't published](#publish-workspace-changes)\n\n## Solutions\n\n### Check the URL and slug\n\n1. In the VTEX Admin, go to **Catalog**, or type **Catalog** in the search bar at the top of the page.\n2. Click **Products and SKUs** or **Categories** to access the affected product or category.\n3. Confirm whether the current [product](https://help.vtex.com/docs/tutorials/adding-or-editing-products#seo) or [category](https://help.vtex.com/docs/tutorials/registering-a-category#filling-in-the-category-registration-fields) URL slugs are correct.\n4. Check whether the storefront URL matches the current slug exactly.\n5. If the slug changed recently, test the new URL.\n6. If internal or external links still point to the old URL, create a redirect from the old path to the current one, following the instructions in [Managing URL redirects](https://help.vtex.com/en/docs/tutorials/managing-url-redirects).\n\nAfter completing these checks, open the current URL again and confirm that the page no longer returns `404`.\n\n### Confirm storefront availability\n\n1. In the VTEX Admin, go to **Catalog**, or type **Catalog** in the search bar at the top of the page.\n2. Click **Products and SKUs** or **Categories** to access the affected product or category.\n3. Confirm that the product or category is active and is configured to be shown in the store. For products, confirm that at least one SKU is active.\n4. Check whether the product has a valid price and stock for the [sales channel (trade policy)](https://help.vtex.com/en/docs/tutorials/how-trade-policies-work) used by the store.\n5. If your operation shows unavailable products, make sure that the corresponding display setting is enabled based on the [availability](https://help.vtex.com/en/docs/tutorials/availability) criteria.\n6. Confirm that the item is assigned to the expected brand, category, and business structure.\n\nAfter validating these settings, test the storefront again to confirm that the product or category is available and no longer behaves like a missing page.\n\n### Reindex the affected item\n\n1. In the VTEX Admin, trigger [reindexing](https://help.vtex.com/en/faq/why-is-the-product-not-visible-on-the-website#indexed-info) for the affected product or category.\n\n> ⚠️ If multiple related pages are failing, you may need to perform a full reindex of the catalog.\n\n2. Wait for the indexing process to finish and monitor the status in [Indexing History](https://help.vtex.com/en/docs/tutorials/indexing-history) or check the [catalog reindex log](https://help.vtex.com/en/docs/tutorials/view-reindex-log) if needed.\n3. Test the affected URL again in an anonymous browser window.\n\nOnce the indexing process is complete, test the affected URL again and confirm that the page resolves normally.\n\n### Refresh route generation\n\n1. Check whether the expected route exists in the [rewriter configuration](https://help.vtex.com/troubleshooting/i-cant-view-the-product-in-the-search-results).\n2. Confirm that the route points to the correct product, category, or subcategory path.\n3. If the route is stale or inconsistent, refresh route generation based on your internal procedure.\n4. If your team uses route versioning, increment the route version and wait for the storefront to rebuild the routes.\n5. Test the affected URL again.\n\nAfter refreshing the route, test the URL again to confirm that the storefront rebuilt the path correctly.\n\n### Check the category hierarchy and breadcrumb path\n\n1. In the VTEX Admin, open the [category tree](https://help.vtex.com/en/docs/tutorials/deactivating-and-reorganizing-categories#changing-the-category-tree).\n2. Confirm that the affected subcategory is attached to the expected parent category.\n3. Check whether the breadcrumb path in the storefront matches that hierarchy.\n4. Compare the failing subcategory with another subcategory under the same parent that works correctly.\n5. If the breadcrumb points to an outdated or malformed path, correct the category structure and reindex the affected categories.\n\nAfter correcting the category structure, test the breadcrumb and subcategory links again and confirm that they open valid pages.\n\n### Publish workspace changes\n\n1. Confirm where the change was applied in the [workspace](https://developers.vtex.com/docs/guides/vtex-io-documentation-workspace).\n2. Validate the corrected route in the workspace.\n3. Publish or promote the workspace changes following your release process.\n4. Test the page in the live store and confirm that production is using the updated route.\n\nIf the page still returns `404` after following all the steps above, contact VTEX Support using the instructions in [Opening tickets to VTEX Support](https://help.vtex.com/en/docs/tutorials/opening-tickets-to-vtex-support)."}