Google says your website is dangerous: how to check what happened
If Google or Chrome warns that your website is dangerous, learn where to check the issue, what to review with your technical team and when to request a review.
Security, performance and technical decisions. A little context to understand what to look at and where to start.
Guides for your website
Page 3 of 740 articles
If Google or Chrome warns that your website is dangerous, learn where to check the issue, what to review with your technical team and when to request a review.
Signs that your website may have been hacked, what to review without touching anything yet, and how to coordinate the response with your technical team without losing information.
Seeing “There has been a critical error on this website” or error 500 in WordPress? What to check after an update or code change, and how to fix it.
Did the update fail to finish, or did something stop working afterwards? Identify what happened, preserve important information and prepare a focused review with your team.
An old update date is not enough to decide. Check support, compatibility and security notices before choosing whether to keep, update or replace a plugin.
Identify the accounts on your website, who uses them and what each can do. Organise access without removing necessary functions or locking out your team.