◆ Elasticsearch

Boost search relevance by field value

This is real work, not a feature someone invented — it comes from real job ads and real questions people asked. Below are four ready AI prompts: get it done, make it easy for the next person to say yes to, work out the right move when you are stuck, and stop it coming back.

4prompts

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskBoost the search relevance for documents where the 'status' field is 'active' in our main…+
Boost the search relevance for documents where the 'status' field is 'active' in our main product catalog index. Apply a weight of 2.0 to 'active' documents.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
BImprove — make it easier to acceptBefore we push this search relevance change to production, make sure it genuinely improves user…+
Before we push this search relevance change to production, make sure it genuinely improves user experience. Test how boosting 'active' items impacts searches for 'discontinued' products, and flag any unintended side effects or queries that now perform worse.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentI just boosted the 'product_name' field for search relevance in our e-commerce site, and now…+
I just boosted the 'product_name' field for relevance, and now all searches return irrelevant results.
I just boosted the 'product_name' field for search relevance in our e-commerce site, and now all searches return irrelevant results, even for exact matches. The marketing director is expecting a demo in 30 minutes, and I'm afraid this will tank conversion rates. I can't tell them I broke search without looking careless. What's the likely diagnosis for this sudden drop in relevance, and what's the best next move to quickly restore search quality without reverting everything?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI keep struggling to improve search relevance without introducing new problems or unexpected…+
I keep struggling to improve search relevance without introducing new problems.
I keep struggling to improve search relevance without introducing new problems or unexpected behaviors for users. It feels like every change is a gamble. What habit should I change to approach relevance tuning more systematically and predictably, ensuring better outcomes for our buyers?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?

Questions people actually ask

honest answers, no sign-up

Every task here was seen in the real world. Someone doing the job named it, a real job ad asked for it, or a lot of people asked about it online.

If nothing real showed a task, it is not on the page. That is the whole rule.

They are the same job approached four ways, because what you need depends on where you are.

Get it done today. Make it easy for the next person to say yes to. Work out the right move when you are stuck. Learn the pattern so the job stops coming back.

For most of these jobs it can carry the heavy thinking - draft it, sort it, check it, rehearse it with you.

It cannot sit in your chair, take the blame when a number is wrong, or notice what nobody wrote down. Let it do the first 80%. Keep the last 20% that is truly yours.

No. Copy any prompt and paste it into the AI you already use. No account, no score, no wall in the way.

Any of them. The prompts describe the work rather than naming a product, so they are not tied to one assistant.

That is also why they keep working when you switch.

Change it freely. Every prompt is a starting line, not a rule.

Put in your real numbers, your real names and your real deadline. The more you make it yours, the better the answer comes back.

The tasks come from real job ads, published job data and the questions people ask in public forums.

The steps come from Elasticsearch's own documentation, with practitioner sources for the traps the manual does not mention.

Push once. Ask it to sharpen the weakest part and to say what it assumed.

Most wrong answers come from a missing detail rather than a bad prompt - tell it the thing it could not know.