> For the complete documentation index, see [llms.txt](https://help.rankability.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rankability.com/researcher/keyword-opportunities-and-scoring.md). # Keyword opportunities and scoring Interpret Researcher’s Opportunity score separately from the KO Score shown in Keyword Overview. ## Opportunity score Opportunity score appears in the main Researcher experience. Use it as a prioritization signal alongside search volume, difficulty, intent, relevance, and the client’s strategy. ## KO Score KO Score belongs to Keyword Overview. It combines keyword data for that separate analysis experience. Do not treat a KO Score filter as if it were the Opportunity score column. ## Use scores responsibly * Confirm which score label is visible. * Compare keywords within the same country and data context. * Check intent and relevance before choosing a higher numeric score. * Use live rank checks and client performance data when the decision requires current evidence. ## Next actions Save selected keywords to a list, analyze them in a batch, create a content project, or add them to tracking. Each downstream action can have its own credit cost. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://help.rankability.com/researcher/keyword-opportunities-and-scoring.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.