Web Scraping Timeout
This is a common issue when using Machine Translation with web scraping methods.
MT Engines That Use Web Scraping:
1. Google Lite
2. Google Web
3. DeepL Web
4. Bing
5. Papago
6. Yandex
7. Baidu
How Web Scraping Works
Web scraping works by sending URLs to a Virtual Browser Window and searching for matching HTML elements that contain the translated text. If no matching HTML elements are found within the specified time limit, a TIMEOUT error occurs.

Common Causes:
Website structure updates
Unstable internet connection
Blocked user IP address
Too many requests
CAPTCHA verification
Cookie consent banner
Website under maintenance
Troubleshooting Steps
1. Check for MT Engine Updates
PRO Version: Go to Settings → MT Engines → Updates
NEO Version: Check the #custom-mt channel on Discord for updates
2. Avoid the "Detect Language" Option
While this option is available, using "Detect Language" is not recommended as it may cause compatibility issues in some updates.
3. Inspect the Virtual Browser Window
Enable "Show Browser" in MT Settings to visually inspect the web scraping process.
If a CAPTCHA Appears Too many requests may trigger a CAPTCHA. Complete the CAPTCHA verification or use a VPN.

If a Cookie Banner Appears Accept or decline the cookie banner, especially if you are in the EU or another region where these banners are displayed.

If You See a "Free Usage Limit Reached" Message Clear Cookies or restart MT. If this doesn't work, try using a VPN.

If the Page Fails to Respond or No Translation Appears This may be caused by too many requests. Clear Cookies or restart MT. If this doesn't work, try using a VPN. You can watch this video, which demonstrates an example of the "too many requests" issue: https://www.youtube.com/watch?v=JdhLtNgVdYc
If the Page Loads Incorrectly or Appears Blank This may indicate an unstable internet connection or that the translation website is under maintenance.

If You Can See Source and Translated Text in the Virtual Browser Window but VNTranslator Still Shows TIMEOUT This likely indicates a website structure update. You can report this issue in the #report-an-issue channel on Discord.