New and Returning Visitors Share One Website: How Should UX Check Their Different Search Paths?

When new and returning visitors use one site, check understanding before selection and direct discovery of known objects separately. Navigation may be shared, but starts, explanations and success criteria differ. Familiar employees completing tasks do not prove first-time visitors can do so.

Describe What Visitors Already Know

New visitors may know a business problem but not service names or models, while returning visitors have models, historic files or familiar categories. Preserve these knowledge differences instead of introducing the entire site to everyone before testing.

Choose representative real materials and required information. A newcomer assessing service suitability and a returning customer finding current attachments may both visit information pages but need different entries and judgments.

Success means test cards define prior knowledge, goal, start and completion criteria. Staff knowledge helps choose tasks but does not equal new visitor understanding. See How to Run an Effective Usability Test for related checks.

Check Terms and Selection Evidence for New Visitors

Observe interpretations of category names, services and product groups. Repeated guessing may indicate organization or explanations, not a need for more animation. Ask why an entry was chosen and check necessary supporting information.

Do not supply internal terminology as task answers. To test judgment, allow users' own expressions. Testing known categories needs a separate task instead of mixing both questions.

When discussing planning and UI/UX with JVDS Design Studio, provide new visitor questions and returning visitor materials separately to define hierarchy and entries. Research, prototype validation and implementation require explicit scope.

Retain Stable Identification Clues for Returning Visitors

Returning visitors need quick location and relationships between current and old versions. Renaming, merging or reordering should retain recognizable names, models or context rather than removing clues solely for visual preferences.

If customers return with an old product name, observe whether they find current explanations or explicit replacements. When unfamiliar new terms dominate navigation or search, an explanatory entry may target the issue better than rearranging every menu.

Check whether mobile, language changes or smaller screens hide key clues. Familiarity does not eliminate device limits; validate both paths under actual access conditions.

Retest Shared Entries with Both Tasks

Compare prior knowledge, entry terms, decision information, targets and failures. If both groups fail in one place, inspect shared structure. If only one fails, adjust for its knowledge and goal.

Record which path each change affects. More explanations may lengthen pages for new visitors, while returning users need direct location. Hierarchy and direct entries can help, but task results should determine solutions rather than assuming two websites.

Success means newcomers understand and choose next steps, while returning visitors locate known objects and valid versions. Report both separately rather than one vague easier website claim or an inference of business results.

Frequently Asked Questions

Can Employees Pretend to Be New Visitors for Testing?

They can find obvious issues early, with their business familiarity stated as a limitation. To assess first-time understanding, add participants matching target knowledge conditions instead of treating employee results as external validation.

Do Explanations for New Visitors and Long-page Complaints from Returning Visitors Require Two Sites?

Usually assess hierarchy and direct entries in one site first. If both groups meet goals, different reading depths do not require splitting. Discuss larger structures only where business and management boundaries warrant them. See How to Plan a Corporate Website: From Business Goals to Page Structure for related checks.