Suggestions for Enhancing Sitemap Generation Features

·Jan 15, 2025 05:29 PM

Are there any plans to add the ability to generate your sitemap in a more granular format? This would be a huge addition. things like being able to generate your sitemap incrementally across multiple prompts (e.g. one page group at a time instead of the whole site), or adding your open LLM API key to allow for a higher quality output or more extensive output with more pages?

5 comments

· Sorted by Oldest

Matt J.
·
Madison S. hmm yeah this is interesting, I dont know that there are any immediate plans right now, no. But we should add this to the backlog of ideas. One thing to keep in mind is that we do have page level prompts as well. So in theory, you could do some of what you are referring to, today.
Madison S.
·
I appreciate the reply and unfortunately it is still quite limited context. Take for example, the 3000 character limit in the global sitemap prompt, and the 500 character limit in each page prompt. Across a 30 page site that is 18,000 total characters, or around 4k tokens we can prompt with. o1-mini can output 64k, and most other top-tier models can output at least 16k. The sitemap prompt only needs to be maybe 4,000-5,000 characters. 3,000 feels just a hair too small when you’re using it for a professional workflow and need specific details implemented, since those details take a lot of space. The page prompts are the more limiting factor. 500 characters per page prompt is pretty low, I barely have enough room to describe what the page copy is supposed to say before it cuts me off. I guess the best way to get around that right now is to generate a different sitemap for each page group? Haven’t tried it yet but I’ll see how it works.
Matt J.
·
I guess another way would be to see what kind of output you get from 100 characters, versus the full 500. Are you seeing a dramatic difference in the results? As far as I know, our team has done hours upon hours of testing. Its basically all we do internally - we breathe AI...we're even convinced Jonathan N. might even be one....so from our testing, we didn't notice dramatically different results by providing more information. But you could see different results by providing less info that is more specific. I am also guessing that those limits are imposed by us directly, not because of any integration we have. Maybe there is an opportunity to increase the character limits on both the sitemap prompt and page prompts. But again, what kind of ROI are you getting from making sure you have a 16k character prompt versus a 400?
😂1
Madison S.
·
It is mainly for static site generation capabilities. As an example, if I have to make 20-25 (however many is too many to do by hand manually without it being a time sink) service pages for a website, I can set up the Webflow CMS, or another CMS, add framework specific props and go through the hassle of generating them. Or, I can just go in Relume and an outline of my copy and tell it to fill it in, basically replacing a CMS for all of that stuff.
Matt J.
·
yeah got it

Suggestions for Enhancing Sitemap Generation Features | Relume Community

Matt J.
·
Madison S. hmm yeah this is interesting, I dont know that there are any immediate plans right now, no. But we should add this to the backlog of ideas. One thing to keep in mind is that we do have page level prompts as well. So in theory, you could do some of what you are referring to, today.
Madison S.
·
I appreciate the reply and unfortunately it is still quite limited context. Take for example, the 3000 character limit in the global sitemap prompt, and the 500 character limit in each page prompt. Across a 30 page site that is 18,000 total characters, or around 4k tokens we can prompt with. o1-mini can output 64k, and most other top-tier models can output at least 16k. The sitemap prompt only needs to be maybe 4,000-5,000 characters. 3,000 feels just a hair too small when you’re using it for a professional workflow and need specific details implemented, since those details take a lot of space. The page prompts are the more limiting factor. 500 characters per page prompt is pretty low, I barely have enough room to describe what the page copy is supposed to say before it cuts me off. I guess the best way to get around that right now is to generate a different sitemap for each page group? Haven’t tried it yet but I’ll see how it works.
Matt J.
·
I guess another way would be to see what kind of output you get from 100 characters, versus the full 500. Are you seeing a dramatic difference in the results? As far as I know, our team has done hours upon hours of testing. Its basically all we do internally - we breathe AI...we're even convinced Jonathan N. might even be one....so from our testing, we didn't notice dramatically different results by providing more information. But you could see different results by providing less info that is more specific. I am also guessing that those limits are imposed by us directly, not because of any integration we have. Maybe there is an opportunity to increase the character limits on both the sitemap prompt and page prompts. But again, what kind of ROI are you getting from making sure you have a 16k character prompt versus a 400?
😂1
Madison S.
·
It is mainly for static site generation capabilities. As an example, if I have to make 20-25 (however many is too many to do by hand manually without it being a time sink) service pages for a website, I can set up the Webflow CMS, or another CMS, add framework specific props and go through the hassle of generating them. Or, I can just go in Relume and an outline of my copy and tell it to fill it in, basically replacing a CMS for all of that stuff.
Matt J.
·
yeah got it