Education & Childcare

How parents shortlist a centre or school

Parents researching childcare, outside-school-hours care or a small education provider in Perth are doing two jobs at once: checking logistics, and deciding whether they trust the room. A family in Victoria Park and a family in Mandurah may search the same phrases, but they will abandon a site that hides hours, age groups or how to book a tour.

The website is not a substitute for a visit. It is the filter before the visit. If a parent cannot tell who you take, what a day looks like, and how to ask for a tour, they will not start an application in any portal.

Tours, waitlists and enrolment — without replacing portals

Many centres already send applications through a government or third-party portal. That is a reason to make the website clearer, not a reason to skip it. Portals assume the family has already chosen you. The site has to earn that choice.

Typical conversion paths are: book a tour, join a waitlist, ask about a vacancy, or request a callback at a time a parent can actually talk — often during a lunch break or after pickup. UX and UI design matters here because forms filled on a phone, one-handed, fail when they ask for too much too soon. Collect enough to respond; do not recreate an enrolment pack in the first enquiry.

Waitlist and vacancy language should stay honest. If you cannot promise a place, the page should not imply one. Describe the steps you actually use: enquiry, tour, offer, then whatever application process you already run.

Programs, fees and the questions parents actually ask

Multiple programs — nursery through kindergarten, school-age care, vacation care or specialist classes — collapse into mush when they share one undifferentiated page. Each program needs its own page with age range, hours, what children do in a typical session, and who to contact. Fees belong as an overview you can stand behind, with an invitation to ask for the current schedule rather than a number that will be wrong in six months.

Parents also look for unglamorous details: meals, rest, what to pack, late pickup, and how you communicate during the day. You do not need every internal procedure on the site. You do need to show that those questions have answers and a human to ask.

We will not invent funding, rebate or regulatory detail. If you explain a scheme on the site, the wording should come from you or your advisers.

Trust, photos and a careful tone

Trust on an education site is built from specificity, not slogans. “Nurturing environment” means little until a parent can see the outdoor space, the daily rhythm, and the people at the door. Staff profiles (with the details you are willing to publish) and a tour page that sets expectations do more than a stock photo of alphabet blocks.

Photos of children are a consent question, not a design preference. We only use images you supply with appropriate permission. Where those photos are limited, we design around rooms, routines, and staff — still warm, still real. We do not scrape social feeds or manufacture a gallery.

Tone should be parent-friendly without becoming casual about safety. Avoid guarantees about development or waitlist times. Say what you do, how you do it, and how a family starts a conversation.

Content that serves new families and current ones

New families need programs, tours and location. Current families need term dates, newsletters, policy summaries, and a way to contact the office without ringing during rest time. A simple “current families” area keeps operational content from burying the enrolment path.

WordPress is a common fit because coordinators already think in pages, PDFs and seasonal updates. The content model should make it obvious what can change weekly (news, dates) versus what should stay stable (program descriptions, tour process).

Local search, mobile moments and useful features

Parents search by suburb, age group and “near me”. SEO here is usually local and practical: service-area clarity, program pages that match how people search, and hours that search engines can read. Keyword stuffing does not help a parent who needs Wednesday availability.

Mobile context is a lunch-break or evening-couch session. Maps, tap-to-call, and a tour form that remembers the program they were reading reduce drop-off.

Our process starts with how you currently handle tour requests, then we map pages around that workflow. Timeline depends on how ready program copy and photos are — project timelines give a realistic range. Get a quote with your locations, programs, and whether tours are booked by form, phone, or both.

Common pain points

• Tour and enrolment enquiries
• Multiple programs and fees
• Trust and compliance tone

Website workflows that matter

• Program pages
• Tour booking forms
• Parent resources

Buying objections we hear

• Government portals handle applications
• Photos and consent constraints