The page exists but is not returned
Search its title and inspect the localised index. If absent, fix inclusion or extraction. If present, examine indexed terms before creating duplicate content.
In-depth practical guides
Test internal search relevance
Build representative queries, check results by language and improve journeys without confusing the existence of search with successful discovery.
Updated :
Can users find the content that answers their need?
Internal search serves different intentions: finding a known profile, exploring a topic or choosing a tool. A returned result does not prove useful content is visible. Connect each query to a task and check title, excerpt, destination and language. A documented set of meaningful questions is more useful than a score based on purposeless queries.
Build a task set
Select important content in each main family: guide, profile, category, tool and dossier. Describe the need and pages that actually answer it. Include a need with no known answer to test empty results.
Vary meaningful wording
Test exact title, everyday expression, specialist term and shorter wording. Include accents, apostrophes, non-Latin characters and abbreviations actually used. Variants should represent plausible usage rather than merely mirror editorial vocabulary.
Check every language separately
Search from all six interfaces. Check filter labels, excerpts, messages and destination language. For a localised corpus, results should not silently lead to another language version.
Evaluate result and destination
Record the expected page’s position and whether its title is recognisable. Open it and confirm useful content still exists. Stale excerpts, deleted profiles and overly broad categories can mislead despite seemingly good rankings.
Check journey states
Test empty query, no results, active filter, pagination and back navigation. Confirm query and language retention. Use the keyboard and check that the form’s label describes the action and messages remain understandable.
Fix the cause and repeat
Distinguish missing content, stale index, vocabulary differences, wrong links and unsuitable ranking. Apply the corresponding fix. Rebuild the index and repeat tasks to verify improvement and catch regressions elsewhere.
Situations and decisions
Typical situations for preparing a check. They do not describe completed assignments or actual observations.
A filter creates a dead end
Check that it limits the intended type and remains visible when there are no results. Offer removal or useful rewording, not invented results to fill the screen.
Opening a result changes language
Compare its URL with the equivalent content. Fix parameters or routing and test pagination and return navigation. A translated title is insufficient if the destination resets language.
Record to retain
- Task, exact query, language, filters and justified expected pages.
- Observed rank, excerpt, opened URL and useful content.
- Empty state, keyboard journey and pagination behaviour.
- Index version, cause, correction and retest outcome.
Official references
Related protocols
Frequently asked questions
How many queries should be tested?
Cover main families and intentions, then actual problem cases. Add queries revealing distinct gaps. Count alone does not establish representativeness.
Must every query return results?
No. Honest empty results with visible filters and useful suggestions beat irrelevant matches. Then examine whether the need warrants valuable new content.
How should improvement be measured?
Repeat the same tasks and compare success, useful-page rank and required steps. Keep environment and corpus version; more results can hide lower relevance.
Should the index retain everything?
Index useful searchable content and parameters needed for identity. Exclude errors, stale content and valueless technical states. Check that corpus updates trigger the intended rebuild.