Why Schools Need a Modern Website for Admissions and Parent Communication

A family visiting a school website for the first time is trying to settle three questions quickly: is this the right kind of school for our child, is there a process we can follow, and how do we speak to someone. A modern website answers those questions in that order, on a phone, without making a parent hunt through menus or download a brochure to find the basics.

The questions sound simple, but they arrive in a particular sequence. Parents rarely start with facilities or the principal’s message. They start with their own situation — a child of a certain age, a move to a new area, a change of board, a sibling already enrolled — and look for the part of the site that speaks to it.

• Fit: what the school believes about learning, what the day looks like and what kind of child tends to thrive here.
• Programme: which classes, stages or streams are offered, and what is taught at the stage that matters to them.
• Admissions: whether admissions are open for their child’s grade, what the process is, what eligibility the school publishes and when the key dates fall.
• Practicalities: location, timings, transport, and where the school publishes fee information.
• People: who leads the school and who will teach their child.
• Next step: how to enquire, book a campus visit or begin an application.

Current parents come with different questions. They want to know what is happening this week, whether a date has moved, where a notice has been published and who to contact about something specific. Admissions teams have a third need that the website quietly serves: when the basic information is clear online, conversations with families can focus on fit rather than on repeating timings and document lists over the phone.

This article follows the path a family actually takes — from their need, to a programme, to the admissions information the school publishes, to the wider school information that builds confidence, and finally to an enquiry, a visit or an application. That last step is a beginning, not an outcome. An enquiry is not an admission, and good websites for schools never suggest otherwise.

The opening of a school website should state, in one or two plain sentences, what kind of school this is: its stages, its board or curriculum where relevant, its setting and what it believes about how children learn. If a parent reads only the first screen, they should still be able to describe the school accurately to someone else.

Many school homepages open with a large banner, a motto and a welcome message that could belong to almost any institution. None of those is wrong, but none of them helps a family decide. “Nurturing tomorrow’s leaders” tells a parent nothing about whether this is a co-educational day school with a primary wing, a senior secondary school with science and commerce streams, or a pre-primary centre with a play-based approach.

Philosophy a parent can picture

A school’s philosophy becomes useful when it is described in terms of what happens in a classroom. Instead of abstract values, describe the patterns a visiting parent would notice: how early years learning is structured, how much of the week involves projects or practical work, how the school approaches reading, how pastoral care is organised and how teachers communicate with families. Specific descriptions are more believable than superlatives, and they help the right families recognise themselves.

The principal’s message, placed where it helps

A message from the principal or head of school still has a place, but it works better as a considered page than as a long paragraph on the homepage. Keep it signed, dated where it refers to a particular year, and focused on what the school is trying to do rather than on general statements about education. A short excerpt with a clear route to the full message is usually enough on the homepage.

Distinguishing features, stated carefully

If the school has genuine distinguishing features — a particular language offer, a boarding option, a sports programme, provision for children with additional learning needs, a strong arts tradition — name them plainly and give each one a page that explains it. Avoid claims that cannot be checked, such as being “the best” or “the leading” school in a city. Parents discount them, and they add nothing that a clear description would not.

Programme pages should be organised around the stages parents think in — pre-primary, primary, middle, secondary and senior secondary, or whatever structure the school actually uses — and each page should explain what a child experiences at that stage. A single long “Academics” page that tries to cover every class at once rarely answers anyone’s question well.

Organise by stage, not by department

Parents looking at a nursery place are not interested in senior secondary stream options, and a family considering Class 11 does not need to scroll past the early years approach. Give each stage its own page with its own address, so it can be shared, found in search and reached directly from the admissions section. Where a school runs more than one curriculum or board, make that choice visible early and keep the pages clearly separate.

What each programme page should carry

• The classes or grades the stage covers, and the entry age the school publishes where that applies.
• A short description of the learning approach at this stage, in the school’s own words.
• The subjects or learning areas offered, including optional subjects and streams where relevant.
• How assessment and progress reporting work, in general terms.
• Co-curricular activities, clubs or sports typical of this stage.
• The school day: timings, and anything distinctive about the routine.
• A route to the admissions information for this stage, and a way to enquire.

Describe curriculum without overclaiming

Curriculum descriptions should stay factual. Name the board or framework the school follows if it follows one, describe how the school delivers it and what it adds, and avoid statements about outcomes the site cannot substantiate. If a subject combination runs only when enough students choose it, say so. If streams or electives depend on availability or published criteria, say that too. A parent who discovers a condition after enquiring loses trust faster than one who read it clearly upfront.

It also helps to separate the public programme overview from the learning material itself. The website explains what is taught and how; assignments, worksheets, recorded lessons and class resources belong in a platform used by enrolled students, not on public pages.

The admissions section should explain the process in order, show the eligibility and age information the school publishes, and state the key dates for the current cycle. When those three things are clear, families arrive at the enquiry step already knowing what comes next, and the admissions office spends less time on questions the page could have answered.

The process, step by step

Write the admissions process as a numbered sequence rather than a paragraph. A typical pattern looks like this, though every school should describe its own:

1. Read the programme and admissions information for the relevant stage.
2. Submit an enquiry or register interest.
3. Visit the campus or attend an information session, where the school offers one.
4. Complete the application and provide the documents the school lists.
5. Take part in any interaction, assessment or meeting the school describes for that stage.
6. Receive the school’s decision and, if a place is offered, the steps to confirm it.

Each step should say what the family does, what the school does and what happens next. Avoid vague phrases such as “the admissions team will get back to you” without any sense of what that involves or when.

Age, grade and programme information

Where the school publishes age criteria, entry points or grade-wise availability, put them in one clear place and keep them consistent with the programme pages. Age and eligibility rules can depend on a school’s board, its state or local authority and its own policies, so the website should reflect what the school has decided and what applies to it — not a general rule copied from another school’s site. Schools should check the requirements that apply to them before publishing, and review the page whenever those requirements change.

Dates, documents and fee information

Admissions pages usually go stale at the dates. Show which cycle the information refers to, so a parent can tell at a glance that it is current. List the documents families are asked to provide, and explain where fee information is published and what it covers. Some schools publish a full fee structure, some share it on request and some share it at a particular stage of the process; the website should be honest about which approach the school takes, and never imply that a place is assured once a form is submitted.

Finally, add a short admissions FAQ at the foot of the section. Questions about sibling applications, mid-year transfers, changes of board, transport availability and waiting lists come up again and again, and answering them once on the page saves time for families and staff alike.

After the programme and admissions information, families look for evidence that the school can deliver what it describes. Facilities pages show the environment a child will spend their days in, and faculty and leadership pages show the people responsible for it. Both work best when they are specific, current and honest about what exists.

Facilities that are explained, not just photographed

A gallery of classrooms and labs is a start, but a parent learns more when each facility is explained. Say what the space is used for, which stages use it and how it supports the programme. A science laboratory page might describe how practical work is scheduled at different levels; a library page might explain borrowing and reading programmes; a sports page might describe the activities on offer and how the grounds are shared across the week.

Only show facilities that exist and are in use. If a new building is under construction, describe it as planned rather than presenting drawings as finished spaces. Safety-related arrangements such as supervision, medical room provision or campus access can be mentioned in general terms, without publishing detail that would compromise security.

Faculty and leadership pages

Leadership pages should introduce the principal, the heads of sections and, where relevant, the governing body or management, with names, roles and a short professional description. Faculty pages vary more from school to school. Some publish every teacher with a photograph and qualifications; others introduce heads of department and describe the wider team collectively. Either approach can work, provided the information is accurate and staff have agreed to what is published about them.

The most common problem with faculty pages is age. A list of teachers who left two years ago tells a parent that nobody maintains the site. If the school cannot commit to keeping individual profiles current, a well-written description of how teachers are recruited, supported and trained, with named section leaders, is more trustworthy than an outdated directory.

For families already at the school, the website is most useful as a dependable public reference: the academic calendar, term dates, holidays, public events and general notices that apply to everyone. It should be the place a parent checks when a forwarded message is unclear, and it should always agree with what the school has communicated elsewhere.

Many schools rely on messaging groups, printed circulars and phone calls, and those channels remain useful. The difficulty is that information scattered across them is easy to miss and hard to find again. A calendar and notices section gives general information one stable home.

What belongs on the public calendar

• Term dates, holidays and the shape of the academic year.
• Whole-school events such as annual days, sports days, exhibitions and open days.
• Admissions events and information sessions for prospective families.
• General examination or assessment periods, where the school chooses to publish them.
• Parent–teacher meeting windows described at a whole-school level.

What does not belong there

Class-specific messages, individual reminders, results, attendance alerts and anything relating to a particular child should not be published on the open website. Those belong in a login-protected parent portal, a school app or whichever communication system the school uses for class-level messages. The line is easy to state: if the information concerns the whole school and would be fine for any member of the public to read, it can go on the website; if it concerns a class, a group of students or a family, it belongs behind a login.

Keeping notices trustworthy

Every notice should carry its date of publication and, where relevant, the date it applies to. Old notices should be archived rather than left on the homepage. If a date changes, update the calendar and the notice together and mark the change clearly, so a parent reading an older message can see the correction. A notices page that is kept current is one of the most practical ways a website shows that the school is well organised.

The practical pages — policies, transport, contact and location — are rarely the reason a family shortlists a school, but they are often the reason a family hesitates. They should be easy to reach from any page, short enough to read on a phone and visibly maintained.

Policies the school actually publishes

Publish the policies the school has adopted and is willing to share publicly — for example admissions, child protection, anti-bullying, fee refund, uniform and privacy, depending on the school. Some boards, authorities or affiliation bodies expect schools to publish particular information or disclosures on their websites. Those expectations differ, so schools should check the requirements that apply to them rather than working from another school’s list. What matters on the website is that each published policy is current, dated and available as a readable page, not only as a scanned document.

Transport, where the school offers it

If the school runs or arranges transport, explain the general coverage area, how families request a place and where they can find timing information. Detailed route lists, pick-up points and live tracking usually belong in a parent-facing system rather than on public pages, both because they change often and because they reveal where children are at particular times.

Contact and location

Contact information should include the school’s address, a map, the main phone number, an admissions contact and office hours, with numbers and addresses that can be tapped on a phone. If the school uses WhatsApp for admissions questions, say which number and what it is for. Directions for first-time visitors — the correct gate, parking and where to report — make a campus visit far less stressful, and they are easy to overlook.

Keep the school’s name, address and phone number identical wherever they appear: on the website, in its map listing and in any directories the school controls. Inconsistent details confuse families and weaken local search visibility.

The enquiry path should give a family one obvious way to take each next step — ask a question, book a visit or start an application — from every programme and admissions page. Each form should ask only for what the school needs at that moment, and each should end in a clear confirmation that explains what happens next.

Enquiry forms

An enquiry form for prospective families usually needs the parent’s name, a phone number, an email address, the child’s intended grade, the academic year of interest and a space for questions. Resist the urge to ask for everything upfront. Detailed family information, previous school records and documents belong later, in the application itself. A short form that a parent can complete on a phone, with large fields and visible labels, is more likely to be completed accurately.

The confirmation matters as much as the form. After submission, show a message that thanks the family, tells them how and roughly when they will be contacted, and offers a useful next step such as the visit booking page or the admissions FAQ. Avoid wording that sounds like an offer. “We have received your enquiry” is accurate; anything that implies a seat is being held is not.

Campus visits and information sessions

Campus visits are often where families make up their minds, so booking one should be straightforward. Show the days and times visits are offered, or let families request a slot, and confirm how long a visit takes, what to bring and who they will meet. If the school holds open days or information sessions, list them on the calendar and link them from the admissions section.

Application forms

Some schools accept applications online, some provide a form to complete and return, and some issue the application only after an enquiry or visit. Whichever approach the school takes, the website should describe it accurately. Where an online application exists, it is usually provided by the school’s admissions system rather than built as a stand-alone web page, because the application becomes a record that staff need to review, update and keep secure. The website’s job is to explain the process and send families to the right place.

Clear ownership of every enquiry

Every form submission should arrive somewhere a named person or team is responsible for. An enquiry that lands in an unmonitored inbox is worse than no form at all. Before launch, agree who receives each type of enquiry, how the school aims to respond and where enquiries are recorded, so that nothing depends on one member of staff remembering to check.

Trust on a school website comes from accurate, current and specific evidence: real photographs of the campus and school life, clear descriptions of what the school does, visible people and dated updates. It does not come from large numbers, unverified rankings or promises about outcomes.

Photography that shows the school as it is

Families can usually tell stock photography from real school life. Use photographs taken at the school, in ordinary moments as well as at events, and keep them reasonably current. Show classrooms in use, play areas, libraries, labs, assemblies and activities. Good photography does not need to be elaborate, but it should be well lit, sharp and chosen with care.

Photographs of children need particular attention. Follow the school’s own consent policy and any rules that apply to it, keep a record of which images families have agreed to, avoid publishing names alongside identifiable photographs of students, and remove images promptly when consent is withdrawn. Group shots and images where individual children are not the focus are a sensible default.

Video and virtual tours

A short walk-through video or guided tour can help families who cannot visit easily. Keep videos brief, add captions and make sure they do not slow down the pages they sit on. Video should complement written information, not replace it; a parent on a weak connection still needs to be able to read the admissions process.

Proof that does not overstate

Achievements can belong on a school website when they are accurate, verifiable and presented with context — a named competition, a dated event, an accreditation the school genuinely holds. What should never appear are invented or unverifiable figures, results that cannot be substantiated or implied guarantees about a child’s future. Parent testimonials should be real, attributed with permission and published only if the school is comfortable standing behind them. If the school has none yet, a clear description of its approach and a well-run campus visit will persuade more than filler ever could.

The public website handles information, discovery, admissions information and enquiries, trust and navigation. School systems handle internal workflows — admission records, attendance, fees, grades, class-level communication and student learning — through tools such as an admissions CRM, a school management system or ERP, a parent portal and an LMS, depending on what each system actually does. The two should connect at clear points, but they should never be confused.

The table after this section sets out that division area by area. It is a useful reference during a redesign, because many problems schools describe with their websites are really problems of placement: private information published publicly, or public information buried inside a system that families cannot see before they join.

Read across the rows and the pattern is consistent. For admissions, the website publishes the process, criteria and key dates as the school sets them, while application records and their status live in the admissions workflow that a form feeds. For enquiries, the website offers enquiry and campus-visit forms, and follow-up happens in a CRM or admissions module with clear ownership of every enquiry. For fees, the website explains what fees cover and where the school publishes them, but invoices, payments and receipts belong in a payment system reached by a secure link. For notices, the website carries public events and the school calendar, while class-level messages go through the school’s own channels. Student records never appear on the public site at all, and assignments and learning material stay in an LMS, linked for enrolled students only.

This division protects families as well as the school. A public website is built to be read by anyone, indexed by search engines and shared freely. That is exactly right for a programme page and exactly wrong for a report card. Keeping student data, fee accounts and class communication behind proper logins is part of treating families’ information with care.

It also keeps expectations honest. A website can make a school easier to discover, understand and contact. It cannot take attendance, reconcile fees or manage a timetable, and adding a login button to the header does not turn it into a school management system. When a school needs those capabilities, they come from systems designed for that work, chosen according to what the school actually needs.

A school website connects to school systems at a small number of deliberate points: enquiry and application forms that pass information into an admissions workflow, secure links to a parent portal or fee payment system, and links for enrolled students to a learning platform. Everything else on the website should work on its own, without depending on those systems.

Admissions CRM or admissions module

When enquiries arrive only as emails, follow-up depends on individual inboxes and memory. An admissions CRM, or the admissions module within a wider school system, records each enquiry, who owns it, what has happened and what should happen next. The website’s role is to capture the enquiry accurately — the grade and year of interest, the page it came from and the family’s agreement to be contacted — and pass it on. An enquiry and follow-up CRM earns its place when a school handles enough enquiries that a shared record, reminders and a view of each family’s stage genuinely save effort; a small school with a handful of enquiries a week may manage well with a shared inbox and a clear routine.

Some schools also use messaging tools to acknowledge enquiries and remind families about booked visits. If that is part of the plan, keep messages useful and expected, and make sure families have agreed to be contacted that way.

Parent portal and school management system or ERP

A school management system or ERP typically covers internal operations such as student information, attendance, fee management, timetables, examinations and staff records, depending on the product. A parent portal, often part of that system, gives families login-protected access to their own child’s information and to class-level messages. The website links to the portal login and explains, in general terms, what parents can do there; it does not display any of that information itself. Evaluating school management and ERP software is a separate decision from redesigning the website, and the two are best scoped separately even when they are planned together.

Learning platforms

A learning management system holds course material, assignments, submissions and feedback for enrolled students. The website’s connection to it is usually a link for students and parents who already have accounts, and perhaps a general description of how the school uses digital learning. Public programme pages describe the curriculum; the platform supports its delivery.

Does every school need every system?

No. The right set of systems depends on the school’s size, structure, existing tools and the problems it is actually trying to solve. A single-campus primary school and a multi-branch senior secondary group have very different needs. Many schools already use a system for fees or records and simply need the website to link to it clearly. Start from the work that is currently difficult — lost enquiries, fee reconciliation, scattered communication — and choose tools for that work, rather than assuming a new website must arrive with a full software stack.

A school website must work well on a phone first, be usable by people with different abilities and load quickly on ordinary mobile connections. Many families look at school websites on a phone, often in short moments between other responsibilities, so a site that is slow, cramped or hard to navigate on a small screen fails at the point it matters most.

Mobile experience

• Navigation that shows the main paths — About, Programmes, Admissions, School life, Parents, Contact — without deep nested menus.
• A persistent, easy-to-reach way to enquire or call the admissions office.
• Text that is readable without zooming, and tap targets large enough for a thumb.
• Forms that bring up the right keyboard for phone numbers and email addresses, with clear error messages.
• Important information as page text, not locked inside images or PDFs that are awkward to read on a phone.

Accessibility basics

Accessibility means every parent, student and member of staff can use the site, including people who rely on screen readers, keyboard navigation or larger text. The basics are well understood: enough contrast between text and background, meaningful headings in a logical order, descriptive alternative text for informative images, captions on videos, form fields with visible labels and focus states that show a keyboard user where they are. Schools should also check whether particular accessibility standards apply to them. Beyond any requirement, an accessible site is simply clearer for everyone.

Page speed and reliability

Slow school websites usually share a handful of causes: very large photographs uploaded straight from a camera, auto-playing video banners, heavy sliders, too many third-party widgets and hosting that struggles when many parents visit at once, such as when admissions open or an urgent notice goes out. Compress and correctly size images, avoid auto-playing media on key pages, remove widgets that do not earn their place and choose hosting that can handle predictable peaks. Reliability matters as much as speed: a website that goes down during an admissions window leaves families without an official source of information at exactly the wrong moment.

Families find schools through two broad kinds of search: local searches that combine a type of school with a place, and admissions-intent searches that ask about a specific stage, process or date. A school website becomes visible for both when it has a clear page for each topic, accurate location information and a consistent presence on maps.

Local search

Searches that pair a board with a neighbourhood, a stage with a city, or simply look for schools near home depend heavily on location signals. The school’s map listing should be claimed, accurate and consistent with the website: the same name, address, phone number, office hours and category. Current photographs and considered responses to reviews help families judge the school before they click through. The local search fundamentals that apply to any organisation serving a neighbourhood apply to schools too, with extra care because reviews and photographs involve children and families.

Admissions-intent search

Admissions-intent searches are more specific: nursery admission for a particular year, the age criteria for a grade, whether a school offers a certain stream, or when registration opens. They are best served by dedicated, well-titled pages — one for each programme stage, a clear admissions process page and a dates page that names the current cycle. A homepage that tries to hold everything cannot match a page written for the question.

Page basics that search engines and parents both use

• A unique, descriptive title and meta description for each page, naming the school and the topic.
• One clear main heading per page, with sub-headings that follow the content.
• Readable page addresses for programmes and admissions rather than numeric identifiers.
• Links between related pages, such as from a programme to its admissions information.
• Text versions of information that might otherwise sit only in a prospectus PDF.

Ongoing search and answer-engine optimisation for a school is less about tricks and more about keeping these pages accurate, well structured and current, cycle after cycle.

A school website is easier to use, and easier for search engines and AI assistants to understand, when each page answers its main question in its opening lines and the pages are arranged the way families think. Clear architecture and direct answers serve the same purpose: they get a parent to the right information with the least effort.

Answer first

Open each important page and section with a sentence or two that answers the question directly, then add detail. An admissions page might open by saying which grades are open for the coming year and how to begin. A transport page might open by describing where the school provides transport and how to request it. This helps a parent skimming on a phone, and it gives search engines and assistants a clear summary to draw on — so the school’s own wording, rather than someone else’s guess, is more likely to be what a family sees.

FAQs on the site

Well-chosen FAQs reduce repeated calls and help people find answers through search. Gather the questions the admissions office and front desk actually receive, answer each in a few sentences and place them on the pages they relate to: admissions questions on the admissions page, transport questions on the transport page. Keep answers consistent with the policies and dates published elsewhere, and review them at the start of every admissions cycle.

A content architecture for schools

A common and workable structure looks something like this, adapted to each school:

• About: philosophy and approach, the principal’s message, leadership, history and the affiliations the school holds.
• Programmes: one page per stage, plus pages for distinctive offers.
• Admissions: process, eligibility and age information, dates, documents, fee information as the school publishes it, the admissions FAQ, and enquiry and visit booking.
• School life: facilities, co-curricular activities, pastoral care, photography and news.
• Parents: calendar, notices, policies, transport, uniform, and portal and payment links.
• Contact: address, map, phone numbers, office hours and directions.

Each section should have a clear owner inside the school. Architecture rarely fails because it was designed badly; it fails because nobody is responsible for the pages within it.

Structured data where appropriate

Structured data is code that describes a page’s content to search engines in a consistent format — for example, identifying the school as an educational organisation with its name, address, contact details and logo, or marking up genuine events and FAQs. It should describe only what is visibly true on the page, and it never substitutes for clear content. For a non-technical introduction, schema markup explained in plain language is a useful starting point before discussing it with a developer.

A school website stays useful only if named people keep each part of it current, and if the school can see, in simple terms, how families are using it. School websites rarely fail at launch; they fail in the second year, when dates, notices and staff pages quietly drift out of date.

Who updates what

Assign ownership by section rather than making one person responsible for everything. The admissions team owns admissions pages, dates and FAQs. The office or communications lead owns the calendar and notices. Section heads review programme pages each year. Leadership approves policies and the principal’s message. A named person looks after photography consent records. The admin area should let these people make updates without technical help, with roles that limit who can publish or change sensitive pages.

A termly and annual rhythm

• Before each admissions cycle: update dates, eligibility information, documents, fee information as published and the admissions FAQ.
• Each term: refresh the calendar, archive old notices, add current photographs and check that forms still reach the right people.
• Each year: review programme pages, leadership and faculty information, policies and contact details.
• Whenever something changes: update the website and the map listing together.

Analytics that answer school questions

Analytics should answer a few practical questions rather than produce reports nobody reads. Which programme pages do families visit? How many enquiry and visit forms are submitted, and from which pages? Do families leave the admissions page without taking a step? Which searches bring people to the site? Track form submissions as events, keep reports simple and review them with the admissions team at regular intervals. Set analytics up with privacy in mind: collect only what the school needs, respect consent choices and never send personal details from forms into analytics tools.

Analytics can show where families hesitate; it cannot tell the school why. Pair the numbers with what the admissions office hears, because the questions families ask on the phone often point straight to the page that needs rewriting.

Most school website problems fall into a few recognisable patterns: information that is out of date, information that is hard to find on a phone, and information in the wrong place. Each is fixable, and each is easier to prevent during a redesign than to repair afterwards.

• Last year’s admissions dates still live. Little undermines confidence faster than an admissions page for a cycle that has already closed.
• Essential information only in PDFs. Prospectuses and circulars are useful downloads, but the process, dates and contact details should be readable page text.
• A homepage that tries to say everything. Sliders, tickers, welcome messages and long link lists compete for attention and hide the paths families need.
• Enquiry forms that go nowhere. Submissions arriving in an unmonitored inbox, or no confirmation after submitting, leave families unsure whether anyone received their message.
• Private information on public pages. Class lists, individual results, student names beside photographs or detailed pick-up points should never be on the open website.
• Treating the website as the school system. Expecting a website plugin to manage fees, attendance or class communication usually produces a fragile and insecure workaround.
• Stock photography and generic copy. Families want to see this school, not a school.
• Unverifiable claims. Superlatives, invented figures and implied guarantees weaken trust rather than build it.
• Outdated staff pages. Teachers who have left still listed as current.
• Inconsistent contact details. Different phone numbers on the website, the map listing and printed material.
• Nobody owns the site. A site built well and never maintained becomes a liability within a year or two.

If several of these apply at once, the fix is usually structural rather than cosmetic. Replacing the banner and colours will not help if the admissions information is still scattered, the forms still go nowhere and the notices still have no owner.

A school website redesign goes best when it starts from the family’s path and the school’s information rather than from visual design, and when launch is treated as the start of a maintenance routine. The checklist below follows that order; a general website redesign checklist covers the wider technical and migration steps in more depth.

Before design

1. List the questions prospective and current parents ask most often, with input from the admissions office and front desk.
2. Audit existing pages: what is current, what is outdated, what is missing and what should move behind a login.
3. Agree a site structure around the family path: need, programme, admissions, school information, then enquiry or visit.
4. Decide which school systems the website will link to or send information to, and which it will not.
5. Assign an owner for each section and agree the update rhythm.

Content and build

1. Write answer-first programme, admissions and practical pages in the school’s own voice.
2. Confirm eligibility, dates, fee information and policies against what the school has decided and the requirements that apply to it.
3. Commission or gather current photography, with consent records in order.
4. Build short enquiry and visit forms with clear confirmations and named recipients.
5. Check mobile layouts, accessibility basics and page speed on real phones.
6. Add accurate titles, descriptions, links between related pages and structured data where appropriate.

Launch and after

1. Redirect old page addresses to their new equivalents so existing links and search listings keep working.
2. Test every form end to end, including what the family sees and what the school receives.
3. Update the map listing and any profiles the school controls with consistent details.
4. Set up analytics for form submissions and key pages.
5. Train section owners on the admin area.
6. Schedule the first content review before the next admissions cycle.

What a school website costs depends on the number of stages and pages, how much writing and photography is needed, the forms and system connections involved, the admin tools staff will use and the level of ongoing maintenance. Rather than quoting a figure here, the starting points on our pricing page show how those factors are scoped.

Whoever does the work, a premium website build for a school should be judged by the test running through this article. Can a family on a phone understand the school, find the admissions information that applies to their child and take a clear next step? Can current parents rely on what they read? If the answer to both is yes, and the school’s systems handle the private work behind the scenes, the website is doing its job.