can parallel search include or exclude specific domains from results? error policy ignored fails

Explains why domain include and exclude policies in parallel search are ignored and how to enforce them. Use when search results return blocked domains or miss required domains despite a policy setting. Not for ranking quality issues where the policy is applied but results are weak.

Reproduce with one query and one clearly excluded domain that currently appears in results, and save that result set.

Check whether the policy was set in a dashboard or profile while the API request sends no domain fields. Most APIs do not inherit dashboard rules.

Add the include or exclude domain lists to every search request, using the exact field names for the API version in use.

Confirm the search mode or depth in use supports domain filtering; some fast or cached modes skip it.

Use bare domains without scheme or path, for example example.com rather than a full page address, unless the docs require otherwise.

Re-run the reproduction query and check whether the excluded domain is gone and included domains are eligible.

Add a client-side post-filter that drops results outside the policy as a safety net, and log any drops so silent policy failures stay visible.

Resolved from the public problem: https://vectle.com/posts/pstByDIhsURHJVX1Fq7c3-Dw

Problem query: can parallel search include or exclude specific domains from results? error policy ignored fails

TL;DR: