A school can have a polished website and still make prospective parents work far too hard to take the next step.
They search for the school, open the website, and then have to hunt for admissions dates, fees, age groups, curriculum, a prospectus, a visit button or even a working phone number. Some are sent straight into a parent portal that only makes sense after enrolment. Others submit a form that disappears into an inbox nobody owns.
If your school website gets attention but few useful admission enquiries, the first question is not “Do we need a redesign?”
It is:
Where does the prospective parent lose confidence or momentum?
The best admissions website is not the one with the most pages. It is the one that helps a parent move from uncertainty to a clear next step.
Start with the full parent journey, not the homepage
A prospective parent rarely experiences the website as a design project. They experience a sequence of decisions.
A useful admissions journey looks roughly like this:
search → relevant page → understand the school → trust the school → ask a question or book a visit → receive a response → apply → continue the admissions process
Your website only controls part of that journey, but those handoffs matter.
Audit each stage:
- Can the parent find the correct school and official website?
- Can they quickly tell whether the school is relevant to their child?
- Can they find the information needed to decide whether to enquire?
- Is the next action obvious on a phone?
- Does the enquiry or visit request actually reach the right person?
- Does someone respond consistently?
- Can the parent move into the formal application process without starting over?
A beautiful admissions page cannot rescue a broken follow-up process. A good admissions team also cannot recover every parent who gave up because the website buried the application link.
Separate prospective-parent needs from current-parent needs
School websites often become internal noticeboards over time.
The navigation fills with portals, calendars, circulars, homework links, staff resources, newsletters and existing-parent notices. Those things can be useful, but a prospective family has a different job to do.
They are usually asking questions such as:
- Is this school appropriate for my child’s age or year group?
- What curriculum or programme does it use?
- Where is it located?
- What does the school environment look and feel like?
- What is the admission process?
- When is the next intake?
- What documents will we need?
- What are the fees, or how can I get the current fee schedule?
- Can I visit before applying?
- Who can answer a specific question?
Do not make those parents decode a system organised around people who are already enrolled.
A clear top-level Admissions route can collect the important steps without turning the whole website into one enormous page.
Do not confuse the public website with the school portal
A school management system, student portal or parent portal usually solves operational problems: attendance, results, fees, assignments, records, communication or internal administration.
The public website has a different commercial and communication job:
- help new families discover the school;
- explain the school’s offer and fit;
- establish credibility;
- answer pre-admission questions;
- collect useful enquiries;
- route people into visits, applications or the appropriate next system.
Those systems can connect. They do not need to be the same interface.
For example, the public website can explain the admission process and then send a qualified parent into an application portal at the correct stage. That is usually clearer than putting Portal Login beside Apply Now and expecting every visitor to understand the distinction.
Put the information parents need before the form
A form should not compensate for missing information.
If every parent must contact the school simply to learn whether you accept their child’s age group, the website is creating avoidable work for both sides.
Before asking for an enquiry, make the important decision information easy to find. Depending on the school, that may include:
- age ranges, classes or year groups;
- curriculum or educational approach;
- day, boarding or hybrid arrangements;
- campus location and transport information where relevant;
- admission stages;
- application requirements;
- current or next intake dates;
- visit or open-day information;
- fee information, a downloadable fee schedule, or a clear way to request current fees;
- contact details for admissions.
You do not need to publish information that is genuinely private or changes too frequently to maintain accurately. But hiding basic decision information often creates low-quality enquiries rather than better-qualified ones.
Make the admission action obvious on mobile
Many parents will first encounter the school from a phone: a Google result, a shared link, social media, a WhatsApp message or a recommendation.
The mobile page should answer three things quickly:
- Is this the right school to keep considering?
- What do I need to know before I contact you?
- What should I do next?
Depending on the school and stage, the primary action might be:
- Book a school visit
- Ask an admissions question
- Request the prospectus
- Start an application
- Join the next-intake waitlist
Avoid making five actions equally prominent. A parent should not have to decide between Apply, Register, Enrol, Contact, Book, WhatsApp and Get Started without knowing which one actually advances the process.
For accessibility, readable content, keyboard-friendly navigation, clear labels and usable forms matter across devices. The W3C’s WCAG guidance is a useful reference when evaluating whether important journeys work for people with different access needs.
Keep the enquiry form short enough to finish
An admission enquiry is not necessarily an admission application.
If the school only needs enough information to route a parent and respond intelligently, a first enquiry form might ask for:
- parent or guardian name;
- phone or email;
- child’s intended class or year group;
- preferred intake or start period;
- whether they want a visit or a response;
- a short question or note.
The formal application can collect the detailed records later.
This distinction matters because asking a curious parent for a full application dossier too early adds friction without necessarily improving lead quality.
On the other hand, if the school is highly selective and the admissions team genuinely needs more information before speaking with a family, the form can be more structured. The fields should follow the real admissions process, not whatever form template came with the website theme.
Test what happens after somebody clicks Submit
This is one of the least glamorous parts of website work and one of the most important.
Submit the enquiry yourself on both phone and desktop and check:
- Did the form actually submit?
- Did the parent see a useful confirmation?
- Did the right staff member receive the notification?
- Did it arrive in spam?
- Is there a backup recipient if that person is unavailable?
- Can staff see which campus, class or intake the enquiry concerns?
- Is there a clear owner for responding?
- Can the team tell whether the parent later booked a visit or applied?
A website can report successful submissions while the admissions office receives nothing useful.
The whole system is:
page → form or call → notification → admissions response → visit/application → follow-up
Fixing the page but ignoring the remaining steps only moves the leak.
Show proof that answers a parent’s risk, not just a gallery
Prospective families are making a trust-heavy decision.
A wall of polished photographs can help them picture the environment, but proof becomes stronger when it answers real questions.
Useful proof may include:
- real campus and classroom photographs;
- clear leadership and teacher information where appropriate;
- curriculum or accreditation details that can be verified;
- safeguarding or pastoral information where relevant;
- facilities explained in context rather than merely listed;
- student work, activities or programmes presented accurately;
- testimonials with enough context to feel credible;
- transparent contact and location information.
Avoid manufactured certainty. If a programme is new, say what exists now rather than presenting future plans as established history.
Give admissions staff control over information that changes
Admission dates, fees, prospectus files, open days, notices and application status can change more often than the main website design.
If every small update requires the original developer, the site becomes stale because operational staff hesitate to touch it.
A practical website should make frequently changing admissions content editable through an appropriate CMS or admin workflow while protecting the parts that should not be accidentally broken.
The goal is not unlimited editing. It is safe ownership.
The school should also control foundational accounts such as its domain, DNS, hosting or deployment, analytics and recovery access rather than depending permanently on one freelancer’s personal account.
Help search engines understand the public admissions information
Search visibility cannot create demand by itself, but an official school website should make important public information easy for search engines and people to discover.
Google’s Search Essentials and broader Search Central documentation cover the technical and content foundations for making pages eligible and understandable in Google Search.
For a school, that means practical basics such as:
- indexable admissions pages rather than important information hidden only inside images or private portals;
- descriptive page titles and headings;
- stable, crawlable links;
- useful information about the school and its programmes;
- accurate contact and location details;
- sensible redirects when old admissions URLs are replaced.
Do not create dozens of thin pages for every possible phrase. One strong page that fully answers a real parent question is better than many pages that only swap keywords.
Measure more than website visits
Traffic tells you somebody arrived. It does not tell you whether the admissions journey works.
The more useful measures are closer to the school’s actual process:
- admission enquiries;
- booked visits or open-day registrations;
- prospectus requests if they matter;
- started applications;
- completed applications;
- qualified applicants;
- enrolments where attribution is practical.
You do not need perfect attribution before improving the system. You do need enough visibility to avoid celebrating traffic while parents are abandoning the next step.
If the website already receives visitors but produces very few useful enquiries, my broader website traffic but no leads guide gives you another diagnostic framework.
Fix the current site or rebuild it?
Do not assume a weak admissions journey requires a new website.
Repair the existing site first when:
- the pages load reliably;
- mobile layout is fundamentally usable;
- staff can update content safely;
- navigation can be simplified without fighting the whole theme;
- forms and notifications can be repaired;
- the domain, analytics and deployment are under proper control.
A larger redesign or rebuild becomes reasonable when problems are systemic:
- the mobile experience is broken across the site;
- navigation cannot support prospective and current families clearly;
- the CMS makes routine updates risky or impossible;
- forms, portals and third-party systems are badly tangled;
- nobody can safely deploy or maintain the code;
- the school does not control critical accounts;
- old architecture makes every small improvement expensive.
The decision should come from the failure pattern, not from whether the homepage looks old.
A practical admissions website improvement order
If I were reviewing a school site for admissions, I would normally work in this order:
- Test the existing enquiry and application journey. Find broken forms, confusing links and missed notifications first.
- Clarify admissions ownership. Decide who responds, what qualifies an enquiry and where each lead should go.
- Create one clear Admissions route. Give prospective families a reliable place to understand the process.
- Fix the mobile next step. Make visits, enquiries or applications obvious.
- Strengthen proof and decision information. Answer the questions that block confidence.
- Separate public and portal journeys. Keep existing-family tools available without making them the admissions navigation.
- Make changing information editable. Let authorised staff maintain dates, fees, files and notices safely.
- Measure the admissions outcomes. Connect website activity to visits, applications and enrolments where practical.
- Rebuild only if the underlying system keeps blocking those improvements.
That order keeps the project tied to admissions outcomes instead of redesigning pages without knowing what was actually failing.
The website should reduce uncertainty before the admissions team speaks
A prospective parent should arrive at the first conversation knowing more than they knew before opening the website.
They should understand whether the school appears relevant, what the admissions process looks like, what they need to do next and how to reach a real person when they have a question.
That is the website’s job in the admissions system.
If your school website is difficult to update, confusing prospective families, losing enquiries or mixing the public website and parent portal into one messy journey, see my web design service or tell me what needs to change.
