Free Tree Testing Tool

Know your users get where they need to be.

The fastest way to audit and optimize your information architecture: one screen to set up, one click to iterate, and a card sort that flows straight into your tree test.

No credit card required.

What is tree testing?

Tree testing checks whether people can find information in a proposed website or app navigation. Participants get a short task and navigate a text-only version of your structure (stripped of visual design, layouts or colours), so the labels and groupings are all they have to go on.

Their choices expose confusing labels, unexpected groupings, misleading paths, and dead ends before design work begins. Reach for it before designing a new navigation, after a card sort to validate a sitemap, or whenever an existing product has findability problems.

Tree testing in action:
  1. 1 · The task
    “You need to change the delivery address for an order.”
  2. 2 · They navigate the structure
    • Account ›
    • Orders ›
    • Track a shipment ›
    • Manage an order ›
    • Change delivery details ✓
    • Payments ›
  3. 3 · Your results
    First click
    Orders
    Path
    Orders → Change delivery details
    Time
    8 seconds
    Outcome
    Direct success
UXbeam tree testing guide → View a tree test example →

From first test to better navigation

  • 1

    Create a tree test in 1 screen

    Paste an indented outline, upload a CSV or TXT file, or import a structure directly from a UXbeam card-sorting study.

    Write findability tasks, then mark one or more acceptable destinations inside the tree. That can be a specific item, one of several valid items, or an entire parent category when you want to test where participants expect related content to live.

  • 2

    See where navigation breaks

    For every task, see participants' first clicks, chosen destinations, time on task, and paths:

    • Direct: correct destination reached without backtracking.
    • Indirect: correct destination reached with a detour.
    • Elsewhere: the participant chose an unexpected destination.
    UXbeam tree test results showing task outcomes and paths
  • 3

    Iterate and optimize findability

    A first tree test shows where the navigation breaks. Breaks that slip into design cost far more to detect, diagnose and fix. Create and test revisions from the same tree and tasks instead of rebuilding the study from scratch.

    UXbeam keeps every version's results separate and shows which tasks improved, regressed, or stayed difficult, so you can recommend a demonstrably better information architecture.

    Comparing direct task completion across tree test iterations in UXbeam

Reliable findings start with a reliable study

Poor structures and leading task wording can produce confident-looking results that don't reflect genuine findability.
UXbeam helps you catch common study-design problems before and after launch.

  • Start with strong candidate structures

    A stakeholder-defined structure may not reflect how representative users naturally group information. Run a UXbeam card sort to discover audience-driven groupings, turn a candidate structure into a sitemap, and send it directly to tree testing.

    Why this matters

    It's easy to get stuck with a structure that remains passable even after sensible tweaks and iterations... and miss the better one you never tested. When iterating on a tree fails to produce meaningful gains, card sorting can uncover a structure closer to your users' mental models and offer an alternative to test against stakeholder-led versions. Card sorting takes mere minutes to set up in UXbeam.

    Explore card sorting

  • Avoid tasks that reveal the answer

    When a task repeats a label from the tree, participants may match words rather than interpret the situation. UXbeam checks for likely leading terms while you write and can suggest less revealing task wording before launch.

    Why this matters

    Leading tasks are a major source of bias in tree-test results. When a task repeats a label from the tree, participants can match the words instead of navigating by meaning. A findability test becomes a reading test, and success rates rise for the wrong reason. Whether it's your first tree test or your fiftieth, repeated wording can slip in when you're writing several tasks quickly.

    Learn how to write unbiased tasks

  • Know which results to trust

    Leading wording can still slip through. UXbeam checks completed results for suspicious overlap between task language and the destinations participants selected, so you can decide whether a success reflects understandable navigation or accidental word matching.

    Why this matters

    Catching leading wording before launch isn't foolproof. Some slips through, and a task can score direct for the wrong reason. The same leading-term check runs again on your results: when a task shares wording with a destination people landed on, especially a top-level menu label, UXbeam marks the task and surfaces the exact leading terms, making it easy to catch and remove bias.

    Learn about task-quality checks

Complete tree-testing analysis

  • First clicks

    See the categories participants expected to contain the answer before exploring elsewhere.

  • Final destinations

    Identify where participants ultimately believed the content belonged, including common incorrect destinations.

  • Navigation paths

    Explore the routes participants followed through your information architecture, including backtracking and repeated wrong turns.

  • Task outcomes

    Separate direct success, indirect success, and results that ended elsewhere, instead of treating every arrival as equally intuitive.

  • Time per task

    See how long participants needed to make and complete a navigation choice.

  • Participant-level results

    Inspect each participant's attempts across the full study, not only aggregate percentages.

The complete tool, free

  • Unlimited studies
  • Unlimited tasks
  • Unlimited responses
  • Unlimited participants
  • Full analytics included
  • Advanced exports (CSV, SVG)
  • Card sorting → tree testing
  • One-click iteration

Your research belongs to you

  • Participant CSV

    Every participant-by-task attempt in an analysis-ready format for Excel, statistics tools, or your own reporting workflow.

  • Tree & tasks

    The complete tree and task set as plain text for documentation, tickets, research repositories, or version history.

  • Sitemap presentation cards

    SVG menu cards for reviewing a proposed sitemap with collaborators and stakeholders.

For first-time and experienced researchers

New to tree testing?

UXbeam helps you build a valid study without requiring you to know every methodological risk in advance. Start with a simple tree and realistic tasks.

Built-in checks highlight wording that may reveal the answer, while the results explain where people clicked, where they finished, and whether they got lost along the way.

Learn how to run your first tree test →

Already experienced?

Test multiple correct destinations, score parent-level expectations, inspect complete participant paths, and distinguish direct from recovered success.

Compare revisions without losing the results from earlier rounds, so every change is measured against real evidence rather than intuition.

Review the methodology and analysis reference →

Frequently asked questions

What is included with free tree testing?

UXbeam's complete tree-testing workflow is free. Free plans across tree-testing tools differ on four points: how many studies you can run, how many responses you can collect, how many of those responses you can view, and whether exporting your data costs money. On UXbeam there is no cap on studies, tasks, or participant responses; every collected response is viewable; the complete tree-testing analysis is included; and participant-level results export at no cost. No credit card is required.

How do I import a navigation tree?

Paste an indented outline, upload a supported CSV or TXT file, or import a candidate structure from a UXbeam card-sorting study.

Can a task have more than one correct destination?

Yes. You can mark several destinations as acceptable when a task has more than one valid answer.

Can I test an entire parent category as the destination?

Yes. You can designate a parent category when you want to learn which child item participants associate with the task rather than forcing a single terminal answer.

How does UXbeam help prevent leading tasks?

UXbeam checks whether task wording repeats or closely echoes labels in your tree. It can flag likely leading language before launch and surface suspicious wording in completed results.

Do participants need an account?

No. Participants open the study link in their browser and complete the tree test without installing an application or creating a UXbeam account.

Can people take a tree test on a phone?

Yes. The participant experience supports mobile and desktop browsers.

What results will I receive?

You can review task outcomes, first clicks, final destinations, complete navigation paths, individual participant attempts, and average time per task.

What can I export?

You can export participant-by-task results as CSV, the complete tree and tasks as text, and proposed sitemap screens as SVG menu cards. Nothing is locked in: every study leaves in open formats you can read without UXbeam.

Can I revise and retest the same navigation?

Yes, and it's one click: iterate by creating a new version that starts from your existing tree and task set. Each version keeps its own results, so you can compare what improved or regressed.

Why and when to iterate?

A first run usually mixes two problems: your test setup (leading terms, compound instructions, a valid destination you forgot to mark) and the structure itself (competing labels, weak grouping). Iterating is how you tell them apart. Reword the task and re-run, or move the labels and re-run. Each version keeps its own results and shows what improved, so you reach real findability before anything hits wireframing.

Run tree tests

in minutes and for free

Get started