Creating and publishing a website page

Create a website page, give it a clear address, review its content on desktop and mobile, and publish it for visitors. This guide follows the visual page builder in Site → Pages.

For a short first-page example, use Getting started. For the differences between drafts, published versions, schedules, and revisions across content types, see Understanding drafts, previews, and publishing.

Before you start

Open the admin for the site you intend to change. You need permission to create and edit pages and to publish the finished page. If Pages or an action is missing, see Why can’t I see or edit a feature?.

Have the page's purpose, approved text, images, and main link destination ready. Decide what a visitor should be able to do after reading it: understand a service, contact you, make a booking, or continue to another page. You do not need an AI provider to write a page yourself.

Check whether you are creating a page or editing one that is already live. A new page's Save draft keeps it unpublished. In the visual builder, Save on a published page publishes the changes. Follow Update a page that is already published before editing an existing live page.

Create the page and choose its address

1. Go to Site → Pages. Search for the intended page first so you do not create a duplicate. To update an existing page, use its pencil-shaped Edit page action.
2. Choose New page. If the How do you want to build? screen appears, choose Use Page Builder. Write Raw Code is the alternative for custom-coded pages; it is not needed for this walkthrough.
3. Enter a descriptive Page title, such as “Bicycle repairs.” The title identifies the page in Cedros. Check the visible heading in the page content too; a layout can have its own heading text.
4. Check the route beneath the title. A new title can generate a route such as /bicycle-repairs. Click the route to edit its slug, or open the builder's Page tab to edit Route directly.
5. Resolve any route conflict before continuing. Choose a different address, or return to Pages and edit the page already using that address.

A route is the part of the address after the domain: /bicycle-repairs becomes https://your-domain.example/bicycle-repairs. Enter the path in Route, not the full web address. Use a short, readable path with words separated by hyphens. For a nested address such as /services/bicycle-repairs, use the Route field in Page.

The root route / is the homepage. Do not use it for an additional information page. If you intend to change the homepage, edit the existing homepage entry.

Choose the address before publishing and check it again before release. Changing a title and changing an address are different decisions. For an established page, plan redirects and update links before changing its route; do not assume old addresses automatically forward.

Add the content visitors need

In Builder, choose Start with an empty section, or choose a starting layout under Start from a design. You can add more sections and click or drag blocks from Add to page. Select a section or block on the canvas to edit its fields in the inspector.

For section and block controls, follow Building a page with the visual editor. To begin from a starter, see Using a page template.

Build a complete page around its purpose:

• Explain the subject: use a clear opening heading and a short explanation of what the page offers.
• Answer practical questions: include the details customers need to decide what to do, such as service area, availability, what is included, or how to prepare.
• Provide a next step: add a useful link or button with a specific label, such as “Request a repair,” and a working destination.
• Use supporting media: replace sample images and write meaningful descriptions where the block provides them. Check image cropping and readability at smaller widths.

For a repair-service page, a useful sequence might be an introduction, supported repairs, appointment information, and a contact action. Publish only prices, turnaround times, and claims you have confirmed.

Replace every starter's sample name, statistic, testimonial, image, and link. A button that looks correct but leads nowhere is unfinished. Adding a form, calendar, or payment-related block does not by itself configure the service behind it; check its destination and setup separately.

Generate with AI is optional and depends on the site's AI setup. Review generated facts, wording, images, and destinations before release. A generated page is a draft, not a verified description of your business.

If the page uses a Shared page template, edit its Page content fields for page-specific values. Edit template changes the shared design, and publishing that template can update other linked pages. Keep that separate from publishing one page's content. See Reusing a shared layout across pages for editing the shared design.

Check page and search settings

Open the builder's Page tab and confirm Page title and Route. For a page you are still preparing, keep Publish status set to Draft. Selecting a status is not a substitute for completing the corresponding save, publish, or schedule action.

In the builder's SEO tab:

• Review SEO title. This is a read-only preview based on the page's saved title settings and the site name. Check it for clarity and accidental repetition.
• Write an accurate SEO description that explains the page's value. Avoid copying unrelated site-wide wording.
• Set OG image if you want a specific social-sharing image, using an image address visitors can access.
• Review Show this page in search results. Turning it off asks search engines not to list the page; it does not make a published page private.

Search engines and social services can choose different snippets or retain older previews. Publishing metadata does not guarantee an immediate listing or a particular appearance. Site-wide access and search settings also apply; see Controlling when your site is public.

Save the draft and review the page

For a new, unpublished page:

1. Choose Save draft and wait for Draft saved. Resolve any error before leaving the editor. The page is still unavailable at its normal public address.
2. Open the builder's Preview tab. Check Desktop, Tablet, and Mobile Web. The “Live preview” shows current editor changes; it does not mean the page is published.
3. Read the entire page. Check headings, spacing, image crops, readable text, and buttons at each size. Confirm that no section contains sample copy or unintended blank space.
4. To review a saved version separately, choose Generate share link, then Open preview. Check the displayed route, revision, and expiry. Share the link only with intended reviewers; it provides access to that preview.
5. If you make corrections, save the draft again and choose Update share link. Open the refreshed preview and confirm it contains the latest change before approving it.

The in-editor preview and saved share preview can show different versions when you have unsaved edits. Generating a share link does not replace saving the draft. If a preview expires or fails to load, generate a fresh link from the intended saved version; do not publish unfinished content just to make it viewable.

Where the editor shows a Publishing tab, use it to inspect the saved preview, media, metadata, and release messages. The saved-preview action is labeled Generate Saved Preview or Update Saved Preview; the builder can show Refresh Saved Preview when its saved preview is out of date. Review Final Site Preview opens the saved page for inspection. Follow any displayed blockers and recheck the preview after corrections.

A rendered preview is a layout check. Test connected forms, bookings, downloads, or purchases separately using the service's appropriate test process; a successful render does not prove those actions work.

Publish and verify the public page

1. Finish reviewing the title, route, copy, media, links, and search settings. Resolve any publishing or review message that requires action.
2. For the new visual page, choose Publish. Wait for the publication confirmation. If the action reports an error, treat it as incomplete until the saved state is checked.
3. Return to Site → Pages and confirm the entry is Published. Use View page to open its normal public address.
4. Confirm that the exact wording and layout you reviewed appear at the intended route. Check the main button and important links.
5. Open that same address in a private browser window or while signed out. Check that a visitor can reach it without your admin session, using a customer account only if the page is intended to require one.
6. Repeat the visitor check on a phone and test the intended customer action. For a form, for example, check both the confirmation and receipt of the submission before relying on it.

If the site is in Maintenance, Internal, or a holding-page mode, a published page may still be unavailable to ordinary visitors. Confirm the intended access settings before announcing the page.

Make the page easy to find

Publishing makes a page available at its route; it does not automatically put it in every menu. Open Site → Menus to add a link to the appropriate navigation menu, complete that menu's save or publication action, and check the public result.

Use a short menu label that customers recognize. Then start from the homepage and follow the navigation to the new page on desktop and mobile. Check footer links separately if the page belongs there.

If you deliberately want a page reachable only through a campaign or a direct link, leave it out of the menu. An unlisted public URL is still public; omitting a navigation link is not access protection.

Publish later instead

For a new unpublished page, save and review the draft first. In the builder's Page tab, choose Scheduled under Publish status, set Publish at, and complete Schedule Publish. Check the date, time, and your browser's local timezone before confirming the schedule.

Follow Schedule a release for confirmation, cancellation, and what to do if the draft changes afterward. Do not choose Publish if your intention is to wait for the scheduled time.

Update a page that is already published

Open the existing entry from Site → Pages and review its current public version before editing. Make the change, check Preview, and inspect any affected links and settings.

In the visual builder, Save saves and publishes changes to an already-published page. Save and exit also publishes. Use these actions only when the entire update is ready for visitors, then check the public page again.

If you need to keep an unfinished replacement as a saved draft while the old page remains live, ask your site administrator or an authorized Cedros assistant to use a draft-only workflow for the existing page. State explicitly that the current public version must remain unchanged. Do not use the visual builder's Save merely to prepare a private review link.

Selecting Draft and choosing Unpublish removes the live page. It is not the same as privately saving an update. To recover a previous saved version, follow Restore an earlier revision, review the restored draft, and release it intentionally.

If something does not work

The route is already in use. Search Pages for the address and check whether you should edit the existing entry. If this is a different page, choose a unique route. Do not delete another page simply to clear the message.

Save draft or Publish is unavailable. Check permission, required title and route, incomplete content, and the displayed release messages. Where shown, review Publishing and Media for the exact problem. A pending operation can also temporarily disable buttons; wait for its result before retrying.

The saved preview shows old content. Save the latest draft, update the share link, and confirm the revision and visible change. For an already-published visual page, remember that Save releases changes; use the draft-only approach above for unfinished work.

Saving or publishing reports a conflict or fails. Preserve the text you still need, then reopen the entry to check what actually saved. If another editor has changed it, compare their version before reapplying your edits. Avoid repeatedly publishing without checking the error and current state.

The public URL shows the old page, a holding page, or “not found.” Confirm the site, exact route, and published state first. Open the normal URL without a preview link, refresh it, and check site access settings. A saved draft or scheduled page is not proof of a completed publication.

The page opens directly but is missing from navigation. Add it to the intended menu, complete the menu's save or publication action, and check both desktop and mobile navigation.

For an unresolved issue, follow Getting help and reporting a problem. Include the page title, normal public URL, exact error, and whether the problem appears in the editor, saved preview, or public page. Keep private preview links and credentials out of public reports.