Last post 5 hours 55 min ago

Posts last week 89

Average response time last week 30 min

All time posts 67735

All time tickets 10467

All time avg. posts per day 21

Helpdesk is open from Monday through Friday CET

Please create an (free) account to post any question in the support area.

Please check the development versions area. Look at the changelog, maybe your specific problem has been resolved already!

All tickets are private and they cannot be viewed by anyone. We have made public only a few tickets that we found helpful, after removing private information from them.

#5865 – Twitter Card Image url path

Posted in ‘sh404SEF’

This is a public ticket. Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.

Saturday, 22 June 2019 13:27 UTC

theralphuwe

I have noticed that my Twitter card image meta tags do not include the full URL but a shortened version. See source code below:

<meta name=twitter:image content=//static.xxxx.org/images/2019/06/13/threeviewsiranx840.jpg />

Here is the page that the source code above appears in: https://www.xxxx.org/frcw

This is causing the images to not appear in Twitter. I did some research at Stack Overflow and was told the source code should include the entire url.

https://stackoverflow.com/questions/49738722/twitter-card-image-not-working-despite-meta-tags

I am sure I must have played with some setting somewhere to make sh404SEF remove the https://www.xxxx.org part of the url.

Let me know what you think might fix this issue.

Best,
Ralph-Uwe

Monday, 24 June 2019 09:30 UTC

wb_weeblr

have noticed that my Twitter card image meta tags do not include the full URL but a shortened version

THis is not a shortened version. It's a fully URL but one that accept either the HTTP or HTTPS version of your site. I'm not sure why you use this syntax for your images, you probably should use the direct link using HTTPS.

I did some research at Stack Overflow and was told the source code should include the entire url.

That SO thread is about a different situation, where the site uses a relative URL, ie

<meta name=twitter:image content=images/2019/06/13/threeviewsiranx840.jpg />

sh404SEF would never create such meta tags. We create Twitter card tags based on the image we find inside your page (unless you manually override that). If you use relative URLs in the images on your site, we would be able to fix them automatically. For instance, if you had an image such as:

<img src="/images/2019/06/13/threeviewsiranx840.jpg">

we would create this Twitter Card:

<meta name=twitter:image content=https://www.xxxx.org/images/2019/06/13/threeviewsiranx840.jpg />

and Twitter would be happy.

However, you are using images such as:

<img src="//static.xxxx.org/images/2019/06/13/threeviewsiranx840.jpg">

And we cannot fix them automatically because they are on another domain: sh404SEF does not know whether static.xxxx.org is accessed through HTTPS or HTTP so it cannot complete the URL and make it fully qualified.

The fix is to stop using those links, /static.xxxx.org/xxxxx and instead use normal links as in: https:/static.xxxx.org/xxxx

Best regards

Tuesday, 09 July 2019 05:34 UTC

system

This ticket has been automatically closed. All tickets which have been inactive for a long time are automatically closed. If you believe that this ticket was closed in error, please contact us.

This ticket is closed, therefore read-only. You can no longer reply to it. If you need to provide more information, please open a new ticket and mention this ticket's number.