Create and edit pages - slugs and 301 prompts, drafts and scheduling, password protection, internal links, and the content/SEO analysis panel.
Loading the guide...
Help us make the guides more useful.
0 helpful · 0 not helpful
Pages are the core of every client site. Each page has a title, a slug, and a content tree you lay out in the visual builder, plus SEO and publishing controls in the page editor.
One rule to internalize before anything else: publishing a page does not change the live site. Publish updates the page's status in the CMS; the static site is only rebuilt when you press Deploy. See Preview, Publish, and Deploy.
Pages in a site's sidebar lists every page with its status (draft or published) and last-updated time. From here you can:
The slug is the page's URL path, edited in the sidebar. A new page starts with a placeholder slug, and the slug does not follow the title, so set it yourself.
about page.Renaming a published page's slug changes its URL, which breaks inbound links unless you redirect. After a slug change the editor shows a dismissible prompt offering to create a 301 redirect from the old URL to the new one. Accept it unless you have a specific reason not to. Redirects ship with the next deploy.
If the renamed page was the home page, the home-page setting follows the rename automatically.
Opening a page shows the editor: the main Page Content card (with the Open in Builder button) and tabbed cards for SEO, Social, Schema, Content, and Linking, plus sidebar controls.
| Control | What it does |
|---|---|
| Status | Draft or Published |
| Slug | The URL path (see above) |
| Featured Image | The page's representative image, picked from the media library. Used as the SERP thumbnail and social fallback |
| Schedule Publish | Publish automatically at a future date and time |
| Page Password | Password-protect the page. Leave empty for public access |
| Cornerstone | Marks the page as pillar content you want to funnel internal links toward |
Setting a Page Password gates the page behind a password prompt. The protected content is encrypted in the published output, not just hidden, so the static file does not leak the body.
When a button or link in the builder points at another page, use the internal page picker rather than typing the URL. Picked links store a stable reference to the target page, so they keep working even if that page's slug is later renamed - the rendered link always resolves to the current URL.
The editor's Linking tab helps you build internal-link coverage: it surfaces the site's other pages (cornerstone pages first) as link candidates.
The Content / SEO analysis panel scores the page against the Focus Keyword you set in the SEO tab:
Treat it as a checklist, not a law: fix the red items, consider the yellows, and keep the copy written for humans. Per-page SEO fields themselves are covered in Page SEO.
| Task | Where |
|---|---|
| Create / duplicate / delete a page | Pages list |
| Build the layout | Open in Builder, on the page editor |
| Change the URL | Slug field (+ accept the 301 prompt if published) |
| Publish later | Schedule Publish (deploy afterward) |
| Protect a page | Page Password |
| Optimize for search | SEO tab + Content / SEO analysis panel |
| Make it live | Deploy - publishing alone never touches the live site |