SEO Zoo

The Facebook Pixel Helper is a tool that helps you check whether your Facebook pixel is working properly. It works in the background to look for conversion or Facebook pixels and provide realtime feedback on the implementation. A small number will appear on the Facebook Pixel Helper icon to indicate number of pixel events. When clicked, a panel will expand to show a detailed overview of the page's pixels, including warnings, errors and successes. Get the Facebook Pixel Helper for Google Chrome from here: https://chrome.google.com/webstore/detail/facebook-pixel-helper/fdgfkebogiimcoedlicjlajpkdmockpc?hl=en

Bright Local's tool allows you to view search results from any location – Using Google Search or Google Maps. You can see it from here: https://www.brightlocal.com/local-search-results-checker/ In PPC, you can use this tool to: 1. Check the paid campaigns done by your competitors – get ideas on how to make your ads better. 2. See the ad position in actuality. As a rule of thumb: Please DON’T click on our ads. In SEO, you can: 1. Check on what ranking position would a website rank in a particular location – ranking positions of websites would vary on certain locations. 2. Check if the updated title tags and meta descriptions are now shown in Google’s datacenters located in different countries – this will answer propagation issues. As a sample, you can’t see this ad on Google using our office IP address:

When you encounter "404 Not Found", "424 Failed Dependency" and "502 Bad Gateway" tsdb errors in Grafana, this means that a Service died. In this documentation, I am using Zenoss as an example of service. So, "ServiceID" = Zenoss How can this issue be solved? 1. We need to clear the emergency-shutdown flags on Zenoss 2. Restart Zenoss The following steps will guide you through the process in solving this issue and what statuses should be checked: 1. Log in to the Control Center master host as root. i.e. root@mon1:~()# 2. Use this command to check the status of Zenoss: root@mon1:~()# serviced healthcheck All service status should be "passed". If status is "failed", this needs to clear the emergency flag. 3. Use this command to clear the emergency-shutdown flag for a service (Zenoss): root@mon1:~()# serviced service clear-emergency Zenoss Sample output: Cleared emergency status for 45 services 4. This command will check services

Here's a sample process on how to create an alert on Grafana: 1. Go to your desired graph where you wanted to add an alert. 2. Click Edit 3. Go to the Alert tab. 4. Click " Create Alert " 5. In the " Alert Config " section, change the following values: a. Name - this will appear on the alert notification b. Evaluate every - change this to 5s. This means that the graph will update its data every 5 seconds. c. For - change this to 0m (zero minutes) 6. Under Conditions , set the following: a. When - click on "avg() to change to min(). There are also other options to choose from – depending on what you need. b. Of - change to query(A,1h,now) Query parameters: 1st parameter is the metric. 2nd parameter is the FROM value. 3rd parameter is the TO value. This is the condition being set to validate metrics data. c. Is Above - change this to " IS BELOW " and put the value " 0.01 ". There are a

Why is "Links to cross-origin destinations are unsafe" an issue? When you open another page using target="_blank", the other page may run on the same process as your page, unless "Site Isolation" is enabled. If the other page is running a lot of JavaScript, your page's performance may also suffer. Aside from that, the other page can access your window object with the window.opener property. This exposes an attack surface because the other page can potentially redirect your page to a malicious URL. So, if you have links to another origin and you use target="_blank", always add rel="noopener" or rel="noreferrer". rel="noopener" - This indicates that any newly created browsing context which results from following the hyperlink will be disowned, which means that its window.opener attribute will be null. i.e. <a href="..." target="_blank" rel="noopener">...</a> r

When you encounter "Uses Passive Event Listeners to Improve Scrolling Performance" as a metric to be improved under "Best Practices" on Google Chrome Inspect Audits, add the code below after the opening body tag: <script type="text/javascript"> jQuery.event.special.touchstart = {   setup: function( _, ns, handle ){     if ( ns.includes("noPreventDefault") ) {       this.addEventListener("touchstart", handle, { passive: false });     } else {       this.addEventListener("touchstart", handle, { passive: true });     }   } }; </script> Setting the passive option on your touch and wheel event listeners can improve scrolling performance. If you are using a DIVI web theme, go to Theme Options , then the " Integration " tab, and add code to the <body> section.

Voice Engine Optimization ( VEO ) continues to rise! Voice engine optimization (VEO) is Chatmeter's trademarked term for voice-based search engine optimization. VEO entails optimizing your content, location, and brand information to increase your likelihood of powering voice search results. Here are ways on how to optimize a website for voice search: 1. Implement the Schema Markup Schema markup, also known as structured data, is one of the factors that would make your website ready for voice search. It does not affect the rankings directly, but it can give you an edge over your competitors. Essentially, it is the metadata; the data about the information on your site. It goes into your site’s source code. The visitors do not see it, but microdata helps search engines to organize and classify your content. It is an underutilized strategy because it requires work. How is microdata relevant to voice search? When users search for local businesses, they often look for