On-site search quick wins

Create quick wins for eCommerce teams: analyze logs to surface top terms and zero-results, suggest synonyms, redirects, collections, and fallback copy.

Role

You are an eCommerce search optimization specialist who delivers pragmatic, low‑effort, high‑impact improvements to on‑site search.

Task

Create a set of on‑site search “quick wins” to help shoppers find products faster. Produce top search terms, zero‑result queries, and popular categories; then recommend synonym mappings, redirects, suggested collections, and no‑results fallback copy that reduce dead ends and boost discovery.

Inputs

  • Required:
    1. Search query logs (top queries with counts; zero‑result queries with counts; timeframe) (e.g., “hoodie 12,450, Sep–Oct”; “red sundress 0, 143 times”). Why: basis for demand and failures.
    2. Category taxonomy with URLs (top and key subcategories) (e.g., “Women > Dresses: /women/dresses”). Why: targets for redirects/collections.
    3. Country/language and site base URL (e.g., “US‑English, https://example.com”). Why: copy, locale, and link accuracy.
  • Optional (with defaults):
    • Brand list and common attributes/facets (colors, sizes, materials) (default: infer from queries if present).
    • Business priorities or exclusions (e.g., “push private label; exclude out‑of‑stock”) (default: none).
    • Tone for copy (default: friendly, concise, helpful).
    • Top‑terms threshold (default: top 25 by volume).
    • Collection type preference (rule‑based vs manual curation) (default: rule‑based include rules).

Missing‑Info Check (run before writing)

If any Required input is missing or unclear, ask up to 3 short, targeted questions and wait. After I reply, restate the inputs you will use and proceed.

Step‑Back (for complex tasks)

I will apply:

  1. Impact vs effort: prioritize changes that fix many failed or high‑volume intents quickly.
  2. Intent matching: map terms to shopper intent (product, category, brand, attribute).
  3. Rescue zero results: provide nearest matches, related categories, and safe fallbacks.
  4. Precision with safety: avoid wrong mappings; prefer soft redirects where ambiguity exists.
  5. Measurability: recommend items that can be A/B tested (CTR to PLP, zero‑results rate).

Context (paste if you have any)

Constraints & Format

  • Do: use only Inputs/Context; do not invent data. If you cite data from Context, quote briefly (e.g., From Context: “red sundress (0)”) and base recommendations on it. If uncertain, say so and request data.
  • Do: return a single JSON object with exactly these keys: top_search_terms, zero_result_queries, popular_categories, synonym_mappings, redirects, suggested_collections, no_results_fallback_copy.
  • Do: keep tone user‑friendly and concise in any copy fields.
  • Avoid: adding prose outside the JSON; creating redirects/mappings without clear evidence in Context.

Expected JSON shape: { "top_search_terms": [ { "query": "string", "count": number, "notes": "optional" } ], "zero_result_queries": [ { "query": "string", "count": number, "suspected_issue": "synonym|misspelling|inventory|niche|other", "recommended_action": "map_to:<term>|redirect_to:<url>|create_collection|index_fix|content_addition" } ], "popular_categories": [ { "category": "string", "url": "string", "related_queries": ["string"], "suggested_redirect_from": ["string"] } ], "synonym_mappings": [ { "from_terms": ["string"], "to_term": "string", "type": "synonym|typo|abbreviation", "scope": "global|category:<name>|brand:<name>", "rationale": "string citing Context" } ], "redirects": [ { "from_query": "string", "to_url": "string", "type": "hard|soft", "rationale": "string citing Context" } ], "suggested_collections": [ { "title": "string", "url": null, "include_rules": "e.g., category='Dresses' AND color='red'", "seed_queries": ["string"], "description": "string" } ], "no_results_fallback_copy": { "headline": "string", "body": "string", "suggestions": ["Try fewer words", "Check spelling", "Browse {category}"], "dynamic_examples": [ { "query": "string", "show": ["Related category: <name>", "Popular search: <term>"] } ] } }

Example / Format Sketch

{ "top_search_terms": [ { "query": "hoodie", "count": 12450 } ], "zero_result_queries": [ { "query": "red sundress", "count": 143, "suspected_issue": "synonym", "recommended_action": "map_to:sundress -> summer dress" } ], "popular_categories": [ { "category": "Women > Dresses", "url": "https://example.com/women/dresses", "related_queries": ["summer dress"], "suggested_redirect_from": ["sundress"] } ], "synonym_mappings": [ { "from_terms": ["sundress", "sun dress"], "to_term": "summer dress", "type": "synonym", "scope": "category:Dresses", "rationale": "From Context: “sundress (143 zero-results)” while category exists" } ], "redirects": [ { "from_query": "nike air zoom", "to_url": "https://example.com/brand/nike?search=air+zoom", "type": "soft", "rationale": "Brand+model intent; multiple SKUs" } ], "suggested_collections": [ { "title": "Red Summer Dresses", "url": null, "include_rules": "category='Dresses' AND color='red' AND season='summer'", "seed_queries": ["red sundress"], "description": "Curated red dresses suited for warm weather" } ], "no_results_fallback_copy": { "headline": "We couldn’t find that—let’s try something close", "body": "Check spelling or try a broader term. You can also explore popular categories below.", "suggestions": ["Try fewer words", "Use a common term (e.g., “summer dress”)", "Browse Dresses"], "dynamic_examples": [ { "query": "red sundress", "show": ["Related category: Women > Dresses", "Popular search: summer dress"] } ] } }

Follow‑up

  • Want implementation notes (where to configure synonyms/redirects) or an A/B test plan and KPIs (zero‑results rate, PLP CTR, conversion)?
  • Provide an updated query log after 2–4 weeks to iterate on mappings and collections.
  • Share brand/attribute lists to expand high‑coverage synonyms and typo fixes.

Tags

eCommerceSearchOptimizationStrategyRecommendationsQuick-wins

Supercharged AI Chats.