Hey @dr-scott-best,
Thank you for your feedback.
After investigating your website, our team believes that Cloudflare is aggressively caching the page.
Can you check if Cloudflare isn’t aggressively caching your robots.txt file. Can you clear the cache inside Cloudflare and see if that has any effect?
Alternatively, it’s possible that there is a static robots.txt file in the root directory of your website. AIOSEO hooks into the virtual robots.txt file that WordPress generates to rewrite it and add our custom rules, but a physical, static robots.txt file takes precedence over this, which is why the changes you’re making may not have any effect currently.
Can you please check out your root directory using FTP to see if there is a static robots.txt file present there, and remove it if so? Once you’ve done that, the changes you’ve made in AIOSEO should take immediate effect.
With regard to the issue we fixed in 4.4.1 for Divi, this was just a minor bug fix where our TruSEO content analysis was running when Divi’s Wireframe design mode is active.
The reason why the analysis’ score is different between the Divi visual builder and the regular Block Editor is because our algorithm isn’t able to properly get the final content of the post inside the Block Editor if you’re using a page builder plugin like Divi.
This is a technical limitation due to how page builders generate the post content that we unfortunately cannot work around currently. We recommend you to only rely on the TruSEO score inside the visual builder.
I believe that you also reached out to us via e-mail so I’ll respond to you there as well, but feel free to let me know here if you have any other questions.