How to set up Google for Jobs Indexing API?

In this guide, we’re going to take a look at how you can use Google’s new Indexing API to get your ShopHire jobs posted to Google for Jobs in minutes! 🖖

Here’s why this really is worth the extra effort. 

  1. Increase your job visibility to actively search for job seekers
  2. Outrank competing jobs
  3. Branded ‘Apply Button’ in the Google for Jobs rich snippet
  4. Keep search results up-to-date for higher-quality user traffic

The process of setting this up isn’t typically very easy, but if you follow this step-by-step guide, you’ll be up and running (or, I guess you could say up and ranking) in no time! So, without further ado – let’s jump right in and take a look at how to set this up.

Before you begin

  • Make sure you have account owner privileges for the Google Search Console for the site you are configuring Indexing API onto. This is typically also the Google account that owns the Google Analytics for your site. It is common for this Google account to be controlled by the owner of the company and/or the original developer of the website. A delegated user will not work.
  • Verified your domain in Google Search Console

Steps to set up the Google Indexing API

  1. Go to Google API Console
  2. Create a Service Account
  3. Add the Service Account as an owner
  4. Add API Key
  5. Send first indexing request to Google
  6. Most Common Errors & Their Fixes

Go to the Google API Console and create a new project

Ensure that you’re creating a new IndexingAPI project which you can do automatically by clicking here. And click Continue.

If you see the following screen then you’ve successfully created the project:

Note: There is no need to click the ‘Go to Credentials’ button. You can close this tab.

Now create a Service Account

Once you’ve created your project, create a service account by opening the service accounts page. And, if prompted, select the project you just created using the button near the top of the page:

And once you have selected a project, click the Create Service Account button highlighted below:

On the Create service account screen, enter a name and description for the newly created service account.

Select and copy the whole Service Account ID (the one that looks like an email address) because you will need it later. Then, click on the Create button at the bottom:

Once you’re taken to the next page, don’t forget to change the role to Owner and, as you might’ve guessed, click Continue.

Now download the file that contains your API key by clicking the Create Key button.

Choose the default JSON format when prompted in the overlay, and click Create.

Add the Service Account as an owner of your Google Search Console Property

To do this, you’ll need to register and verify your website with the Google Search Console (if you haven’t done so already) which is super easy: just follow the recommended steps to verify ownership of your property.

After verifying your property, open the Google Search Console, select your property on the left (if prompted), and then click on Settings near the bottom:

Click on Users and permissions

Click on the three dots next to your account, and then click on Manage property owners.

A page will open in a new tab. Scroll to the bottom and click on the Add an owner button in the Verified owners section:

Enter the Service account ID (the one you copied out earlier) in the new owner’s email address field and click Continue:

Switch back to the previous tab and refresh it. You should now see the Service account listed as a new Owner.

Email me the Service Account email address and JSON API Key.

Input Key and “Email” Into the Google for Jobs Indexing API section on the Settings page

Go to your settings page in ShopHire and do the following:

  1. Click the ‘Edit’ button
  2. In the service email address–the one ending with into the Google service account email field
  3. Copy & paste the contents of the JSON file into the JSON key field. 
  4. Click the Enable button
  5. Click the Save button

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.

Still need help? Contact Us Contact Us