Job SEO Troubleshooting

Problem: You do not know whether Google has added your job page to its search index. A page must be indexed before it can appear as a normal search result.

Solution: Check the job address in Search Console:

1. Open Google Search Console and sign in with the Google account connected to your website.
2. Select your website from the website selector, called the property selector.
3. Paste the full job-page address into the inspection bar at the top and press Enter.
4. Read the result. If it says the URL is not on Google, open Page indexing and read the reason.
5. Select Test live URL to check whether Google can access the page as it is now.

If your website is not listed, select Add property and follow the website-ownership check. For a URL-prefix property, use the same https address and www version as the live website. See Google’s website setup instructions.

The first result shows Google’s recorded version. Test live URL checks the page now. Passing the live test does not mean Google has already indexed it.

1. Open the public job page and copy its address from the browser. Inspect that individual page, not the careers listing, editor, or preview link.
2. If the address is outside the selected property, switch to the property matching the live website. For a URL-prefix property, the https and www versions must match.
3. Expand Page indexing and note the reported reason, last crawl date, and canonical addresses where available. Use those details to choose the next check below.
4. Compare the recorded result with Test live URL. A passing live test shows the page can meet the checks now; it does not confirm that Google has indexed the corrected version.

Problem: Search Console says your job is not on Google.

Solution: Find the reported reason below and follow its steps.

Excluded by noindex

Problem: The page tells Google to leave it out of search.

Solution: Open the job’s SEO settings. Set the page to allow search engines to show it, rather than noindex. Then open WordPress → Settings → Reading and make sure “Discourage search engines from indexing this site” is unchecked. Save the changes.

Blocked by robots.txt

Problem: A website rule stops Google from reading the page.

Solution: Open your website’s robots.txt file by adding /robots.txt to your website address. Look for Disallow rules that cover the job’s address. Check the robots.txt settings in your SEO tool or website files and correct the rule blocking public job pages. Leave rules for private pages in place. Save the corrected rule.

Not found, soft 404, or server error

Problem: Google could not read a usable job page. The job may have been hidden, expired, empty, or unavailable when Google visited.

Solution: For a job posting still accepting applications, open Careers → Jobs and check that Current Status is Open. Check the display, closing, and expiry dates, then save. Open the public job address in a private window. Confirm that the full posting appears.

Page with redirect

Problem: The address sends visitors to another page.

Solution: Check where it goes. Inspect the final job address in Search Console.

Duplicate or alternate page

Problem: Google treats another address as the main version. Search Console calls that address the canonical URL.

Solution: In Search Console, open Page indexing and compare the User-declared canonical with the Google-selected canonical. Open both addresses. If your SEO settings point this job to an unrelated page, remove or correct that custom canonical setting. Keep the address of the actual job posting as the intended main page. In Yoast SEO, the override is under Advanced → Canonical URL. Leave it blank to use the automatic canonical unless you have a specific reason to override it. Save the job after changing it. See Yoast’s canonical URL instructions.

Discovered, currently not indexed

Problem: Google knows the address but has not read the page yet.

Solution: Open the public job page and make sure it loads. Check that your careers listing links to it. Google still needs to read it before deciding whether to index it.

Crawled, currently not indexed

Problem: Google has read the page but has not included it in its index.

Solution: Replace unfinished template text or copied details with this job posting’s accurate information. Check whether another address already represents the same job. This result does not prove that word count caused the problem.

Where to change a noindex setting in Yoast SEO: Edit the job under Careers → Jobs. Open the Yoast SEO panel or sidebar, expand Advanced, and find “Allow search engines to show this Post in search results?” The wording can vary by content type. Select Yes for a public job that should appear in search, then save or update the job.

Also open Yoast SEO → Settings → Content types and select the content type used for jobs. Check its search visibility setting. Settings for ordinary Posts or Pages do not necessarily apply to Jobs. See Yoast’s content-type instructions. If Advanced is unavailable, check whether your account has permission to use those settings.

After changing an indexing setting, clear the relevant website cache and run Test live URL again. If noindex remains, check other plugins or hosting settings that can add the same directive. Keep staging and private websites excluded if that is intentional.

Problem: Search Console says the page is indexed, but you cannot find it for your search. It may appear for other searches or below the results you checked.

Solution: Check what you are searching for and what Google has reported:

• In Search Console, open the Performance report and filter by the job-page address.
• Look at Impressions to see how often it appeared, Clicks to see visits from search, and Queries to see the searches reported for it.

Search results vary by place, device, and time. Your own search is one check; Search Console gives you recorded data for the dates you select.

1. Open Performance → Search results in Search Console and select a date range covering the time since the job was published.
2. Add a Page filter using the full job address. Check Impressions and Clicks, then open Queries to see the search terms reported for the selected period.
3. If there are no impressions, check a longer date range and confirm that you filtered the indexed canonical address. No impressions alone does not identify the cause.

Problem: The job name does not clearly identify the role. For example, “AP2” is an internal code, and “Great Opportunity” does not name a job.

Solution: Open Careers → Jobs and edit the job name. Use the actual role, such as “Accounts Payable Clerk”. Use the same title in the Description’s first sentence. Remove sales wording, salary, addresses, and job codes from the job-name field. Check the meta title* for old wording, then save.

After saving, open the public posting and check its visible heading. Then check the meta title* in your third-party SEO plugin separately. For example, the job name can be “Accounts Payable Clerk” while the meta title* adds “Kelowna | Example Company”. Correct any old wording in either place.

Problem: The posting has missing fields, too little detail, or information copied from another job posting. For example, “We are hiring. Contact us” does not explain the work.

Solution: Open the Helpful Tip for each written field and follow its instructions:

• Description: Its Helpful Tip lists the details to include and recommends at least 300 words. The grader flags fewer than 80 words as a major issue and 80–299 words as a minor issue.
• Duties: Follow its tip on action verbs, bullet points, and 5–7 key responsibilities.
• Qualifications: Follow its tip on Required and Preferred Qualifications, specific experience, and recognised skills or certifications.
• Education: Follow its minimum-education and certification guidance. Its tip recommends at least 20 words.
• Additional Information: This is optional. Its tip explains what company and workplace details to add and recommends at least 20 words if used.

Add missing facts rather than repeating text to reach a length target. Field-tip recommendations are not Google word-count rules.

Read the saved posting as a candidate. Can you tell what the person will do, which requirements are essential, where they will work, and how to apply? Replace placeholders and facts from copied jobs. Preview the public page after saving to confirm the sections display as intended.

Problem: The page title is blank, says only “Careers”, or names an old job posting. Google may use this title as the clickable heading in ordinary search results. It is also called the meta title*.

Solution: Open the job and find the meta title* field in your SEO plugin. Enter a short title for this job posting, then save.

Example: Accounts Payable Clerk in Kelowna | Example Company.

The job name itself should remain “Accounts Payable Clerk”. The meta title* can include the location and employer. Google may shorten or rewrite it.

1. Edit the job under Careers → Jobs and open your third-party SEO plugin’s panel or sidebar. In Yoast SEO, find the field labelled SEO title in the search appearance section. This is the meta title*.
2. Check whether the title uses automatic variables or a custom title copied from another job. Adjust it so the preview names the current role, with the relevant location and employer.
3. Save or update the job. Reopen the editor to confirm the saved value. A preview is an estimate; Google can display a different title.

If Yoast controls are missing, check Plugins → Installed Plugins to confirm Yoast SEO is active. Check that its SEO controls are enabled for the Jobs content type. See Yoast’s content-type settings.

Problem: The short search summary is blank, generic, or describes another job posting. This field is separate from the full job description.

Solution: Open the job’s Meta description* field in your SEO plugin. Write a short summary naming the role, location, and main work. Save and check the search preview.

Example: Join Example Company as an Accounts Payable Clerk in Kelowna. Process supplier invoices and reconcile accounts in a full-time finance role.

Google may display text from the page instead. A missing or rewritten meta description* alone does not prove why a job is absent from search.

1. Edit the job and open your third-party SEO plugin’s panel or sidebar. In Yoast SEO, find Meta description* in the search appearance section.
2. Write a summary of this specific job. Include the role, workplace or remote arrangement, and main work. Only include pay, benefits, or employment terms that the posting supports.
3. Save or update the job, then reopen the editor to confirm the text was saved. This does not change the full Description field in Kraken Careers.
4. If Google still shows an old summary, inspect the job address in Search Console and compare its last crawl date with your update date. Google can also choose page text instead of your meta description*.

Company profile

Problem: No company is selected, its name is missing, or it identifies the wrong employer.

Solution: Complete the Company Profile’s required fields using their hints. Select that profile in the job’s Company field. Creating the profile alone does not assign it to the job.

Job location

Problem: The workplace is missing or inaccurate, or a remote job has no eligible country.

Solution: Follow the Location and Remote Work field hints. Office Only and Hybrid Remote need a physical workplace, including its country. Fully Remote needs Remote Eligible Country. The company’s address does not replace these job-location fields.

Problem: Google cannot find or use the JobPosting data, the copy of the job’s details it reads from the page. An indexed page can still be missing from Google Jobs.

Solution: Test that data:

1. Check that the job posting is Open and its display, closing, and expiry dates allow applications.
2. Open Careers → Settings → Integrations. Under Google Jobs Integration, check Enable Feed.
3. Open Google’s Rich Results Test and enter the individual job address.
4. Open the JobPosting result. Correct the errors it names using the corresponding field’s Helpful Tip.

In the test, hiringOrganization means the employer, jobLocation means the workplace, and description means the full job information. If JobPosting is missing, check the feed setting and incomplete company or location records.

Passing the test confirms the checks it covers. Google also applies its content rules and chooses which jobs to display.

Use the public address of one job in the Rich Results Test. Expand each reported error and read the named field. After correcting that field, save the relevant job, company, or location record and test the same address again. Warnings identify recommended information; errors can prevent eligibility. Passing the test does not guarantee Google Jobs placement.

Problem: Your posting is complete and passes the tests, but other job postings appear for the same role and location. Competition is one possible explanation for limited visibility. Google does not report an exact reason for leaving your job out.

Solution: Check the search and improve any missing information:

1. Search using the accurate role and workplace location. For example, try “Accounts Payable Clerk Kelowna” rather than just “jobs”.
2. Clear location, employment-type, and remote-work filters that do not match the job posting.
3. Read comparable postings. Check whether yours is missing useful facts about duties, pay, hours, qualifications, or benefits.
4. Add the missing facts where they apply. Keep the title accurate and use the plugin’s Helpful Tips. Do not copy another employer’s claims or rename the role just to attract searches.

Competition can affect visibility; it does not explain a noindex setting, missing job data, or a broken page. Correct those problems first. Search Console does not show a “too much competition” error.

Problem: Setting a closing or expiry date too far in the future could signal to Google that the vacancy is not urgent, which might affect whether it appears in Google Jobs. This is a possible explanation, not a confirmed Google ranking rule.

Solution: Open Careers → Jobs and edit the posting. Check the closing and expiry dates against the actual recruitment plan. Use the field’s Helpful Tip to understand what each date controls. Correct dates copied from another posting or chosen only to keep the job visible. Save the job and check the public page.

If you fill the role before the planned deadline, close the posting promptly. Run Google’s Rich Results Test on the individual job address and check the expiry information, called validThrough, against the actual deadline. Do not keep extending the dates for a role that is no longer accepting applications.

A distant deadline alone does not establish that Google considers the vacancy less urgent or reduces its visibility. Google’s published guidance requires accurate expiry information and timely removal of expired jobs; it does not identify hiring urgency as a ranking signal. See Google’s job-posting guidance.

Problem: You corrected the job, but Google still shows the old information or has not added the page.

Solution: Check the saved page, then test it again:

1. Save the job and any company or location records you changed.
2. Open the public job page while signed out. Make sure the corrections appear and candidates can apply.
3. If old details still appear, use the clear-cache or purge-cache control in your caching plugin or hosting dashboard, then reload the job page.
4. Run Search Console’s Test live URL again. For a Google Jobs problem, run the Rich Results Test again too.
5. Use Request indexing in Search Console if it is available for the corrected page.

Wait at least a week before checking for the update in Google. Google needs time to read and process the corrected posting. It can take longer, and a week is not a guarantee that the job will appear. Repeated indexing requests do not speed this up.

Save changes made in your third-party SEO plugin too. After clearing any cache, compare the public page with the editor. If Search Console still reports an older version, check the last crawl date before assuming that the correction failed.