Hi! I want to create a public “profile page” for each user. Something like Facebook / Twitter / Airbnb basically any app with a community (with a url like yoururl.com/user-name)
- Preferably this profile page appears in Google (seo)
- A profile page is created when users sign up that users can edit on their own
How do I do this? My understanding is that “static collections” can only be used if data is static and in this case data is not static as users are the ones creating / editing their own profile page. And “dynamic collections” won’t appear in Google…
Is this not possible in Weweb? Pretty sure this is a fairly common / essential use case. 
That’s actually a really common issue for single page application!
Having dynamic pages with good SEO would require Server Side Rendering and we don’t have this feature (yet).
What a social media like twitter or linkedin will do is create a dynamic page and render it server side when requested so you receive a page containing all the data already, including the metadata required to index the page properly and display it nicely when shared.
We already have dynamic page so you can create a path like /profile/username and when the page load you can fetch your data depending of the username found in the path. But we don’t have the server side rendering so the metadata will be common for every profile, common to the profile page, not different depending of the user.
If new users are freely joining your app, this is the way to go and you will have to wait for a new feature allowing you to improve the SEO of these pages.
If your users was mostly static (not the content, but the list of users), like business users you would add one by one for exemple, you would be able to use static collection page and publish again every time you have a new user, so you would pre generate profiles pages for every users (the content of the page can still contain dynamic data, but the existence or not of the page itself will be statically determined). But I understand its not your case.
I’m not an SEO expert, maybe a workaround exist. We have a feature allowing people to import sitemap, maybe its possible to automate something to help but I’m not sure.
Hmm, trying to understand this.
Would binding the metadata to specific user data allow for google to rank these profile pages and treat each user profile page as separate?
So we are able to have pages with a different url, but will these pages be able to rank?