Title: Content Analysis- BUG
Last modified: July 10, 2019

---

# Content Analysis- BUG

 *  [donkeysticks](https://wordpress.org/support/users/donkeysticks/)
 * (@donkeysticks)
 * [6 years, 11 months ago](https://wordpress.org/support/topic/content-analysis-bug-2/)
 * When my keywords are not capitalized the same way as my H1/H2 content then the
   Content Analysis tells me “None of your target keywords were found in Heading
   2 (H2)”

Viewing 2 replies - 1 through 2 (of 2 total)

 *  Plugin Author [Benjamin Denis](https://wordpress.org/support/users/rainbowgeek/)
 * (@rainbowgeek)
 * [6 years, 11 months ago](https://wordpress.org/support/topic/content-analysis-bug-2/#post-11721075)
 * Hi,
    can you copy and paste the target keywords field please? Can you share the
   URL of your site?
 * Thank you!
 *  Thread Starter [donkeysticks](https://wordpress.org/support/users/donkeysticks/)
 * (@donkeysticks)
 * [6 years, 11 months ago](https://wordpress.org/support/topic/content-analysis-bug-2/#post-11733260)
 * TESLA ACCESSORIES, APPAREL
 * [https://teslaries.com](https://teslaries.com)
 * It looks like the problem only persists on multiple word keywords.

Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘Content Analysis- BUG’ is closed to new replies.

 * ![](https://ps.w.org/wp-seopress/assets/icon-128x128.gif?rev=3158903)
 * [SEOPress - AI SEO Plugin & On-site SEO](https://wordpress.org/plugins/wp-seopress/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/wp-seopress/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/wp-seopress/)
 * [Active Topics](https://wordpress.org/support/plugin/wp-seopress/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/wp-seopress/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/wp-seopress/reviews/)

 * 2 replies
 * 2 participants
 * Last reply from: [donkeysticks](https://wordpress.org/support/users/donkeysticks/)
 * Last activity: [6 years, 11 months ago](https://wordpress.org/support/topic/content-analysis-bug-2/#post-11733260)
 * Status: not resolved