Skip to content

Be found: six job board checks to send your web vendor

The report's checklist has six Be found checks for whether Google and AI search can find an agency's jobs. On the weakest, JobPosting data, only 55% of the 1,195 job pages we tested in October 2026 for The Staffing Career Site Report 2027 passed. This page is the brief to send your web vendor: per check, the question, a good and a weak answer, and the proof to ask for.

Co-Founder & CDO6 min read

Open this page in your assistant with a prompt ready.

ChatGPTClaudePerplexityGoogle AI Mode
Staffing consultant managing candidate placements on laptop in modern office chair

In short

  • Send your web vendor one question per check, and ask for proof you can open in a browser: test results, a page source, job addresses, the robots.txt text.
  • A weak vendor answer comes without proof: 'SEO is built in', 'Google runs JavaScript anyway' or 'the # is how the ATS works'.
  • Ask for Google Search Console access to your job pages; on a vendor's domain, the report notes it is usually not available to the agency.
  • On the weakest check, JobPosting data, only 55% of the 1,195 agency job pages we tested in October 2026 passed.
On this page

The questions build on the report's own list of what to ask a provider before signing. Checks 1 to 3 run from the lowest pass rate up, and checks 4 to 6 from the largest failing share down.

You need no knowledge of SEO for job postings, the work of getting jobs found in search: a real answer comes with something you can open in a browser. Shares come from the findability chapter; why each check fails and the ten-minute self-audit have their own pages.

How agency job pages did on the six checks

Does every job page carry JobPosting data?

JobPosting dataof 1,195 job pages55%

Does a sitemap list every live job?

Sitemap foundof 1,087 job pages79%

Is the job text in the HTML, readable without JavaScript?

Job text readable in the HTMLof 1,094 job pages83%

Does every job have its own address? Share failing

Hash URLof 1,195 job pages11%

Do the jobs live on your own domain? Share failing

On a vendor or ATS domainof 340 hand-checked job pages9%
Inside a frame from another domainof 340 hand-checked job pages9%

Does robots.txt let Googlebot and the AI search crawlers in? Share failing

Blocks AI search crawlersof 1,585 job boards4%
Blocks Googlebotof 1,585 job boards3%

Teal bars show the pass rate the report prints, lowest first; red bars show the failure share it prints, highest first. Each bar names its base.

Figure 1. Bar chart: how agency job pages did on the six findability checks, pass rates or failure shares as the report prints them, each with its base. Base: bases 1,195 job pages, 1,087 job pages, 1,094 job pages, 340 hand-checked job pages, 1,585 job boards, October 2026. Source: The Staffing Career Site Report 2027, Figure 6 page 46, Table 3 page 41, page 50.

1. Does every job page carry JobPosting data?

55% of the 1,195 job pages we tested carried JobPosting data. JobPosting data is the hidden label Google reads for a job's title, pay, location, employer and closing date. A job page without it cannot be listed in Google for Jobs, the job search box Google shows above normal results.

Send this: "Does every job page you run for us carry JobPosting data that passes Google's Rich Results Test, with a salary and an expiry date? Please send the test result for three live jobs." You can also read your JobPosting data field by field.

  • A good answer says the label comes from the job template, so every job gets it, salary and expiry date included.
  • A weak answer is "SEO is built in", with no test result. Ask them to add JobPosting structured data to the template.
  • The proof is three results from Google's free Rich Results Test (search.google.com/test/rich-results), each with a job posting and no errors.

2. Does a sitemap list every live job?

79% of the 1,087 job pages we could check had a sitemap; the report did not measure whether it listed every live job. A sitemap is the list of a site's pages that helps search engines find new jobs faster. A job posted on Monday should not still be missing from it on Friday.

Send this, the report's question plus the address: "Do closed jobs come down straight away, and is Google told, through the Indexing API or the sitemap? What is the sitemap's address?"

  • A good answer gives the address, says jobs come and go automatically, and covers the Indexing API, a way to tell Google at once that a job opened or closed.
  • A weak answer is "Google finds the jobs anyway", or a sitemap with no jobs in it.
  • The proof is the sitemap address, with this week's newest job in it and a job you closed yesterday gone from it.

3. Is the job text in the HTML, readable without JavaScript?

83% of the 1,094 job pages we could check had the job text in the HTML before any script ran. JavaScript here means a script in the browser that builds the page after it loads.

Send this: "Is the full job text in the HTML your server sends, before any JavaScript runs? Please send the page source of one live job with the title highlighted."

  • A good answer says the job pages are rendered on the server, so they are readable without JavaScript.
  • A weak answer is "Google runs JavaScript anyway", which holds for Google only, after a delay.
  • The proof is the page source of a job posted this week, with the title and description in it as text.

4. Does every job have its own address, without a "#"?

11% of the 1,195 job pages we tested used hash URLs, addresses with a # before the job's part of the address. Google generally ignores what follows the #, so a Warehouse Associate job at agency.com/#/jobs/123 is unlikely to be kept as a page of its own.

Send this: "Is every job its own page, at an address without a #, such as jobs.agency.com/jobs/warehouse-associate-columbus? If not, when can that ship?"

  • A good answer is yes, today or by a date.
  • A weak answer is "the # is how the ATS works". The report reads hash URLs as a setup choice.
  • The proof is three job addresses that each open the right job in a private window.
Staffing manager smiling while using AI Resume Builder in office

5. Do the jobs live on your own domain?

Of 340 job pages checked by hand, 57% sat on the agency's main domain and 21% on a subdomain such as jobs.agency.com. 9% sat on a vendor or ATS domain and 9% inside a frame, a window showing another site's page inside yours.

Send these two from the same list: "Who owns the job addresses, and what happens to them if we leave? Do we get Google Search Console and analytics access for the job pages?"

Search Console is Google's free tool that shows a site owner which of its pages Google has (see Search Console for a jobs subdomain).

In the report's comparison, links and rankings on a vendor's domain stay with the vendor when you leave. Search Console is usually not available to the agency there, so jobs belong on your own domain.

Treat both 9% shares as rough: the sample is accurate to about 5 points either way, and our researchers agreed least on where the job sits.

  • A good answer is a path on your site, or a subdomain set up with one entry in your domain settings that can later point at a new provider. Search Console access comes in your own name.
  • A weak answer is an address like agency.vendor.com, a frame, or no Search Console access.
  • The proof is a live job address on your domain, the subdomain entry in your domain account, and the job pages in your own Search Console.

6. Does robots.txt let Googlebot and the AI search crawlers in?

robots.txt kept Googlebot out of 3% of the 1,585 job boards we checked and at least one AI search crawler out of 4%. robots.txt is a short file at the root of a website that tells crawlers, the programs search engines and AI assistants send to read pages, what they may read. A candidate asking ChatGPT search for warehouse jobs meets yours only if OAI-SearchBot, OpenAI's search crawler, may read them; our AI job search statistics show how candidates use it.

Send this, with the crawlers named: "What does robots.txt on our job address allow, for Googlebot and for the AI search crawlers OAI-SearchBot, PerplexityBot and Claude-SearchBot? Which crawlers does our bot protection let through?"

Bot protection, a security layer against visitors that do not act like a browser, turned away requests on 8% of the job pages we tested.

  • A good answer names each crawler and confirms that no "Disallow: /" line applies to it. A rule that names only GPTBot, OpenAI's training crawler, is a separate question, covered in Googlebot vs the AI search crawlers.
  • A weak answer is "we block all bots for security".
  • The proof is the robots.txt address and a written list of the crawlers the bot protection allows.

The tick sheet: all six checks on one page

Tick each row once you have opened the proof yourself.

CheckProof to ask forDone
1. JobPosting data on every jobRich Results Test results for three live jobs☐
2. A sitemap of live jobsThe sitemap address, with this week's newest job in it☐
3. Job text in the HTMLThe page source of a job posted this week☐
4. No # in job addressesThree job links that open in a private window☐
5. Jobs on your own domainA job address on your domain, the subdomain entry, Search Console access☐
6. Crawlers let inThe robots.txt address and the bot protection list☐

We sell a job board for staffing agencies ourselves, a product you connect to Bullhorn and run on your own domain. This brief asks the same of every vendor, us included. To have the six checked for you, request a free job board audit.

Frequently asked questions

Which of the six checks can my vendor fix in the job template, and which need my hosting provider?
The board's builder fixes JobPosting data, job text, clean addresses and the sitemap. The subdomain entry in check 5 needs whoever holds your domain name. robots.txt and bot protection sit with whoever runs the domain and the hosting.
What if my vendor says the fix is on the roadmap?
Ask for the date in writing, with the proof you will get on that date: the same proof this brief asks for today. A date with no proof is a weak answer.
What if my vendor says our ATS does not allow it?
Ask which setting stops it, in writing. The report reads these results as setup choices, because the same ATS can feed a board that passes every check.
Where are the other nine checks?
In the report's full 15-check checklist, under show the job, make applying easy and stay in touch. A candidate who never finds the job never meets the rest.

Open this page in your assistant with a prompt ready.

ChatGPTClaudePerplexityGoogle AI Mode

Read next

Be found

Audit your own job board in ten minutes: seven steps, with screenshots

Get the free report

The Staffing Career Site Report 2027. Free PDF, 77 pages, A4 and US Letter.