[Enhancement] If Keyword contains an ending punctuation like period exclamation point or question mark do not count it as a sentence ending

[Pcosta88]

If my keyword has an ending punctuation, Yoast considers it the ending of a sentence. This can affect the keyword analysis.

1.Have keyword with an ending mark like FRITZ!App WLAN

2.Add it to the first paragraph and see Yoast pick it up

3.But outputs notification that it cannot find it within the same sentence: Keyphrase in introduction:Your keyphrase or its synonyms appear in the first paragraph of the copy, but not within one sentence. Fix that!

Therefore, If Keyword contains an ending punctuation like period exclamation point or question mark do not count it as a sentence ending

This can help improve UX and Content SEO

[Pcosta88]

Please inform the customer of conversation # 496015 when this conversation has been closed.

[Pcosta88]

related Yoast/wordpress-seo#2163

[ansoncraig]

What shoud we do then if my company name has exclamation points in it, and we frequently want to check our content against it.

Does it only affect Yoast's ability to correctly ascertain density and usage, or does it actually affect Google's ability to scan our pages?

thanks!

[Djennez]

It does not affect Google rankings.

For a workaround:
If you are checking for keyphrases with exclamation marks (or any sentence-ending marks for that matter) you can maybe temporary replace the mark for another symbol (one that isn't used), use that for your analysis, and once your text is done and the check passes you can replace that character with your exclamation mark.

[nataliashitova]

A development issue was created for this problem Yoast/javascript#402.

[mmikhan]

Please inform the customer of conversation # 564774 when this conversation has been closed.

[laurasacco]

Please inform the customer of conversation # 608321 when this conversation has been closed.

[Pcosta88]

Please inform the customer of conversation # 626340 when this conversation has been closed.

[jdevalk]

We should move this to the bugreports jira.