Your website doesn’t need to know who someone is to better understand what they need. See how intent-driven experiences can make personalization more useful, immediate, and privacy-conscious.
A website can know your name and still have no idea what you need.
Much of what passes for personalization online changes what a visitor sees without reducing the work they have to do. The page greets them, swaps a banner, or recommends content based on past clicks. They still have to navigate the site and piece together an answer.
I’d judge personalization by a more practical standard: does it help someone understand their options and take the next step?
Traditional approaches often rely on identity, audience segments, browsing history, or CRM data. That creates a tricky balance: organizations need to handle personal data carefully, while visitors don’t know whether the experience is worth the data they're sharing.
A visitor’s question gives you context you might never get from a profile. Someone asking about part-time postgraduate study has already told you something useful about what they need.
Conversational search can use that context to draw an answer from your content, without requiring a persistent profile. You still have to maintain the content, check the answers, and make sure the suggested next step actually goes somewhere useful.
Identity-based personalization can work well in authenticated services, where people knowingly sign in and expect to be remembered. This works seamlessly on streaming, social media, and ecommerce platforms, where accounts and extensive histories of behavior or purchases inform recommendations. Student portals and customer accounts can similarly surface relevant information based on what they already know.
On open websites, where this history is usually unavailable, personalization is more complex. It can require connecting multiple systems, defining audience segments, creating content variations, and coordinating teams across marketing, technology, privacy, and security.
Even with that investment, the result can still be too broad. Knowing that a visitor is a prospective student doesn’t reveal which program they’re considering, whether cost is their main concern, or what they hope to do next. Identity provides context, but it may not reveal the need driving the visit.
That’s a lot of ongoing work for an experience that may still miss the visitor’s actual question. The integrations need maintaining, the segments need reviewing, and the content variations need owners. Before investing in that machinery, I’d want evidence that it helps people complete the task they came for.
Intent-driven personalization uses what a visitor is trying to accomplish in the moment, rather than relying only on what an organization already knows about them.
Conversational Search, a capability of Squiz Funnelback Search, generates answers from a structured question-and-answer foundation prepared by Content Intelligence from monitored website content. Teams approve which topics it can use. The visitor’s question and conversation context shape the answer, with citations back to supporting sources.
The visitor supplies the context instead of leaving the website to infer everything from a profile or past clicks. You still need relevant content behind the answer.
The visitor supplies the context instead of leaving you to infer it from past clicks. The experience can then bring together information that would otherwise take several pages to find.
Intent-driven personalization is most useful when people arrive with complex questions and the relevant information is spread across publicly accessible website pages. The information needs to be in the monitored content; a search interface doesn’t give you access to the systems behind it.
The following examples show how it can reduce the work required to understand the available options and take the next step, while still leaving room for useful discovery.
A prospective student might ask:
I have five years of experience in communications and want to move into data analytics. Which postgraduate programs could fit, what would they cost, and can I study part-time?
A conversational search experience could bring together relevant programs, entry requirements, indicative fees, scholarships, study modes, and the next open day or enquiry route.
The student could refine the question, compare options, and move towards a decision without starting again elsewhere on the site.
A business leader might ask:
My company is expanding overseas. Which legal, tax, and compliance services might we need, and where should we begin?
A conversational search experience could draw together relevant expertise, service options, practical guidance, and supporting case studies, then suggest an appropriate consultation or next step.
Instead of requiring the visitor to understand the firm’s internal practice structure, it could organize the response around the outcome they’re trying to achieve.
A resident might ask:
I’ve recently lost my job. What support could I be eligible for, what evidence will I need, and how do I apply?
A conversational search experience could bring together published eligibility criteria, required documents, and application steps, with links to the relevant services.
The person could ask follow-up questions to understand the published guidance and find where to apply. That should help them navigate the process, without treating the answer as a decision about their eligibility.
All of these examples depend on what the source content contains. Fees, deadlines, and eligibility requirements need links back to authoritative pages so people can check the details before acting. Conversational Search can retrieve figures; I wouldn’t rely on it to calculate costs or make a high-stakes decision.
Discover how Conversational Search can use trusted content to provide relevant answers and guide people towards an appropriate next step.
The experience doesn’t need a persistent personal profile to respond to a question. That doesn’t mean the interaction disappears when the visitor leaves. Conversational Search records questions and answers, and permissioned administrators can review and export them.
People can put personal or sensitive information into a question. Teams still need to decide who can access those records, how long they are retained, and what visitors are told. Those decisions belong in the design work, before launch.
Authenticated personalization still has a role when people knowingly sign in and expect a service to remember them. On an open website, responding to a question and building a personal profile are separate decisions.
A conversational search interface can make a website feel more intelligent, but it can’t compensate for weak foundations.
If the source content is outdated, contradictory, inaccessible, or poorly governed, the resulting experience will reflect those issues and remain unhelpful. If permissions are unclear, the system may retrieve information that shouldn’t appear in a public response. If important policies exist only in unstructured documents, the experience may miss the detail that changes the answer.
Trusted, current, and approved content is therefore a prerequisite for useful personalization.
This is where content governance becomes part of experience design. Teams need to define authoritative sources, ownership, review cycles, and rules for what the experience can retrieve and present.
They also need somewhere useful to send the visitor next: a program page, published eligibility guidance, an event listing, an application form, or the right contact. Helping someone find a form is different from completing it for them. Be clear about what the experience actually does.
See how Squiz Content Intelligence can help teams find missing details, conflicting information, and unclear language in the content behind conversational answers. Your team still needs to review the findings and fix the source.
Organizations don’t need to personalize an entire website at once. Nor do they need to replace working authenticated experiences or abandon conventional navigation.
A suggestion is the practical approach below, beginning with one audience need that is both valuable and difficult to resolve today.
Start small enough that you can inspect where the experience fails. Review unanswered questions, check the source content, and fix the gaps before adding another use case. Expanding coverage is easier than keeping every answer dependable.
On an open website, I’d start with the question the visitor is asking. Use it to surface relevant information and make the next step easier. Keep conventional navigation available for people who prefer it.
Then check whether the experience actually helps. Can people make a decision or complete a task with less effort? If they still have to call someone to interpret the answer, there’s more work to do.
Is your website ready for what comes next?
Use this 10-step checklist to assess how ready your website is, identify the gaps, and decide what to tackle next.
The Intelligence Era changes how digital experiences work. Use this 10-step checklist to assess how ready your website is, identify the gaps, and decide what to tackle next.
