Audit your own job board in ten minutes: seven steps, with screenshots
You can run six of the seven steps from The Staffing Career Site Report 2027 in ten minutes with a laptop, a phone and one live job. Step 7 needs a second look later that day. Steps 1 to 4 are checks our script ran in October 2026, and 45% of the 1,195 agency job pages we tested would already fail step 3.
Daniel BartakovicsCo-Founder & CDO10 min read
Ask AI

In short
- Six of the seven steps take ten minutes with a laptop, a phone and one live job; the step on closed jobs needs a second look later that day.
- View a job's page source (Ctrl+U on Windows) and search for its title: if it is not there, crawlers that do not run scripts see no job.
- Google's free Rich Results Test shows whether a job carries the JobPosting data Google for Jobs reads: paste the address, look for a job posting with no errors.
- Write down every fail and who owns it: your team, your web agency or your ATS provider. That list is the brief for the fix.
On this page
- What do you need before you start?
- Does the job have its own address, without a "#"?
- Is the job text in the page source, with no noindex tag?
- Does Google's Rich Results Test find a job posting?
- Does robots.txt let the crawlers in?
- Can you find the job with a site: search?
- How long does applying take on a phone?
- Does a closed job come down the same day?
- What do your results mean?
Steps 5 to 7 cover what our tests measured only in part or not at all. Each step below gives the exact clicks, what a pass and a fail look like on screen, and who to ask about a fail.
The steps follow what we found on 1,195 job pages. For the six findability checks, the questions to send your web vendor and the proof to ask back for are on a page of their own.
What do you need before you start?
Have your ATS login ready for step 7 and somewhere to write pass or fail seven times, and use Chrome, Edge or Firefox on the laptop. Pick a job a recruiter posted this week. Reach it the way a candidate would, from your careers site, the part of your website where candidates look for jobs.
The screenshots use our demo board for a fictional agency at jobs.talentbird.ai, labelled as a sample. Next to it are one real agency board that fails and, for step 5, one that passes, both with name, logo and address blurred.
Step 1: Does the job have its own address, without a "#"?
A job passes step 1 when it has an address of its own, on your domain, with no # before the job path. Google generally ignores everything after a #, so jobs at addresses like agency.com/#/jobs/123 all look like the same page to Google.
- Look at the address bar of the job you opened.
- Check that it shows your own domain, or a subdomain of it such as
jobs.agency.com. - Look for a
#anywhere before the job's title or number. - Paste the address into a new private window and check that the same job opens.
A pass is your domain, no #, and the same job in the private window. A fail is a # in the path, a job that only opens from the list, or an address on your vendor's domain.
Hash addresses turned up on 11% of the 1,195 job pages we tested, and Google is unlikely to keep those jobs as pages of their own.
The report reads hash addresses as a setup choice. So before anyone tells you it cannot be done, ask the person who set up the board for a clean address per job.
Step 2: Is the job text in the page source, with no noindex tag?
A job passes step 2 when its title and text are in the HTML the server sends, the page as it arrives before any script runs, and the page carries no noindex tag. AI crawlers that do not run scripts only see what arrives, and Google sees the rest later, after it runs the scripts.
- On the job page, open the page source with Ctrl+U on Windows. The Mac shortcut differs by browser, and our guide to checking the job text in the page source shows each click. A new tab opens with a wall of code.
- Open the browser's find bar on that tab and search for the job title exactly as it appears on the page.
- Search again for a short phrase from the job description.
- Search the source for noindex, a tag that tells Google not to show the page in search. A match on a line that also says robots or googlebot is a fail.
A pass is the title and the phrase found in readable text, and no noindex. A fail is no match for the title, which means the job only exists after a script in the browser builds it, or a noindex tag on the page.
Of the 1,094 job pages where bot protection did not stop the check, 17% had no job text in the HTML the server sends, and 3% of the 1,195 job pages we tested carried a noindex tag. A candidate on a phone sees the job either way.
The words to use for the fix are "job pages rendered on the server". Before anyone removes a noindex tag, find out who set it and why.
Step 3: Does Google's Rich Results Test find a job posting?
A job passes step 3 when Google's Rich Results Test finds a job posting on the page. That means the page carries JobPosting data, a hidden label that tells Google the title, pay, location, employer and closing date in a form a machine can read. Google for Jobs is Google's own job search box, and it builds its job list from that label.
- Go to search.google.com/test/rich-results.
- Paste the job's address into the box and click the button to test the URL.
- Wait for the result to load.
- If it lists a job posting, click it and look through the fields for a salary (baseSalary) and an expiry date (validThrough).
A pass is a job posting found, with no errors, and with salary and expiry date in the fields. A fail is no items found, or an error instead of a job posting.
Only 55% of the 1,195 job pages we tested had JobPosting data, so of the four steps our script ran, this is the one job pages failed most often.
The request is short: JobPosting data on every job page, with salary and expiry date filled in.
Step 4: Does robots.txt let the crawlers in?
A job passes step 4 when robots.txt, a short text file at the root of a website, lets in Googlebot and the AI search crawlers. Crawlers are the programs search engines and AI assistants send to read pages, and ChatGPT search needs OpenAI's search crawler, OAI-SearchBot, let in.
- Copy the job's address up to the end of the domain name, for example
jobs.agency.com. - Type it into the address bar followed by
/robots.txtand press Enter. - Read your robots.txt line by line. Each "User-agent:" line names a crawler, or
*for all of them, and the "Disallow:" lines under it say what that crawler may not read. - Look for a "User-agent:" line naming Googlebot or OAI-SearchBot, and for one with
*.
A group is a "User-agent:" line and the rules under it. The fail is a line that reads exactly "Disallow: /" under Googlebot or OAI-SearchBot. If the file has no group for them, look under * instead.
Google's robots.txt documentation, checked 6 November 2026, says Google's crawlers follow only the most specific group that matches them, and treat a missing file as no restrictions, which passes.
"Disallow: /admin" only closes that folder and is fine. A rule that names only GPTBot does not fail this step; Googlebot vs the AI search crawlers explains why.
Of the 1,585 job boards we checked, 3% shut Googlebot out with robots.txt, and 4% shut out at least one AI search crawler. The AI job search statistics show why that matters: ChatGPT has shown live job listings to US users since June 2026.
The company that runs the board's domain can fix a fail by letting Googlebot and the AI search crawlers in by name.

Step 5: Can you find the job with a site: search?
A job passes step 5 when Google shows the job page itself for a search limited to your board's address. It is the quickest sign that Google has the job as a page of its own.
- Go to google.com.
- Type
site:followed by your board's address without https, then the job title in quotes, for examplesite:jobs.agency.com "Warehouse Associate". - Press Enter and look for the job page itself in the results.
A pass is the job page in the results. A fail is no result, or only your job list page. A site: search is a rough check, because it does not show every page Google has, so test an older job too before you call it a fail.
Our tests ran no site: searches. They did look for a sitemap, the list of pages a site gives search engines, and found one for 79% of the 1,087 job pages we could check.
If the job is missing, open the address on the "Sitemap:" line of the robots.txt from step 4, or /sitemap.xml on the job's address, and search it for the job title with Ctrl+F.
To see properly which of your jobs Google has indexed, meaning kept as pages it can show in search, you need Google Search Console, Google's free tool for site owners. If steps 1 to 4 pass and the job is still missing, ask your provider how Google is told about new jobs.
Step 6: How long does applying take on a phone?
A job passes step 6 when a candidate can apply on a phone in under five minutes without creating an account. Steps 1 to 5 decide whether candidates find the job; this one decides whether they finish applying. The full phone timing walkthrough has more detail.
- Send the job's address to yourself by email or text and open it on your phone.
- Start a stopwatch and tap Apply.
- Fill in the form as a test candidate, with a resume if the form asks for one.
- Stop the stopwatch when the confirmation appears, and note whether you had to create an account first.
A pass is under five minutes with no account. A fail is anything longer, a required account, or a form that cannot be finished on a phone. Tell the recruiter on the job first, then delete the test candidate from your ATS afterwards.
Our tests never applied to a job, so the report has no timings, but 6% of the 207 boards where we could judge it without applying asked for an account first.
A fail here belongs to your job board provider or your ATS, depending on which one runs the form.
Step 7: Does a closed job come down the same day?
A job passes step 7 when it disappears from your board, or says it is closed, on the same day you close it in your ATS. This is the one step you finish later: close the job now and look again before you leave work.
- Pick a job that is about to close, or agree with a recruiter to close a test job.
- Close it in your ATS the way your recruiters normally do, and write down the time.
- Before you leave work, open the job's address on your board again.
- Search your job list for the title too.
A pass is the job gone, or marked closed, in the list and at its address when you look again that day. A fail is the job still live, or still in the list, when you look again. A closed job left online sends candidates applying for work that does not exist.
An expired job was still listed on 2% of the 316 boards where we could judge it; how fast closed jobs come down was not measured.
The connection between your ATS and the board decides this step, so ask its owner how often it updates.
What do your results mean?
Every fail on your list has an owner, and the report names three: your team, your web agency or your ATS provider. If you bought your board, read web agency as your board provider. Send each owner only the steps that are theirs.
| Step | What a fail points to | Who to ask first |
|---|---|---|
| 1. Own address, no "#" | Hash addresses or vendor domain | Your web agency or board provider |
| 2. Job text in the source | Page built by a script, or a noindex tag | Your web agency or board provider |
| 3. Rich Results Test | Missing or broken label | Your web agency or board provider |
| 4. robots.txt | A platform or security setting | Whoever runs your domain and hosting |
| 5. site: search | Job not found yet | Your web agency or board provider |
| 6. Apply on a phone | Long form or account wall | Your board provider or ATS provider |
| 7. Closed job | Slow sync with the ATS | Your ATS provider or board provider |
A written-up list can be two lines long: "Step 3, no job posting found: your web agency" and "Step 7, closed job still live at 5pm: your ATS provider". Each owner gets only their line.
The demo board in the screenshots is ours: a job board for staffing agencies that an agency connects to Bullhorn and runs on its own domain or subdomain. If you would rather have the findability steps run for you, bot protection included, request the free job board audit below.
