{"slug":"publish-roles","title":"Publishing open roles that get found","description":"How to list open roles on Parlel so candidates, Google for Jobs and AI agents all find them: verification, JobPosting markup and indexing.","cluster":"Find work","updated":"2026-09-21","url":"https://parlel.com/guides/publish-roles","markdown":"A role published on Parlel is read in three places at once: by candidates on the [job board](/jobs), by Google for Jobs through structured markup, and by AI agents through the API. One publishing flow feeds all three -- if you write the posting right.\n\n## Before you publish: verify\n\n[Verify your company](/guides/verify-company) first. Candidates filter toward verified employers, every role page carries the company's verification state, and an unverified posting asks the reader to trust an unidentified author. Verification takes minutes and upgrades every role you will ever publish.\n\n## Write the posting for three readers\n\n**The candidate** wants specifics: responsibilities, stack, seniority, location posture, comp band if you have one. Concrete postings attract concrete applicants; vague postings attract volume you will have to filter by hand.\n\n**Google for Jobs** reads the JobPosting structured data Parlel renders server-side on every open role page -- title, employer, location, employment type. Because the markup is in the served HTML (not built in JavaScript), Google indexes it directly, and Parlel additionally pushes new postings to Google's Indexing API on publish. Your part of this contract: accurate titles and locations. A \"remote\" role with an on-site location field confuses the index and the applicant alike.\n\n**AI agents** read the same posting through `search_jobs` and `get_job` ([MCP guide](/guides/parlel-mcp-guide): https://api.parlel.com/mcp). Agents match literally -- they do not infer that \"customer-obsessed problem solver\" means \"support engineer\". Plain titles and explicit skills are machine-readable kindness.\n\n## Closing matters as much as publishing\n\nWhen a role fills, close it promptly. Closed roles leave the board and the sitemap immediately (the page itself stays live so existing citations never 404 -- a deliberate choice), which keeps your company page honest and the job index clean. A company page full of stale postings reads as a company that stopped paying attention, and candidates notice.\n\n## Roles are also prospecting\n\nEvery open role advertises what you need, which -- as [finding customers](/guides/find-customers) explains -- is exactly what vendors read. Publishing specific roles is free market signaling: partners, candidates and customers all update their picture of you from it. Publish deliberately, in both senses.\n","html":"<p>A role published on Parlel is read in three places at once: by candidates on the <a href=\"/jobs\">job board</a>, by Google for Jobs through structured markup, and by AI agents through the API. One publishing flow feeds all three -- if you write the posting right.</p>\n<h2>Before you publish: verify</h2>\n<p><a href=\"/guides/verify-company\">Verify your company</a> first. Candidates filter toward verified employers, every role page carries the company's verification state, and an unverified posting asks the reader to trust an unidentified author. Verification takes minutes and upgrades every role you will ever publish.</p>\n<h2>Write the posting for three readers</h2>\n<p><strong>The candidate</strong> wants specifics: responsibilities, stack, seniority, location posture, comp band if you have one. Concrete postings attract concrete applicants; vague postings attract volume you will have to filter by hand.</p>\n<p><strong>Google for Jobs</strong> reads the JobPosting structured data Parlel renders server-side on every open role page -- title, employer, location, employment type. Because the markup is in the served HTML (not built in JavaScript), Google indexes it directly, and Parlel additionally pushes new postings to Google's Indexing API on publish. Your part of this contract: accurate titles and locations. A \"remote\" role with an on-site location field confuses the index and the applicant alike.</p>\n<p><strong>AI agents</strong> read the same posting through <code>search_jobs</code> and <code>get_job</code> (<a href=\"/guides/parlel-mcp-guide\">MCP guide</a>: https://api.parlel.com/mcp). Agents match literally -- they do not infer that \"customer-obsessed problem solver\" means \"support engineer\". Plain titles and explicit skills are machine-readable kindness.</p>\n<h2>Closing matters as much as publishing</h2>\n<p>When a role fills, close it promptly. Closed roles leave the board and the sitemap immediately (the page itself stays live so existing citations never 404 -- a deliberate choice), which keeps your company page honest and the job index clean. A company page full of stale postings reads as a company that stopped paying attention, and candidates notice.</p>\n<h2>Roles are also prospecting</h2>\n<p>Every open role advertises what you need, which -- as <a href=\"/guides/find-customers\">finding customers</a> explains -- is exactly what vendors read. Publishing specific roles is free market signaling: partners, candidates and customers all update their picture of you from it. Publish deliberately, in both senses.</p>","related":[{"slug":"find-jobs","title":"How to find open roles on Parlel","description":"Search open roles by keyword, remote posture and seniority on Parlel's job board. How to read a posting and what to do next.","url":"https://parlel.com/guides/find-jobs"},{"slug":"verify-company","title":"Verifying your company on Parlel","description":"How company verification works on Parlel, why the verified badge matters for hiring and sales trust, and how to get it.","url":"https://parlel.com/guides/verify-company"},{"slug":"company-page-guide","title":"Building a company page that ranks","description":"How to write a Parlel company page that candidates, customers and search engines all find: description, roles, verification and freshness.","url":"https://parlel.com/guides/company-page-guide"},{"slug":"find-customers","title":"Finding customers and early adopters on Parlel","description":"How founders find their first customers: searching companies by hiring and size signals, reading pages for pain, and first-contact outreach.","url":"https://parlel.com/guides/find-customers"}]}