Company websites
A website that stays tidy after launch.
Home, about, services, a page per service, contact, privacy, a 404 somebody eventually sees. A company website is not hard to build. It is hard to keep consistent two years later, when the footer has four versions and nobody remembers which page is missing a description.
Start with the sitemap,
not the homepage.
Generate the page tree with AI from a few lines of instruction — and a source URL if an old site exists. You get nested pages in the page tree, ready to reorder by dragging, each with its name, URL, parent and template. Mark one as the homepage and one as the 404 in project settings.
Then generate each page's content, choosing which components to draw from, or build it by hand from the component library. Every page has a description and a "purpose of this page" field; filling those in is the single cheapest way to get better AI drafts.
One header,
one footer,
everywhere.
The template holds the shared frame: header and footer blocks, fonts, CSS and JavaScript. Change the footer once and every page that includes the template footer changes with it. A page that should not have them — a campaign page, a thank-you page — switches them off in its settings.
Menus are separate objects: a main menu, a footer menu, a legal menu. Elements nest by dragging and link to a page or an external address, so renaming a page's URL does not leave a broken link in the navigation.
Contact details that appear in six places belong in global variables. Change the phone number once.
- 1HomeHomepage flag. Template header and footer.
- 2ServicesThree child pages, one per service.
- 3AboutTeam block, history block, one photo from the library.
- 4ContactAddress and phone from global variables.
- ·DraftMarked draft: not publishable until unmarked.
- 5404Not in sitemap. Links back to Services.
Eight pagesOne template
Every page accounted for,
including the one nobody visits on purpose.
Before it goes live
SEO, redirects and your domain.
META for all pages
One table of every page's URL, title, description, keywords and canonical, editable inline. "Generate META for all pages" fills the gaps. See SEO and migration.
Redirects
A redirection list with 301 and 302, so the old /offer.html still lands somewhere useful after the restructure.
Your own domain
Publish the whole project to your connected domain, or to cstmui.com first while it is checked. See publishing.
Which plan
Regular, €100 a month, one seat. Pages, templates, menus, SEO, redirects and publishing to your domain are all in it. Move to Team when more than one person edits and you want roles, invitations and shared notes. Compare plans.
Questions
Can some pages stay out of the sitemap?
Yes. Each page can be hidden from the sitemap, hidden completely, or set to noindex and nofollow.
What happens to the old site's addresses?
Add them to the redirection list as 301s. If you are replacing a whole site, rebuilding a website covers the crawler route.
Can the favicon and share image be set once?
Yes. Favicons live in project settings and OpenGraph defaults apply to every page unless a page overrides them.
Statistically: the 404 page is the one every company website forgets and every visitor with an old bookmark sees first. It takes four minutes. Do it now.
Your website next.
Start it today.
Open the editor, describe the website, and publish the first version to a cstmui.com address.
Open castomUI See pricing