Hi all, Seeking more detailed understanding of the SEO issues commonly discussed for WeWeb apps. My main goal is to improve Google visibility, and I’m wishing to add a blog ro my app soon. What are the core SEO problems within WeWeb that I need to be most concerned about for a blog and general site visibility, and what are the most effective strategies or workarounds you’ve found to tackle them? Appreciate any guidance!
Hi Tomerer, I’ll see if our team has a good answer for this one.
1 Like
Hi @tomerer2000
WeWeb is built primarily for single-page applications that run behind a login—blogs and public content sites aren’t the main focus for now. That said, we’re in the process of exploring server-side rendering support to cover more use cases, though we don’t yet have an ETA. In the meantime, you can improve your app’s search-engine visibility by following our SEO recommendations here: Frequently Asked Questions | Documentation
I’d also check https://prerender.io/
2 Likes
Hey Daniel and Agustin,
Thanks for the response, I understand that there is a thing static collection that can help with the website SEO performance, if you have any suggestions about it and how to implement it in general it would be fantastic.
Either way, thanks a lot for the help.
Static collections are no longer pre-rendered. Pre-rendering has been removed to improve deployments. They don’t offer many SEO benefits compared to dynamic collections anymore.
Got it, i will try to do what you recommend while also waiting for the server_side rending :]
1 Like
Hey daniel, im a lil bit confused i joined a session of office hours, and flo and matthew did recommended to use static collections for better seo, but you said it’s not relevent.
It’s a bit easier to add metadata to them, but they are no longer pre-rendered, which is one of the main reasons why our users used them for SEO in the past.
So tell me if im understanding it now, in the past having a static collection would have make the content “static” and therfore easier for google crawles to index it, now it’s not working like that any more, but what is left static is the metadata which is better thn nothing but not perfect and therfore i should use other products for contect rendering.
1 Like
But how about custom Metadata for each page (bind from collection)? With dynamic collection it’s not possible, only with Static collection + Static collection page. i’m right?
Fwiw, do not use WeWeb for your entire website if you need SEO performance. In fact don’t use any SPA if you need SEO impact from those pages. Even if you can prerender most of the required elements there can still be so many issues. I highly recommend using a server side rendered tech stack like Wordpress/PHP for “SEO” pages and using WeWeb on a subdomain, e.g. app.example.com.
2 Likes
Hello Daniel,
This is a regression on previous WeWeb versions, as SSR was an available option when the website was published and built.
It seems that this option was removed to improve building time at the cost of SEO. Even though the guidelines provided in the FAQ are good, they are clearly not enough for SEO centric websites.
Is there any plan to bring back this feature that was part of WeWeb before ?
From what Weweb’s team said it sounds like it’s going to take a few months at the least and maybe even more. so if you have a marketplace or any other heavy SEO platform, Weweb doesn’t sound like the best option. Only if your core app is not SEO dependent, you can use weweb for it and then other products for the SEO needed pages.
1 Like
I understand but except that, that was not the case a year or so ago when my project started. The static generation was possible and allowed proper SEO optimization, other than the technical limitations due to WeWeb technical stack.
The static part of WeWeb is getting more and more tedious, and for me, it’s a bit of a pity because at that time it was the best hybrid solution on the market.
That is typically my issue here, and where I see that others are facing the same problems.