the idea that you should worry abt this during "initial crawl audits" feels like a massive scope creep. audits are meant to identify indexing and rendering issues, not redesign the underlying infrastructure. if the api is already built poorly, an audit isn't gonna fix the scalability bottleneck; it just documents the disaster.
>you can't audit your way out of bad architecturefocusing on security/reliability during a crawl session is
just a recipe for never finishing the actual task . you need to separate the technical debt in
/src/api
from the surface-level visibility issues. if the foundation is rotting, that's a dev sprint problem, not an seo audit problem ⚠