Turning a single feature like an AI background remover into a full page cluster is a smart SEO play, especially when you are dealing with heavy Rust-native processing on the backend. I have found that mapping out the internal linking layer early prevents massive refactoring later, as the URL structure dictates how link equity flows to your core tool pages. I ran into a similar routing and SEO structuring challenge when building our Next.js SaaS boilerplate, which eventually led us to bake in a more modular internal linking strategy for PubliFlow. How are you handling the dynamic route generation for the cluster pages without bloating the Next.js build times?
Turning a single feature like an AI background remover into a full page cluster is a smart SEO play, especially when you are dealing with heavy Rust-native processing on the backend. I have found that mapping out the internal linking layer early prevents massive refactoring later, as the URL structure dictates how link equity flows to your core tool pages. I ran into a similar routing and SEO structuring challenge when building our Next.js SaaS boilerplate, which eventually led us to bake in a more modular internal linking strategy for PubliFlow. How are you handling the dynamic route generation for the cluster pages without bloating the Next.js build times?
time of next.js build it is not problem for me, but all my content I keep on DB