Nursery website: show-round bookings, waiting list and parent consent in one place
A nursery website answers what a parent asks before visiting: ages taken, opening hours, fees, waiting list and how to book a show-round. ALTAI Digital builds nursery and childcare sites around those questions. The show-round is booked from the site or by WhatsApp. The waiting list form runs with a GDPR consent notice, and photos of children appear only with parental consent. Ofsted registration in England, or the LRK number in the Netherlands, is shown where parents look first. Delivery takes four weeks.
A parent looking for a nursery does the same three things in Rotterdam and in Manchester. They ask other parents, read the reviews on the Google Business Profile, then open the website. If the site does not say which ages are taken, what the hours are and what a place costs, the parent closes it. The next nursery on the list gets the call. A nursery website is not a brochure. Its job is to answer those questions and turn the visit into a booked show-round.
Two things set a nursery site apart from other small-business sites. The first is registration. In England, nurseries are registered with Ofsted, and the Ofsted report is the first thing many parents read before they visit. In the Netherlands, childcare organisations (kinderopvang) hold a registration in the Landelijk Register Kinderopvang, and parents look for the LRK number. The site shows this in its own section rather than in a footer. The second is children's data. Under GDPR, photos and videos of children are personal data and are published only with parental consent.
Waiting lists are common, and they change what the site has to do. A parent who cannot get a place this term still wants to leave their details and hear back when a place opens. A site that only offers a phone number loses that parent. A site with a waiting list form, a consent notice and a clear reply time keeps them. The same form feeds the show-round diary, so a parent who visits does not fill in their details twice.
Below is the scope of a nursery website build, the process and the questions we are asked most. We work from Rotterdam and Istanbul and write the site in English and Dutch where needed. The site is built on Next.js from scratch; the domain, hosting and source code stay in the nursery's name. Pricing is given after the discovery call, once the number of pages and the booking scope are clear. Delivery takes four weeks: one for discovery, two for design and writing, one for corrections and launch.
What goes wrong today
- 01
Ages, hours and fees are not on the site
The home page has a welcome paragraph and a photo; the ages taken, the opening hours and the fees are nowhere. The parent messages on Instagram. The message reaches a manager who is in a room with the children, and the answer comes that evening or not at all.
- 02
The show-round depends on the phone
Visits are arranged by phone; nobody can answer during the session, and parents do not call in the evening. Without a diary on the site the visit is agreed over three messages and then forgotten. The site should write the show-round into a calendar and let the nursery confirm with one tap.
- 03
Children's photos without consent
The gallery and the Instagram feed show children's faces, and nobody can say which parents gave written consent. Under GDPR a child's photo is personal data; publishing it without consent exposes the nursery to a complaint it cannot answer. The gallery needs a consent record behind it.
- 04
Waiting list requests lost in a shared inbox
Enquiries arrive in an office mailbox; who was called back, who is still waiting and for which start date is nobody's job. After a week of silence the parent takes a place elsewhere. Requests should land in a list with a date, a status and a consent notice.
- 05
Ofsted or LRK details hard to find
The parent wants to see the registration before booking a visit. On many sites the Ofsted report or the LRK number sits in a footer or is missing. The parent then searches for it elsewhere and reads the report without the nursery's own context next to it.
- 06
Slow pages on a phone
Parents search on a phone, often at night. A page full of large photos loads slowly and hides the hours and the show-round button below several scrolls. Sites built on old platforms break on small screens. The page should open in under three seconds with the booking button on the first screen.
Scope of the build
Show-round booking: web diary and WhatsApp
The parent picks a date and a time from the nursery's diary; the nursery confirms with one tap. The visit goes into the calendar and a reminder goes to the parent. The same button opens WhatsApp for parents who prefer to write. After the visit, the waiting list or registration request starts from the same record.
Age group and daily routine pages
Each age group gets its own page: the room, the daily routine, the hours and the staff in that room. The routine and the weekly menu are edited by the nursery from an admin screen. Google finds each age group on its own page, so a search for a specific age lands on the right one.
Waiting list and registration form with GDPR consent
The parent leaves the child's date of birth, the start date they want and their contact details. The form shows the privacy notice and runs with a consent box. Each request is written to a list with a date and a status. The nursery sees who has been called back and who is waiting for which start date.
Photo policy built on parental consent
The gallery runs on a consent record: which parent consented to which use is stored. A child without consent does not appear on the site or in social posts. Consent is collected with the registration paperwork and can be withdrawn; a withdrawn photo comes down. Room and garden photos without children need no consent.
Staff page and registration details
Each staff member gets a card with name, role and qualification; photos appear only with the person's agreement. Ofsted registration in England, or the LRK number in the Netherlands, is shown in its own section with a link to the public register. The parent reads it before the visit instead of asking on arrival.
Google Business Profile and reviews
The site is linked to the Business Profile; address, hours, phone and photos are maintained from one source. Organisation schema is written into the page so that Google shows location and hours in the result. Reviews are listed on the site, and a review link is added to the message parents receive after registration. Instagram links to the site; the decision is made on the site.
Speed and phone layout
Pages are coded on Next.js from scratch and open in under three seconds on a phone; the show-round button sits on the first screen. Photos are resized on upload so the gallery does not slow the page. Domain, hosting and source code are registered in the nursery's name, so the nursery can continue with another team later.
How the build runs
- 01
Discovery (1 week)
Ages, routine, staff and registration details are collected; the current site, the Business Profile and Instagram are measured. The show-round and waiting list flow is drawn with the nursery.
- 02
Design and writing (2 weeks)
Pages are written in English and Dutch where needed; the diary, the waiting list form, the consent record and the privacy notice are set up. An interim preview is shared.
- 03
Corrections and launch (1 week)
Corrections are applied, domain and hosting are registered to the nursery, the site goes live; staff are shown the booking and request screens.
- 04
Connection and measurement
Search Console and the Business Profile are connected and pages are submitted for indexing. A report with show-round, request and visit counts follows at the end of month one.
Nursery site
- Seven pages: home, age groups, daily routine, staff, waiting list and registration, questions, contact and location
- Show-round booking: web diary and WhatsApp
- Waiting list form with privacy notice and consent box
- Photo gallery built on a parental consent record
- Ofsted or LRK registration section
- Google Business Profile and Search Console connection
- Domain, hosting and source code in the nursery's name
Pricing is given after the discovery call, once the scope is clear.
Products used in this build
Request handling
Requests from five channels collect in one list, the draft reply arrives ready, and the decision to send stays with you.
WhatsApp Business integration
Notifications, order tracking and customer conversations gather in the business account; the history stays with the company.
Online booking and scheduling
Online booking for clinics, salons and hotels; reminders and cancellation handling close the empty slot.
Web and mobile development
Code written from scratch: web with Next.js, mobile with React Native and Swift; the repository is yours from day one.
Terms used on this page
- Show-round
- A show-round is the visit a parent makes before choosing a nursery, walking through the rooms with a member of staff.
- Waiting list form
- A waiting list form is the site page that takes a child's age, a start date and contact details, with a consent box.
- Parental consent
- Parental consent is the written, informed agreement a parent gives before a child's photo or video is published, as GDPR requires.
- Ofsted registration
- Ofsted registration is the entry an English nursery holds with the national inspectorate, whose report parents read before they visit.
- LRK number
- The LRK number is the registration number a childcare organisation in the Netherlands holds in the Landelijk Register Kinderopvang, the national childcare register.
nursery websiteFrequently asked questions
Four weeks: one for discovery, two for design and writing, one for corrections and launch. If the age groups, routine, staff list and registration details arrive in week one, the schedule holds. If an intake is close, the show-round page can go live first and the rest follows.
The parent picks a day and a time from the diary on the site. The request lands on the nursery's screen and in WhatsApp, and the nursery confirms with one tap. The parent gets a confirmation and a reminder. The diary only offers the times the nursery has opened for visits, so nothing is booked in the middle of a session. Parents who write on WhatsApp receive the same diary link.
Only with parental consent. Under GDPR a child's photo or video is personal data. The build includes a gallery that keeps a consent record, and a child without consent does not appear anywhere on the site. Consent is collected with the registration paperwork; if a parent withdraws it, the photo comes down. Photos of rooms and the garden without children need no consent.
Yes. The form carries the two things GDPR asks for at the point of collection. The first is a privacy notice that says who holds the data, for what purpose and for how long. The second is a consent box that must be ticked before the request is sent. Requests stay in the nursery's own list rather than a third-party platform. The notice is written to match the nursery's existing privacy policy and shown to the nursery before launch.
In their own section, with a link to the public register. In England, nurseries are registered with Ofsted and the report is the first thing many parents read. In the Netherlands, childcare organisations hold an LRK registration and parents look for the number. Showing it on the site, with the nursery's own context next to it, means the parent does not go looking elsewhere.
It takes show-round bookings and waiting list requests all year. A parent who cannot get a place leaves their details, and the request sits in the list with the start date they want. The nursery works through the list when a place opens. The age group and staff pages keep being found on Google, and the review link keeps adding reviews to the Business Profile.
We measure first: speed, phone layout, the show-round and waiting list flow, the photo consent record. On a site built on an old platform with a welcome paragraph and a gallery, rewriting is usually faster than repairing. The decision is made on the discovery call. The existing domain is kept and old page addresses are redirected to the new pages.
Pricing depends on the number of pages and age groups, the languages, and the scope of the booking and waiting list flow. It is given after the discovery call. The scope of the nursery site is listed in the package above, and domain, hosting and source code are in the nursery's name. The measurement report at the end of month one is part of the build.
The process first, the proposal after
In a short discovery call we map the process together and tell you plainly whether it is worth automating. If it is not, we say that too.
30 minutes · no preparation needed
