|HubPages Device ID||This is used to identify particular browsers or devices when the access the service, and is used for security reasons.|
|Login||This is necessary to sign in to the HubPages Service.|
|HubPages Traffic Pixel||This is used to collect data on traffic to articles and other pages on our site. Unless you are signed in to a HubPages account, all personally identifiable information is anonymized.|
|Remarketing Pixels||We may use remarketing pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to advertise the HubPages Service to people that have visited our sites.|
|Conversion Tracking Pixels||We may use conversion tracking pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to identify when an advertisements has successfully resulted in the desired action, such as signing up for the HubPages Service or publishing an article on the HubPages Service.|
I want to give everyone a quick heads up that we are disabling rich snippets for recipes and product reviews. If you aren't sure what these are, read this. https://developers.google.com/structure … ts/recipes
We are doing this because Google isn't displaying them in the search results and we have seen a handful of authors get manual actions for using them incorrectly. Did you know you can't use a recipe capsule for a facial scrub recipe?
I believe that most Hubbers that have manual actions from Google on their subdomain for rich snippets did it innocently, so we are going to help get these actions removed. Once the manual actions have been removed, we will hand review a hundred or so Hubs and turn the rich snippets back on and then monitor the search results to see if Google honors them once again.
All of the capsules will still show content in your Hubs, but they won't have the markup in the page that Google reads.
Until then, you may want to review the guidelines for proper use. It's easy to make mistakes with these.
- Recipe markup should be used for content about preparing a particular dish. For example, "facial scrub" or "party ideas" are not valid names for a dish.
- Recipe markup should be used for a specific recipe, not a category of recipes or a list of recipes. For example, “10 apple pie recipes” is not a specific recipe.
- If the recipe markup contains a single review, the reviewer’s name must be a valid person or organization. For example, "50% off ingredients" is not a valid name for a reviewer.
- Product markup should be used for a specific product, not a category of products or a list of products. For example, “shoes in our shop” is not a specific product.
- Adult-related products are not supported.
- If the product has been reviewed by a single reviewer, the reviewer’s name needs to be a valid name for a Person (e.g. "James Smith") or Team/Organization (e.g. "CNET Reviewers"). For example, "50% off on Black Friday" is not a valid name.
Would it be an email from Google if we were in violation? According to these guidelines, I think my recipe hubs are okay. Will check back later to see discussion on this.
And I'll ask would the WMT front page (where all our domains are listed) warn us?
edit. And is the ratings capsule one of those rich snippet capsules?
edit2. Never mind. Your OP caused me to be reasonably certain I wasn't using those things correctly, so I went ahead and deleted them all. As far as I could tell, they weren't doing anything for me anyway.
edit3. Meanwhile, glad we weren't hit by a Panda strike.
I think my recipes are OK; however, I can't always give accurate info on the nutrition of the recipe. Would I be in violation if I omit the nutrition info??
I read the referenced link, and it's pretty much "all Greek to me." I don't understand "markups," or html, or any other tech-side things.
I would have thought that the recipe capsules themselves would be already formatted behind the scenes to provide whatever The Big G wants, or not provide what is not wanted by the Google God.
None of my recipes have ambiguous titles, and all have a minimum of 2 recipe capsules; most have more. So I would presume I'm okay?
There are still terms used on HP that I don't understand either, like you DzyMsLizzy. I'm certainly not a techy!
Greek to me, too, MsLizzy. Hope we're okay.
Count me in. I´m not a techy person, too. Now I´m having headache for all the new updates here in HP.
Copyright © 2018 HubPages Inc. and respective owners.
Other product and company names shown may be trademarks of their respective owners.
HubPages® is a registered Service Mark of HubPages, Inc.
HubPages and Hubbers (authors) may earn revenue on this page based on affiliate relationships and advertisements with partners including Amazon, Google, and others.