-
Notifications
You must be signed in to change notification settings - Fork 367
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SSR support for results pages #673
Comments
This would be great! |
We hear ya. We definitely want to get this done soon. |
Hey @JasonStoltz, is there an update on this? This would be a game-changer when it comes to SEO! |
Hey @janoschsworkspace, we haven't had the time to get to this, but it is definitely on the top of our priority list! |
Hello, I encountered the same issue as described above. Could you please provide an update on the progress of this problem? Thank you! |
Hi there - there hasn't been any progress yet. We have big changes planned soon for Search UI and will share soon. If you need SSR support today, its worth looking into building your own components, using the app-search-javascript client in a SSR framework like next.js. If you're using Elasticsearch directly, another alternative is using searchkit which with instantsearch, supports SSR. |
Is your feature request related to a problem? Please describe.
Kind of. I run a website where I would love for some search results pages to rank in Google. Currently, these pages aren't being indexed by Google, presumably because the content isn't rendered server-side.
Describe the solution you'd like
I'd love to have the option for search results pages to be generated server-side, so that they would be picked up by search engines. I'm using NextJS, so having a way to combine Search UI and Next for SSR would be awesome.
Describe alternatives you've considered
The current alternative as described by @joemcelroy on Slack would be interact with the Search API directly, instead of using Search UI.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: