Page vs Post vs Custom Object — how to choose
How to decide between a Page, a Post, and a Custom Object
SGEN gives you three distinct ways to publish content. Each has its own URL structure, archive behavior, draft handling, and relationship with custom fields. Picking the wrong one creates extra work — a product catalogue built in Blog will fight you at every step; a coffee-origin profile library built in Pages cannot scale to twenty entries without becoming a maintenance burden.
This guide answers the one question you face before clicking Add New anywhere in SGEN: which content type fits this piece of content?
What is this for?
These three content types live side by side in every SGEN site. Each serves a distinct role.
Pages hold evergreen, timeless content that visitors navigate to directly. Your About, Contact, Services, and legal pages all live here. A Page sits at a flat URL you control — /about, /contact, /holiday-gift-guide-2026 — and has no archive of its own. Pages are never grouped by date or category. Visitors find them through your nav or via direct links.
Blog Posts are time-stamped content on a chronological timeline — news, announcements, tutorials, product updates, seasonal stories. Every post lands automatically on the blog archive at /blog/, is grouped into categories, and can collect comments. A post's URL follows the permalink structure you choose in Blog Settings, typically encoding the category and slug: /blog/coffee-origins/apr-2026-ethiopia-yirgacheffe. Posts are built for volume — you expect to add more over time, and older ones age gracefully into the archive.
Custom Object types are structured, repeatable collections. You define a type once — giving it a slug, templates, and a permalink structure — then add as many entries as you like under that type. Each entry gets its own public URL under the type's prefix: /origins/ethiopia-yirgacheffe. Custom Objects are built for shape: every entry shares the same fields, the same URL pattern, and the same SG-Builder template.
The decision tree is short:
- Is the content timeless and standalone — one document at one URL? Page.
- Is it time-stamped and lives on a feed — part of a growing stream of dated stories? Blog Post.
- Is it one entry in a structured collection where every entry has the same fields? Custom Object.
The mock below shows what the SGEN admin sidebar looks like for a site using all three — Pages, Blog, and two Custom Object types registered for a coffee roasting business: