A new ‘Security Issues’ section added into the new Google Search Console, announced Google Webmaster team on its official Twitter account.
The new tab is designed to help webmasters by letting them know when Google finds harmful activities on a site related to hacking and malware.
Moved from the classic Search Console to the new Google Search Console under a new section called “Security and Manual Acttions.”
This tab will alert verfied site owners any security issues that prompts Google Chrome to display a warning to visitors on their site, including hacked URLs, malware, deceptive pages, harmful downloads and more..
The security issues covered by this tab include:
- Social Engineering (Phishing and Deceptive Sites)
- Malware infection type: Server configuration
- Malware infection type: SQL injection
- Malware infection type: Code injection
- Malware infection type: Error template
- Cross-site malware warnings
- Hacked type: Code injection
- Hacked type: Content injection
- Hacked type: URL injection
- Harmful downloads
- Uncommon downloads
- Deceptive pages
- Unclear mobile billing
In addition to notify webmaster of security issues, this tool will also help in fixing the specific issues on a website.
Affter the issues are resolved, webmasters can request a review to Google.
Here is a screenshot that shows an example Google warning of detected issues along with a request review:
In the event of no security issues, this tab wiil disaply a “green checkmark” along with a “No issues detected” message.
To access the tab, after logging into Search Console, scroll down to the “Security & Manual Actions > Security Issues” on the left side navigation.
For more details on the specific issues this tab detects and report, head over to this Help page.
Here is how the “no issues detected” with green checkmark looks:
The guide goes on to explain the implementation dynamic rendering for node.js express web application using Rendertron, which is an open source solution based on headless Chromium.
For those unaware, dynamic rendering is term used for the capability that let switch between client-side rendered and pre-rendered content for specific user agents.
Take a look at the diagram below:
For step-by-step guide, head over to this post that covers:
- Take a look at a sample web app
- Set up a small express.js server to serve the web app
- Install and configure Rendertron as a middleware for dynamic rendering