Parents don’t type “Pupil Transportation.” They type “bus,” or “bus stop,” or “my son missed the bus what do I do.” Nobody types “Multi-Tiered System of Supports.” They type “my daughter is behind in reading, who do I talk to?”
District websites are built the way districts are organized: by department, program, and acronym. That makes sense to the people who work there. They know registration sits under central office and that the reading help a parent wants has a four-letter name. Families don’t know the org chart, and they shouldn’t need to.
The website’s search box usually widens the gap. Most site search matches words, not meaning. A parent who types “bus” can get the board minutes where the bus contract was approved, while the page with the bus stop lookup never appears because its title says “Pupil Transportation.”
The fix starts with the pages. One of the best-known rules in web design, from usability researcher Jakob Nielsen, is that a site should speak its users’ language, using words and concepts familiar to them rather than internal jargon. Title pages with the words families use. Spell out acronyms the first time they appear. Put the phone number on the page, not two clicks away.
To learn which words families use, read what they type. A website chatbot’s question log is a running list of the exact words families use, misspellings and all, in their own languages. It’s the most honest survey your district will ever run, and it shows you which page titles nobody would ever think to search for.
A good chatbot closes the rest of the gap by matching what a family means, not just what they typed. “Bus” should find “Pupil Transportation.” “Behind in reading” should find the intervention page. And the answer should link to that page, so the family knows where to look next time.
AskK12 matches each question to the meaning of your district’s pages, not only their words, and links the page it used.