Dynamic pages

From a list, Obelisk automatically creates a separate page for every item, each with its own web address.

Example: every item gets its own page

Give every event its own detail page under /agenda/.

Why dynamic pages help your SEO

Every generated page gets its own URL, its own title and its own content — exactly what search engines need to index each item separately, which directly supports your SEO. A list of fifty products becomes fifty indexable pages instead of one crowded overview.

Dynamic pages are generated straight from your data type: add a new item to the list and its page appears automatically, with no separate step needed to publish it.

A common use case: an events calendar where every event gets a shareable link people can send directly, instead of pointing them to a long overview page and asking them to scroll.

Practical tip: if you ever rename a slug or remove an item, set up a redirect to the new page so old links and search rankings don't break.

What belongs on a template versus what belongs per item

A dynamic page template works best when it separates what stays the same from what changes per item. The layout, the navigation, the surrounding branding — that all belongs in the template. The title, the description, the photo, the price — that belongs on the record. Mixing the two, for example hardcoding one item's details into the template "just for now," defeats the purpose and usually needs to be undone later.

A related decision is how much detail a single template can reasonably hold. A product with only a name and a price needs a much simpler template than a product with variants, a gallery and related items — trying to force every case into one rigid layout usually means the simple products look over-designed and the complex ones feel cramped.

Dynamic pages across different kinds of content

A recipe site generates one page per recipe from a single template, each with its own photo, ingredient list and method. A real-estate site generates one page per listing, each with its own gallery and floor plan. A documentation site generates one page per article from the same layout, with a consistent sidebar generated from the table of contents block so long articles stay navigable.

In every one of these cases, the number of items can grow into the hundreds without anyone building pages by hand — new listings, new recipes or new articles simply appear as records are added.

Common pitfalls with generated pages

The most common pitfall is forgetting that each generated page still needs a distinct title and description for search engines, not a generic one copied across every item — see SEO titles and meta descriptions for how to make each page distinguishable in search results even when they share a template.

The second is deleting or unpublishing a record without a plan for the page that used to exist at its address. If that page had any traffic or backlinks, a missing redirect turns a tidy content update into a dead link.