NO BUG: Sharing on Whatsapp of a page rendered with Bricks but with non-empty post_content

Bugs
1

Browser: Chrome 110
OS: macOS .
URL: Link to a page that illustrates this issue
Bricks version: 2.3.5

On one of the sites I have developed with Bricks there are pages with content in the post_content (i.a. wp-content rendered with Bricks templates) and others with content created with Bricks. On the latter pages I have included a hint to my clients in the post_content to inform them that they need to use Bricks to edit the content. These pages are rendered with Bricks and in the browser this works perfectly fine, and it is the Bricks content which is shown.

Problem is when you attempt to share such a page, e.g. What to do – arild.se on Whatsapp. Whatsapp only sees the wp_content, not the “real” Bricks content.

Could possibly be related to Javascript if “Render with Bricks”/”Render with Wordpress” is handled in Javascript??

3

Hi Christer,
Thanks so much for your report!

This is expected for the setup described. WhatsApp builds the preview from the page’s Open Graph/meta description, not from the visual page content after it renders in the browser.

Well, you basically just wrote it into the meta description, but WhatsApp seems smart enough to ignore it, as it doesn’t bring any value.

CleanShot 2026-07-03 at 08.31.32@2x
CleanShot 2026-07-03 at 08.31.32@2x1158×282 99.2 KB

Also, there are some other things that might cause this:

  • <meta name='robots' content='noindex, nofollow' /> – should probably be removed
  • Replace the meta description with real copy and keep it as short as possible
  • Use a proper 1200x630 preview image

Also, once you changed the mentioned points, add a random parameter to the URL to force WhatsApp to reindex the page, as otherwise, you might get a cached result:

https://arild.se/welcome-to-arild/what-to-do?test123

If you share any page from bricksbuilder.io, e.g. https://bricksbuilder.io/builder/, you can see that it works, right? All of these pages are built and rendered with Bricks.

4

Hi Timmse,

Thanks a lot for looking into this and giving excellent feedback! It was Wordpress’ generation of og:description that messed things up. I installed Slim SEO which I often use, and fixed the descriptions. The ‘noindex’ was on purpose until the site is finished. I hadn’t thought about the preview image, but I’ll look into that. Good idea!

6

Okay, cool :slight_smile: I’ll consider the issue as resolved :v: