InfiniteRanks documentation
Query fan-out: distinguish suggestions from observed retrieval
A model may use related searches in a search-enabled workflow, but a suggested related question is not proof that a particular hidden search occurred.
Label the evidence you have
If a provider returns explicit search-query metadata, preserve it with the answer and method. If the tool only suggests related questions, label them as research ideas. Do not claim to reveal a model’s internal reasoning or private user query volume from a generated list.
Use expansion to test missing requirements
Take a broad question such as “best CRM for recruiters” and identify constraints: email history, candidate records, permissions or migration. Turn useful constraints into reviewed prompts. Save the source of each suggestion and remove duplicate questions that test the same decision.
Keep the baseline separate
Put exploratory prompts in a separate cohort so they do not silently change the headline trend. Record when a question was added, revised or paused. InfiniteRanks research and prompt organization can support this process; a public write API or universal hidden fan-out capture should not be assumed.
Sources and further reading
Sources explain the underlying standards. They do not endorse InfiniteRanks or guarantee a ranking outcome.