1 files changed, 43 insertions, 0 deletions
diff --git a/content/docs/configuration/domain-filter.md b/content/docs/configuration/domain-filter.md
new file mode 100644
index 0000000..184ee2f
--- /dev/null
+++ b/content/docs/configuration/domain-filter.md
@@ -0,0 +1,43 @@
+---
+title: 'Domain Filter'
+weight: 3
+---
+
+The `allowedDomains` and `blockedDomains` config options allow you to specify a list of domains which are accessible or blocked during scraping.
+
+```javascript {filename="Configuration"}
+export const options = {
+  url: "http://example.com/",
+  allowedDomains: ["subdomain.example.com"],
+  // ...
+};
+```
+
+## Allowed Domains
+
+This config option controls which additional domains are allowed to be visted during scraping. The domain of the initial URL is always allowed.
+
+You can also allow all domains to be accessible by setting `allowedDomains` to `["*"]`. To then further restrict access, you can specify `blockedDomains`.
+
+```javascript {filename="Configuration"}
+export const options = {
+  url: "http://example.com/",
+  allowedDomains: ["*"],
+  // ...
+};
+```
+
+## Blocked Domains
+
+This config option controls which additional domains are blocked from being accessed. By default all domains other than the domain of the initial URL or those specified in `allowedDomains` are blocked.
+
+You can best use `blockedDomains` in conjunction with `allowedDomains: ["*"]`, allowing the scraping process to access all domains except what's specified in `blockedDomains`.
+
+```javascript {filename="Configuration"}
+export const options = {
+  url: "http://example.com/",
+  allowedDomains: ["*"],
+  blockedDomains: ["google.com", "bing.com"],
+  // ...
+};
+```