Let's say I have a SPA with Server Side Rendering. Some pages show a list of items and offer a filtering facility. When the user selects some options or fills in some input field to filter the list, I'd like to embed this information in the URL (eg.
/items?sort=price&order=desc&q=something) via the history API (client side routing). Behind the scene, an API call is made to get the results.
Since I do SSR, the server will also be able to understand these URLs and render these pages (hence the user can bookmark the page or share it). But nowhere in the HTML pages these URLs will appear, there are only generated client side in response to user events.
Am I wrong ?
(I guess if someone shares publicly that kind of URL, it could suffice to make this page crawled ? In any case, what I'm worried about is the cost on the crawling budget if all these pages are visited, but I'm ok with a few pages being crawled, they could be marked as "noindex" for instance).