Sanity cutover smoke test
A throwaway post that exercises every custom block so the Sanity blog can be verified end to end on staging.
This post exists to verify the Sanity cutover end to end. If you can read this sentence in the page source without JavaScript running, server-side rendering works.
Every custom block, once
Below is one of each block type defined in studio/schemaTypes/blocks, so a single page proves the whole renderer.
Callout block
If this renders as a styled aside rather than plain text, the callout component is wired correctly.
Comparison table
| Capability | Before (Outrank) | After (Sanity) |
|---|---|---|
| Source of truth | 4 places | 1 place |
| Renderer | 2 (string + React) | 1 (React) |
| Edit a redirect | Requires deploy | Edit in Studio |
| Sitemap lastmod | publishedAt (stale) | _updatedAt (accurate) |
A link back to the blog index
This is an internal link — it should render without target=_blank.
curl -s https://whisper-ai-staging.replit.app/blog/sanity-cutover-smoke-test | grep -c "<h1"Frequently asked questions
Does this post prove SSR is working?
Yes. curl does not execute JavaScript, so if the body appears in the raw HTML response, the server rendered it.
Why does the FAQ block matter?
FAQ blocks are structured content, so they emit FAQPage JSON-LD as well as visible markup. A raw HTML blob could not do that.
WhisperAI Team
Product