Nurseries guide

What should a nursery website include? A checklist for managers

A practical checklist of the pages and information every UK nursery website needs to turn parent visits into enrolments.

The short answer

A nursery website should include a visit booking form, age groups and sessions, fees and funded hours, your Ofsted rating with a link to the report, staff introductions, parent policies and clear contact details.

See our nursery website design work, or tell us what you need.

The pages parents look for first

Parents usually check location, age range, opening hours and fees before anything else. Put these within one tap of the homepage.

A short, warm introduction from the manager helps parents picture their child in your setting.

Trust signals

Your Ofsted rating, qualified staff, safeguarding approach and real photos of your rooms do more than any slogan. Avoid stock photos of children who are not at your nursery.

Make the next step obvious

Every page should end with a way to book a visit. Keep the form short: name, phone, email, child age and preferred start date is usually enough.

Check the journey from home page to visit request

Start with a parent who has never heard of your nursery. Can they find the location, age groups, sessions and fees without opening several menus? Give funded childcare a clear explanation and point eligibility questions to official guidance. Show genuine rooms and introduce the people families will meet. Put your inspection report link next to accurate information rather than presenting an old rating as current. Keep the visit form short and use an age band rather than a child’s name or date of birth. Explain what happens after the request so families know whether a visit is confirmed.

For this topic, prepare a short written brief using your own business information. Start with the advice on check the journey from home page to visit request, then identify who can approve each detail and what needs checking before publication. Ask someone outside the business to read it and explain the next step back to you. Keep a copy of the agreed wording so future updates remain consistent with the service you actually provide.

Plan the information before choosing a layout

Start by collecting the information a first-time visitor needs to make a decision. List the essential pages, the questions people ask and the action each page should support. Use your own business details, real photographs and current policies. Separate information that rarely changes from details that need regular updates, such as fees or availability. This makes the brief clearer and reduces the risk of paying for pages nobody maintains. Ask a colleague to read the draft without explanation: if the next step is unclear, improve the wording before spending time on decorative details.

Test the complete journey on a phone

Open the site on a small phone with no saved session and follow the journey from the first page to the final request. Check the menu, contact choices, form errors and confirmation. Make sure a sticky control or cookie notice does not cover the submit button. Test every external booking link and confirm the correct location is selected. A form is only useful if the message is saved and reaches the person responsible for replying. Keep the number of required questions proportionate and explain what happens next. Do not judge the experience only from a large desktop screen.

Agree ownership and maintenance

Keep the domain and essential accounts under the business’s control. Agree who can change content, how support requests are handled and what the ongoing charges cover. Ask for a handover that includes the tasks you will actually perform, not just a list of passwords. Set a routine for checking contact details, broken links and outdated prices. Search performance depends on several factors and cannot be promised by a launch checklist. Focus first on an accurate, usable site, then review real enquiries to decide what needs improving. Keep measurement subject to the visitor’s cookie choices.

Keep the parent journey and records proportionate

Nursery communications should help families understand the setting and arrange a visit without collecting unnecessary information. Use age bands rather than child names or dates of birth in an initial website enquiry. Funding wording should link to current official eligibility information and distinguish eligibility from availability at the nursery. Keep enquiry follow up separate from ongoing promotional messages. Manager approval is useful when an email refers to availability or next steps that can change. Leo Digital’s visit system is already running at two London nurseries; it brings enquiries, stages and open days into a private admin panel. That is a specific deployed system, not a promise that every website includes the same scope.

Want a fixed price for your nursery?

Tell us what you need and we will arrange a quick, no pressure call.

Book a free 15 minute call