JobPosting<\/code> Schema<\/strong>: Put it on every single live job page. Include title, description, location (or remote status), salary, and the validThrough<\/code> date ^(1).<\/li>\n\n\n\n- Get into Google for Jobs<\/strong>: Push your jobs directly to Google. Use your new schema and the Indexing API, or have your Applicant Tracking System (ATS) handle the feed ^(2).<\/li>\n\n\n\n
- Publish Sector + Location Pages<\/strong>: Create landing pages for your core business, like \u201cIT Recruitment Agency in Manchester.\u201d Load them with unique proof, client FAQs, and a simple lead form ^(3).<\/li>\n\n\n\n
- Fix Duplicates & Expired Jobs<\/strong>: Stop confusing Google. Use canonical tags or 301 redirects for duplicates. For expired jobs, remove the schema and set an
unavailable_after<\/code> header ^(4).<\/li>\n\n\n\n- Optimize Google Business Profile (GBP)<\/strong>: Claim a GBP for each office. Add your services, fill out the description, and post weekly updates to stay active.<\/li>\n<\/ol>\n\n\n\n
The 30-Day Recruitment SEO Action Plan<\/h2>\n\n\n\n
A week-by-week sprint to build your foundation and get results.<\/p>\n\n\n\n
Week 1 , Technical Foundation & Google for Jobs<\/h3>\n\n\n\n
Get your house in order. This week is about making sure Google can find and understand your jobs.<\/p>\n\n\n\n
\n- Get on Google’s Radar<\/strong>: Verify your site in Google Search Console. Upload an XML sitemap that includes your jobs, location pages, and service pages. Use the
<lastmod><\/code> tag for jobs to show freshness.<\/li>\n\n\n\n- Ensure Crawlability<\/strong>: Check your
robots.txt<\/code> file to make sure you are not blocking Googlebot from your job pages. Ensure your entire site uses HTTPS.<\/li>\n\n\n\n- Deploy <\/strong>
JobPosting<\/code> Schema<\/strong>: Add the JobPosting<\/code> JSON-LD code to all active job detail pages. Use Google\u2019s Rich Results Test to validate it and fix any errors ^(1).<\/li>\n\n\n\n- Set Expiration Dates<\/strong>: Use the
validThrough<\/code> property for every job. The moment a job expires, your system should automatically remove its schema.<\/li>\n\n\n\n- Use the Indexing API<\/strong>: This tells Google instantly when a job is added, updated, or removed. Connect to it directly with developer help, via a plugin, or check if your ATS supports it ^(1).<\/li>\n<\/ol>\n\n\n\n
Week 2 , Winning Locally with GBP & Reviews<\/h3>\n\n\n\n
This week, you appear on your local map. Stop being invisible to clients in your backyard.<\/p>\n\n\n\n
\n- Claim Your GBP<\/strong>: Get a Google Business Profile for every physical office. Set your primary category to \u201cEmployment agency\u201d or \u201cRecruiter.\u201d Add secondary categories for your niches.<\/li>\n\n\n\n
- Detail Your Services<\/strong>: Add every service you offer (e.g., “IT Recruitment,” “Executive Search”). Write short descriptions and include your target sectors and cities.<\/li>\n\n\n\n
- Nail Your NAP<\/strong>: Your Name, Address, and Phone number (NAP) must be identical across your website footer, GBP, and major business directories. Consistency builds trust with Google.<\/li>\n\n\n\n
- Get Reviews<\/strong>: Ask every successfully placed candidate and every satisfied client for a review. Automate requests to send an email or SMS immediately after a positive interaction.<\/li>\n\n\n\n
- Reply to All Reviews<\/strong>: Respond to all reviews within 24-48 hours. Thank positive reviewers. For negative reviews, acknowledge the issue, apologize, and invite an offline conversation.<\/li>\n<\/ol>\n\n\n\n
Week 3 , On-Page SEO & Internal Linking<\/h3>\n\n\n\n
Make your pages easy for both Google and humans to read.<\/p>\n\n\n\n
\n- Structure Your Job Ads<\/strong>: Use one H1 tag with the exact job title. Use H2s for \u201cRequirements,\u201d \u201cSalary & Benefits,\u201d \u201cLocation,\u201d and \u201cHow to Apply.\u201d No jargon.<\/li>\n\n\n\n
- Write Better Metas<\/strong>: Create a clear meta title:
Job Title \u2013 City \u2013 Key Benefit<\/code>. Write a meta description that includes a benefit and a call-to-action (CTA).<\/li>\n\n\n\n- Build Internal Links<\/strong>: Every job page should link back to its main sector page and location page. Also, link to a few related jobs using descriptive anchor text like \u201cView more marketing jobs in London\u201d.<\/li>\n\n\n\n
- Add a “Why Us” Block<\/strong>: On your sector and location pages, add a short section with 3 bullet points on your key wins (e.g., time-to-hire, placement success rate) and a clear CTA.<\/li>\n<\/ol>\n\n\n\n
Week 4 , Cleanup, Speed & Measurement<\/h3>\n\n\n\n
Finalize the setup and start tracking what matters.<\/p>\n\n\n\n
\n- Handle Expired Jobs<\/strong>: Redirect expired job URLs to the most relevant live page, like its category (
\/jobs\/marketing\/<\/code>) or a similar role. If there is no good match, let it return a 404 or 410 error. Just do not leave it active ^(4).<\/li>\n\n\n\n- Scrub Schema from Old Jobs<\/strong>: On any expired job pages you must keep live, remove the
JobPosting<\/code> schema. Add an unavailable_after<\/code> header tag or a noindex<\/code> tag.<\/li>\n\n\n\n- Fix Page Speed<\/strong>: Your site needs to load in under 3 seconds. Compress images, minify CSS\/JS, and enable server caching. Use Google’s PageSpeed Insights to find bottlenecks.<\/li>\n\n\n\n
- Track Key KPIs<\/strong>: Set up tracking for job applications from organic search, employer inquiry form submissions, and phone calls. Focus on conversions.<\/li>\n<\/ol>\n\n\n\n
Google for Jobs Setup (End\u2011to\u2011End)<\/h2>\n\n\n\n
Google for Jobs is a major job source, and you need to be on it ^(2). Here is how.<\/p>\n\n\n\n
\n- Choose Your Path<\/strong>: You have three options:\n
\n- ATS Feed<\/strong>: Many Applicant Tracking Systems (like Bullhorn or Greenhouse) integrate directly. This is easy but gives you less control.<\/li>\n\n\n\n
- Syndication<\/strong>: Post to a major job board that Google trusts. This is also easy but adds a middleman.<\/li>\n\n\n\n
- Custom Schema + Indexing API<\/strong>: The best option. You add the schema yourself and use the API to ping Google directly for total control and the fastest updates ^(1).<\/li>\n<\/ul>\n<\/li>\n<\/ol>\n\n\n\n
Path<\/th> Ease of Use<\/th> Control<\/th> Key Consideration<\/th><\/tr> ATS Feed<\/strong><\/td>High<\/td> Low<\/td> Easy setup, but you have less control over the data and update speed.<\/td><\/tr> Syndication<\/strong><\/td>High<\/td> Low<\/td> Simple way to get listed, but adds a third-party between you and Google.<\/td><\/tr> Custom Schema + Indexing API<\/strong><\/td>Low (Technical)<\/td> High<\/td> Offers total control and the fastest updates, which is the best option for performance.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n\n- Mark Up Single Job Pages Only<\/strong>:
JobPosting<\/code> schema belongs only on pages with one job, not on category or list pages. The content on the page (title, salary, description) must exactly match the content in the schema.<\/li>\n\n\n\n- Handle Remote Roles Correctly<\/strong>: For remote jobs, set
jobLocationType: \"TELECOMMUTE\"<\/code>. Then, use applicantLocationRequirements<\/code> to specify which country or region the candidate must be in (e.g., “GB”) ^(1).<\/li>\n\n\n\n- Implement the Indexing API for Instant Updates<\/strong>: This is a technical task but critical for keeping job listings fresh.\n
\n- Prerequisites:<\/strong> Your developer will need to verify domain ownership in Google Search Console, create a Google Cloud project, enable the Indexing API, and create a service account with a JSON key file.<\/li>\n\n\n\n
- Grant Access:<\/strong> The service account must be added as an “Owner” in your Google Search Console.<\/li>\n\n\n\n
- Execution:<\/strong> Use backend code to send an HTTP POST request to
https:\/\/indexing.googleapis.com\/v3\/urlNotifications:publish<\/code> each time a job is posted (URL_UPDATED<\/code>) or filled (URL_DELETED<\/code>). This tells Google to re-crawl the page immediately.<\/li>\n<\/ul>\n<\/li>\n\n\n\n- Validate Your Schema<\/strong>: Before you do anything else, run at least 10 of your job URLs through Google’s Rich Results Test. Fix every error and warning.<\/li>\n<\/ol>\n\n\n\n
Template , JobPosting JSON\u2011LD<\/p>\n\n\n\n
Paste this into the <head><\/code> of your single job pages, updating the placeholder values.<\/p>\n\n\n\n{
\"@context\": \"https:\/\/schema.org\",
\"@type\": \"JobPosting\",
\"title\": \"Senior Java Developer\",
\"description\": \"<p>Plain-English summary of the role. Add 5\u20137 bullet points for responsibilities and 5\u20137 for requirements. Avoid fluff.<\/p>\",
\"datePosted\": \"2025-01-10\",
\"validThrough\": \"2025-02-10T23:59\",
\"employmentType\": \"FULL_TIME\",
\"hiringOrganization\": {
\"@type\": \"Organization\",
\"name\": \"Acme Recruitment\",
\"sameAs\": \"https:\/\/www.example.com\",
\"logo\": \"https:\/\/www.example.com\/logo.png\"
},
\"jobLocation\": {
\"@type\": \"Place\",
\"address\": {
\"@type\": \"PostalAddress\",
\"addressLocality\": \"Leeds\",
\"addressRegion\": \"West Yorkshire\",
\"addressCountry\": \"GB\"
}
},
\"jobLocationType\": \"TELECOMMUTE\",
\"applicantLocationRequirements\": {
\"@type\": \"Country\",
\"name\": \"GB\"
},
\"baseSalary\": {
\"@type\": \"MonetaryAmount\",
\"currency\": \"GBP\",
\"value\": { \"@type\": \"QuantitativeValue\", \"minValue\": 55000, \"maxValue\": 70000, \"unitText\": \"YEAR\" }
}
}<\/code><\/pre>\n\n\n\nSector + Location Page Framework (Rank + Convert)<\/h2>\n\n\n\n
These pages are for attracting clients, not candidates. They target high-value, long-tail keywords like \u201cfinance recruitment agency Birmingham\u201d ^(3).<\/p>\n\n\n\n
![\"BlockNote](\"https:\/\/www.dropbox.com\/scl\/fi\/wpb7a928j410pjguyjh96\/image-65.png?rlkey=mdry38c4p7nmf4q9h5ee86m8u&dl=1\")
<\/figure>\n\n\n\n