VellumUp
PricingBlogIntegrationsComponents
Sign inRegister
Back to components

On this page

All components

Backend

Webhook receiver for Next.jsWebhook receiver without a server - Edge Function

Full Examples

Full Article Page

Blog Layouts

Blog Post LayoutBlog Post Layout - MinimalBlog Post Layout - Sidebar Meta

Blog Sections

Blog SectionBlog Section - EditorialBlog Section - Minimal RowsBlog Section - Simple

Navigation

Table of ContentsTable of Contents - FloatingTable of Contents - InlineTable of Contents - Pill

Cards

CardCard - MagazineCard - BareCard - Frame

Key Takeaways

Key Takeaways - BoxedKey Takeaways - CardKey Takeaways - Numbered
Back to components

Blog Layouts

Blog Post Layout

A complete, ready-to-use blog article page — hero image, title, byline, and article body

Preview

The Real Cost of Not Publishing SEO Content Consistently

The Real Cost of Not Publishing SEO Content Consistently

VellumUpVellumUpMay 28, 20266 min read

Most teams don't lose organic traffic overnight — it erodes quietly, one skipped week at a time. Search engines reward the sites that keep showing up, and punish the ones that don't.

Why consistency compounds

Every published article is a small bet on relevance. Skip a month, and competitors who kept publishing quietly absorb the rankings you left on the table. Search engines crawl and re-evaluate sites on a rolling basis, and a site that publishes nothing for weeks starts to look inactive.

The sites that win long-term aren't the ones that publish the single best article — they're the ones that never stop showing up.

The fix isn't writing more

It's writing on a schedule you can actually keep. A realistic cadence — even one solid article every two weeks — beats an ambitious plan that collapses after a month.

Consistency is a system problem, not a talent problem — and the fastest way to solve it is to lower the weekly bar until the schedule feels easy to keep.

Ready to use — just copy it in

See how to use it on your page, then copy the component file itself.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20

Props

PropTypeDefaultDescription
titlestring—Article title, shown as the page heading
coverImagestring | nullnullCover image URL — hero image at the top of the page, hidden entirely if omitted
coverImageAltstring | nullnullAlt text for the cover image - falls back to the title if omitted
authorNamestring"Editorial Team"Author name, shown in the byline
authorAvatarstring | nullnullAuthor avatar URL — shows a colored initial badge if missing
publishedAtstring—ISO 8601 publish date, shown formatted in the byline
readingTimeMinutesnumberundefinedEstimated reading time in minutes — hidden if omitted
accentColorstring"#4A68E5"Accent color for the author badge, links, and blockquote border
contentstringundefinedMarkdown article body (e.g. VellumUp's webhook content field) — rendered internally via react-markdown. Use this or children, not both.
childrenReact.ReactNodeundefinedPre-rendered article body — JSX or raw HTML, for when you already have rendered output instead of raw Markdown

Making it fully SEO/GEO-ready

The hero image is likely your Largest Contentful Paint element, so its loading strategy matters more here than in the other two layouts. Add structured data so search engines and AI answer engines understand the page as an article.

The full-width hero image is almost always the Largest Contentful Paint (LCP) element on this layout, and LCP is one of Google's three Core Web Vitals — a slow-loading hero image is the single most common reason a page like this scores poorly. The component itself uses a plain <img> tag rather than next/image so it works outside Next.js too — if you are on Next.js, swapping in next/image with priority set is worth doing specifically for this layout, so the hero image is requested immediately instead of waiting behind other page resources.

The layout above covers the visible SEO signals (semantic <article>/<h1>/<time>, alt text, page metadata). For search engines and AI answer engines to fully understand the page as an article — author, publish date, image — add Article structured data (JSON-LD) in the page file that renders it:

page.tsx
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30

Writing articles with code blocks? Add syntax highlighting to the content renderer inside BlogPostLayout.tsx — most SEO articles don't need this, so it's left out by default:

BlogPostLayout.tsx
1
2
3
4
5
6
7

Dependencies

react-markdownremark-gfm

Want SEO content
without the effort?

Try it risk-free — a content plan, keyword research, and up to 5 articles on us.

Say hello

support@vellumup.com

Follow us

Product

PricingFree ToolsShopify App StoreWix App MarketWordPress Pluginnpx vellumup-init

Company

BlogIntegrationsComponentsAffiliates

Integrations

DocumentationWordPressShopifyWebflowWixWebhooksNext.js

Legal

Terms of ServicePrivacy PolicyAccessibility
VellumUp

© 2026 VellumUp. All rights reserved.