Blocked Words, Phrases, and IP Addresses
Blocked-word matching supports one entry per line and * wildcards. IP blocking supports exact IPv4/IPv6 addresses and IPv4 CIDR ranges.
Blocked words inspect message text against one entry per line, using word boundaries and optional * wildcards. The IP blocklist compares an exact detected IP or an IPv4 address inside a CIDR network. These are explicit administrator rules, so their precision and the reliability of reverse-proxy IP headers determine whether legitimate visitors are affected.
The practical starting point is to enable blocked words only if a maintained list exists. Continue through the workflow until you test a match, a near-match, an allowed phrase, an exact ip, and a cidr boundary, then use the field notes below to understand which choices affected AI output and which only changed delivery, access, or presentation.
What this feature does and when to use it
Section titled “What this feature does and when to use it”Use explicit blocks for known unwanted phrases or network sources after reviewing false-positive and proxy risks.
Use this feature in the following situations:
- A clearly defined phrase must be flagged or denied for this website’s policy.
- A confirmed abusive exact IP or justified IPv4 network must be blocked.
- You need to test how wildcard, near-match, exact-IP, and CIDR boundaries behave.
Where to find it
Section titled “Where to find it”Before you begin
Section titled “Before you begin”- SmartSite Assistant is installed and activated.
- You are signed in with an account that can manage WordPress options.
Set it up step by step
Section titled “Set it up step by step”- Enable Blocked Words only if a maintained list exists.
- Enter one word or phrase per line; use * sparingly.
- Choose Warn, Block, or Flag and set the public message.
- Enable IP blocking only with validated addresses/ranges.
- Enter one exact IP or IPv4 CIDR range per line.
- Save.
- Test a match, a near-match, an allowed phrase, an exact IP, and a CIDR boundary.
Fields, controls, and important values
Section titled “Fields, controls, and important values”Blocked terms and IP rules decide which requests are flagged or denied before a normal answer is returned. They can reduce abuse, but broad words, wildcards, or incorrect proxy addresses can also suppress legitimate questions and make the assistant appear unreliable. Test realistic language and production IP handling before enabling enforcement.
| Field, control, or status | What SmartSite Assistant does with it | How to use it and why it matters |
|---|---|---|
| Blocked words enabled | Default off. Exact terms use word boundaries; * supplies wildcard matching. | Turn this on only after the word and wildcard list has been tested against normal site vocabulary. When enabled, each message is compared with the configured patterns; the chosen action determines whether a match is merely flagged or denied. |
| Blocked-word action | Default Warn. In current runtime only Block changes visitor outcome; Warn and Flag both allow and flag the turn. | Choose what happens after a blocked-word match. Only Block denies the request; Warn and Flag both allow processing and attach a flag, so do not select Warn expecting a distinct visitor warning. |
| Blocked-word severity | Matched content contributes High severity (default score 5). | Treat each blocked-word match as a High-severity contribution using the configured weight, which is 5 by default. That score can combine with other detections and reach the automated threshold even when the blocked-word action itself allows the turn. |
| IP block enabled | Default off; exact IPs and IPv4 CIDR supported. | Turn this on to reject requests whose detected client IP exactly matches the list or falls inside a supported IPv4 CIDR range. Verify proxy forwarding first so the plugin evaluates visitor addresses rather than one shared reverse-proxy address. |
| CIDR limitation | CIDR calculation uses IPv4 conversion; IPv6 CIDR is not supported, though exact IPv6 can match. | Use IPv4 CIDR notation only; the audited calculation does not support IPv6 CIDR. An exact IPv6 address can still match, so record whether each entry is an exact address or IPv4 range and test it safely. |
How to confirm it is working
Section titled “How to confirm it is working”Judge Blocked Words, Phrases, and IP Addresses where its effect is actually consumed—by the administrator, visitor, model, or connected service. The expected result above is more useful than a green badge because it describes the behavior the configuration was meant to produce.
Practical example
Section titled “Practical example”Block a confirmed abusive exact IP while leaving broader networks unblocked unless CIDR evidence justifies it.
Recommended practice
Section titled “Recommended practice”- Change one part of Blocked Words, Phrases, and IP Addresses at a time and keep a short record of the previous value and test result.
- Include ordinary near-matches in every test so protection is not tuned only against deliberately obvious abuse.
Important warnings
Section titled “Important warnings”Common problems and focused checks
Section titled “Common problems and focused checks”| Problem | What to check and what to do next |
|---|---|
| Blocked Words, Phrases, and IP Addresses is missing or does not match this guide. | Confirm the plugin is active and the account can manage WordPress options. Reproduce the exact message safely and identify the matching limit, pattern, score, address, or whitelist entry. |
| A change on Blocked Words, Phrases, and IP Addresses does not produce the expected result. | Keep the exact notice and test case, then review the browser console and WordPress/PHP log. Reproduce the exact message safely and identify the matching limit, pattern, score, address, or whitelist entry. |
Screen reference
Section titled “Screen reference”- Capture
- Show fictional blocked phrases including one wildcard and TEST-NET IPv4/CIDR examples, with action selection visible.
- Show
- Enable toggles, phrase list, wildcard example, action/message, IP/CIDR list
- Viewport
- Desktop, 1440 × 900
- Annotate
- Use numbered callouts only for controls referenced in the procedure.
- Redact
- OpenAI keys, tokens, secrets, personal information, private URLs, IP addresses, and conversation text