A childcare website should help families understand a real centre and take the next appropriate step. That means clear service information, a usable phone and enquiry route, and a careful distinction between asking a question, arranging a visit and applying for enrolment.
This guide is written by No Brainer Creative, an Auckland web design and digital marketing agency. It is a planning framework for centre owners and teams, informed by our published childcare website work. It does not establish a guaranteed ranking, enquiry increase or enrolment result.
Start with the questions families need answered
Before selecting a visual style, gather the information the centre can verify. Which ages does it serve? Where is it? What hours and attendance options apply? What does the early-learning approach look like in practice? Who can explain fees, availability and the next step?
The Ministry of Education’s guide to choosing an early learning service discusses hours, age groups, costs, staff, visiting, waiting lists and ERO reports. Use those topics to check whether your website helps families ask informed questions. Have the centre verify its own information; do not copy a general rule or another centreβs details into your service description.
Keep information about actual availability current, or explain how to ask staff. An enquiry form is not evidence that a place is available. If the service has a waiting list, make the process clear without promising a start date the team has not agreed.
Give each real centre a clear place in the site
A single-centre website may need a straightforward structure covering the setting, learning approach, practical information, team and contact options. A group needs an easy way to choose and understand its actual locations.
Where a group has distinct centres, a useful location page can show the correct address, contact details, hours, age groups, images and enquiry destination. Include information that actually differs. Do not create a near-identical page for every surrounding suburb merely to repeat a keyword.
A shared enquiry form can work if the location choice and routing are clear. Separate forms may suit another arrangement. Choose the system staff can manage and test, rather than assuming more forms automatically create more enquiries.
Separate the enquiry, visit and enrolment steps
Map what happens after someone chooses a contact option. A general enquiry might ask for an adult’s name, a preferred contact method, the centre they mean and their question. Decide which fields are needed for the purpose, and explain what happens next.
A full enrolment application serves a different purpose and may require more detailed information. Agree that process with the centre before selecting forms, storage or integrations. Avoid inviting sensitive family or child information into a general free-text field when it is not needed for the first response.
For tour requests, distinguish a request from a confirmed booking. If staff need to check a time, say so in the confirmation. If an existing booking system is used, agree how the website hands over to it and who maintains availability. Do not promise an immediate reply unless the centre can support it.
Write the handoff before building the form
- Which team or centre receives the enquiry?
- Who is responsible when the usual staff member is away?
- What acknowledgement does the family see?
- How does the team identify delivery failures or unanswered requests?
- Which records belong in the approved enrolment or booking process?
These decisions are more useful than an arbitrary limit on the number of clicks or fields. Keep the route easy to understand, then test the actual experience.
Choose imagery with a clear purpose and permission process
Photographs can show rooms, outdoor areas, learning materials and the people a family may meet. They should represent the service truthfully. A public website does not need identifiable photographs of children to communicate the setting.
Agree who supplies and approves images, where each image may appear and how a later removal request will be handled. Do not assume that an image available in a parent communication system is approved for a public marketing page.
The Office of the Privacy Commissioner’s children’s photography and filming guidance covers collection, use, sharing and storage of images. It recommends thinking about the information an image reveals and whether an activity can be shown without focusing on childrenβs faces. The centre should apply its own approved process and obtain advice where needed.
For the design brief, record image permissions and intended use alongside the asset list. If suitable images are unavailable, discuss alternatives rather than publishing unapproved material or presenting stock photographs as the actual centre.
Use a real project to discuss design decisions
Our Blooming Buds website project shows how childcare imagery, practical information and navigation can work together. The published project presents its West Auckland centres in New Lynn and Glen Eden, common questions and tour-enquiry routes.
The case study is evidence of the design and content presentation. It does not establish a measured increase in enrolments or a particular Google position. Use the visible work to discuss a useful layout and information structure, then agree what your own centre needs.
A different centre may need different content, editing responsibilities or enquiry tools. Retain useful information and existing URLs when redesigning an established website; a new visual direction should not quietly remove pages families already use.
Plan search visibility around the service you actually provide
Use clear page titles, headings and service descriptions that identify the centre and its genuine location. Check that important pages can be crawled and indexed, have the intended canonical URL and are included in the appropriate sitemap. A saved setting or sitemap entry does not itself establish Google indexing.
For an eligible local business profile, keep its public details accurate and consistent with the real service. Do not invent additional branches or publish a location solely to target searches. Local visibility is not secured by a particular wording pattern or a weekly posting quota.
Report organic website results and Maps separately. A position observed on one device or in one part of Auckland is not a universal result for every family. Record the date, location, device and query before comparing rankings. Our Auckland SEO service explains how search research, technical checks and content work can fit into a scoped plan.
Check the website before launch and at handover
| Check | Evidence to review | Who confirms it |
|---|---|---|
| Centre information | Correct locations, contacts, hours, age groups and service descriptions. | The person responsible for the centre’s public information. |
| Content and imagery | Approved copy, genuine project assets and intended image permissions. | The centre’s nominated approver. |
| Phone reading | Readable text, usable menus, labelled fields and visible contact routes on a real or representative phone screen. | The centre and website team. |
| Enquiry delivery | A controlled test reaches the intended team and has a clear sender confirmation. | The receiving staff member and website team. |
| Existing URLs | Important pages remain useful or have an appropriate destination after a redesign. | The website team, with centre review. |
| Ongoing ownership | Named editing responsibilities, access, hosting, support and a backup/restore plan. | The centre owner and service providers. |
Agree a controlled enquiry test with the centre and label it as a test. Check staff receipt and any record the approved system should retain. Do not submit surprise applications or use a real child’s sensitive information merely to demonstrate that a form works.
Include keyboard navigation and clear focus states in the check. A table should remain usable on a small screen without widening the entire page. A good laboratory performance score can help identify technical conditions, but it is not proof of a particular family’s experience or an enrolment result.
Scope the work around your centre
A quote should explain content, imagery, location pages, design, implementation, integrations, testing and handover. Clarify hosting, ongoing care, third-party tools and later changes separately. A template, custom build or targeted repair may each be appropriate depending on the requirements.
Bring a list of real centres, the information families ask for, current website problems and the process staff use after an enquiry. Our website briefing guide can help organise those decisions. No Brainerβs web design service covers planning and building a site around the agreed content and customer journey.
To discuss a childcare website, contact No Brainer or call +64 22 125 2166.
Frequently asked questions
What should a childcare centre website explain?
Explain the real centre, its early-learning approach, location, hours, age groups, practical information for families and how to arrange a conversation or visit. Have the centre approve factual service information and keep it current. A website should not promise availability or an enrolment outcome that staff have not confirmed.
Does every centre need a custom-built website?
No. Choose the approach around the content, editing needs, locations and integrations. A well-configured template may suit a straightforward site. A custom build may be useful where the requirements justify it. Compare what each proposal includes and how it will be maintained.
Should an initial enquiry form collect a full enrolment application?
Separate a general enquiry from a formal application. Agree the minimum information staff need to respond and explain the purpose of the form. If later enrolment steps require more detailed information, the centre should use its approved process rather than adding every field to a public contact form.
Do we need photographs of children on the public website?
No. Rooms, outdoor areas, approved staff images and other centre details can explain the setting. If images include identifiable children, follow the centre’s approved permissions and review process. The Privacy Commissioner’s guidance is a useful starting point; do not assume permission for one use covers every public channel.
Should a group have a separate page for each real centre?
A distinct page can help families compare actual locations, hours, age groups and contact routes. The content should reflect real differences. One well-routed enquiry form may work across centres; a separate form for every location is not automatically necessary.
Will a new website improve our Google rankings or enrolments?
A useful website can support discovery and enquiries, but neither outcome is guaranteed. Check technical eligibility, accurate local information and helpful content, then measure dated search observations and genuine enquiries. Enrolments also depend on availability, service fit and the centre’s follow-up process.
How much does a childcare website cost?
Request a scoped quote covering the number of centres, content, imagery, design, editing needs, integrations, testing and handover. Clarify hosting, ongoing care and third-party costs separately. No single price applies to every centre or rebuild.
How do we check that tour enquiries reach the right team?
Agree a controlled test with the centre using clearly labelled test details. Verify routing, staff receipt and the confirmation shown to the sender. Test how a failure is handled as well. A website success message alone does not prove delivery, a tour appointment or an accepted enrolment.