In one paragraph
Website search missing means this scan did not recognise a search form or route once its crawl-size gate was reached. It does not prove search is absent or that every site over that size needs a search box. Review actual findability and user tasks, including existing native or scripted search. If adding search, implement useful results and accessible interaction rather than a recognisable empty form.
Why it matters
Navigation helps people browse an information structure; search can support a specific known target or phrase. Their relative usefulness depends on content, terminology, catalogue size, and task complexity, not a universal eight-page boundary.
An input field alone does not supply search quality. Relevant results, understandable no-results recovery, permission handling, and working links matter. A small focused site can be easier to use through clear navigation, while a complex knowledge resource may benefit from both.
Search terms can also contain sensitive information or reflect private tasks. Decide collection, retention, access, and analytics deliberately rather than logging every query indiscriminately because it may be interesting.
How WebAuditOS evaluates this finding
The supplied rule starts only after at least eight pages are crawled. It recognises source forms whose action contains search, or observed links whose address contains /search, with documented rendered-link fallback.
A recognised candidate passes; no match with readable coverage warns informationally; insufficient crawl size or unavailable rendered coverage can be ungraded. WordPress-style root actions with an s parameter, other query names, translated routes, or scripted overlays can be missed. It does not submit queries or assess results.
How to fix it
- Review the content and the actual questions visitors need answered. Inspect navigation and existing search before deciding whether an additional search service is useful.
- For a real search route, provide a clear labelled interface. A structural example is:
<form action="/search" method="get" role="search"><label for="site-query">Search this site</label><input id="site-query" name="q" type="search"><button type="submit">Search</button></form>Implement actual processing and result pages. This fragment does not provide an index, ranking, permissions, or a complete accessible search experience.
- Keep the route appropriate to the application. Do not change a working root-action or localised search merely to include an English substring; document recognition limitations where appropriate.
- Test representative queries, spelling variations, filters, empty input, and no-result cases. Provide a useful next step without fabricating matching content.
- Respect content access boundaries. A search index or snippet must not expose private account records simply because the destination itself requires login.
- Test keyboard use, mobile layout, focus, labels, suggestions, and result navigation. A custom autocomplete needs its own complete interaction model.
- Review indexing freshness and stale or removed destinations. Search should not continue sending visitors to retired routes because only the page template was updated.
- Rescan and assess task success separately. The crawl threshold and one recognised address are not proof of the site's size, search quality, or need for a particular vendor.
What the fix can break
Adding a search box can create an unreliable promise when its index is incomplete or outdated. Assign ownership for relevance and maintenance.
Query logging can capture information the product does not need. Use an appropriate privacy-aware approach and avoid publishing private query data as content.
Do not strip useful navigation because search was added. People may need browsing and contextual routes even when they know a word to search.
Questions
Does eight crawled pages mean search is mandatory?
No. It is the supplied detector's applicability gate, not a usability standard.
Why can working WordPress search warn?
Its action and query route may not match the detector's patterns. Test actual behaviour first.
Does a recognised form prove results work?
No. The scan does not run a functional query assessment for this check.
Which related checks help?
Review navigation, 404 recovery, and documentation access.