Google Jobs and SEO
How Kit exposes structured data and sitemaps, sends job-update notifications, and handles indexing requirements for custom domains.
Why It Matters
Kit exposes job data in formats Google supports. This helps Google discover postings, but does not guarantee indexing, timing, or search ranking. See Google’s job posting documentation.
How It Works
Kit uses three mechanisms to make your job postings visible to Google:
Structured Data (JSON-LD)
Every published job posting page on your career portal includes machine-readable structured data in the JobPosting schema. This tells Google exactly what the job is: title, description, salary range, location, employment type, and how to apply.
Google uses this structured data to display rich results with your company name, logo, salary, and location directly in search.
Sitemap
Kit generates an XML sitemap for your career portal that lists every published job with its last-updated timestamp:
https://startupkit.app/careers/your-subdomain/sitemap.xml
If you use a custom domain, the sitemap is available at the root:
https://careers.yourcompany.com/sitemap.xml
The sitemap updates automatically as you publish, close, or modify job postings.
Update Notifications
Publishing, closing, pausing, or reopening a job queues an Indexing API notification. Publication notifications require external job-board publishing to be enabled. Delivery requires a configured Google service account with ownership permissions for the posting’s domain.
| Action | What happens |
|---|---|
| Publish a job | Kit requests indexing of the page |
| Close or pause a job | Google is notified to remove it from results |
| Reopen a job | Google is notified to re-index the page |
Notifications are sent in the background. Missing credentials or domain permissions prevent delivery.
What You See in Google
Once Google processes your job posting, it can appear in:
- Google Jobs widget: the dedicated job search box at the top of Google search results
- Rich results: enhanced search listings showing salary, location, and an “Apply” button
- Google for Jobs: Google’s standalone job search at google.com/search?q=jobs
Google decides when to process a page and whether to show it in results.
Kit Subdomain vs Custom Domain
| Setup | What Kit handles | What you need to do |
|---|---|---|
Kit subdomain (startupkit.app/careers/...) |
Structured data, sitemap, and indexing notifications when the integration is configured | Nothing |
Custom domain (careers.yourcompany.com) |
Structured data, sitemap, and indexing notifications | Verify your domain in Google Search Console and grant the service account used by Kit owner access for Indexing API notifications |
Structured data and sitemaps remain available on custom domains. Indexing API notifications require domain verification and service-account ownership. Contact Kit support to identify the service account to authorize.
Tips for Better Visibility
- Write descriptive job titles: “Senior Backend Engineer” works better than “Engineer III” for search
- Include salary ranges: salary information helps candidates assess the offer
- Use specific locations: “Berlin, Germany” is better than just “Berlin” for structured data accuracy
- Keep descriptions detailed: Google uses the full description to match candidate searches
Quick Checklist
- Publish at least one job posting to your career portal
- Check the posting’s indexing status in Google Search Console
- Verify your custom domain in Google Search Console to monitor performance
- Use the Rich Results Test to check your job posting’s structured data