How this blog is built, and why it renders on the server
A short tour of the publishing setup behind the Tropika Labs blog — how posts are written, how the SEO fields work, and the one architectural decision that keeps link previews from silently breaking.
15 August 2026 · 1 min read · Umer
Every technical decision on this site was made to serve one thing: pages that load fast and describe themselves accurately to the machines that index them. The blog is built the same way.
Why the pages are rendered on the server
A blog that fetches its content in the browser looks identical to a human visitor. It is not identical to a link preview scraper.
LinkedIn, WhatsApp and X do not run JavaScript when they build a preview card. Anything written into the page by a script is invisible to them — which is covered further in our answers section.
What the editor gives you
- Headings, bold and italic, links, lists, quotes, inline code and images with alt text.
- Separate meta and social fields, each falling back to the post content when left blank.
- A published date that can be set in the future to schedule a post.
A note on headings
The post title is already the page heading. Inside the body, start at Heading 2 — the structure then reads correctly to screen readers and to search engines.
curl -s https://www.tropikalabs.com/blog/hello-world \
| grep -E 'og:title|og:description|og:image'Write the post first. Fill in the SEO panel second. They are different jobs.