---
title: "Configure Post Jobs to Google"
slug: "configure-post-jobs-to-google"
updated: 2024-03-06T11:50:03Z
published: 2024-03-06T11:50:03Z
canonical: "documentation.infinite.com/configure-post-jobs-to-google"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://documentation.infinite.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Configure Post Jobs to Google

Abstract

Product: **Workbench**

### Post Jobs to Google

- Updated **Release 18.07.23**. Clients can configure BrassRing and Talent Gateways to post open and posted jobs to Google. This feature enhances the possibility of finding jobs posted to Responsive Talent Gateways in Google Search, resulting in increased number of job applications per job.
- Google determines the frequency that reqs are posted and unposted from their Google Jobs site. Typically new jobs are posted once per day (1:00 AM ET) but Google controls when jobs are removed.
- The logo that is used on the Google Jobs posting is the logo that is loaded into the Workbench Talent Gateway setting Client Logo. For more information on configuring the Talent Gateway and its logo, see [Manage Talent Gateways](/v1/docs/manage-talent-gateways).
- If requisition details are updated, the requisition must be reposted on the BrassRing Posting Options page for the changes to reflect on the Google Jobs site.
- Candidates that select Apply through the Google Jobs posting are not marked with a source code automatically.

### Process

#### Configure Post Jobs to Google

1. Select Tools → Talent Gateways.
2. Select the **Edit icon**for the Talent Gateway.
3. Select **Google**in the **Enable Job Feed Integration**field.
4. A notification opens stating to configure Google field mapping in the Req fields page. Select **OK**.
5. Select **Save**.

#### Map the Google fields

1. Select Tools → Forms → Reqs → Req Forms.
2. To view the current field-mapping, select Google Field Mapping.

![image044.jpg](https://cdn.us.document360.io/4bb62c4c-9973-48ec-ab93-23d4b1755503/Images/Documentation/6a33f7f2-cb7d-4c5b-9b57-8521ad8dd4e6.jpg)
3. If needed select the I icon for information about mapping that field. Notes are also included on this screen about the fields that can be mapped to Google.
4. To map a req field to a Google Field, select **Define custom req fields**, or**Define Standard Req fields**.
5. Select **Define New req field** to create a new Req field, or select the **Edit field attributes icon** if the field exists.
6. Select the **Google Field** to map the req field to, by selecting it in the**Posting interface mapping** pull-down menu.

![image045.jpg](https://cdn.us.document360.io/4bb62c4c-9973-48ec-ab93-23d4b1755503/Images/Documentation/f66ac9f6-6ab5-4b0d-85c6-c60d0604aae6.jpg)
  - If your organization is integrated with a Job Board Aggregator Partner, this field also controls what is sent to that vendor. Updating the option in this field affects both the aggregator and Google integration.
  - The required fields that must be mapped to have jobs successfully post to Google are:
    - **Job Description**
    - **Hiring Organization**
    - **Job Location fields**– Each location field must be mapped separately. However, if a proximity field is being used on the req, then mapping the location fields is not necessary. This information is pulled from the backend automatically to post to Google.
    - **Title**
  - Required properties for specific fields:
    - **Job Description** – text field
    - **Hiring Organization**– text field
    - **Job Location fields**– can be text or ISO codes
    - **Job Title** – text field
    - **Base Salary** – text or custom list field. If custom list field is used, the codes must be: **HOUR, DAY, WEEK, MONTH,** or**YEAR**.
    - **Employment Type** – custom list field. Codes must be **FULL_TIME, PART_TIME, CONTRACTOR, TEMPORARY, INTERN, VOLUNTEER, PER_DIEM,**or**OTHER.**
    - **Currency**: Official ISO 4217 format
7. **Save**all changes.
8. Repeat this process for all needed fields.