Thanks for the help, Andy. The notes on robot.txt and twitter:card tags are both components we can address.
Regarding interactivity, I’m reading:
Do not build end-to-end interactive experiences inside the video or audio player unrelated to Player Card content, such as the following: purchasing, gaming, polling, messaging, and data entry. Instead, build these interactive experiences with our other Card types or enhance your Player Card content with links to your website or mobile application.
Beyond player cards, are there any other card types/solutions you can think of that would allow us keep the hover functionality? We have a library of 10B+ visualizations that we’re trying to make Twitter-friendly.