Zero-results pages: the navigation fallback that saves sales

“No results found for your search.” That single sentence is one of the most expensive lines of text in ecommerce. It is a dead end — the shopper asked a question, the store answered with nothing, and now the shopper has to decide whether to try again or leave. Most leave.

Zero-results pages are more common than store owners think. Baymard Institute’s research found that even well-optimized stores produce no results for 10 to 15 percent of queries. For stores with smaller catalogs or weaker search engines, the rate can reach 30 percent. Every one of those empty pages is a session at risk of ending.

The fix is not just better search relevance (although that helps). The fix is treating the zero-results page as a navigation opportunity — a place where the menu structure can rescue a session that search failed.

Why searches return nothing

Before fixing the zero-results page, it helps to understand why queries fail. The causes fall into a few consistent categories:

Misspellings and typos. Mobile keyboards make this inevitable. “Runnign shoes,” “cotten shirt,” “leaher bag.” A search engine without fuzzy matching treats these as completely different terms from the intended queries and returns nothing. Most modern search apps include spell correction, but the default Shopify search does not handle this well for every language.

Synonym gaps. The shopper searches for “sneakers” but the catalog uses “trainers.” The shopper searches for “couch” but the store lists “sofa.” These are not errors — the shopper and the catalog are using different words for the same thing. Without a synonym dictionary, the search engine treats them as unrelated terms.

Out-of-stock or discontinued products. The shopper saw a product on social media or remembers buying it last year. They search for it by name, but it has been removed from the catalog. The search finds nothing because the product no longer exists.

Overly specific queries. “Blue polka dot midi wrap dress size 8.” The search engine tries to match every word and fails because no single product matches all of those terms simultaneously. A human would understand the intent, but keyword-based search treats this as a precise requirement.

Products the store doesn’t carry. The shopper assumes the store sells something it doesn’t. They search for “shoes” on a clothing-only store, or “dog food” on a home goods site. The search correctly returns nothing — the issue is expectation mismatch, not search failure.

Each cause suggests a different fix, but all of them share the same fallback need: when search returns nothing, the page should not be empty.

Anatomy of a good zero-results page

The default zero-results page in most Shopify themes is minimal: a message saying no results were found, sometimes with a suggestion to try a different search term. This is technically accurate but practically useless. The shopper already knows the search failed — what they need is a next step.

A well-designed zero-results page includes several navigation elements:

A reformulated search suggestion. If the query might be a misspelling, show the corrected version: “Did you mean ‘running shoes’?” This is the simplest rescue — one click and the shopper is back in a valid search session.

Top-level categories from the menu. Show the store’s main category links — the same ones that appear in the header menu. The shopper who searched for “sandals” and got nothing can tap into “Women’s Shoes” or “Men’s Shoes” and browse their way to what they want.

Popular products. A grid of bestselling or trending products serves double duty: it shows the shopper that the store has products (even if not the one they searched for), and it provides inspiration for a different purchase. This is especially effective for stores where browsing and discovery are core to the shopping experience.

Recent or related searches. Show queries that other shoppers have used successfully. “Other shoppers searched for: running shoes, hiking boots, slip-on sneakers.” These serve as navigation shortcuts — each one is a pre-tested query that will return results.

A link to the full menu or homepage. Explicit navigation: “Browse all categories” or “Back to homepage.” This gives the shopper a clear reset button.

The navigation rescue pattern

The core idea is to transform the zero-results page from a dead end into a crossroads. The shopper’s search failed, but instead of leaving, they are presented with multiple paths back into the store — all of which use the navigation structure the store already has.

This is where search and navigation genuinely complement each other. The menu is always there. It doesn’t fail because of typos or synonym gaps. It shows the full scope of what the store offers. When search fails, the menu can step in as the fallback discovery tool.

The implementation pattern:

1. Keep the search bar active. The shopper should be able to immediately try a different query without navigating away. Pre-populate the search bar with their original query so they can edit it.
2. Show category navigation below the message. Pull the top-level categories from the menu (or a curated subset) and display them as clickable links or cards with images.
3. Add product recommendations. Bestsellers, new arrivals, or products related to the failed query (if the search engine can infer partial matches).
4. Track the failed query. Log every zero-results query for later analysis. These are signals about what shoppers expect to find and what the store is missing.

Using zero-results data to improve navigation

Every zero-results query is feedback. Aggregated over time, these queries reveal patterns:

• Repeated product requests. If multiple shoppers search for a product the store doesn’t carry, that’s market research. It might be worth adding the product — or at least creating a category that addresses the need.
• Terminology mismatches. If “sneakers” produces zero results but the store has 200 products under “trainers,” that’s a labeling problem. Fix it with synonyms in the search engine and consider adding “sneakers” as an alternate category label in the menu.
• Navigation gaps. If shoppers frequently search for category-level terms like “gift ideas,” “new arrivals,” or “clearance,” those terms should probably be in the menu. The shoppers are telling you what they expect to find through browsing.
• Seasonal demand. Zero-results spikes around holidays — “valentine gifts,” “halloween costumes” — signal seasonal categories that should appear in the menu during those periods.

Quick checkSearch for a nonsense term on your own store right now. If the page shows only "No results found" with no categories, products, or next steps, you are losing sessions every day. Adding fallback content to the zero-results template is a one-time theme edit that pays off permanently.

Shopify implementation

In most Shopify themes, the zero-results page is a template file (usually search.liquid or a section within it) that renders when the search query returns an empty product array. Customizing it involves editing this template to add fallback content.

The basic approach:

• Check if the search results are empty.
• If empty, render a fallback section instead of (or in addition to) the “no results” message.
• The fallback section pulls from existing data: menu links (from the Shopify navigation API), popular products (from a curated collection or best-selling sort), and optionally recent searches (from a cookie or local storage).

For stores using Navi+ with a mobile tabbar, the zero-results page can include a prominent “Browse Categories” button that opens the same slide menu the tabbar uses. This creates a direct bridge from failed search to structured navigation — one tap from “I can’t find it” to “here’s everything we sell.”

The technical effort is modest — a few hours of theme work — but the impact on session quality is significant. A zero-results page that sends shoppers into navigation instead of out of the store rescues sessions that would otherwise be lost.

This article is part of the larger guide on Search vs navigation: which converts better and when to use each.