How to Preview a Blog Post in Sparkforge

By Sparkforge Support Team ·Last reviewed May 3, 2026

Open the editor's three-dot menu and click Preview Post to see the live render. Toggle between desktop and mobile views from the top bar. Hyperlinks and videos are clickable in preview, but the back-to-blog button is not.

Preview every blog post on both desktop and mobile before publishing. Layouts that look fine on a 27-inch monitor often break at phone width.

What's visible in preview mode

Featured image from SEO Blog Post settings
Title
Category (if set on publish screen)
Publish date and read time
Full post content
Tags (if set on publish screen)
Author block (if assigned)
Back-to-blog button (visible but not clickable in preview)

Hyperlinks, videos, and author social links are all clickable in preview mode.

How to preview

Open the post in the editor.
Click the three dots in the top-right menu.
Select Preview Post.

Switching between desktop and mobile

Inside preview mode, the top bar has a device toggle. Click it to switch between desktop and mobile renders. Test both before publishing — the Compact layout especially looks different on phones.

What to check on each view

Headings and image scaling on mobile
Tables and code blocks (often the worst at small widths)
Featured image crop
CTA button placement and tap target size
Author block alignment

Frequently Asked Questions

How do I preview a blog post?

Inside the editor, click the three-dot menu in the top right and select Preview Post. The preview opens in a new view with desktop and mobile toggles.

Why doesn't the back-to-blog button work in preview?

Preview mode renders the post but doesn't connect to the live blog list URL. The button works correctly once the post is published.

Can I share the preview link with someone for feedback?

Preview mode is local to the editor. To share with stakeholders, save as draft and have them log in, or publish with a noindex meta to keep search engines out until ready.

What should I check on mobile preview specifically?

Tables, code blocks, image scaling, heading sizes, and CTA tap target size. These are the elements most likely to break or feel cramped at phone width.