Join the Webstudio community

Updated 2 months ago

Handling large sitemaps in webstudio

At a glance

The community members are discussing the use of large sitemaps in Webstudio. They have heard that sitemaps should not exceed 50,000 URLs, and that they need to be split when they do. The community members are curious about the resource intensity of making an API call to fetch 50,000 items for the sitemap, particularly when doing this from a self-hosted Baserow. The comments suggest that there are two separate issues to consider: whether Google likes large sitemaps, and the performance implications. Some community members suggest simulating the scenario to measure the impact, and note that 50,000 links may only be 5-10KB of data, which is not a lot.

Does anyone have some experience with large sitemaps in Webstudio? I've heard that they shouldn't exceed 50k URLs. When that happens they need to be split is what I've read. I'm curious if making an API call to fetch 50k items for the sitemap is something resource intensive, doing this from a selfhosted baserow for instance.
O
R
5 comments
There are 2 separate issues here:
  1. if google likes the fact that you got 50k urls in one sitemap
  2. performance
  1. I don't know, need to search some expert opinions on this
  1. it could be fine, but depends on the backend, I would simulate this and measure
in the end 50k links is probably 5-10kb of data, which isn't a lot
Thanks, I'll do some simulation to verify
Add a reply
Sign up and join the conversation on Discord