Guest
0

Help visitors find what they came for

A page cannot help a customer if they never find it.You may know exactly where a useful service or delivery rule lives on your site. A first-time visitor sees a menu full of unfamiliar labels. Ask workers to find one specific thing without a direct link or a list of clicks. Their reports reveal wrong turns, confusing categories and searches that lead nowhere. You can then fix the route before spending more on attracting visitors. This check is about navigation, not generating visits for analytics.

Create a navigation test Other website testing tasks

A ready-to-edit microtask brief

This is an editable draft, not a published task. Add your resource link, adjust the conditions, and choose the reward and number of completions.

Task title
Check whether a visitor can find information on the website
What should the worker do?
  1. Open the starting page supplied in the task. Record your device and browser. Use the public site only; do not sign in with an administrator account.
  2. Try to find the product, service or information specified by the customer. Choose your own route through menus, search or filters. Do not use a direct link to the answer.
  3. Write down your first choice, the search phrases or filters you used, and any wrong turns. If you cannot reach the goal within the agreed limit, describe the stopping point instead of inventing a successful result.
  4. Send the final page address and a screenshot of the answer or difficulty. Suggest a clearer label if one confused you. Do not place an order, contact staff or enter private information.
How to prove the result
Provide the device and browser, the route you took, search phrases or filters, the final page address and a screenshot. Explain whether the requested information was found. A completed route or an accurately documented difficulty can both be useful results; the customer must define acceptance criteria in advance.
Create a task from this example

Improve the route, then check it again

Group reports by the first wrong turn, not just by whether someone finished. Repeated choices of the same wrong category suggest a naming or structure problem worth investigating. A failed search may need better synonyms or clearer results. Fix one obstacle and give the same goal to a new group. Compare routes and stopping points without treating a small paid group as a representative usability study. Keep tester visits separate when measuring ordinary traffic.

Workers are paid for testing and reporting, not for purchases or favourable opinions. Their feedback can reveal problems, but cannot guarantee more sales or higher search rankings. A small group of paid testers does not replace research with your target audience.

Help visitors find what they came for: tasks and rewards

See what has already been posted and what workers are currently paid. This can help you set clear terms for your own task.

Create a navigation test
0Active tasks
0Available completions
No available tasksPayment per completion

Activity in this area

See how many clients and workers were active and how many results were accepted during the last 30 days.

Last 30 days
0customers with open tasks
0accepted results
0workers with accepted work
Not enough data yetaverage payout per accepted result

Calculate the budget for Help visitors find what they came for

Set the reward for one completion and the number of results you need. You can carry these values directly into the creation form.

Price for you2 USD

The form validates your final price and available balance again before publication.

Create a task with this budget

Set the number of results and reward in advance

For testing, surveys, feedback, and data work, you can define how many results you need and how much you will pay for each accepted report.

Create a microtaskLearn about pay per result

Choose a ready example

Open a suitable option and add your link, instructions, number of completions, and reward.

What a navigation check can reveal

Find out whether visitors can locate a product, service or useful information. Test your website menu, search and filters with an editable DitWork microtask brief.

Where the first click leadsSee which menu label a new visitor chooses and whether that choice takes them closer to the goal.
What people search forCollect the phrases someone actually enters instead of assuming they know your catalogue terminology.
Which filters cause confusionFind labels, combinations and empty results that make it difficult to narrow down a choice.
A useful route after a changeRepeat the same goal with new workers to see whether the revised path is easier to follow.

Related checks for improving your resource

Choose a nearby problem to investigate next. Each guide includes an editable brief, reporting requirements and ideas for turning observations into changes.

Find out whether your website is easy to use on a phone Find awkward buttons, obscured forms and mobile menu problems. Use DitWork microtasks to check your mobile website with people on their phones. See your online store through a shopper's eyes Find out what gets in the way of a purchase. Use DitWork microtasks to test product search, product pages, the shopping cart and checkout with users. Find out what stops visitors enquiring on your landing page See your landing page through a new visitor's eyes. Collect feedback on the opening screen, trust and the enquiry journey with DitWork microtasks. Make your product page answer a shopper's questions Learn what shoppers understand and what information is missing on a product page. Collect private user feedback through DitWork microtasks, without buying reviews.

Test one route, not the entire website

Set a starting page and a goal. Leave the route open so the worker's decisions remain visible.

Menus and category namesAsk someone to find a service or product without telling them the correct section. Record the first choice, wrong turns and labels they expected to see.
Internal search and filtersProvide the item or information to find, not an exact query to copy. Ask for search phrases, selected filters and the result shown after each attempt.
Information before a decisionChoose a delivery rule, compatibility note or support contact. Check whether someone can find it from the agreed starting point without contacting your staff.

Small checks with a clear goal

Use separate tasks for different goals so the reports remain comparable.

Find a suitable item in the catalogueDescribe a need and two relevant constraints. Ask the worker to find an item, show its address and explain which search or menu path they used.
Find a delivery or returns conditionStart on the homepage or a product page. Ask where the condition is explained and what was missing. Do not send people straight to the answer.

Tasks from the website testing category

These are general website testing tasks. Use the brief above to create a separate navigation check for your resource.

All tasks
No matching tasks yet

Change the selected action, category, or search query. New tasks appear automatically.

Other task types

If this option is not right for you, choose another category or return to the full task list.

Order microtask completion onlineCreate DitWork microtasks: define the action, reward, number of results, instructions and review worker reports.Microtasks for businessUse DitWork microtasks to check a website, app, form, business listing, text, survey or custom scenario with payment for accepted results.Launch your project with microtasksShow a new website, app, or service to its first users before the big launch. Collect genuine impressions, test essential actions, and fix what gets in the way of discovering the project.Promote your project with microtasksHelp people discover your website, app, community, or product. Create clear tasks, receive meaningful actions and honest feedback, and pay only for accepted results.Revive your project with microtasksGive a website, app, community, or service a second life. Discover what feels outdated, why people leave, and which changes can make the project interesting again.Microtasks with payment per accepted resultCreate microtasks with payment per accepted result: exact action quantity, fixed price, worker report and controlled budget.
Website testingTest forms, pages, navigation, and user journeys on real devices.App testingCheck installation, screens, user journeys, and interface clarity.Bots, games, and scenariosTesting bots, game actions, and short step-by-step flows.Registrations and formsRegistration, profile completion, form testing, and actions after signup.Content feedbackReview the clarity of an article, page, description, script, or instruction.Surveys and researchShort surveys, interviews, hypothesis checks, and structured responses.

Related microtask directions

Compare related directions to choose the right scenario, proof format, and expected result.

Microtasks for website and app testingOrder checks of a website, form, app or user scenario from DitWork workers with reports, screenshots and pay for results.Website feedback by usersOrder website checks by real users: page clarity, forms, flows, mobile version and short reports with issues.User feedbackGet user feedback through DitWork microtasks: website, product, content, form, app or service card checks.Order microtask completion onlineCreate DitWork microtasks: define the action, reward, number of results, instructions and review worker reports.Microtasks for businessUse DitWork microtasks to check a website, app, form, business listing, text, survey or custom scenario with payment for accepted results.Launch your project with microtasksShow a new website, app, or service to its first users before the big launch. Collect genuine impressions, test essential actions, and fix what gets in the way of discovering the project.Promote your project with microtasksHelp people discover your website, app, community, or product. Create clear tasks, receive meaningful actions and honest feedback, and pay only for accepted results.Revive your project with microtasksGive a website, app, community, or service a second life. Discover what feels outdated, why people leave, and which changes can make the project interesting again.

Questions about navigation testing

Should I show workers the correct route?

Not when you want to check whether the route is discoverable. Specify the starting point and goal, then ask for their steps. Give safety restrictions and a time limit, but avoid instructions that reveal the answer.

What if a worker cannot find the page?

A precise account of the difficulty can be valuable. State in advance whether a documented unsuccessful attempt is an acceptable result and what evidence it needs. Do not make workers claim success when the route failed.

Is this a complete website usability audit?

No. It checks a defined navigation goal. Accessibility, technical performance and a broader audience study need separate work. Use these reports to identify a concrete path to improve.