Improve Care Recruitment Pages With Claude Code: Reduce Anxiety Before Applying

Care providers do not lose applicants only because the salary is low. Many people leave the recruitment page before applying because they cannot picture the shift, night duty, transportation, documentation tool, break room, onboarding period, or whether a casual visit is allowed. A page that says “friendly workplace” and “training available” may be true, but it does not answer the candidate’s quiet questions.

Japan’s Ministry of Health, Labour and Welfare publishes a long-term care workforce outlook: about 2.4 million care workers will be needed in fiscal 2026 and about 2.72 million in fiscal 2040. The Care Work Foundation’s FY2024 survey also points to hiring and retention issues around wage level, leave, flexible shifts, workplace relationships, and workload. That is why a care recruitment page should explain the actual work before it asks for an application.

This article shows how to use Claude Code to improve a care and welfare recruitment page. The goal is not louder copy. The goal is a page that turns shift tables, facility photos, interview questions, resignation reasons, training notes, and application forms into information candidates can trust.

Key Points

• Put practical work conditions above vague mission statements.
• Ask Claude Code to organize job postings, shift examples, interview questions, photos, and candidate concerns.
• Keep salary, allowances, medical scope, night duty, privacy, and legal job terms under human review.
• Match visible page text with Google JobPosting structured data.
• Track visit booking, form starts, form submissions, interviews, acceptance, and agency dependency.

The Failure Scene On A Care Recruitment Page

A care facility often writes the recruitment page from the employer’s side. It lists philosophy, greetings, service types, and a broad message about caring for residents. The candidate reads the page from a different angle. They want to know what tomorrow’s shift feels like.

For a day-service role, the candidate may wonder whether they drive a vehicle, support bathing, use paper records, or stay late after service hours. For a group home, they care about night-staffing, rest breaks, emergency contacts, and handover. For home care, they want to know transport, cancellation rules, shadowing, and whether direct travel is allowed.

If those details are missing, candidates do not always ask at the interview. Many simply leave. The recruitment page should make a first visit or application feel possible.

Workflow: From Job Posting To Visit Booking

Start with one role, not the entire facility. Put the job posting, shift table, facility photos, training document, interview questions, decline reasons, and form fields into one table.

Input	Page artifact	Human review
Job posting	role, salary, location, employment type	legal terms and allowances
Shift table	day and night examples	whether examples match reality
Facility photos	workplace captions and order	consent and privacy
Interview questions	FAQ and visit notes	no misleading promise
Decline reasons	upper-page anxiety answers	salary, commute, night duty
Application form	fields and CTA	no sensitive data too early

Before Claude Code sees the material, remove applicant names, previous employer names, family situations, health details, and interview evaluations. The page needs patterns of concern, not personal data.

What Claude Code Handles And What Humans Review

Claude Code can draft the page structure, FAQ, photo captions, visit CTA, JobPosting checklist, and comparison table for candidate types. It can turn “transport work exists” into specific candidate questions: What vehicle? Which area? Is there ride-along training? Can a non-driver apply?

Humans review the conditions that create real risk: salary, allowances, care-worker treatment improvement payments, night duty, medical acts, qualification requirements, probation, contract renewal, overtime, breaks, privacy, and photo consent. If Claude Code writes “safe and reassuring” without evidence from a rule, shift table, or manager decision, delete it.

Google’s JobPosting structured data can make job pages eligible for a special job-search experience. It does not replace truthful page content. The job title, salary, location, employment type, and application method in JSON-LD must match the visible page.

Three Use Cases

Use case 1: Turn candidate anxiety into FAQ

Input interview questions, decline reasons, visit questions, and form drop-off notes. Claude Code classifies them by candidate intent and writes FAQ entries in the order a candidate needs them before applying. Output is a page FAQ, an upper-page reassurance block, and visit-preparation notes.

The weak answer is “Night shifts exist.” A better answer names the number of shifts, staffing model, break practice, and emergency escalation. A human checks the shift roster and manager explanation.

Use case 2: Reorder facility photos for hiring

Input the photo list: exterior, entrance, care floor, bathroom, break room, record tablet, vehicle, training scene, uniform, lockers. Claude Code proposes the order, captions, missing shots, and privacy checks. Output is a hiring-focused image plan.

Recruitment photos should not only show residents smiling. They should show where staff work. Candidates inspect the record screen, break space, vehicle, storage, and training setting. A human checks consent, name tags, posted schedules, and records visible in the image.

Use case 3: Compare JobPosting schema with the page

Input visible page text, JSON-LD, job posting, and external media listing. Claude Code compares title, location, salary, employment type, date posted, and application method. Output is a mismatch table and publish checklist.

Care roles often split base salary, night-duty allowance, qualification allowance, and treatment-improvement payments. If JSON-LD says one number, the page says another, and the job board says a third, candidates lose trust.

Copy-Paste Prompt

Act as the editor for a care and welfare recruitment page.

Goal:
Move candidate anxiety above the application form and make a visit booking or application easier.

Input:
- Role:
- Facility type:
- Location:
- Salary and allowances:
- Shift examples:
- Night duty:
- Transportation/driving:
- Documentation method:
- Training and shadowing period:
- Visit availability:
- Frequently asked interview questions:
- Decline reason notes:
- Facility photo list:
- Application form URL:

Output:
1. First-view headline
2. FAQ that reduces anxiety before applying
3. Photo order and captions
4. Salary, shift, and allowance review table
5. JobPosting structured data fields
6. Human review checklist before publishing

Rules:
- Do not guess salary, night duty, allowances, medical scope, or qualifications
- Do not include applicant or staff personal data
- Do not end with vague words such as friendly or rewarding
- Choose one primary CTA: visit booking or application

Working Check Code

const recruitmentPage = {
  role: "介護職員",
  location: "大阪市内のデイサービス",
  salaryRange: "月給 235,000円〜285,000円",
  shifts: ["早番 7:30-16:30", "日勤 8:30-17:30", "遅番 10:00-19:00"],
  applicationFlow: ["見学予約", "面談", "条件確認", "内定"],
  carePolicy: "利用者さんの生活リズムを尊重し、記録と申し送りを丁寧に行う",
  privacyNote: "応募フォームでは健康情報、家族情報、マイナンバーを入力させない",
  jobPostingFields: {
    title: "介護職員",
    hiringOrganization: "サンプル福祉会",
    jobLocation: "大阪府大阪市",
    datePosted: "2026-07-19",
    employmentType: "FULL_TIME",
  },
  ctas: ["apply"],
};

const requiredPageFields = ["role", "location", "salaryRange", "shifts", "applicationFlow", "privacyNote"];
const requiredJobPostingFields = ["title", "hiringOrganization", "jobLocation", "datePosted", "employmentType"];

const missingPageFields = requiredPageFields.filter((field) => {
  const value = recruitmentPage[field];
  return Array.isArray(value) ? value.length === 0 : !value;
});

const missingJobPostingFields = requiredJobPostingFields.filter((field) => !recruitmentPage.jobPostingFields[field]);
const asksSensitiveInfo = /健康情報|家族情報|マイナンバー|銀行口座/.test(recruitmentPage.privacyNote) === false;
const tooManyCtas = recruitmentPage.ctas.length !== 1 || recruitmentPage.ctas[0] !== "apply";
const hasShiftDetail = recruitmentPage.shifts.length >= 2;
const hasFlow = recruitmentPage.applicationFlow.length >= 3;

if (missingPageFields.length || missingJobPostingFields.length || asksSensitiveInfo || tooManyCtas || !hasShiftDetail || !hasFlow) {
  console.error("採用ページの公開前チェックに未解決があります。");
  console.error({ missingPageFields, missingJobPostingFields, asksSensitiveInfo, tooManyCtas, hasShiftDetail, hasFlow });
  process.exit(1);
}

console.log("Care recruitment page checklist is ready for human review.");

This code is a small pre-publish check, not legal review. It stops the draft if role, location, salary, shifts, application flow, privacy note, or JobPosting fields are missing.

Pitfall: Common Mistakes And Fixes

Pitfall 1: Ending with “no experience required.” The cause is that onboarding is not written. Fix it by showing day one, week one, and month one.

Pitfall 2: Making salary look cleaner than it is. The cause is mixing base pay, allowances, night duty, and treatment-improvement payments. Fix it with a visible breakdown.

Pitfall 3: Using photos that reveal private information. The cause is checking composition but not name tags, records, calendars, or residents’ faces. Fix it with a photo privacy checklist.

Pitfall 4: Showing application and visit booking with equal weight. The cause is employer impatience. Fix it by choosing a primary CTA based on candidate maturity.

ROI Metrics

Do not start with hires only. Track page views, visit CTA clicks, form starts, form submissions, interviews, acceptance, decline reasons, and agency dependency. If one extra visit booking per month comes through the owned site, the economics of recruitment media can change.

The Ministry’s care workforce page frames policy around entry promotion, skill development, work environment, and treatment improvement. A recruitment page should mirror those points instead of only selling the facility.

FAQ

Is a recruitment page needed if we use job boards? Yes. Candidates often search the facility name before applying. Your page becomes the final confirmation.

Should beginners and experienced staff share one page? Usually no. Beginners inspect training and visit safety. Experienced workers inspect shift, staffing, records, and pay details.

How much should we write about allowances? Write only what you can verify. If conditions vary, separate fixed pay, examples, and items to confirm during interview.

What privacy issue appears most often? Photos and forms. Do not ask for sensitive information too early, and do not publish faces, names, schedules, or records without review.

Consultation Path

For one facility, start by collecting the current URL, job posting, shift example, interview questions, and decline notes. For several facilities or roles, use training and consultation to separate Claude Code drafts from human approval of hiring conditions. The page-design thinking also connects to the agency permission checklist.

What I Actually Checked

For this article, I checked the Ministry care workforce page, the Care Work Foundation FY2024 survey summary, and Google Search Central JobPosting documentation. I also ran the JavaScript checklist locally to confirm role, salary, shifts, application flow, privacy note, and schema fields. The first action for a beginner is to move shift examples, visit availability, and FAQ above the application form.