# Usage/Tips

How keywords works

When you add multiple keywords from the screenshot, Munio will match them in the specified order when scraping websites. For instance, if you add the keywords "Banana, Apple, Orange," Munio will flag a link if the HTML content contains these words in that exact order. However, it will not flag the link if the words are in a different order, such as "Apple, Orange, Banana."

If you want Munio to detect these three words without a specific order, you should add each keyword separately. In the "Add keywords" picture above, add only "banana" and click submit. Then, add a new keyword and repeat the process, adding only one keyword at a time. For example, add "orange," and so on.

## Multiple words per keyword

| Keyword example                               |
| --------------------------------------------- |
| discord nitro free, enjoy bigger file uploads |

{% embed url="<https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FExRFSiGGE6uXpYA2tMPv%2Fuploads%2F18wGm1OMugXaV2W6JP9A%2Fexample%201.png?alt=media&token=49cce63b-a3c1-443e-8d76-be3d28bacc73>" %}

From the image above, the bot will be able to scan these 2 keywords and flag the domain. \
By adding several words per keywords, it allows the bot to specifically target website that continues to use the same text content.&#x20;

{% hint style="warning" %}
In keyword 1 example, it contains 3 words "Discord nitro free", which means that bot will scan these 3 words in that exact order. So if these 3 words are in mixed order example "free discord nitro", then the bot will not detect keyword 1.&#x20;

Another situation is if a sentence contains this:

Get 1 **discord** month of **nitro free** from....\
Then bot will not treat that as keyword 1. That is where **single word** per keyword could be useful instead.
{% endhint %}

Theres pros and cons by adding **multiple** words per keywords which will be listed below.

<mark style="color:green;">+ Highly specialized which will target specific type of website content.</mark>\ <mark style="color:green;">+ Less likely that legitimate domain will get flagged.</mark>\ <mark style="color:red;">-</mark> <mark style="color:red;">If a phishing website decides to change the entire text content then no match will be found.</mark>\ <mark style="color:red;">- Example Keyword 1 must match against identical words in the same order in order to get flagged. If website content has the following words in wrong order: nitro discord free then keyword 1 will not get matched.</mark>&#x20;

## Single word per keyword

| Keyword example      |
| -------------------- |
| discord, nitro, free |

{% embed url="<https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FExRFSiGGE6uXpYA2tMPv%2Fuploads%2Fe5jNIReBVtGB7b7ni2Ri%2Fexample%202.png?alt=media&token=3b1f155e-804d-4b56-a06f-e752a114e55e>" %}

From the image above, it showcases that the bot will individually scan each word on the website content to match against your configured keyword.&#x20;

Theres pros and cons by adding **single** words per keywords which will be listed below.

<mark style="color:green;">+ Cover more variety of websites based on server owners preference, when configured correctly. More keywords you add, the less likely legitimate websites will get flagged.</mark> \ <mark style="color:green;">+ Can scan single keyword in any type of order. Example Keyword 3 can appear first while keyword 2 and 1 comes after and bot will still flag it.</mark>\ <mark style="color:red;">- Higher risk for flagging legitimate websites, as websites tend to use the same words. Requires more effort to configurate with accurate keywords.</mark>  \ <mark style="color:red;">- If you add fewer keywords, the chances are that the bot will flag more legitimate website because there's less specialization in your keyword configuration.</mark> <br>


---

# Agent Instructions: 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:

```
GET https://docs.dis.tf/commands/content-scan/usage-tips.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.