Search Wiki Pages
Find existing wiki pages from the knowledge base list.
Use wiki search before creating a new page. This helps avoid duplicate procedures and keeps the knowledge base easier to trust.
Search is also the fastest way to confirm whether a process already has an owner, an approved procedure, or related pages before you update documentation.
Search for a Page
- Open Knowledge Base or Wiki.
- Use the search field.
- Enter a word or phrase from the page title.
- Open the matching page.
If no pages match, the list shows an empty state.
If you expected a page to exist, try alternate words before creating a new one. Teams often use different names for the same process.
Search before editing too. A process may have a short checklist, a detailed policy, and a related playbook. Updating only one page can leave conflicting instructions in the knowledge base.
When you find several related pages, open the newest or most specific page first and check its owner or last-reviewed note before editing.
If a page affects customer commitments, finance, HR, security, or legal process, confirm the owner before changing it. Search helps you find the page; ownership decides who should approve the update.
Search Tips
- Search for the process name, not only a department name.
- Try customer-facing words and internal team words.
- Search before creating a new page.
- Rename old pages when the title no longer matches the team's vocabulary.
If the same page should be found by several terms, add those terms naturally in the page introduction or resource links. Do not create duplicate pages just to cover alternate names.
Use the words teammates actually search for. If support says "refund" but finance says "credit note", mention both terms on the relevant page.
When Search Finds Too Many Pages
Use more specific titles and split broad pages into smaller procedures. For
example, replace Finance Process with pages such as Invoice Approval,
Payment Follow-Up, and Expense Receipt Rules.
When splitting a broad page, add links from the old overview to the new specific procedures before archiving or shortening it. This prevents existing bookmarks from becoming dead ends.
When Search Finds Nothing
Before creating a new page:
- Try alternate names and abbreviations.
- Search for customer-facing and internal terms.
- Ask the likely process owner whether a page exists under another name.
- Check related pages that may link to the procedure.
Create a new page only after confirming the process is not already documented.
Keep Search Useful
Rename pages when titles drift from team vocabulary, archive or update duplicate pages, and add links between related procedures so users can move from a broad overview to the exact task they need.
When a search result is wrong or stale, fix the source page immediately if you own it. If you do not own it, add a review task or ask the owner before the team keeps using outdated instructions.
If a page should no longer be used, archive it or add a clear replacement link instead of leaving it discoverable with outdated steps.
Review common failed searches with the team. If people repeatedly search for the same word and find nothing, add that term to the relevant page or create a clearer title.
Use search results as a maintenance signal. If the best result is old, rename, update, or archive the stale page before creating new documentation.