Skip to main content

Google SEO and Google for Jobs

Help your Job Portal postings appear in Google, Google for Jobs, and Bing search results, and control how each Job page appears to search engines.

L
Written by Lauren Hickey-Jednat

Search engine optimization (SEO) makes the Jobs on your Job Portal more likely to appear higher in search results. In Crelate, you can turn on SEO for Google, Google for Jobs, and Bing, and customize the search details for each Job you publish. This article covers:

  • What you need before you start

  • What each SEO setting does

  • Turning on SEO

  • Customizing SEO for a Job

  • How your Job page URLs are built

  • Tracking portal visits


Before you start

The SEO settings are available only after job board publishing is enabled for your organization. Once it is enabled, all three settings are turned on by default.

To enable job board publishing, start a chat with Crelate Support, or email support@crelate.com. See also Enabling Job Boards for Your Organization.


What each SEO setting does

  • Google and Bing: Include your Jobs in sitemap files for that search engine. A sitemap lists the pages on your portal, which makes it easier for the search engine to find and crawl your Jobs.

  • Google for Jobs: Adds structured data to each Job’s page on your portal. Structured data is a machine-readable description of the Job that Google uses to show it in its jobs search panel. It includes the Job’s title, description, company, location, and posted date, and an expiration date 45 days after the Job is posted.


Turn on SEO

  1. Select Settings, then Portals, then Job Portal, and then Job Portal Settings.

  2. Scroll down to the Search Engine Optimization section.

  3. Select Enabled next to each search engine you want your Jobs optimized for: Google, Google for Jobs, or Bing.

Disabling SEO for a search engine makes your Jobs less likely to appear in its search results.


Customize SEO for a Job

When you publish a Job, you can set its search details under Advanced SEO Options in Step 2: Options of the Publish Job window. Every field is optional.

  • Portal URL: Adds a custom ending to the Job’s page address. See What is a Portal URL?

  • Custom Title: Sets the page title search engines show for the Job. If left blank, the page title is the Title from Step 1: Job Details.

  • Description: Sets the description search engines show for the Job. If left blank, the description from Step 1: Job Details is used.

  • Keywords: Adds search keywords to the Job’s page. If left blank, no keywords are added.

These fields are set one Job at a time. They cannot be set or defaulted for many Jobs at once.

💡 Pro Tip: When a Job’s page is shared on social media, the link preview always uses the Title and Description from Step 1: Job Details, even if you set a Custom Title or Description. Write your Step 1 title and description with both applicants and search results in mind.


How your Job page URLs are built

Each Job’s page on your portal uses this address:

jobs.crelate.com/portal/YOURORGNAME/JOBCODE/PORTAL-URL

  • YOURORGNAME is your organization’s name.

  • JOBCODE is the Job’s code. This part of the address cannot be changed or removed.

  • PORTAL-URL is the Portal URL you set when publishing. If you leave it blank, the address ends with the Job code.


Track portal visits

To track visits to your portal with Google Analytics, add your ID under Analytics, Tracking Pixels, Custom CSS/JS in Job Portal Settings. The Google Analytics field accepts GA4 measurement IDs (G-), Google tag IDs (GT-), and Google Ads IDs (AW-). Google Tag Manager container IDs (GTM-) are not supported. See Job Portal Advanced Configuration Settings.


Key takeaway

Once job board publishing is enabled for your organization, open Settings, Portals, Job Portal, Job Portal Settings, and enable Google and Bing to add your Jobs to their sitemaps, and Google for Jobs to add structured data for Google’s jobs search. To customize how a single Job appears in search results, use Advanced SEO Options when you publish it.


What's Next?

Did this answer your question?