Fix Deceptive Site ahead warning or Error: Google Chrome has just edged past Internet Explorer as the most preferred browser and this is one of the many cases where Google has proven their top position. For Apple, they have Safari browser but that isn't that popular. One of the main features why people prefer Google Chrome is that they have adapted to technology changes.
Fix Deceptive Site Ahead
One major reason why I like Chrome browser is the ability to sync bookmarks, logins and other data effectively on different devices, it has given me the freedom to work from anywhere, just enter your email ID and all the relevant data will be available, quick and fast.
Why Deceptive Site ahead warning
The site ahead contains malware
One of the latest features that Google Chrome has added to its web browser is Safe Browsing technology. It's also known by other names as 'Deceptive site ahead warning' notification.
It can be detected on Safari, Mozilla Firefox, UC Browser, and other browsers. It is designed to flag deceptive sites which might install unknown software or reveal your personal information.
The error looks like this -
Sad! 🙁 Many bloggers in the past have even complained of it and once you are caught in this error, it's painful to remove it. Alternatively, the site works perfectly on other browsers like Firefox, Safari, and Opera.
The complete error message that you get is here -
Deceptive site ahead
Attackers on yourwebsite.com may trick you into doing something dangerous like installing software or revealing your personal information (for example, passwords, phone numbers, or credit cards).
Google Safe Browsing recently detected phishing on adsadvices.com. Phishing sites pretend to be other websites to trick you.
You can report a detection problem or, if you understand the risks to your security, visit this unsafe site.
Bypass Deceptive Site Ahead on Chrome:
You can easily bypass this deceptive site error on Google Chrome. Google is just trying to let you know that phishing attack ahead, right on their browser if they detect something while crawling your website.
Here is how to fix deceptive website warning error -
Learn how I make $3000+ a month from blogging
- Open Google Chrome and go to Settings.
- Under that scroll down to the bottom to find "Show Advanced Settings".
- Finally, Uncheck "Protect you and your device from dangerous sites".
- Now reload the website and you will see no such error.
While you can browse by turning OFF the option, but we don't recommend doing this, unless and until you are so sure of the website that you are browsing. Once you do this Google will bypass all the sites which are caught in this browser filter. This, however, isn't recommend and so this is not the permanent fix and it helps to browse your site and look for the actual cause of the problem.
Fix Deceptive Site Ahead Error:
If it's your site then you should do a certain action in order to comply with Google and remove this notification visible to other users. Use the Red Leg tool to fix this issue.
Scan a Website for Malware, Malicious Script or Redirect
Luckily there is a tool by which you can scan your website or a URL for malware, malicious redirect, malicious script or for any malicious file.
- Visit https://aw-snap.info/file-viewer
- Enter your website or the URL to detect a problem.
Not just that, AW-Snap includes many other tools to identify any bad stuff on your site.
Report Google a Detection Problem
If you are sure that there is no problem on your site, then you can report it Google using 'Report a detection problem'. Here is how you can let Google know about 'detection problem'.
- When you receive the error, click on Details.
- Under details, you will find the option of "Report a detection problem".
- This will lead you to a page where in you will have to submit 'Report Incorrect Phishing Warning' request.
- Just enter the URL and handle the captcha.
- Commenting on what you did in order to fix the issue is very important.
- Click on Submit Report.
Now, wait for a few days until Google does its job. Finally, even after 10 days you still see the error, it means that something is definitely wrong with your site. I urge you to scan your website deeply. If you are unable to find anything, inviting friends and co-bloggers to detect the issue.
Alternatively discussing on popular forums will help you resolve the issue. One of the best source to deal with such problems is the Google Webmaster forum. That community has experienced people who can help you to fix the issue. I too go a good help to fix the issue.
And finally once again submit the report with steps mentioned above and wait until your site is manually approved.
Check out 51 Best WordPress Plugins ever
Your last chance to bypass deceptive site error
If your site issue isn't fixed in the second attempt, then consider this as a final option to get back your site. Follow it very carefully -
- First take a backup of your website with all the posts, pages, and media and then delete the account. There are a number of ways to do it, the best that I can recommend is through cPanel. Login to your cPanel and head to Backup & Restore. Download 'MySQL Database' and 'Email forwarders' backup. For safe protection, I would recommend you to take 'Home directory' backup. You can refer official cPanel documentation.
- Delete your WordPress install through your cPanel or ask hosting provider to reset account to default.
- Now start freshly, with WordPress installed and no article on your site.
- Submit a detection report for the final time.
Your website will be now fresh and definitely, it has no harmful links or content and Google will definitely accept your request.
Afterward, when your site gets back online, you can restore the backup. Ideally wouldn't recommend you to restore the backup but you can do it at your own risk by scanning each post of your site carefully.
But again let me remind you that you should scan your site completely so that it doesn't have any malicious or deceptive code or link.
I hope, the above guide has helped you to fix Deceptive Site Ahead error.
This Content was last modified on August 3, 2019 5:00 PM