Jobio · Product-design decision
Connecting the acquisition promise to the product
Building a marketing website and practical SEO foundation around Jobio’s preparation proposition and different audience goals.
Project context: An AI-powered application workspace for understanding roles, preparing documents and tracking a job search. The work spans the application, marketing website, payment model and practical service delivery.
My contribution: Reframe the website around preparation and the supporting tracking workflow. Create reusable feature, audience, pricing and editorial content structures. Implement the Astro site and practical metadata, canonical, sitemap and internal-link foundations with AI assistance.
As Jobio expanded from tracking into preparation, its public explanation needed to change too. A one-page tracker pitch did not explain role analysis, tailored documents or the different goals that could bring someone to the product.
Designing the public content structure
I reordered the site around the preparation payoff, with organisation supporting that work. Feature pages could explain a particular capability in depth. Audience pages could start from a person's goal rather than repeat the same generic pitch. Pricing needed to explain which work was free and where credits applied.
The public site and the authenticated application also had different delivery needs. Splitting the marketing site into Astro created a dedicated content surface, with reusable layouts, a blog collection, topics and related content instead of treating every page as an addition to the application shell.
- Alternative considered
Keep extending a generic tracker landing page or present a canned demo as live analysis. The old proposition under-explained preparation, while a misleading demonstration would set an expectation the real product had not fulfilled.
- Deliberate choice
- Separate the public Astro website and structure it around preparation, features, audience goals and pricing.
- Accepted trade-off
- A larger content system needs ongoing reconciliation with the product, its pricing and onboarding; SEO implementation alone does not establish acquisition results.
Inspect image and full contextKeeping the demonstration honest
Marketing needed to reflect what the product actually did. The redesign record includes a decision against a canned interactive example that could imply genuine analysis. That was one instance of a wider responsibility: distinguish illustrative content from live output and keep feature/pricing copy aligned with the implemented product.
I also worked on the practical SEO foundation: metadata, canonical URLs, sitemap generation, structured data and internal links. These are concrete implementation and content tasks. A strategy document's general claims about search engines are not evidence that Jobio achieved rankings or acquisition gains.
Inspect image and full contextConnecting acquisition to first use
The website's preparation promise exposed a dependency on onboarding. Registration needed to lead toward a saved job and a useful next action, rather than immediately scatter the user across unrelated product areas. The website and activation work therefore form parts of one journey, even though they use different technical surfaces.
Jobio gained a separate Astro marketing site with preparation-led content, feature and audience pages, pricing, a blog/content structure and practical technical SEO foundations.
This demonstrates website, content and technical SEO work. Search ranking, attributable traffic, campaign conversion and revenue improvements are not established.
I designed and delivered this work with AI assistance. It adds specific marketing-website and SEO experience to my broader product work. It does not establish an SEO-specialist background or a measured traffic, conversion or revenue result.