We can't trust Google Trends to return things exactly as they should be written or pronounced. This is for a number of reasons.
Capitalization of initialisms doesn't always happen where appropriate (e.g. "Espn" and "Nfl" show up frequently, rather than "ESPN" and "NFL"). This breaks the assumption about when to spell-speak these terms.
The apostrophe-S clitic always gets replaced by a space and a capital S. This is unsurprising considering how Google's indexing of terms leaves out punctuation, but it presents a unique challenge.
"Vs" is a special case. It's a common and well known contraction but is processed by RiTa as a semi-silent 'v-z' for not containing vowels.
"Copa América" showed up as a term and predictably, the accented 'e' made it process incorrectly
So some rule changes that could address these would include:
Do an initial RiTa processing of the speakable string. If any syllable has no vowel, has an unpronounceable sequence like 'n-f' or 'p-n', or contains anything that's not a known phoneme rendering, spell it or take other action. Normalize accented characters into non-accented bases.
Assume that "<string> S <string>" sequences are really "<string>'s <string>" and preprocess this to the real word first.
Have a few "known quantities" like the examples above ("Espn", "Nfl", "Vs") and process them at the appropriate steps (known initialisms should be capitalized before making speakable; "Vs" should stay as is but replaced with "versus" in the speakable translation)
We can't trust Google Trends to return things exactly as they should be written or pronounced. This is for a number of reasons.
So some rule changes that could address these would include: