Google indexing
Search engines find your jobs through your board's sitemap, at /sitemap.xml on its main address. Two senders on the console's SEO and Tag Manager page tell them sooner, within minutes of a job opening or closing: IndexNow, and Google's Indexing API. Both come with every plan. Search engines still decide what to show and when; the senders only tell them sooner.
IndexNow: on from the start
IndexNow tells Bing, Yandex and the other engines that take it about new and closed job pages. It is on for every board, with nothing to set up. The IndexNow card shows when JobClay last sent your pages, or "Nothing sent yet." on a new board.
To stop it, untick Send job pages to IndexNow and press Save below the cards.
Connect Google's Indexing API
Google hears about your jobs through a Google Cloud project of your own, and Google gives each project 200 notifications a day. The Google Indexing API card lists these steps too. Only the board's owner can upload or remove the key.
- Sign in to Google Cloud with your company's Google account and create a project.
- Turn on the Web Search Indexing API in the project.
- Make a service account in the project, and a JSON key for it. The service account needs no IAM role.
- On SEO and Tag Manager, choose the key file in the Google Indexing API card and press Upload the key. JobClay checks it with Google, keeps it encrypted and never shows it again. The card then shows the service account's address.
- In Search Console, open Settings, then Users and permissions, then Add user. Enter the service account's address from the card, with the permission Owner.
- Check that your Search Console property is verified and covers your board's main address, because JobClay sends only pages on that address.
Until step 5 is done, the status says Google refused. JobClay tries again every hour; to check at once, upload the key again.
If you later move the board to your own domain, its main address changes, so your Search Console property must cover the new domain.
What JobClay sends
JobClay sends what changes after you connect: a new job, a job whose address changed (such as a retitled job), and a job that closed. Jobs already live when you connect reach Google through your sitemap. An edit that keeps a job's address sends nothing. Jobs from a source with Hide from search engines on are not sent. A job that was already sent before its source was hidden gets a removal notice.
The daily limit
The card shows "Sent today" against your Daily limit, which starts at 200, Google's quota for a project. The day is counted in Pacific time, as Google counts it. Set it higher only if Google gave your project more.
Each day JobClay sends new jobs posted by employers or by you first, then new imported jobs, then closed jobs, newest first among the new ones. What the day's limit leaves waits for the next day. Untick Send imported jobs to keep the limit for posted jobs, and press Save limits. Any admin can change the limits.
What the status means
The card's Status line says where your key stands:
- No key yet. Google hears nothing from this board until you upload one.
- Working. Google hears about new and closed job pages within minutes.
- Google refused. The service account is not an Owner of your site in Search Console, or the Web Search Indexing API is off in the project. Make the address an Owner and check the API is on, then upload the key again to check at once; JobClay also tries again every hour.
- Google refused this key, or it can no longer be read. Upload the key file again, or a new JSON key for the service account.
- Today's quota from Google is used up. Sending starts again after midnight Pacific time.
- Google could not be reached at the last try. JobClay tries again in a few minutes.
To stop sending to Google, press Remove the key, then Yes, remove. Google hears nothing more from this board until you upload a key again.
Submit your sitemap too
The senders cover what changes; your sitemap covers every live job. In Search Console, add your board's sitemap, /sitemap.xml on its main address. Your board's robots.txt names it too.
Still stuck? Write to hello@jobclay.com.
JobClay