When a site needs separate pages, and how Anticode builds them
Plenty of AI builders produce one long page and call each section a page. Separate pages are worth it when visitors arrive with different questions, when search engines should find each topic on its own address, or when one section has outgrown the scroll. Anticode can build up to eight named pages alongside the home page, each with its own address and listed in the site's sitemap.
One page or several: how to decide
A single scrolling page is often the right answer. It works for a launch, a waitlist, an event or a freelancer with one service, because everyone who arrives wants the same thing. It stops working when the people arriving want different things. A wedding venue gets couples comparing packages and suppliers looking for loading times; a studio gets clients who want to see the work and recruits who want to know what it's like to work there.
| Sign | What it suggests |
|---|---|
| People email asking things the page already answers, far down | The answer is buried; give it its own page and link to it from the top |
| You'd like to send someone straight to your prices or your FAQ | That topic needs its own address you can share |
| You offer several distinct services | A Services page with each one explained beats five lines in a strip |
| The page takes more than a minute of scrolling on a phone | Visitors give up before the contact section |
| You want to be found for several different searches | Each page can have a title and description aimed at one of them |
The one page vs multi-page guide goes further into the trade-off. If one long page is still right for you, see one-page websites.
The pages Anticode can add
On top of the home page, a design-engine site can have any of these as separate pages. You pick them in the plan or ask for them in your first sentence.
- Work
- Projects or case studies, for studios, photographers, architects and anyone whose past work does the selling.
- Shop
- Products with buy buttons that go to a payment link from your own provider. There's no cart.
- Services
- What you offer, for whom and how it works, one service after another.
- About
- The people, the story and the reasons to trust you.
- Pricing
- Plans, packages or a price list, with what each includes.
- FAQ
- The questions you get asked, grouped and answered.
- Book
- A booking calendar for appointments or sessions.
- Contact
- A contact form, plus your address, hours or other ways to reach you.
How a multi-page build comes together
Using Anticode as a multi page website builder starts with what the business is and who visits: "a site for Northfold, a two-person joinery workshop, with pages for our work, services, about us and contact". The Architect replies with a plan listing each page and its sections, the design direction and the features (a contact form, say, or a booking calendar), and may ask up to three questions where the answer changes the build, such as whether prices should be public. You can change the plan before anything is built.
The design engine then builds every page under the same design system, so type, the action colour, spacing and corner radius match from the home page to the contact page. It helps to ask for the home page to summarise and point into the other pages rather than repeat them. Every page goes through the Critic's design checks and Sentinel's security checks, and the design gate's check for empty links (an empty or "#" link) matters more once there are pages linking to each other. It doesn't test outside URLs, so click through those yourself.
Search, sitemaps and AI assistants
Separate pages give search engines separate things to show. A Pricing page can answer "joinery workshop prices Leeds" in a way a pricing strip halfway down a home page rarely does. Each published Anticode site serves its own sitemap.xml listing its pages, a robots.txt that points to it, and an llms.txt that describes the site for AI assistants. Write each page's title and description for the question it answers; the guide to title tags has examples.
Editing a site with several pages
- Change requests in words apply across the site: "add a line about free quotes to the Services and Contact pages".
- The visual editor edits text in place and moves sections within a page.
- Version history keeps the most recent saves, up to your plan's number, so you can restore the whole site to an earlier state if a change to one page went wrong.
- The Map tab (in Pro mode) draws the site's sections, forms and connectors and checks nothing broke after a change.
Limits
- A fixed set of page types. The eight named pages above, plus collection pages if you use the CMS (such as
/projects/and one page per project). If you need a page that fits none of them, it has to live inside one of these or on another site. - Small sites, not portals. This suits a business with a handful of topics. A site with dozens of sections, deep menus and its own search is a job for a different tool.
- English only. You can't build parallel pages in other languages.
- No blog engine. A CMS collection can hold posts, but without comments, RSS or scheduled publishing.
Questions people ask
Is a one-page website worse for SEO?
Not inherently. A single page can rank well for one topic. Separate pages help when you want to be found for several distinct searches, each with its own title and description.
Can I add a page after the site is published?
Yes. Ask for it in a sentence, such as "add an FAQ page", and the site is rebuilt from the same project with the new page linked in.
How many pages can an Anticode site have?
The home page plus any of the eight named pages, and as many collection pages as your CMS collections hold.