Why you can't have a site map on Vepple

The Site Map is a valid request. However, given the personalised nature of Vepple, we can't generate a sitemap in the traditional sense because pages exist conditionally based on the applied dynamic filters. For example, your funding for your studies page exists for some audiences but not others. If this was crawled by a bot, it would likely error out because the correct personalisations aren't present in order to serve content. Likewise, the same page can link to different pages depending on the personalisations applied.

It is important to note that every time you change content i.e. adding or removing, the URLs will change. How is this done? As shown below, the paths follow the structure below. With whatever is in the curly brackets being dynamic/changing. The number of URLS could be thousands with every change. There is also no guarantee that the content will reflect since it is dependent on the filters applied.

• /explore/{section/subject}/
• /explore/{section/subject}/{post/group/guided-tour}
• /map/{all/post/group/event}
• /map/{all/post/group/event}/content
• /user/favourites
• /user/events
• /user/profile
• /events/all
• /events/all/{event} 

That is why generating a site map is almost impractical on the platform.