Skip to content
Web design & UX

Careers Page Over Job Ads: Winning Applicants Online

Why applicants google the employer after the ad: building a careers page with JobPosting structured data, short applications and sound data protection.

14 min read KarriereseiteRecruitingFachkräftemangelWebdesignConversion

For many mid-sized companies, the skills shortage has long been more expensive than any marketing problem. An unfilled role costs contracts, delays deadlines and wears down the team that absorbs the gap. Even so, recruiting in many companies stops at paid job ads on third-party portals, while their own website stays silent on the subject of being an employer. That break is entirely predictable: 71.7 percent (KOFA Study 2/2026, German Economic Institute Cologne) of all vacancies that cannot mathematically be filled sit with small and medium-sized enterprises, that is, with precisely the companies least likely to have a careers page worth the name. This article treats the careers page as what it is: a conversion path with a different audience. It covers structure, indexable job pages, JobPosting structured data, a mobile-first short application, the handling of applicant data and measurement that deserves the term. Deliberately without recommendations for recruiting software, and instead with what a web agency can actually contribute: web craft.

Key takeaways

  • A job ad on a portal sits next to dozens of identical ones — your own careers page is the only place where a business looks distinctive.
  • The careers page is not an image surface but a conversion path, just like the customer enquiry path: from interest to submitted application.
  • The most common mistake is not missing content but interchangeable content — every company claims a friendly culture and flat hierarchies.
  • Every vacancy belongs on its own page rather than in a PDF: only then is it findable, linkable and machine-readable via JobPosting structured data.
  • A short application beats the 20-field form — on a smartphone the number of fields decides whether anything is submitted at all.
  • Application documents are especially sensitive: transmit them encrypted, restrict access tightly and delete them once retention periods expire.

The skills shortage hits mid-sized companies hardest

The figures are clearer than the debate suggests. Small and medium-sized enterprises make up 99.3 percent (KOFA Study 2/2026, German Economic Institute Cologne) of all companies in Germany and employ 64.3 percent (KOFA Study 2/2026, IW Cologne) of all qualified employees subject to social insurance contributions, close to two thirds. A new analysis of Federal Employment Agency data allows a first look at the skills gap by company size, and it is stark: between July 2024 and June 2025, 72.3 percent (KOFA Study 2/2026, IW Cologne) of all vacancies were advertised by SMEs, and they were short of 281,532 (KOFA Study 2/2026, IW Cologne) skilled workers in total. The largest absolute bottleneck fell on small companies with up to 49 employees: they lacked 177,347 (KOFA Study 2/2026, IW Cologne) skilled workers, while the gap at large companies stood at 111,240 (KOFA Study 2/2026, IW Cologne). Anyone competing for the same people as a corporation with its own HR department can hardly afford to stay invisible as an employer.

The second look shows where it binds. The Federal Employment Agency assesses roughly 1,200 (Federal Employment Agency, skilled worker bottleneck analysis) occupations each year and most recently classified 163 (Federal Employment Agency, skilled worker bottleneck analysis) of them as bottleneck occupations in which vacancies are hard to fill. Another 181 (Federal Employment Agency, skilled worker bottleneck analysis) occupational categories are under observation because they could develop in that direction. More than half of the bottleneck occupations, 91 (Federal Employment Agency, skilled worker bottleneck analysis) of them, sit at skilled worker level, which means classically trained trades rather than the much-quoted graduate shortages. Care and health professions, construction and trades, and IT roles are most affected, along with chefs, professional drivers and childcare educators. At the same time, the Federal Statistical Office reported 648,200 (Federal Statistical Office) registered vacancies for June 2026, up 2.5 percent (Federal Statistical Office) year on year, with around 45.6 million (Federal Statistical Office) people in employment in the first quarter of 2026. The labour market is not empty, then. It is contested. And in a contested market, presentation decides.

Briefly explained: skills gap and bottleneck occupation

The skills gap describes vacancies that cannot mathematically be filled: roles for which no suitably qualified unemployed people exist nationwide. A bottleneck occupation, by contrast, is a classification by the Federal Employment Agency based on six indicators, among them vacancy duration, the occupation-specific unemployment rate and pay development. Both are market diagnoses, not fates: they describe how hard the competition for a person is, not whether an individual company wins them.

What happens after the job ad has been read

A job ad on a third-party portal is a standardised format. It sits next to dozens of similar ads, in the same layout, with the same building blocks and often the same phrasing. That is precisely why the ad is only the first step. The second step is the candidate's first independent action, and it is remarkably predictable: they type the company name into a search engine. In a country where 97 percent (Federal Statistical Office) of people aged 16 to 74 use the internet, that is not an exception but the norm. The candidate checks the employer before investing their time. What they find in those two minutes decides whether the paid ad takes effect or evaporates.

In many cases they find an imprint, a phone number, a news post from six years ago and perhaps a review portal with three old entries. No employer profile, no faces, no indication of how work actually happens there. The result is not rejection but something worse: indifference. The candidate has found no reason to apply, and none not to. So they do nothing. The ad bought attention; the website did not redeem it. Anyone wanting to fix this should first check what is findable at all: our article on the Google Business Profile and local SEO describes how the picture of a company forms in local search, and the article on a strategy for Google reviews shows how strongly third-party sources shape that picture as long as you contribute nothing yourself.

Strategic employer branding makes a company's attractiveness visible. That pays into recruitment as well as employee retention.

KOFA Study 2/2026, German Economic Institute Cologne

The careers page is a conversion path

The most useful shift in perspective is this: the careers page is not an obligatory page and not an image surface, but a conversion path just like the enquiry path for customers. It has an entry point, a chain of arguments, trust elements, a clear next step and a measurable goal. The difference lies in the audience, and that difference is considerable. A customer asks: can they do what I need? An applicant asks: do I want to spend the next few years there? That is a far more personal decision with a much higher barrier, because it is rarely anonymous and rarely without consequence. Anyone who knows the craft rules that turn visitors into enquiries can apply them directly here. Our article on conversion optimisation for more enquiries describes the mechanics that apply to applications too.

Different content follows from that difference in audience. The applicant is not comparing offers but employers, and they are looking for three things: security, prospects and people. Security means the company exists, pays and will last. Prospects mean the role can lead somewhere. People means they want to see who they will spend eight hours a day with. A service page answers none of these questions, and neither does a job ad in portal format. They are answered on the careers page, or they stay open. That a coherent page concept matters more than isolated measures is central to our web design work.

One page, one decision

Ask the same question of the careers page as of any sales page: what should the visitor do here? If the answer is to inform themselves, the page is a brochure. If the answer is to get in touch or apply, it becomes a path. And then the same rules apply: one dominant next step, little friction, visible trust.

Building a careers page that holds up

The most common mistake on careers pages is not missing content but interchangeable content. A family atmosphere, flat hierarchies, exciting tasks, a strong team: these sentences appear on so many pages that they no longer say anything. They are not wrong, merely ineffective, because they create no picture and support no decision. An employer profile answers concrete questions instead: how many people work here? What does a normal day look like? Which projects are running right now? How is shift planning handled, how is overtime taken back, who decides on holiday? These details are unspectacular and valuable for exactly that reason: no competitor can copy them, because they have to be true. How to turn platitudes into verifiable statements is also covered in our article on website copy that sells.

Employer profile, not platitudes

Headcount, order situation, typical projects, working time models. Concrete details that create a picture and cannot be copied onto every second website.

Real team photos

People from the company at their workplaces, not purchased stock images with headsets. Whoever appears in the picture should also be found at reception.

Location and how to get there

Address, travel time, parking, public transport links. The commute decides acceptances more often than employers assume.

Salary and development range

State a range, a pay grade or a collective agreement. Plus what is possible after two years. Silence is read as bad news.

A contact with a face and a direct line

A name, a photo, a direct line, hours when someone answers. No info address. The barrier drops noticeably when it is clear who picks up.

Training and young talent

Dual vocational training is a decisive building block for securing young talent in SMEs (KOFA Study 2/2026, IW Cologne). Companies that train should show it.

What stands out is that small companies have structural advantages here that they rarely play. The KOFA study names personal contact, faster decision-making and stronger involvement of employees in change processes as strengths that often work better in small companies than in large ones (KOFA Study 2/2026, IW Cologne). These are real arguments, but they only work when they are evidenced rather than asserted. The pressure to show them is growing: while SMEs expanded their employment level over ten years by 6.6 percent (small companies) and 15.0 percent (medium-sized companies) respectively, large companies grew by 23.8 percent (KOFA Study 2/2026, IW Cologne). Anyone fishing in the same pond should at least be recognisable.

Job ads as their own subpages, not as PDFs

A surprisingly persistent pattern is the job ad as a PDF attachment, linked from a collection page headed We are hiring. The PDF is convenient because it falls out of the word processor, and it costs something at every turn. It reads badly on a phone, it cannot be linked sensibly, it provides no cleanly indexable page, it cannot carry structured data, it cannot be measured, it has no apply button, and its modification date reveals how long the role has been open. The alternative is unspectacular: one URL per role, as a normal, indexable subpage. That turns a dead document into a landing page that ads, referrals and search engines can point to. How pages are sensibly cut and ordered is described in our article on website structure and information architecture.

AspectJob ad as a PDFJob ad as a subpage
FindabilityPoorly recognised as a job by search engines, if at allOwn URL, indexable, markable as a job
Structured dataCannot carry JobPosting markupJobPosting markup directly in the page
MobileZooming and panning, frequent drop-offResponsive and readable, no download
ApplicationNo button, fallback to emailShort application directly on the page
MeasurementDownloads instead of applicationsViews, form starts and applications per role
UpkeepOld versions keep circulatingOne source, expiry date under control

The same logic governs how filled roles are handled. A job page without an expiry date becomes a liability: it keeps collecting applications for a role that no longer exists and leaves a stale impression on everyone who gets in touch. What works is a maintained expiry date, a pointer to neighbouring open roles and, when the page disappears, a clean redirect to the careers overview rather than an error page. The technical groundwork for this, from indexability through redirects to markup, is summarised in our technical SEO checklist.

JobPosting structured data for findability

Once every role has its own page, the next step pays off: machine-readable markup. The standard is called JobPosting and comes from the schema.org vocabulary; the requirements for required and recommended fields are documented by Google Search Central (Google Search Central). What gets marked up includes the job title, the description, the publication date, the hiring company and the place of work. Two fields are easily forgotten and matter: validThrough, the expiry date, and baseSalary, the salary range. The salary field is not mandatory, but it is one of the few details that makes a role immediately comparable in a results list. Leaving it out hands the framing to chance.

jobposting.jsonld
{
  "@context": "https://schema.org",
  "@type": "JobPosting",
  "title": "Electrician for Industrial Engineering (m/f/d)",
  "description": "<p>Tasks, requirements, working time model and framework …</p>",
  "datePosted": "2026-07-24",
  "validThrough": "2026-10-31",
  "employmentType": "FULL_TIME",
  "hiringOrganization": {
    "@type": "Organization",
    "name": "Your Company Ltd",
    "sameAs": "https://www.your-domain.invalid/",
    "logo": "https://www.your-domain.invalid/logo.png"
  },
  "jobLocation": {
    "@type": "Place",
    "address": {
      "@type": "PostalAddress",
      "streetAddress": "Industriestraße 12",
      "addressLocality": "Hildesheim",
      "postalCode": "31135",
      "addressCountry": "DE"
    }
  },
  "baseSalary": {
    "@type": "MonetaryAmount",
    "currency": "EUR",
    "value": {
      "@type": "QuantitativeValue",
      "minValue": 3400,
      "maxValue": 4200,
      "unitText": "MONTH"
    }
  }
}

Honesty requires saying what structured data does not do. It makes a page machine-readable; it does not force a placement or an inclusion in a job search. No markup rescues a badly written role, and no markup makes an unattractive package attractive. The markup is still worthwhile, because it moves the effort into the template once: if the markup is bound to the fields of the job page, it is generated automatically with every new role, without anyone having to remember it. That is the difference between a chore and a system. The same discipline applies to other mandatory information on the web, as our article on GPSR mandatory information in online shops shows: the rule sits in the law or the standard, the implementation belongs in the template.

Expired roles cost more than no roles

A marked-up role without a maintained validThrough can keep appearing in job searches long after it has been filled. Anyone who applies then and receives a rejection, or no answer at all, experiences the company as disorganised, and that is expensive: they will read the next ad from the same name with different eyes. Set an expiry date before the role goes live.

A mobile-first short application instead of a 20-field form

The finish line of the careers page is the application form, and that is where what the page built up is regularly lost. The reason is usually a misunderstanding about the situation: application forms are designed at a desk and used on a sofa in the evening. With smartphone penetration at around 82 percent (Statista) among people aged 16 and over, that is not a fringe case. Anyone who encounters a form with twenty mandatory fields, an address request, a cover letter upload and a registration in that situation will abandon it. Not out of laziness, but because the effort bears no relation to the step involved: they want a conversation first, not a personnel file. Why forms should be thought through on mobile first is explored in our article on mobile-first and responsive design.

The short application reverses the order. It asks only for what is needed for the first callback and collects the rest in conversation. Anything not strictly needed now is optional or dropped. What matters is an exit for those who would rather not type: a direct line with hours when someone genuinely answers. And what matters is honesty afterwards, meaning a note on when a response will come, and then the response. In our own projects (project experience), shorter application paths were as a rule not a quality problem: the applications were not worse, there were simply more conversations. What an entry point that leads to exactly one action looks like is shown in our article on the landing page that converts.

  • A name and one way to make contact; more is rarely needed for the first step
  • A reference to the role, ideally pre-filled from the job page itself
  • CV as an optional upload, no compulsory cover letter
  • A callback request with a time window as an equal alternative to the form
  • Large fields, the right keyboard, visible labels instead of disappearing placeholders
  • A clear commitment on when a response will come, and a contact with a name

Applicant data deserves particular protection

Application documents are sensitive. They contain CVs, references, photos, sometimes details about health or disability, and they come from people in a dependent position who rarely follow up. The purpose limitation principle in Article 5 GDPR means these data are collected for the specific application and not for anything else: no adding to a mailing list, no circulating them internally to whoever is curious, no secondary use in a talent pool without explicit consent. A deletion period belongs with it. In practice, retention of around six months after a rejection has become established, because the limitation period under the German General Equal Treatment Act may require evidence. That is a deadline, not an archive: afterwards the data is deleted, including from the mailbox.

Technically the requirement is quickly stated. Transmission belongs encrypted, access to the documents limited to the people who actually decide, and the storage location documented. What is ruled out is an application via an unencrypted contact form or a simple email forward to a shared address that half the workforce can read. Anyone who additionally lets an AI assistant answer applicant questions must disclose its use; the requirements are described in our article on labelling AI chatbots under the AI Act. The groundwork for running the rest of the website in a privacy-compliant way is summarised in our GDPR checklist; anyone who values data minimisation will find the matching measurement approach in our article on analytics without a cookie banner.

No application uploads through the standard contact form

A contact form that sends enquiries unencrypted by email to a shared address is the wrong route for application documents. Applications need encrypted transmission, a defined storage location, a limited set of recipients and a deletion period. If that framework is not in place, offering a callback with a direct line is a better interim solution than an upload into the unknown.

Measure what counts: applications per channel

Most companies know what an ad cost and only guess at what it delivered. That is because the wrong things get measured. Clicks, impressions and page views say something about attention and nothing about staffing. The chain that counts is short and uncomfortable: views of the job page, started short applications, submitted applications, candidates invited from those, and hires from those. Only that chain shows whether an ad was expensive or cheap, because an ad with many clicks and zero hires is more expensive than one with few clicks and one hire. How to choose metrics that support a decision rather than merely filling a chart is covered in our article on measuring website success.

Attributing this to a channel works without a tracking apparatus. It is enough to give each ad its own target URL or its own parameter so that views and applications can be separated by source. The simplest method of all helps alongside it: asking, in the form or in the first conversation, how someone became aware of the company. That answer is messy, because people misremember, and it is valuable all the same, because it exposes the share no measurement captures, namely the referral from the workforce. The KOFA study explicitly highlights employee referrals as a successful recruiting strategy for SMEs (KOFA Study 2/2026, IW Cologne). Anyone who does not ask credits their effect, by accident, to whichever ad happened to run last.

Effort, sequence and an honest assessment

The effort for a careers page that holds up is manageable and rarely sits where it is assumed to. The website share, meaning a careers overview, two or three job subpages with JobPosting markup, a short application with sound data handling and measurement per channel, is a project of a few days when the website has a workable foundation. The real effort sits with the company: getting team photos taken, committing to a salary range, naming a contact who genuinely answers, and obtaining the approvals for all of it (project experience). No agency can take those decisions, and they are the reason careers pages fail more often at coordination than at technology. Anyone wanting to gauge the financial frame beforehand will find the usual ranges in our article on what a website costs; the concrete service packages are set out on our pricing and packages page.

  1. Take stock: what does an applicant find today when they search the company name?
  2. Define the employer profile: figures, facts, working time models, salary range, contacts
  3. Create a careers overview and one indexable subpage per role
  4. Bind JobPosting markup into the template, including validThrough and baseSalary
  5. Build the short application mobile first, with encrypted transmission and a deletion period
  6. Set up measurement per channel, and only then run ads again

That leaves the assessment, and it matters more than any checklist. A careers page does not replace job ads. Ads on third-party portals buy reach among people who do not know the company, and no subpage, however good, replaces that. But the reverse holds just as firmly: ads without a careers page buy attention that nobody redeems. The two do not compete, they depend on each other. The ad prompts the candidate to type the company name, and the careers page decides what happens next. How many applications result depends on the occupation, the region, the pay and the reputation, and cannot responsibly be promised. What can be influenced is the part that sits in your own hands: that something stands at the end of the search which answers the question the applicant actually asked.

Sources and studies

This article is based on data from: KOFA Study 2/2026 on skills shortages in SMEs by the German Economic Institute Cologne (skills gap by company size class, share of SMEs in unfillable vacancies, employment development, employer branding and employee referrals), the Federal Employment Agency's skilled worker bottleneck analysis (number and structure of bottleneck occupations, assessed occupations, occupations under observation, registered vacancies), the Federal Statistical Office (registered vacancies, people in employment, internet usage from the ICT survey), Statista (smartphone penetration), Google Search Central (documentation of JobPosting structured data) and our own website projects. The figures cited refer to the periods stated and may differ by occupation, sector and region; details marked (project experience) are based on our own projects. A specific number of applications cannot be promised.

Related Articles