Prompt

chroma embedding search results not accurate

Artificial Intelligence / AI Search2 observationsLast seen Nov 21, 2026

Latest observation

Nov 21, 2026OpenAI APIWeb search: off

If Chroma embedding search results feel inaccurate, it’s usually one of these issues:

Common causes

1) Bad chunking

If your documents are split too large or too small, retrieval gets noisy.

  • Too large: embeddings blend multiple topics
  • Too small: important context is lost

Typical starting point:

  • chunk size: 300–800 tokens
  • overlap: 50–150 tokens

2) Wrong embedding model

Different models have very different retrieval quality.

  • General-purpose models may miss domain-specific meaning
  • Old/smaller models can be weaker for semantic search

If possible, test a stronger model such as:

  • OpenAI: text-embedding-3-small / text-embedding-3-large
  • SentenceTransformers: all-mpnet-base-v2
  • Domain-specific embeddings if your content is specialized

3) Query text is too vague

Embedding search works better with specific queries.

Bad:

  • “pricing”

Better:

  • “What is the enterprise pricing for the annual plan?”

If the search term is short, try expanding it with context.


4) Metadata filtering is missing

If you have lots of documents, semantic search alone may return “similar but wrong” results.

Use metadata filters like:

  • source
  • date
  • category
  • language
  • document type

Example:

results = collection.query(
    query_texts=["annual enterprise pricing"],
    n_results=5,
    where={"category": "billing"}
)

5) Similarity metric mismatch

Make sure the distance metric aligns with your embeddings.

Chroma often uses cosine-like similarity behavior depending on setup. If embeddings aren’t normalized or the model expects cosine similarity, results can degrade.

Check:

  • embedding normalization
  • collection configuration
  • metric used

6) Poor document preprocessing

If text extraction is messy, embeddings suffer.

Watch out for:

  • headers/footers repeated on every page
  • OCR errors
  • tables flattened badly
  • duplicated content
  • broken sentences from PDF extraction

7) Need reranking

Embedding search is usually a first-pass retrieval method. For higher precision, use a reranker after Chroma returns candidates.

Typical flow:

  1. Chroma retrieves top 20–50
  2. reranker sorts top matches
  3. return top 3–5

Quick debugging checklist

Try this:

  1. Print the retrieved chunks

    • Are they semantically close but not exact?
    • Or completely irrelevant?
  2. Test with a very specific query

    • Compare expected vs actual.
  3. Inspect chunk sizes

    • Are chunks coherent?
  4. Check embeddings

    • Same model used for indexing and querying?
  5. Add metadata filters

    • Reduce search space.
  6. Try another embedding model

    • This is often the fastest way to improve accuracy.

Example of better retrieval setup

results = collection.query(
    query_texts=["How do I reset my account password?"],
    n_results=10,
    include=["documents", "metadatas", "distances"]
)

Then inspect:

  • documents
  • metadatas
  • distances

If distances are clustered closely, reranking may help.


If you want, I can help you debug your exact setup

Paste any of these:

  • your chunking code
  • your Chroma query code
  • your embedding model
  • an example query and the wrong results

and I can suggest concrete fixes.

Observation history

How did Obsurfable measure this prompt?

Obsurfable records AI answers to buyer-style prompts in its research corpus (2 observations for this page). Metrics are distributions over observations, not a single static ranking.

Which AI systems does Obsurfable collect answers from?

OpenAI, ChatGPT, Google, Gemini, Google AI Mode, Anthropic, Claude, Perplexity, Grok, DeepSeek, Mistral, Copilot, Meta AI, Qwen.

How can brands improve their AEO?

Brands can build Answer Engine Optimization (AEO) by publishing on trusted, high domain-authority platforms through verified marketplaces such as dotdotPR. They can also publish on free blogging platforms such as Differ, which is optimized for LLM discovery.

Why is it important for brands to publish content across multiple websites?

Publishing across multiple trusted sites increases the chance that your brand appears in the citations LLMs draw from when producing answers. Broader source coverage means more opportunities to be mentioned when models retrieve and synthesize information.

Want this interpreted for your brand?

Explorer is the free public corpus. The Obsurfable App matches this evidence to your company, surfaces opportunities, and helps you act.