No deep links to key pages

What it detects

Key pages (product, category, checkout entry, account) have no real, directly-loadable URL — navigation depends on prior client-side state.

Why it matters

An agent that reaches a page via search or a citation needs to load it directly, with no prior navigation history; pages that only render correctly after client-side routing break that path entirely.

How to fix

- Directly GET each key page type (product detail, category, checkout entry, account) by URL and check the HTTP status and whether meaningful content is returned, versus a blank SPA shell or an error. - Ensure every key page has a real, shareable URL that server-renders (or statically generates) full content on direct load — replace client-side-only routing (`onclick` handlers, hash-only navigation) with real `<a href="/products/widget-pro">` links backed by server routes. - Fix any deep link that currently 404s, redirects to a generic landing page, or requires prior client-side navigation state to render correctly. - Verify: `curl` a sample of product/category URLs directly (fresh session, no referrer) and confirm HTTP 200 with the expected content, not an empty shell or redirect.

References

• Model Context Protocol specification
• WAI-ARIA 1.2 (W3C)