Hey @nlwebdesign,
We understand your concern and your reaction but Paul’s response is correct. Yoast SEO only analyzes WordPress content and it does not read the frontend like Google or any website crawler does. Yoast SEO is not a crawler. It can’t read your the content of your widgets nor it can see your logo and menus. It only provides insights for your post or page content.
Also, no one can conclude that the drop in your search engine rankings was caused by our theme because no knows Google’s ranking algorithm including content analyzers like Yoast SEO. Google only provides best practices which our theme follows. By follow, I’m referring to frontend code and not the backend which Google can’t see. The backend WordPress content which in Cornerstone’s case, is what Yoast SEO sees but can’t read. Please note that they are different.
Also, SEO has 2 facets as far as I know. They are On-Page and Off-Page. A theme only touches a part of On-Page SEO.
In case you’re not aware, the best thing that you can do is look at the data of Google’s Search Console. That will give you at least an idea of what Google is detecting. This however is not covered by our support. Please consult with an SEO expert to assist you with this.
By the way, Ruenel and Paul was referring to a bug in Cornerstone where Yoast SEO’s content analyzer does not work well if you have a combination of Classic and V2 (non-Classic) elements in a page. Please try using All Classic or All V2 only. The issue could be in Yoast SEO’s API. We are not sure about this yet.
With that said, please don’t treat Ruenel’s reply as a guarantee. Surely, our developers are working on bugs and improvements. But, we can’t provide an ETA nor guarantee it would be fixed in the next release. I understand that it seems not acceptable but there might be technical barriers that both sides are facing.
Thank you for understanding.