Skip to main content

Pages

Each page of your site has a title, a URL slug, and a place in a hierarchy that decides the address visitors reach it at.

The page hierarchy maps directly to your URL paths:

Plan availability

Free for core pages. Higher tiers raise the cap on how many pages a site can publish.

Pages & routing​

  • Each page has a title and a URL slug. Aglyn normalizes slugs and keeps a site routing map.
  • Pages form a hierarchy: pick a parent and the child inherits a nested path (/services/pricing). Changing a slug or parent cascades safe rewrites across the map, with cycle guards so you can't create a loop. See What a move does to a URL.
  • Reorder the hierarchy with drag-and-drop in the pages list. To organize pages without changing their addresses, put them in a group.
  • The pages list shows each page's Published date, and the page's detail view shows Date published. Both stay empty until the page goes live, and clear again if you unpublish it (including a scheduled unpublish) — so the column tells you what's live, not what exists. A page you've just created is a draft: it holds its slug but nothing resolves there until you publish it.
  • Unpublish takes a live page off your site. It's in the row's ⋮ menu on the pages list (on published pages), on the page's detail view under Publishing, and on the Besigner toolbar. The page, its versions and its slug are all kept, so publishing again puts it back at the same address.
  • Unpublishing or deleting a page takes that page alone off your site. Pages nested under it stay live at their own addresses, and the confirmation lists them, so you can unpublish them one by one if that's what you meant. A scheduled unpublish works the same way.

Slug​

A page's Slug is the path it is served at — / for the home page, about for /about — up to 60 characters. Publishing registers it in the routing map, and a nested page puts its parent's path in front of its own. Leave it empty to keep the page unpublished.

The Pages list​

A site's Pages list shows every page in its hierarchy, with when each was published, and is where you add, arrange and open them. Drag a page to reorder or nest it, and use a row's ⋮ menu to View details, Edit in besigner, Open live page, add Translations…, Save as template, Unpublish or Delete it. The plan readout opposite the heading shows how many pages your plan allows — see what counts.

A page's detail view​

View details opens one page's settings without opening its design: its basic details, publishing, who can see it, what links to it, its SEO, versions, traffic and recent activity. Edit in Besigner at the top of the page is where you change how it looks.

Basic Details​

The Basic Details card is the page's record: its Page ID, Display name and Description, and when it was created, published and last updated. The published date stays empty until the page goes live. To change the display name or description, use the Name & description card.

Name & description​

The page's Display name is what it is called across the console: the Pages list, the page switcher and search. Its Description is a note about the page. Edit either one in place and choose Save details in the card's header. The live page uses them as a fallback too: its title falls back to the display name, and its meta description to the description, wherever the page's own SEO leaves them blank.

Used by​

The Used by card finds everything that links to this page before you move, unpublish or delete it: press Find where this is used to scan the published version of every page and layout, every component, the pages nested under this one, and the collections that render their pages through it. Links typed as a plain address rather than picked as a page are not found, because nothing records which page they meant.

Raw JSON​

The Raw JSON card shows the page document exactly as it is stored — a read-only view for developers checking what a page holds. It is closed by default; press the chevron to open it.

Page groups​

A group is a folder in the pages list. It holds pages and is not one: it has no slug, no content and no address of its own, and it's never published, previewed or listed in your sitemap or navigation.

A group adds nothing to the URLs of the pages in it. A page inside a group is served exactly where it would be if it sat at the group's own level, so a group of landing pages keeps /launch-waitlist at /launch-waitlist. Groups can sit inside other groups, and inside a page: a group under Services holds pages at /services/..., just as if they were Services' own children.

  • New group on the pages list creates one. Drag pages onto it to move them in, and drag them out again the same way. Click a group's row to open or close it.
  • Moving a page into or out of a group never changes its address, because the page it's composed under stays the same. The pages list checks this before it saves the move, and refuses the move rather than change a live address.
  • Rename and Delete are in a group's ⋮ menu. Deleting a group keeps everything in it: its pages move up a level, to where the group was, at the same addresses. Nothing is unpublished.
  • A group doesn't count against your page allowance, and you can't pick one where a page is expected, such as an error page, a sign-in page, an A/B test, a redirect or a collection template. In the Besigner's Parent page picker, groups are marked (group).

What a move does to a URL​

A page's address is its own slug under the slugs of the pages above it. Moving a page changes its address only when the page it's composed under changes:

MoveAddress
Into or out of a group at the same levelUnchanged
Under a published page, say ServicesBecomes /services/your-page
Under a page that has a slug but isn't publishedBecomes the composed path. The page stays live there; the parent stays unpublished.
Under a page with no slugUnchanged. It keeps its current address until you publish it again.
To the top levelBecomes /your-page

Pages nested under the one you move come along with it. A move never takes a live page off your site, and it never publishes a page that wasn't live: a draft you move stays a draft.

A page that keeps its address when the page above it loses its slug, or is deleted, stays at that address from then on. If you later publish that parent again, the page doesn't move with it; publish the page itself to give it the new address.

The pages list

Editing a page in the Besigner

What counts against your page allowance​

Your plan's page limit counts the pages that have an address of their own — the ones a visitor can reach at a URL. Some pages you design never get an address, and those don't count:

PageCounts?Why
A page you publish at a slugYesIt has a URL of its own.
A collection's list templateYes/{collection} renders that exact page.
A collection's entry templateNoOne page composes every entry; it has no address of its own.
An error page you've assignedNoIt renders on addresses that matched nothing.
An email you designNoIt's sent, never served at a URL.
A page you've deletedNoDeleting frees the slot straight away.
A groupNoIt holds pages; it has no address or content of its own.

The rule behind the table is one question: does the page occupy a URL of its own? So an error page that is also still published at its own address — say a 404 page you published at /404 while designing it — has an address, and it counts until you remove that address. The Error pages card tells you when that's the case and offers the one-click Remove address; the page carries on rendering for its status code afterwards.

Duplicate a page​

Every row on the Pages list has Duplicate… in its menu. The copy takes the latest saved version whole — the element tree, layout values, description and SEO fields — under the name you give it (Copy of Home by default; a name another page already has gets a number). Its slug becomes home-copy, then home-copy-2, so it never claims the original's address.

The copy is a draft: it has no address on the live site until you publish it, exactly like a page you created from scratch. Components and layouts placed on the original are shared, not copied — the duplicate points at the same ones. A duplicate counts against your page allowance the moment it is made, and is refused with the same message a new page would be when the allowance is spent.

A collection's entry template can be duplicated too, which is how a second collection starts from the first one's design. The copy is still an entry template, with every {{entry.*}} binding kept: it isn't published, and no collection uses it until you pick it as a collection's Entry page in Content. Like the original, it doesn't count against your page allowance. An error page can't be duplicated.

Error & maintenance pages​

You can design custom 404 / 401 / 403 / 503 pages and turn on maintenance mode. See Site protection & error pages.