Why does the Twitter card validator issue a warning on 301 redirects?


When we test URLs in the Twitter Card Validator using our own custom shortener service we receive a warning about a 301 redirect. That’s how shorteners work and we were led to believe that using a shortener was OK.


As this is a warning rather than an error, are your cards working anyway, or are you seeing other issues?


This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.