Did you run an audit of your site and it ended in error?
Here are the known errors and how to solve them.
1. The audit returns a 401 or 403 error
When analyzing certain websites, Shake may encounter HTTP 401 (Unauthorized) or 403 (Forbidden) errors.
These errors can be attributed to two main reasons:
- Private Site Access:
Some websites require prior authentication before allowing access to their content. This usually manifests as a login screen, similar to the one found on our back office. When Shake tries to access such secure areas without the appropriate authentication information, the server returns a 401 error indicating that access is unauthorized.
It is not possible to bypass this authorization, so Shake will not be able to work on sites with private access. - Blocking by Antibot Detections:
Some websites are equipped with bot detection mechanisms (antibot) to protect their content from unwanted automated activities. When Shake is identified as an unauthorized bot, the server returns a 403 error, indicating forbidden access.
To resolve this, you can add Shake's IP address (`54.194.108.249`) to your server's whitelist.
2. List of sites where the audit is blocked
We have blacklisted certain sites to avoid unnecessary audits and to improve Shake's performance.
If you try to launch an audit on one of these sites, it will be abandoned. Here is the list of concerned sites:
- localhost
- bing
- yahoo
- baidu
- duckduckgo
- ask
- aol
- yandex
- wolframalpha
- youtube
- tumblr
- quora
- snapchat
- telegram
- tiktok
- tinder
- netflix
- amazon
- ebay
- aliexpress
- wikipedia
- imdb
- spotify
- soundcloud
- github
- stackoverflow
- medium
- blogger
- twitch
- vimeo
- dailymotion
- flickr
- imgur
- youtubekids
- 4chan
- 9gag
- 9now