A route pattern such as /product/:slug is a rule for your application. Discovery needs concrete URLs such as /product/blue-chair, linked or listed in a sitemap.
Generate URLs from published records
Read the public products from your CMS or database and build their canonical URLs from stable slugs. Exclude draft or restricted records. Use the same slug logic as the page renderer so a product rename does not leave the sitemap pointing at an unintended destination.
Route pattern: /product/:slug
Published URLs:
https://your-site.example/product/blue-chair
https://your-site.example/product/oak-desk
Do not publish /product/:slug as a sitemap entry.Connect the inventory to public navigation
Make categories and important product pages reachable through normal links. Review filters and query-string variants so you are not confusing the list with many versions of the same product. Check one product directly after publishing and another after deleting or redirecting it.
Interpret audit coverage
SiteReadyFor.SI does not enumerate unknown product IDs from a dynamic route pattern. A sitemap provides the concrete URLs it can inspect, subject to its 500-page discovery cap and selected scope. For a large catalog, compare the audited subset with your full inventory before drawing conclusions about every product.