Launch Potato just hired for four talent leads whose job is "pipeline built ahead of demand" and "a sourcing engine ... inbound and outbound". But every role on launchpotato.com is loaded by script after the page opens, every role page has the same title ("Launch Potato - Open Role"), none carries JobPosting structured data, and the Greenhouse board redirects to these pages, so there is no indexable copy anywhere. The sitemap lists none of the 11 roles. Google for Jobs, which reads JobPosting markup, cannot show a Launch Potato role to the performance marketers searching for one.
First action
Test one role page in Google's Rich Results Test and confirm it shows no job.
How to measure it
Applicants from organic job search
- Now
- –
- Target
- +50%
- By
- 60 days
Steps
Pick URLs
One readable URL per role.
Web Engineer 1 day
Render server-side
Description in the HTML.
Web Engineer 3 days
Add JobPosting markup
Title, date, remote location, type, pay where published.
Web Engineer 1 day
Unique titles
Role name and "Remote" in each title.
Head of Talent, Performance Marketing 1 hour
Sitemap
Role URLs with real dates; 410 when closed.
Web Engineer 1 day
Validate
Rich Results Test and Search Console.
Web Engineer 1 day
Tag sources
Applicant source in Greenhouse.
Recruiting Ops Manager 1 day
Measure
Applicants by source each month.
Recruiting Ops Manager monthly
Why it works
Render each role server-side at its own URL (for example /careers/head-of-paid-social-insurance) with a unique title, the full description in the HTML and JobPosting structured data (title, date posted, remote location, employment type, salary where it is published). Add the role URLs to the sitemap with real dates, keep the Greenhouse redirect pointing to them, and remove a page with a 410 when the role closes. Check eligibility with Google's Rich Results Test.
Inbound applicants from job search cost nothing per candidate, and Google for Jobs is where senior and passive candidates browse. For a lean talent team that is a free sourcing channel.
Ready to use
ChecklistIndexable role page
[ ] One URL per role, readable slug [ ] Unique title: role, team, "Remote, US" [ ] Full description in the server HTML [ ] JobPosting JSON-LD: title, description, datePosted, validThrough, employmentType, jobLocationType TELECOMMUTE, applicantLocationRequirements, hiringOrganization [ ] Salary range where it is published [ ] Listed in sitemap.xml with https and lastmod [ ] 410 or redirect when the role closes [ ] Passes the Rich Results Test
Risks and how to handle them
Stale roles stay indexed
Generate pages from the Greenhouse feed and expire them automatically.
Low-fit applicants
Keep the "only apply if" notes from the posts in the page text.
Evidence
- Your websiteCareers pages (checked October 21, 2026): /careers shows "Loading open roles…" and fills the list by script; every role page has the same title "Launch Potato - Open Role", loads its text by script ("Loading this role…") and carries no JobPosting structured data; the Greenhouse board redirects to these pages; the sitemap lists /open-roles but none of the 11 roles, and all its URLs use http://.Source
- HiringHead of Talent, Performance Marketing and Head of Talent Acquisition, Affiliate Marketing (posted October 7, 2026), plus two Talent Acquisition Leads: each owns "Pipeline built ahead of demand, so when a req opens you already know who to call", needs "a sourcing engine you built yourself: inbound and outbound, passive included" and "outreach that converts"; Claude "is in the daily workflow". A Head of People was posted October 8.Source
- HiringLaunch Potato's description in every job post: "the discovery and conversion company" that reaches "tens of millions of people every month through our brands, including FinanceBuzz, All About Cookies, and OnlyInYourState"; "profitable and bootstrapped, with a South Florida HQ and a remote-first team across 18 countries".Source