Welcome to the Q&A Forum

Hi There, There should be no problem in receiving the notifications if you have A.)Turned ON notifications, B.) Removed the admins properly and taken access. Both processes are listed below. Turn alerts on and off Sign in to your Google Admin console. Sign in using an administrator account From the Admin console Home page, go to Reports. To see Reports, you might have to click More controls at the bottom. In the left pane, click Manage Alerts. If you have custom alerts, they'll appear at the bottom of the list. In the Status column on the right, turn the switch on to receive an alert, or turn off to stop receiving the alert. (Optional) Click the Email recipients column to edit alert recipients by email address. You can also check or uncheck Super Administrator(s) to start or stop alerts for users who are super administrators We lost our site owner! If the verified owner of your site leaves, or you're not sure who the verified owner is, simply verify another owner for your site. The new owner will be able to see the list of all owners and users verified to that site, as well as the method used to verify each owner. You can then optionally unverify previous owners by removing their verification token (for example, removing the HTML tag from the site, for HTML-tag-verified owners). See Add or remove owners for more information.

Google tries to index the rendered page, not the raw page code. The best way to see that page as Google sees it is to use the Fetch and Render tool in Google Search Console. Alternately, you can use the developer tools in Chrome or Firefox to show the rendered version of the page code. Right-click in an area of the page you wish to view, and then select Inspect. This will bring up the inspector which will show you the rendered page code close to how Google sees it. (Google uses Chrome V42 for indexing, while the current version of Chrome is 62 - so you're not necessarily seeing exactly what G is seeing, which is why Fetch and Render is more the view G actually sees.) The screenshot below shows the Inspect method of viewing the rendered page in current Chrome - but as I say, safest is to view within Google Search Console's Fetch tool. Hope that helps? Paul P.S. This is an example of why Wix is not recommended for critical websites - it's using JavaScript methods to render basic page content which Google "says" it can index, but it's depending on a completely non-standard way of presenting page content which depends on search crawlers deviating from their standard methods to try to crawl it. (And there have been incidents in the past where G's crawling capabilti8y for this kind of JavaScript wasn't indexing it properly, causing major issues for a huge number of sites.) hgWsq

Hey Flyyazp! I'm Michael, the video guy here at Moz and I'm happy to chime in and offer some assistance. The camera we use is a Canon 5D Mark III with a 24-105mm lens. Igor is right, camera technology has jumped forward quite a bit since 2012, so you can pass on looking for a camcorder and go straight for a nice DSLR, even a used one if it's right for the budget. If you're just shooting a person standing in front of a whiteboard you don't need to spend the extra cash on a brand new camera with 4K technology, unless you need that feature for other videos you plan to make. An important feature you're going to want on any camera you buy will be a headphone jack which will allow you to monitor the sound input to the camera. Here is a video of me talking about how I light Whiteboard Friday and lighting features I recommend regardless of the brand you buy. In addition, our friends at Wistia made a nice little video here that will walk you through some tips for shooting video with a DSLR camera. Our mic is a Sennheiser lavalier our presenter is a Rand Fishkin (super rare). I hope this helps!