Why Some Pages on Your Job Board Are Not Indexed by Google

Google Search Console reports every URL it finds on your board, including ones that are excluded from search results on purpose. Seeing pages listed under "Excluded" or "Not indexed" is not automatically a problem. Some of those pages are excluded deliberately, others are worth looking into. This guide covers which is which.

Apply Links

Every job on your board has an apply URL that sends the applicant to the employer's site or application form. These URLs are kept out of Google's index deliberately.

The reason is that the apply URL and the job page describe the same job. If both were indexed, they would compete with each other in search results, and a searcher landing on the apply URL would skip the job description entirely. Keeping apply URLs out means Google indexes and ranks the job page, which is the page you want people to find.

Technically the apply URL is a redirect rather than a page, so there is nothing for Google to index. These URLs appear in Search Console under "Page with redirect." No action is needed.

RSS and XML Feeds

Your board publishes job data as feeds so other systems can consume it. Feeds are machine-readable data, not pages for people to read, so search engines are told not to crawl them.
Leaving feeds open to crawling wastes your crawl budget on files that will never rank, which slows down how quickly Google finds your actual job pages. These appear under "Blocked by robots.txt" and are expected.

Expired Jobs

When a job expires or closes, its page returns a 404 status. Google reads that status and drops the URL from its index over the following weeks. During that window the URL shows under "Not found (404)," which is the correct behaviour and needs no action.

This is what Google's official documentation recommends. Under Remove a job posting, Google lists three accepted ways to expire a posting, one of which is removing the page so that requesting it returns a 404 or 410 status code. The same page warns that failing to expire closed jobs may result in a manual action.

The 404 is the HTTP status, not the page itself. Visitors landing on an expired job still see a page explaining the role is no longer available, along with related jobs from your board, so someone arriving from an old link or a saved search can keep browsing rather than hitting a dead end.

Google's own guidelines require expired postings to be removed from search results promptly. Leaving closed jobs indexed is what causes structured data errors on your board.

If a Page Is Missing That You Expect to Be Indexed

Anything outside the categories above is worth a quick check on your side first, since the most common causes are configuration rather than faults:

• Block search indexing is set to Yes under SEO Tools → General Settings. This hides your entire board from search engines. Confirm it is set to No.
• The job is expired, unpublished, or draft. Only live jobs are indexable.
• You recently connected a custom domain. Google treats it as a new site and needs time to crawl it, and your Search Console property must point at the new domain.
• Your board or the pages are new. Crawling is not instant. Give it a few weeks before treating slow indexing as a fault.
• Server errors (5xx). A few across thousands of URLs is normal and needs no action. It means your board was unreachable for a 1-2 secconds at the moment Google crawled, and Google will retry on its own. We monitor platform availability 24/7 and hold our infrastructure to a high reliability standard, but if you see widespread 5xx errors, contact our support immediately.

Updated on: 02/08/2026