Long URL whitelisted, shortened domain not whitelisted

website-card
cards

#1

My long domain is whitelisted, but my short domain isn’t.

When I use my long domain (http://listentorta.weebly.com/) in the Twitter Card Validator it says, “Card loaded successfully”, and the summary card shows up as normal.

But, when I use my short domain (http://rta.space/) it returns the following:
INFO: Page fetched successfully
INFO: 5 metatags were found
WARN: Not whitelisted

I mainly use Twitter cards for my blog/episode posts and I don’t like using the long domain (http://listentorta.weebly.com/episodes/11-get-it-regret-it) and prefer using my shorter domain (http://rta.space/11/).

I know that Twitter no longer requires summary cards to be whitelisted so does anyone know what’s going on?

This is the HTML I use on my homepage:

This is the HTML I use on my blog/episode posts:

Facts:

  • I use Hover as my domain registrar
  • I use the free version of Weebly to build/host my website.

Any help would be appreciated.


#2
$ curl -A Twitterbot http://rta.space/                                   
<!DOCTYPE html>
<html>
<head>
<meta content='text/html; charset=UTF-8' http-equiv='Content-Type'>
<meta content='width=device-width, initial-scale=1.0' name='viewport'>
<title>Rocket to Anywhere</title>
<meta content='Bi-weekly podcast where brother and sister Corban and Sofia Garcia discuss the headlines (maybe), play games and keep getting off topic.' name='description'>
<meta content='iTunes, podcast, comedy, family, fun, apple, subscribe, entertainment, education' name='keywords'>
<style>
  html {
    overflow: auto;
  }

  html, body, iframe {
    margin: 0px;
    padding: 0px;
    height: 100%;
    border: none;
  }

  iframe {
    display: block;
    width: 100%;
    border: none;
    overflow: auto;
  }
</style>
</head>
<body>
<iframe src='http://listentorta.weebly.com'></iframe>
</body>
</html>

Your short URL does not contain any Twitter cards markup.


#3

How would I add them to my short URL?

(This is my first time working with HTML so I’m not very good at it.)


#4

Well, because you’re loading the whole of the other page into the short domain via an iFrame, this isn’t straightforward (because your container page will never change, so you’ll never have the individual card metadata per page). You’d be better configuring proper redirects from the short domain to the full domain, rather than loading the full domain into a static iFrame - I don’t use weebly and don’t know your domain registrar so wouldn’t be able to advise on how you’d do that properly.


#5

Ok. I set the some of the domains to forward to the long domain instead of masking them. This warn pops-up though. Will this effect the performance of the card?


#6

Looks good to me - should work just fine, I believe.


#7

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