Website-Only Content

Spectacles-Brain · July 25, 2021, 1:22am

Hi, in the ghost editor, if I want to embed HTML content into my article on the webpage, this will not render in the email, leaving an awkward blank space. The Ghost editor has a content block for email-only content, which is great, but is there any way to create website-only content, like HTML embeds, which will appear on the website but not in emails? This would allow emails to look clean and the website post to have all the right stuff.

Any help or input would be appreciated.

v 4.10.1

Bert_O · July 25, 2021, 11:33am

I have this problem and what I am doing at the moment is sending the post out and then adding the html to the post after it has been sent.

Not ideal but it’s a workaround that works for my use case.

BruceInLouisville · July 25, 2021, 12:34pm

Thanks for posting this – was unaware of this problem. (I don’t test-send every newsletter, which I probably ought to do.)

Would be good to have Management change the email template to catch HTML blocks and take them out of the rendering flow.

Spectacles-Brain · July 25, 2021, 5:23pm

That is a good idea. Tough for us, since we schedule posts to send early morning, but I could just wake up early, do that, and go back to sleep I suppose. Thank you!

filipesm · November 2, 2025, 8:42pm

Could I bump this topic and request this feature? It might be relatively easy to implement and would allow for great use cases, like the most obvious one: sending a snippet/excerpt of the post by email, but showing the entire post on the website, without having to publish twice (which is a big burden on some publishing teams). Any change, Ghost team?

I wouldn’t mind collaborating on the development.

github.com/TryGhost/Ghost

ghost/core/core/server/services/koenig/node-renderers/email-renderer.js

main

const {addCreateDocumentOption} = require('../render-utils/add-create-document-option');
const {removeSpaces, removeCodeWrappersFromHelpers, wrapReplacementStrings} = require('../render-utils/replacement-strings');
const {renderEmptyContainer} = require('../render-utils/render-empty-container');

function renderEmailNode(node, options = {}) {
    addCreateDocumentOption(options);
    const document = options.createDocument();

    const html = node.html;

    if (!html || options.target !== 'email') {
        return renderEmptyContainer(document);
    }

    const cleanedHtml = wrapReplacementStrings(removeCodeWrappersFromHelpers(removeSpaces(html),document));

    const element = document.createElement('div');
    element.innerHTML = cleanedHtml;

    // `type: 'inner'` will render only the innerHTML of the element

This file has been truncated. show original

Would it be maybe just duplicating this node (email-only) but inverting it to be website-only?

Cathy_Sarisky · November 2, 2025, 9:39pm

The ability to mark an html card as web-only or email-only went in about a year ago. Please don’t bump 4 year old threads.

If you’d like to start a thread (after searching to see if there is one!) over in the Ideas forum with the idea of sending excerpts, please do! (I think there’s probably already one.)

Topic		Replies	Views
HTML or Markdown in Email Card? Developer help	2	536	August 11, 2023
Only show on web and not in the email Developer help	4	2039	March 4, 2022
HTML in email-only card (CLOSED) Using Ghost	6	523	August 29, 2022
Instagram Embeds - you have to add the HTML? Developer help	2	548	September 22, 2023
Clicking in email re-directs to Youtube, not website - any work around? Using Ghost	25	813	December 21, 2023

Website-Only Content

Related topics