SEO vs dynamic collection problem

Ask us anything
1

Hello!

I have “magazine” feature in my product where there are posts that should be searchable in google and should have good SEO & tags for each post.

These posts will be added by creators daily and edited/fixed often.

To bind post info to metatags I should use static collections otherwise for dynamic collection I cannot pass “post name” to meta tag so my page for each post cannot even have a unique name…

If I make my collection static then it should be published every time my creator does something.

If I work at the same time on some features and my app is published randomly when I haven’t finished I will have crashes and broken features, as I understand the process.

Can you please help to understand how to continuously build project & not publish it all time when new record is added and to have a good SEO?

Now my app looks useless because I cannot setup my SEO :frowning:
And for non developer the collection type topic looks unclear…

Can you help guys to come up with the best solution @aurelie ?

2 Likes
2

Have you found the solution to this?
I am coming across similar issue and I think that many people really need the solution to this.
Any help from Weweb team would be appreciated a lot too!

3

Hey @Jay12 WeWeb team may have a better solution. But a workaround is to use versioning.

You can have multiple versions and merge the versions only when you’re ready to push them live

4

Got it. Thank you!

5

Does anyone have update on dynamic SEO feature that Weweb team is working on?

6

same here + 1

7

same here +1

8

Hi there :wave:

We had a closed beta running for 8 months to test an approach to metadata for dynamic pages. After much back and forth, we decided to stop the closed beta because:

  • it wasn’t being used that much by the beta testers.
  • with competing priorities, we couldn’t find space on our 2024 roadmap for new SEO features.

That said, we realize there are use cases where SEO is paramount (e.g. marketplaces) and have put together a tutorial that shows you how to use Cloudflare as a reverse proxy to have dynamic metadata on the dynamic pages of your WeWeb apps.

Here’s the link to the user documentation on the topic.

It’s a little bit more on the technical side so if you struggle with this, don’t hesitate to create a new topic in the community, sharing screenshots or a video of what you tried, and where you’re stuck.

And if you’re wondering which features WeWeb is prioritizing in 2024, the replay of the live stream in which @Raphael answers a bunch of user questions and presents the roadmap priorities.