Hello, unfortunately I have some seo problems with weweb.
Google can’t see my H1, H2 etc. marked as html tag. In addition, my loading speed is super bad which is of course not good for SEO and I have tried to create the dynamic meta data with this guide Dynamic page metadata | WeWeb Documentation and I’m honest, I just can’t get any further. I don’t even know at which step I failed. Here is a page of my online marketplace, where dynamic meta data should actually be displayed: example dynamic page
Can someone explain this to me for complete low coders or maybe know a video tutorial or have time for a short call?
I would be really grateful! <3
Hey @luisamariee,
I’m unfortunate to tell you that weweb’s production has a lot of trouble handling seo, as you can see in a discussion we had in the past with weweb team: Understanding weweb seo limitations - Ask us anything - WeWeb Community.
There are solutions that help you overcome it, but I will recommend you to maybe think about transferring to another platform if your main focus is a marketplace with MUST NEED SEO, if you also want to have also another layer of dashboards and automation etc, maybe you can migrate both solutions.
Hi @tomerer2000, thanks for your quick feedback, I’m honest I only switched to Weweb 3 months ago because of the good options for marketplaces and I’m satisfied in this regard, but it is absolutely incomprehensible to me how it can be that not even my H1 is readable by google. Congratulations, I may have the most beautiful website in the world, but in the end it doesn’t matter if nobody can find it. 
Is there a solution @weweb-team ? 
1 Like
I know it’s pretty crazy that they let people build on their platform for months, only to discover their app will be broken at the last hurdle of SEO. However, it might be easier to migrate it to platforms like WordPress, Shopify, or other more marketplace-oriented solutions.
I really like Weweb for my use case, but some functionalities are currently broken
Literally every post in all the years here says WeWeb shouldn’t be used for sites that are supposed to load fast and be SEO friendly. You can’t really blame WeWeb for your lack of research 
I think when you have a lot of guids when you build matketplace interface and you aim for the whole market without saying anything about your limitations, you cant really say oh people talk about in the forum so they need to know. And i guarantee there are plenty of people that in this moments building marketplaces on the platform.
And as i said i really enjoy working with weweb and they are building something spacial but still it has some stuff that will waste a lot of time for some people.
2 Likes
well, a marketplace also has to be found, so i wouldn’t say that the research explicitly shows that seo is simply not properly optimizable. Also, according to my research, it used to be “easier” to insert dynamic meta data. And yes, it works somehow, but to be honest, it’s just too complex for weweb, which is aimed at low coders.
What I really don’t understand, however, is why the html tags aren’t marked as H1, H2,… if you can set them as such. I haven’t found anything about this yet 
I find it especially surprising that the issue with WeWeb has been known for so long and yet there seems to be no update. I understand that it might be complex to develop, but before I invest all my energy into a rather limited AI, I would focus on getting the basics right. I hope that every comment helps steer the WeWeb team toward focusing on the truly important topics.
Hey there 
Totally hear you on SEO limitations in WeWeb having been a known concern for a while, especially around structured headings and metadata on pages with dynamic collections. We’ve tried to be upfront about this in our docs and product scope, but I get how frustrating it can be if you’re hitting a wall while building.
A couple of options that might help in the meantime:
- If you have fewer than 10,000 items, using static collections could work. That way, you get native support for dynamic titles, metadata, and Open Graph. The downside is that, when you have an update, you have to refetch the collection manually and republish the app.
- If you’ve got more than 10,000 items, the Cloudflare caching trick is a legit workaround. Many users have set it up successfully. It is quite technical though and we do need to update our docs on the topic to provide you with a genuinely helpful solution!
Now, neither solution is ideal so we are planning to add SSR (server-side rendering) at some point. Unfortunately, we don’t have an ETA for that yet because there are a couple of big topics we need to prioritize first and it’s hard to predict how much time those will take.
I know the AI features have been the most visible updates lately, but I can assure you that there’s a lot of non-AI related work going on behind the scenes to significantly improve other parts of the building experience in WeWeb.
Some things do take longer than we’d like but we’re definitely not standing still, and we really appreciate your feedback. Keep it coming!
4 Likes
Thanks for the feedback, I can understand that you are not the only one to blame and I don’t want to get personal. It’s just that my marketplace is so difficult to find and in retrospect I wouldn’t choose weweb again for this reason. I can only emphasize again that a sensible solution is very important, I have over 2k products and also no capacity and skills to simply implement the Cloudflare variant.
Hi @luisamariee 
With 2k products, the static collection workaround would work for you. It is a bit annoying because you’ll need to resync the collection and republish the app when there’s a chance but it’s more straightforward than setting up the Cloudflare worker.
Would you like me to record a video showing how to setup metadata for static collections in WeWeb?
EDIT: I just remembered that with Supabase, static collections are not available 
What backend are you using?
Interesting, has this changed?
1 Like
Hey Broberto,
Ah no, that’s a great point! That hasn’t changed. My understanding is that, on first load, the metadata will not be seen by the bots. It will take a second crawl for them to read the title, meta, and content.
Before we removed the pre-rendering, the metadata and content of static collections had the benefit of being pre-rendered (so the bots didn’t need a second visit to index the content). Now the only advantage of static collections is that you can bind dynamic metadata and save the hassle of the Cloudflare workaround. That said, the Cloudflare workaround allows you to render the metadata on first load so it is a superior solution.
Does that make sense?
I’m very confused right now, I’ll describe my case again in detail, because I don’t know myself whether this option is an option for me.
I use Supabase as my backend. The products on my marketplace are updated regularly and new ones are added. i sell unique items, each product can only be sold once.
What does the following mean for me?
- Static collections are no longer pre-rendered
- on first load, the metadata will not be seen by the bots
Hey Luis, if you use Supabase, the static collections trick is not an option for you unfortunately You’ll need to setup dynamic metadata externally, using a Cloudflare worker for example.
If you use Supabase and want to benefit from the static collections, you can simply use the REST API plugin to fetch the data for your content and set the collection to static.
How do I use the REST API plugin with supabase and what are the advantages of the static collection other than it being simpler. Could you maybe make me a pro contra list or something, I’m really low/ no coder