When I post a link to a page on Facebook the image preview link works fine. But when I post to X it doesn’t retrieve the card. Since X (or twitter at the time) has stopped using card validator it makes even harder to troubleshoot. So I did some digging….
However, these tags don’t come through on the page when loaded. Even when I have cleared the browser cache and reloaded from source. Server-side caching maybe, but regardless it wouldn’t solve the problem of other standalone (non-collection) pages showing twitter cards.
Hey! @**Sailinginhope** Great job digging into this — you’re very close.
You added the meta tags to the blog collection item, but Sitejet doesn’t automatically apply those to the <head> of each individual post. That’s why they’re not appearing when you inspect the final page, and why Twitter isn’t picking them up.
Try this instead:
Open the individual blog post in Sitejet.
Scroll down to the Meta Tags section.
Paste this:
<meta name="twitter:card" content="summary_large_image"> <meta name="twitter:title" content="Turning the Tide: Rock Bottom to Sailing in Hope"> <meta name="twitter:description" content="Join John on a transformative journey from adversity to adventure."> <meta name="twitter:image" content="https://sailinginhope.com/images/0/13586504/SailinginHope.jpg">
Save and publish the post again.
When will it show on X (Twitter)?
Twitter/X caches link previews, so changes may take a few hours — or even up to 24h — to appear correctly.
Since X no longer offers a card validator, here’s what you can do instead:
Tip: Open a new post or reply on X, paste your link, and wait a few seconds.
You’ll usually see a preview card appear right inside the tweet composer — you don’t have to actually post it.
That’s a quick way to test if your meta tags are now working properly.
Saved and published the site. But still not coming through on the page source. I can only assume there is some caching going on between me and the server and only time will tell.
To force X to reload a link preview (since you can no longer flush the x cache in card validator) I just add ?something 1, 2,3 whatever and I think it goes off (after a while!) and re-inspects the link.
Am I correct in saying there is no way to mod the header tags on a regular page?
I will check back later to see if the tag code from the blog post is coming through on the page source.
Yes, in Sitejet you can modify header/meta tags for regular pages using the Page Settings → Meta Tags section — exactly where you’ve placed your Twitter card code. That’s the correct method.
However, if you’ve added the tags and they still don’t show in the page source, it’s very likely due to caching (either on Sitejet’s side or at the edge/CDN level). It sometimes takes a little while for the updates to propagate. Publishing the site again or waiting a bit usually resolves it.
Your workaround using ?something=1 to trigger a refresh on X is clever and exactly what developers do to get around card caching issues!
If the page you’re working on is a blog post, keep in mind that blog templates in Sitejet might not pull in the Meta Tags section from the page settings. In that case, the meta tags may need to be injected in the blog’s template code or CMS settings.
Let me know if it’s a blog post or a regular page, and I can help you narrow it down further.
And you’re most welcome — glad the quick help was useful!
Thanks for bringing this up here. Hopefully, you find a solution. Sadly “X” changed a lot for the worse and its not really a useful platform anymore, but I do recognize that a few people still like to use it.
There is a big medical community on X which represents a large part of my target audience. However, I have concluded that, in my case, the custom meta tags field does not work on collection pages or regular pages. Even after weeks they are still not appearing in the page source.
Would you be able to send a ticket about this with more links and screenshots? Also with a mention of this here? We might need to check on this with a Dev. Maybe we find something. That would be suitable for your case as it might involve sensitive data to help.
Great job digging into this — you’re very close.
When will it show on X (Twitter)?
