What if they don&#x27;t actually &quot;render&quot; the dom as part of the &quot;load&quot; analysis... this means they don&#x27;t necessarily need to handle certain UI&#x2F;UX aspects that can be bypassed.. they could then output the &quot;rendered&quot; content for passthrough to the same system that does their general crawl analysis for additional details.<p>The work could be broken up in any number of ways... from my own testing, and experience with others testing.  Content crawls&#x2F;recrawls from JS data tends to lag a couple days behind initial scan... having an updating sitemap xml resource is a good idea for &quot;new&quot; content if you&#x27;re doing JS based content.. also, rescans will still lag well behind the general non-js content scans...