diff --git a/WPScan-User-Documentation.md b/WPScan-User-Documentation.md
index 4aa7dd6..6e57d30 100644
--- a/WPScan-User-Documentation.md
+++ b/WPScan-User-Documentation.md
@@ -146,6 +146,10 @@ _NOTE: Get your API token from [wpscan.com](https://wpscan.com/) if you also wan
 
 If you get the `Scan Aborted: The remote website is up, but does not seem to be running WordPress.` error, it means that for some reason WPScan did not think that the site you are trying to scan is actually WordPress. If you think WPScan is wrong, you can supply the `--force` option to force WPScan to scan the site regardless. You may also need to set other options in this case, such as `--wp-content-dir` and `--wp-plugins-dir`.
 
+#### Redirects
+
+By default WPScan will follow in scope redirects, unless the `--ignore-main-redirect` option is given.
+
 ### Docker Cheat Sheet
 
 #### Pull the Docker repository