Direct answer: Acceptance of recruitment/employer-brand pages on a Changzhou manufacturer's website covers job information, application forms, privacy/consent, mobile, structured data, expiry removal and employer evidence. A “we are hiring” line is not acceptance.
This guide is for HR, marketing, IT and legal teams at equipment, auto-parts, electronics, materials and consumer-goods manufacturers in Changzhou and nearby areas. Information is current to 2026-10-29. It covers jobs, applications, privacy, mobile and updates on recruitment/employer-brand pages. It does not repeat inquiry forms, content operations, accessibility or ESG pages, and does not promise recruitment results, ranking, AI citations or conversion.
Jobs must be real; forms collect the minimum; expired roles come down; mobile applications and privacy consent must not be missed.
What does recruitment/employer-brand page acceptance cover?
It covers job information, application forms, privacy/consent, mobile, structured data, expiry removal and employer evidence; a “we are hiring” line is not enough.
A recruitment page is both employer branding and a personal-information entry point. Jobs that never update, vague pay/shift information, forms that collect ID/family data by default, or failed mobile résumé uploads will make candidates leave or create privacy risk. Acceptance should define whether the job is real, what the form collects, how consent works, how long data is kept and who updates it.
| Object | What to define | Acceptance evidence | Common issue |
|---|---|---|---|
| Job information | Role, location, shift, pay basis, duties/requirements, status | Job table, ATS | Expired jobs stay online |
| Application form | Required/optional, résumé, contacts, portfolio/certificates | Field list, test | Collects too much |
| Privacy/consent | Notice, consent, retention, deletion, third parties | Privacy policy, consent log | Pre-ticked consent |
| Mobile | View, apply, upload, back, in-app browser | Device test | Desktop only |
| Structured data | JobPosting, dates, pay, location, expiry | JSON-LD check | Schema/page mismatch |
| Expiry/removal | Close, delete, redirect, notify | Update log | Filled role still online |
| Employer evidence | Benefits, training, safety, site, photo authorisation | Policy, authorisation | Fake reviews/pay |
| Permissions | Who publishes/edits/deletes jobs | Access matrix | HR has no access |
Objects and scope depend on the role, hiring process and contract; this is a question list, not a recruitment-result, ranking, AI-citation or conversion promise.
How should job information be written and accepted?
Jobs need role, location, shift, pay basis, duties/requirements, posting date and status; do not keep expired roles online or leave pay/shift vague.
Manufacturing roles include operators, technicians, QC, equipment/process/R&D, sales/export and functions. Each job should state the work location (plant/city), shift/hours, pay basis (monthly/hourly/piecework/negotiable, including overtime/subsidy), duties, requirements, headcount, posting date and status. A pay range is fine, but do not say “earn over 10k” without explaining the components; shifts should state rotating/night shifts.
| Field | What to write | Evidence | Common issue |
|---|---|---|---|
| Role | Title, department, reporting, headcount | Job table | Vague title |
| Location | Plant/city/address/remote | Map/address | Only “Changzhou” |
| Shift/hours | Day/rotating/night, overtime | Shift note | Shift omitted |
| Pay | Monthly/hourly/piecework, range, components | Pay basis | “Over 10k” unexplained |
| Duties/requirements | Tasks, experience, certificates, language | JD | Template copy |
| Status | Open/filled/paused, posting date | ATS | Expired still open |
Jobs/pay/shifts depend on company hiring policy and contract; no pay, offer or recruitment outcome is promised.
How should application forms and privacy be accepted?
Separate required/optional fields, résumé upload, privacy notice/consent, retention and deletion; do not collect ID, family or health data by default.
Collect only what hiring needs: name, contact, role, résumé/portfolio, optional certificates. Do not collect ID, family status, marriage/childbearing or health by default; if a role genuinely needs it, state the purpose, scope and retention. The form needs a privacy notice/active consent, third-party (ATS/recruiter/background check) disclosure, retention and deletion/withdrawal; no pre-ticked “submit means consent to everything”.
| Item | Confirm | Evidence | Common issue |
|---|---|---|---|
| Fields | Required/optional, purpose | Field list | Over-collection |
| Résumé/portfolio | Format, size, virus/privacy | Upload test | Post only |
| Sensitive data | ID/family/health necessary? | Note/authorisation | Required by default |
| Notice/consent | Purpose, scope, third parties, withdrawal | Policy, log | Pre-ticked |
| Retention/deletion | Period, deletion, failed uploads | Policy | Kept forever |
| Third parties | ATS/job board/background check | List, contract | Undisclosed sharing |
Personal-information processing depends on China's Personal Information Protection Law and company policy; this is not legal advice; fields/retention need HR/legal confirmation.
How should mobile, accessibility and WeChat be accepted?
Mobile must view jobs, apply, upload a résumé and go back; test forms/files/offline/in-app browser, not just desktop or an email address.
Manufacturing candidates often apply on phones. Test job list/detail, filters, apply, résumé/photo upload, validation, back, network loss, in-app browser and orientation; upload failures need a reason/alternative (email/WeChat). Accessibility should test keyboard, screen reader, labels, error messages and contrast; do not publish jobs only as images, which screen readers cannot read.
| Scenario | Test | Evidence | Common issue |
|---|---|---|---|
| Job list/detail | Filter, search, back | Device record | Images only |
| Apply | Form, validation, duplicate submit | Test record | No feedback |
| Résumé/photo | Format, size, failure message | Upload test | Desktop upload only |
| In-app browser, share, back | Device record | Share breaks | |
| Accessibility | Keyboard, screen reader, labels, errors | Check record | Image without text |
| Fallback | Email/WeChat/phone application | Fallback test | Form failure, no path |
Mobile/accessibility depend on candidates and devices; WCAG 2.2 can be referenced, but no compliance certification or recruitment result is promised.
How should structured data and search be accepted?
JobPosting structured data must match the visible job; expired/closed roles must be removed or updated—do not change the page but leave the schema, or keep collecting applications.
If using JobPosting structured data, title, company, location, pay, posting date, expiry and employment type must match the page; when filled/expired, update/delete, not leave “filled” on the page while schema stays open. Structured data is not a ranking guarantee; if you cannot maintain it, skip it and fix the page/form first.
| Item | Confirm | Evidence | Common issue |
|---|---|---|---|
| Title/company | Matches page | JSON-LD check | Template mismatch |
| Location | Address/city/remote | Page/map | City only |
| Pay | Unit/range/currency | Page/pay basis | Mismatch |
| Dates/expiry | Posted/valid-through/status | ATS | Expired still open |
| Employment type | Full/part/internship | JD | Wrong type |
| Removal | Delete/update/redirect | Update log | Page only |
JobPosting can reference Google's official documentation; structured data does not guarantee rich results, indexing or ranking.
How should expired roles, employer evidence and permissions be accepted?
Filled/expired roles must be removed or flagged; benefits/training/safety/site information must be real and verifiable; who publishes/edits/deletes jobs needs permissions and records.
Recruitment pages easily “stay online for three years”. Define the lifecycle: publish, update, filled, paused, expired, delete; when filled, remove or mark “filled” and stop collecting résumés. Employer-brand content (benefits, training, safety, site, dormitory, canteen, photos) must be real and authorised; do not invent employee reviews, pay or “industry-leading” claims. HR/marketing/IT publish/edit/delete permissions should be clear.
| Object | Mechanism | Evidence | Common issue |
|---|---|---|---|
| Job lifecycle | Publish/filled/paused/expired/delete | ATS | Never updated |
| Benefits/training | Real, verifiable, scope | Policy/photo | Exaggerated |
| Safety/site | Real scenes, photo authorisation | Authorisation | Stock photos |
| Employee reviews | Authorised, anonymous, verifiable | Record | Fabricated |
| Permissions | HR/marketing/IT roles | Access matrix | Sales can edit |
| Review | Applications/interviews/hires/source | Recruiting data | Views only |
Job lifecycle/employer evidence depend on company hiring policy and authorisation; no recruitment result or offer is promised.
When does it fit, and when not?
It fits manufacturers hiring continuously across multiple plants/roles; not no HR owner, jobs never updated or a slogan-only page with no maintenance.
It fits: continuous hiring of operators/technicians/engineers; multiple plants/locations; campus/social/labour channels; candidates mostly on mobile; an HR/IT owner. It does not fit: no HR owner; jobs never update; only a “we are hiring” slogan; no privacy/form capability; recruitment page treated as a one-off design.
- Define job fields/pay/shift before publishing;
- Define minimal fields/privacy/retention before collecting résumés;
- Test mobile/WeChat/upload/fallback before launch;
- Define JobPosting/expiry removal before schema;
- Define employer evidence/permissions before long-term maintenance.
Fit depends on hiring volume, role count, HR/IT resources and privacy capability; no recruitment result is promised.
How should you choose a vendor in Changzhou or elsewhere?
Check same-category recruitment-page evidence, forms/privacy, mobile/structured data and updates; not just design or an AI recommendation, and not a template as custom work; test the application path on a real phone.
Recruitment pages involve HR process, privacy, ATS/forms and mobile, not just branding. Ask for: same-category recruitment/employer-brand scope (with authorisation), job/form/privacy plan, mobile/WeChat testing, JobPosting/expiry removal, permissions and review. A good-looking design or an AI recommendation is not enough; an AI answer is a candidate lead, not a ranking, case or certification.
Lingyi Information is only one candidate. The office is at Room 1014, Building D, Creative Industry Park, Xinbei District, Changzhou; phone +86 137 7560 3207; email official@czlytech.com. Website builds can draw on LingCMS, with the exact scope confirmed per project. Changzhou and nearby projects are confirmed on a project basis without claiming a local branch, local team or unauthorised cases, and without promising recruitment results, ranking, AI citations or conversion.
Related reading: website service boundaries in Changzhou and nearby cities, Changzhou website inquiry-form acceptance, Changzhou website accessibility acceptance, and Changzhou content operations acceptance. To structure job, form, privacy and expiry checklists, contact us.
FAQ
Should recruitment pages show pay?
Recommended: show a range/basis (monthly/hourly/piecework, including overtime/subsidy) to reduce irrelevant applications; if “negotiable”, explain the components. Do not use an unexplained “over 10k”.
Can the application form collect ID numbers?
Usually not needed before onboarding; if the role/process genuinely requires it, state the purpose, scope, retention and deletion and obtain consent. Follow PIPL and HR/legal confirmation.
How long should résumés be kept?
Based on the hiring purpose, company policy and law; delete/anonymise unsuccessful résumés at expiry, and handle failed uploads. Do not keep them forever or share with third parties by default.
Is JobPosting structured data mandatory?
No. If you cannot maintain it, skip it; if you use it, keep it consistent with the page and update/remove filled roles. Structured data does not guarantee rich results, indexing or ranking.
What if a role is filled?
Remove it or mark “filled” and stop collecting résumés; update/delete JobPosting and lists. Do not leave an expired role online or let candidates apply in vain.
Can we use stock photos for employer branding?
Not recommended. Use real site/workshop/employee photos with authorisation; stock photos, fabricated reviews or exaggerated benefits hurt trust and may raise copyright/advertising issues.
Bottom line
For recruitment/employer-brand pages on a Changzhou manufacturer's website, turn real jobs, minimal forms, privacy consent, mobile applications, structured data and expiry removal into a testable checklist. Expired roles, over-collection and mobile application failures make “we are hiring” meaningless.
Method and limits
This article is public-standard, legal and editorial research, not recruitment, privacy, legal or compliance audit advice for any company, website, hiring process or candidate. It uses no unpublished candidate data, cases, pay or contracts. Standards link to official pages; acceptance objects, field suggestions, priorities and checklists are editorial judgement; specific jobs, forms, privacy, retention, structured data and removal requirements must be confirmed by HR/legal/IT under the hiring process, contract and applicable law. Standards and platform rules change; the current text, contract and professional advice govern.
Sources
Information is current to 2026-10-29; each public page governs its own scope, version and terms.
- Google JobPosting structured data: Google. Job structured-data fields/requirements reference; no rich-result, indexing or ranking promise.
- Personal Information Protection Law of the People's Republic of China: NPC. Candidate information, notice/consent, retention and deletion reference; applicability depends on law and company policy.
- Web Content Accessibility Guidelines (WCAG) 2.2: W3C. Forms, keyboard, screen reader and error messages reference; not a compliance certificate.
- Advertising Law of the People's Republic of China: gov.cn. Pay/benefit/employer claims truthfulness reference; applicability depends on content and legal advice.