Automatic updates released for Zip Recipes

This week, we released a great new feature for Zip Recipes: automatic updates. Why is this important for you? If you’re an existing customer, you only need to manually install one  more update, then you can always update with just one click, from the WordPress backend! See detailed installation instructions.

We will be emailing you this week about this update, and you will also receive a download link and license key. The license key tells the server the update is requested by a user with a valid subscription, then WordPress will download the package and install the update for you, like any other plugin. For Zip Recipes Lover users, the license key will also be used to validate access to the nutrition API.

This update als changes the user account on Zip Recipes. We will be migrating you soon, but if you’re not in the system yet, let us know and we can add you straight away.

When you’re in the new back-end, you can register with the email you used for the purchase, and then you’ll be able to access your account, where you can access your downloads, upgrades, renewals, and cancellations.

 

Server availability issues on monday

We were having server connectivity issues on Monday, the issues have been resolved now.

We’re currently working an a renewed licensing and api structure. This was an unintentional side effect. Apologies for any inconvenience caused. If you have any questions, please contact us at https://ziprecipes.net/support

Zip Recipes, some changes coming up!

Some changes coming up for Zip Recipes users! Really Simple Plugins has taken over development and support of Zip Recipes from Gezim. Really Simple Plugins is a small plugin development company consisting of three developers. If you have added SSL to your site you might have encountered us before: we’ve also developed Really Simple SSL, currently the largest plugin to get your site easily on SSL. We’re also currently working on Complianz GDPR, a GDPR and CCPA plugin which handles privacy requirements for US and EU, and for Canada as of later this year.

Of course I also have ideas about what this great plugin can do. So there will also be changes 🙂 The changes you will be seeing in the short term:

  • I will start adding a licensing system to the premium plugins, so users can easily update from the back-end.
  • The current Gutenberg implementation will be adjusted to make more effective use of the wysiwyg possibilities Gutenberg offers
  • Translations will be extended to more languages
  • Conversion between US and Metric measurement systems will be added

A lot more is coming, but I’m hoping for your input as well! If you have any ideas or suggestions for improvements, let me know!

Fix Recipes Markup for Your Website

Recently Google sent emails to website owners that are a bit hard to understand:

Below, we’ll explain the problem and what you can do to fix it right away — it’s not that hard!

“Recipes [with] markup issues” you read?! Then you think I thought Zip Recipes actually handles this for me! In some cases, it’s just a matter of filling out some fields, like the keywords or Cuisine fields.

When you dig further in to the issue, you might discover that Google has these specific issues:

Let’s explain what each one means:

  • Missing field aggregateRating: this means that your recipes don’t have visitor rating information. Likely they don’t have the ability to rate them. Follow the steps in Solution 2 to solve this.
  • Missing field recipeCuisine: this means that you have not set a recipe cuisine when you created your recipes. Follow the steps in Solution 1 to solve this.
  • Missing field keywords: this means that you have no added keywords to your recipe. As of 6.0.4, this is a field in the Recipe editor. Just add some keywords!
  • Missing field video: this means that you have not set videos for your recipes.
  • Missing field nutrition: this means that you recipes lack nutrition information
  • Missing field author: this means that your recipes don’t have an author set
  • Missing field description: this means that your recipes are missing basic descriptions.

Solutions

The good news is that you can fix most of these issues today!
All of the above issues indicate that you did not add some information to your recipes that Google deems important.

Some of the fields are available in the basic (free) plan of Zip Recipes so you can apply them with minimal effort. Some other fields are available in our Friend and Lover plans.

  • Description can be set in the More Options section of the recipe entry screen:
    1. Edit your recipe
    2. Enter your recipe’s description in the Description field :
  • Recipe cuisine can be set in the More Options section of the recipe entry screen as well:
    1. Edit your recipe
    2. Enter the recipe cuisine in Cuisine:
  • Aggregate rating basically means recipe ratings.
    1. Upgrade to the friend plan
    2. Now you visitors can give your recipes a rating based on a 5-star rating system:
  • Author settings is the field that contains your name (you do want the credit for your recipes, don’t you?)
    1. Upgrade to the Friend plan
    2. Set yourself as the author of all your recipes in one step in Zip Recipes > Settings page:

 

Nutrition

    • data can be added to your English and Spanish recipes with 1 click! We call this feature

Automatic Nutrition.

    1. Upgrade to the Lover plan
    2. Edit your recipe
    3. Click Calculate Nutrition button to automatically calculate your nutrition information:
    4. You also get a Nutrition Facts label without any work!
Chrome's NOT SECURE warning on food blog

Will your food blog be affected by Chrome’s security warnings? 😨

According to some stats, Google’s Chrome browser is used by 64% of the internet.

So, when you get an email from Google itself with the subject, Chrome will show security warnings on YOUR WEBSITE, your hearts starts to pound a little faster…because you’re not crazy!

You probably get the majority of the traffic from Google Search and most people coming to your website are probably using Google Chrome!

What does the email actually mean?

The important part of the email states:

Starting October 2017, Chrome (version 62) will show a “NOT SECURE” warning when users enter text in a form on an HTTP page, and for all HTTP pages in Incognito mode.

First off, this change isn’t here just yet. Chrome version 62 will be released in October 2017. This gives you a bit of time to remedy the situation and we’ll cover what you can do in a bit.

“NOT SECURE” warning

This warning will appear in the URL or search bar. Here’s how it appears on My Gluten Free Miami, a Zip Recipes customer (has since moved to https, so no insecure warning anymore).

Chrome's NOT SECURE warning on My Gluten Free Miami food blog

Chrome’s NOT SECURE warning on My Gluten Free Miami food blog

When users enter text

Now, when will this warning appear?

The answer is when your visitors enter text. So, essentially as soon as a visitor starts typing (virtually anywhere) on your website, this warning will appear.

This includes:

  • when visitors try to subscribe to your newsletter (most probably)
  • when visitors search on your website
  • when visitors attempt to comment (unless you’re using another commenting system like JetPack)
  • when visitors try to use the contact form to contact you
  • pretty much when visitors type anything on your website!

Here’s how the warning appears

Chrome warning on food blog as user enters email to subscribe to mailing list

Chrome warning on food blog as user enters email to subscribe to mailing list

Chrome warning on food blog as visitor is about to search

Chrome warning on food blog as visitor is about to search

Why is this happening to you?

In the email, Google mentions “HTTP page”. What does that mean?

HTTP stands for Hypertext Transfer Protocol. If I send you a letter by snail mail, you could say I’m using the Snail Mail Transfer Protocol. That protocol entails that I take a letter, put it in an envelope and, type your address in it and then drop it off at my local post office where I pay a small fee to deliver it to you.

Likewise, when a web page is sent to you, the protocol in use is the Hypertext Transfer Protocol. This ensures that your browser can actually make sense of the web page I might send you.

HTTPS (Hypertext Transfer Protocol Secure)

With HTTP, if I’m at your house or using the same wireless network, say at Starbucks (which is where I happen to be right now), it’s actually quite easy for me, on a different computer to see any text or data you send if the web page you’re interacting with only uses HTTP.

This is where HTTP Secure comes in. Before it sends the data and text you type in a website out of your computer, it encrypts it so people sharing the same WiFi network cannot intercept and read your data.

In a nutshell, if your website uses HTTPS, it will be more secure and respect your visitors’ privacy. When it only uses HTTP, the visitor’s data can be read by other people.

Google Chrome wants to warn people and make them more aware when they are on a page that only has HTTP and they are about to send data or text.

I should mention that HTTPS may be referred to as HTTP over Transport Layer Security (TLS) or HTTP over SSL. At the end of the day, they all mean the same thing.

HTTPS (and SSL benefits) for SEO

When you switch your website to use HTTPS (and hence starting using SSL), you will get some awesome SEO advantages:

  • You’ll get more referrer data and be able to see where more of your visitors come from
  • It’s a ranking factor for Google and it’s becoming more important so you should start ranking higher when you switch to HTTPS

How can you add HTTPS to your website?

This is usually fairly simple:

  1. Ask your hosting provider to install an SSL certificate for you, or how it can be done.
  2. Install Really Simple SSL