Personalization
Keyspider tailors search results to each user's role, profile, and past behaviour. Students see different results to staff. Citizens on mobile see location-relevant content first. Every audience gets a search experience built for them — without creating separate indices.
How it works
Audience segments are defined
In the admin console, you define audience segments — by SSO role, IP range, cookie, URL parameter, or other signals — and map them to result sets.
Results are filtered and ranked per segment
At query time, Keyspider identifies the user's segment and applies the relevant ranking weights, content filters, and boosting rules automatically.
Behaviour is continuously learned
Click signals and zero-result rates feed back into the ranking model, improving relevance for each audience segment over time without manual intervention.
Use cases
University student portals
Enrolled students see course and library results. Staff see HR and admin content. Prospective students see admissions and course information. Same search bar, separate experiences.
Government multi-agency portals
Internal staff searching through an authenticated portal see restricted policy documents. Public visitors on the same domain see only publicly available content.
Enterprise intranets
Sales teams get product and pricing documents first. Engineering teams get technical specs. HR content is surfaced for new starters. One index, many roles.
Healthcare information systems
Clinical staff see patient-facing materials differently from how they appear for administrative staff, with role-appropriate content access controls enforced through the search layer.
Ready to give your users better answers?
AI Search, AI Assistant, and Workplace Search. Deployed in days, not months. See it live on your own content.
No credit card required · Live in 2 weeks · Cancel anytime