A clinic blog has two kinds of work that should never be tangled together.
The clinician or content team owns the article: title, explanation, image, author, category, references, and the decision to publish. The website design owns the layout: typography, spacing, header, article width, sharing, related posts, comments, and the call to book.
When those are stored together, every article becomes a small web-design project. A new card style means editing old posts. An Arabic article exposes a layout that was only tested in English. One accidental change can make a single post look unlike the rest of the clinic.
The new Smart Clinic blog separates them. Write the content once. Design the blog once. Let every route combine the right content with the shared design.
The complete dated release is on What’s new. The evergreen module page is Website Builder & Blog.
Four templates, not hundreds of pages
Blog home, Single post, Category, and Tag are now protected templates inside the visual builder. They are not ordinary pages to rename or add to navigation. They are the designs used whenever a visitor opens the matching blog route.
The Single post template can include article title and metadata, featured image, rich content, table of contents, author profile, categories and tags, sharing, related articles, previous and next links, approved comments, and a clinic call to action. Change the order, hide what is unnecessary, or restyle the entire composition. The next article needs content — not another layout.
Start with an opinionated design
A blank canvas is flexible, but it is a poor starting point for a busy clinic team. Six presets provide complete designs for all four routes. Choose a direction, preview it with sample content, and then adjust blocks, colour, type, spacing, card treatment, and metadata visibility.
Preview remains useful because it uses the same blog blocks and content shape as the public page. Desktop, tablet, mobile, English, and Arabic are not separate hand-built versions.
Publishing is a workflow, not a status field
Authors can recover a local draft, autosave the full form, add an author or taxonomy without leaving the editor, and open a private preview on the clinic website. Publish, schedule, unpublish, and archive are explicit decisions.
After publication, the article appears through the clinic domain and shared website shell. Category, tag, search, and pagination use the same tenant-owned content. Comments enter moderation before they become public.
Discovery belongs in the page, not a checklist
Each public article can ship with canonical metadata, Open Graph and social previews, BlogPosting structured data, sitemap discovery, and RSS. Preview pages are no-index. Arabic pages use the correct direction and locale-aware dates and numbers.
These are not decorations added after writing. They are part of the rendering path, which means the content team does not have to remember a separate SEO ritual for every article.
The practical result
The clinic can build a recognizable publishing voice without asking an author to become a web designer. The designer can improve every article without opening every article. And the website can grow from a brochure with a booking button into a useful library patients can search, share, and trust.
