The 2026 Recruitment Agency SEO Verification Checklist

Use this section to verify whether search systems and users can reach, render, understand, and complete the intended action on live job and service pages.

Check: Active job listing markup Evidence required: A live job page, its rendered content, its JobPosting structured data, and validation output from current Google and Schema.org testing tools. Pass/fail condition: Pass when the markup accurately reflects the visible role details and required fields are valid.

Fail when the markup contains stale, hidden, contradictory, or unsupported information. Severity: High for active roles intended for search discovery. Owner: SEO owner with the job-board or development owner.

Corrective action: Align structured data with the real role and remove unsupported properties. The prior page stated that this search surface captures 30-50% of job-related clicks, but no supporting source URL is present, so preserve that figure only as historical editorial context and not as a verified benchmark. Validation: Re-run the validator, inspect the live page, and confirm that the job remains current.

Check: Expired job URL lifecycle Evidence required: A crawl export of closed roles, inbound links to those roles, the destination users should see after closure, and the current HTTP response. Pass/fail condition: Pass when each closed role follows a documented lifecycle that matches user need.

Fail when a closed role sends applicants to an irrelevant destination, remains open after closure, or leaves a dead path without a reason. Severity: High when the URL has external links, search visibility, or ongoing user demand.

Owner: Job-board product owner with SEO. Corrective action: Use a 301 redirect only when there is a genuinely relevant replacement destination. Allow a 404 response when content is intentionally gone and there is no appropriate substitute, or use another technically correct removal path when required. Validation: Re-crawl the URL set and verify the response, destination relevance, and removal of stale structured data.

Check: Mobile application usability Evidence required: Real-device testing from a search landing page through the application handoff, including any third-party applicant tracking system. Pass/fail condition: Pass when role details, controls, forms, and handoffs remain readable and usable on supported mobile devices.

Fail when scripts, overlays, redirects, or form behavior block progress. Severity: Critical when applicants cannot complete the intended action. Owner: Product, ATS, or web engineering owner depending on the failing layer.

Corrective action: Repair the responsible template, script, integration, or responsive behavior without removing information candidates need. Validation: Repeat the same journey on representative devices after deployment.

Check: Filter and canonical control Evidence required: A crawl of filtered job URLs, canonical output, indexation evidence, internal links, and examples of combinations created by location, salary, sector, or job type filters.

Pass/fail condition: Pass when crawl and indexation behavior matches a documented rule for useful versus duplicative combinations. Fail when parameter pages create uncontrolled duplication, contradictory canonicals, or inaccessible role pages.

Severity: High when the issue affects a large portion of the job inventory. Owner: SEO and development. Corrective action: Define which filtered states deserve independent URLs and which should consolidate, then implement consistent canonical, linking, and crawl behavior.

Validation: Re-crawl representative filter combinations and compare live canonical and indexation signals with the documented rule.

Recruitment content should help a hiring manager or candidate make a specific decision. Avoid mixing commercial employer intent with job-seeker intent on the same page unless the page genuinely needs both.

Check: Sector and service landing pages Evidence required: An inventory of services and specialisms the firm actually delivers, search query evidence where available, and the live landing pages. Pass/fail condition: Pass when each important page explains the sector, role types, client problem, delivery context, relevant recruiter expertise, and a clear next action without duplicating another page.

Fail when the page is generic, unsupported, or interchangeable with other specialism pages. Severity: High for core commercial pages. Owner: Sector lead with content or SEO. Corrective action: Replace generic claims with specific, supportable information from the practice.

Create a new page only when the specialism is real and warrants distinct content. Validation: Have the responsible practice owner confirm factual accuracy and compare similar pages for meaningful differentiation.

Check: Salary and market resources Evidence required: The data source, period, geography, job families, methodology notes, and owner responsible for keeping the resource current. Pass/fail condition: Pass when the guide explains what its data covers and does not imply broader certainty than the evidence supports.

Fail when salary claims lack context, are stale, or cannot be reconciled to a source. Severity: Medium to high depending on how prominently the resource is used in employer or candidate decisions. Owner: Recruitment operations or market intelligence with editorial review.

Corrective action: Add source context, update stale material, or narrow the claim to what internal placement data or another documented source can support. Validation: Reconcile sample figures back to the stated source and review date.

Check: Headings and titles for local commercial intent Evidence required: Search query evidence, the actual office footprint, the page title, H1, body copy, and contact path. Pass/fail condition: Pass when the page naturally describes the service and genuine location.

Fail when a city is inserted into headings without useful local information or when multiple pages target nominal markets the firm does not operate from. Severity: Medium. Owner: SEO and content. Corrective action: Use a clear primary heading that reflects the real page topic, strengthen office-specific information where a genuine location exists, and consolidate unsupported location variants. Validation: Review the live page against the office record and intended search task.

Check: Internal links to recruitment service pages Evidence required: A crawl or manual map of contextual links from relevant articles, salary guides, recruiter profiles, job pages, and office pages to the main recruitment service context at /industry/professional/recruitment-agency.

Pass/fail condition: Pass when links are useful, descriptive, and point to the page that best continues the user's task. Fail when anchors are repetitive, misleading, or inserted only to manipulate authority.

Severity: Medium. Owner: SEO and editorial. Corrective action: Add or revise contextual links where the relationship is genuine. Validation: Re-crawl links and manually confirm anchor meaning, destination, and user usefulness.

Local search work should represent real office operations accurately. A nominal service area is not enough to justify a location page or profile.

Check: Google Business Profile for each genuine office Evidence required: The live profile, office address, staffed operating details, primary business category, website destination, and source-of-truth business records.

Pass/fail condition: Pass when profile information accurately represents a genuine office and matches the linked site. Fail when the profile is duplicated, stale, misleading, or attached to a location that does not qualify as a real office.

Severity: Critical for address, phone, or status errors that can misdirect employers or candidates. Owner: Local marketing or operations. Corrective action: Correct controlled information and remove or resolve duplicates through supported platform processes.

Category selection should describe the business accurately rather than be chosen as a guaranteed visibility tactic. Validation: Re-open the public profile and linked office page after changes.

Check: Review request practice Evidence required: The actual request workflow used with clients and candidates, examples of request language, and the teams responsible for sending it. Pass/fail condition: Pass when eligible customers are asked consistently for honest feedback without incentives, negative-feedback suppression, or selecting only satisfied people.

Fail when the process uses review gating or scripts that pressure users toward a positive rating. Severity: High because the issue affects trust and platform compliance. Owner: Client experience or candidate experience with local marketing.

Corrective action: Replace selective requests with a neutral process. The prior page proposed 5-10 new reviews monthly, but that cadence is not documented here as a ranking requirement and should be treated only as historical editorial text rather than a target. Validation: Audit the live request flow and a sample of recent outreach.

Check: Office structured data Evidence required: The office page, its LocalBusiness markup where used, visible address and hours, and structured data validation. Pass/fail condition: Pass when markup accurately reflects the real office and visible page content.

Fail when geo-coordinates, hours, names, or contact details conflict with the page or source-of-truth records. Severity: Medium, rising when inaccurate data affects multiple office pages. Owner: SEO with development.

Corrective action: Correct the page and markup together. Do not add properties solely to pursue a special search feature. Validation: Re-run validation and compare the rendered office page with the business record.

Recruitment sites handle personal information and make claims about people, markets, qualifications, affiliations, and services. In 2026, these elements should be treated as factual governance issues, not as a checklist of ranking signals.

Check: Recruiter and leadership profiles Evidence required: Current role information, sector responsibilities, approved biographies, professional history the firm is entitled to publish, and links to relevant service or office pages.

Pass/fail condition: Pass when profiles are accurate, current, and specific enough to help employers or candidates understand who handles the relevant work. Fail when biographies are generic, outdated, or contain credentials the firm cannot substantiate.

Severity: Medium to high on pages used to establish specialist capability. Owner: HR or operations with editorial review. Corrective action: Replace unsupported claims with verifiable experience and clearly state current responsibilities. Validation: Have the profile owner or responsible manager approve the live version.

Check: Privacy and data collection Evidence required: Forms, consent language, privacy notices, data flows, vendor agreements, retention rules, and the compliance requirements that actually apply to the firm.

Pass/fail condition: Pass when the implemented process matches approved legal and privacy requirements. Fail when forms collect unnecessary data, notices are inconsistent with the real process, or responsibilities are unclear.

Severity: Critical when the issue creates legal, privacy, or security exposure. Owner: Legal, privacy, security, or the designated internal compliance owner. Corrective action: Route issues to qualified internal or external counsel or privacy specialists.

Do not claim that compliance status itself guarantees indexing or rankings. Validation: Re-test forms and confirm that the implemented workflow matches the approved policy.

Check: Affiliations, certifications, and awards Evidence required: Current membership records, permission to display marks, award details, and the relevant issuing organization. Pass/fail condition: Pass when every displayed affiliation, certification, or award is current, accurately described, and supportable.

Fail when logos are outdated, ambiguous, or used without evidence. Severity: Medium. Owner: Marketing with operations or legal. Corrective action: Remove unsupported marks or add accurate context about what the affiliation or award means. Validation: Reconcile each displayed claim with an internal record or issuing source.

Quick check: Confirm current job posting dates - Evidence required: a live active role, source-of-truth vacancy record, and its structured data. Pass/fail: pass when the visible posting date and structured data agree with the real publication state; fail when a closed or stale job appears artificially refreshed.

Severity: High. Owner: job-board operations. Corrective action: update only when the underlying vacancy record supports the change. Validation: re-open the live page after deployment. Estimated review time: 30 minutes.

Quick check: Make candidate navigation obvious - Evidence required: desktop and mobile navigation plus the candidate journey from the homepage. Pass/fail: pass when current roles or the careers area can be found without relying on a hidden footer-only path; fail when users must guess where jobs live.

Severity: Medium. Owner: web or product. Corrective action: expose a clear candidate route that fits the site's information architecture. Validation: repeat the navigation task. Estimated review time: 15 minutes.

Quick check: Repair broken internal links - Evidence required: the latest crawl report and a sample of broken destinations. Pass/fail: pass when priority internal links resolve to relevant live destinations; fail when important employer, candidate, office, recruiter, or resource links remain broken.

Severity: High. Owner: SEO with content or web. Corrective action: update, remove, or redirect links according to the destination's real status. Validation: re-crawl after release. Estimated implementation window: 1-2 hours for a contained set, with larger inventories scoped separately rather than forced into the same estimate.

• Expired jobs left unmanaged. Evidence: crawl results, job status, inbound links, and current response behavior. Pass when every closed job follows a documented keep, archive, redirect, or removal decision; fail when stale vacancies remain open or users land on dead ends. Severity: High. Owner: job-board operations with SEO. Corrective action: apply the appropriate lifecycle rule. Validation: re-crawl the affected URLs.
• Literal 'near me' optimization. Evidence: page copy, office footprint, and query data. Pass when local pages describe genuine office locations and useful local information naturally; fail when pages repeat 'near me' or city terms without adding value. Severity: Medium. Owner: SEO and content. Corrective action: rewrite around the real office and user task. Validation: review the page against office records and search intent.
• Recurring technical mistakes. Evidence: the existing mistakes guide at /guides/recruitment-agency-seo-mistakes, current crawl data, and issue ownership. Pass when known defects are tracked through correction and validation; fail when the same canonical, redirect, indexation, or job lifecycle problems repeatedly return. Severity: High. Owner: SEO and web engineering. Corrective action: fix the system or template causing recurrence, not only the individual URL. Validation: re-run the relevant audit after release.
• Generic trust imagery and claims. Evidence: the live page, source files, permissions, and factual context. Pass when imagery and claims accurately represent the team, office, or service; fail when stock material or unsupported copy creates a misleading impression. Severity: Medium. Owner: marketing and operations. Corrective action: replace misleading assets or unsupported wording with accurate material. Validation: have the responsible business owner review the final page.