Skip to main content

Search Engine Optimization (SEO),Social Media, Article Submission

Google drops mobile app properties from GSC, reminds site owners to remove G+ integrations

This week, Google sent out notifications to webmasters, SEOs and developers through Google Search Console telling them that mobile app properties and Google+ web integrations will no longer be supported.

Mobile app properties.

In 2015, Google added the ability to include your mobile apps, specifically Android apps, in Google Search Console. Starting in 2017, Google began moving that functionality from Google Search Console to Firebase. And, as expected, several GSC features are shutting down in March, and one of those features is mobile app property support.

Google sent an email to those who have app properties in Search Console that they will no longer be supported in late March.

The mobile app email notification.

The email says “You are the owner of one or more mobile app properties in Search Console. At the end of March, 2019, Search Console will end support for app properties.”

Here is a copy of the email I received:

Google+ web integrations. 

Google+ is closing down soon, at least the consumer version of it, and, with that, the Google+ social sharing buttons will stop working. Google sent notifications to publishers that have Google+ buttons or any web integrations with Google+, telling that they should remove those integrations by March 7, 2019.

The Google+ notification email.

 Here is a copy of the email that says “Google has announced that Google+ for consumers will be sunset. As part of the sunset, all Google+ web integrations will stop serving on March 7, 2019. This has the potential to affect website layouts and/or functionality if no action is taken by website owners.”


Why it matters. 

If you have any mobile app data within Google Search Console, you will want to export as much of it as you can before it gets shut down. In addition, you may want to consider integrating your apps with Google’s Firebase platform to get more functionality and data than you were able to get within Google Search Console.

In addition, if you are using Google+ on your web sites, you will want to remove those dependencies by March 7.

Comments

Popular posts from this blog

Google Image Search updates guidelines, adding structured data, speed and more

Google updated the Google Image Publishing Guidelines document today, adding more details around structured data, page speed, title management and user experience details. The old documentation can be viewed in this screen shot I captured previously. The new guidelines have updated content around creating a better user experience with your images, including adding good context, optimizing placement, embedding tips, device-friendly sites and good URL structure for your images . In addition, Google has explained how the image titles work since the change. Google also added sections for adding structured data for product, video and recipe markup. There is a new section for speed, including information about their PageSpeeds Insights tool, AMP and responsive image techniques. You can check out the new guidelines over here and compare them to the old guidelines over here .

How to recover from a negative SEO attack

Welcome to the next-to-the-last article in our six-part series on negative SEO . If you’ve been following along, you understand what negative SEO is. You’ve audited your situation to know whether or not you were hit, and you know how to reduce your likelihood of being a target in the future. You even know how to try and defend yourself from an ongoing negative SEO campaign. Now, it is time to clean up the mess. This article is meant to serve as a companion piece to the previous articles in the series. As such, we will once again segment the recovery process into three main areas: links, content and user signals. The good news is that you can recover from attacks in any of those areas; the bad news is that, depending on what type of negative activity you’re attempting to recover from, it could be a lengthy process. Inbound links The first step is to build a disavow file of the most toxic links you have identified in your analysis of the attack. You can find more about how to structure ...

Google Search Console reporting currently delayed

Google posted on Twitter Friday morning that some of their reports within Google Search Console are currently delayed more than their normal two-days. “Some Search Console reports are currently a bit more delayed due to issues in the reporting pipeline,” the company said. This has no impact on your search rankings, this is just a reporting issue. Which reports are delayed?  Specifically, the AMP, Rich Results / Structured Data, Hreflang, Index Coverage, and Mobile Usability reports are all delayed according to Google. I will say that I did check several of these reports, and not all of them are delayed. For example, while the mobile usability and AMP reports are both a week old, the index coverage report is only two days delayed, which is the normal expected reporting delay you would see in Google Search Console. Should I worry?  No, this is just a reporting issue which Google said doesn’t affect your site in search. So your rankings should not be impacted by this issue. When ...