Career Page and Online Application Form

The page has four parts: a career home page listing open roles, a dedicated detail page for every posting, a separate section for internship postings and the application form. All four share the same shell, so navigation, footer and branding stay identical everywhere.

The look comes from company settings. Logo, brand color, short intro, about text, address, phone, map and social links are filled in from the panel, and the page reads them. When no brand color is set the default blue applies, so the page opens complete even with zero configuration.

The product name never enters the page title: the browser tab and the search result show the company name next to the job title.

• Career home: intro section, about, open roles, contact
• Job detail: position description, requirements, responsibilities, publish date and application deadline
• Internship section: shown in the menu and on the page only when an internship posting is open
• Interface labels switch between Turkish and English with one click; posting text stays exactly as you wrote it and is never machine translated
• An expired posting appears greyed out, cannot be clicked and stops accepting applications

No posting is indexed automatically. There are three gates and all three have to be open at once. The robots tag on the page and the sitemap run the exact same check, so the "in the sitemap but not indexed" situation never happens.

The 300 character threshold in the third condition is not a guess. Live postings were measured: the shortest body ran 310 characters, the median 489, and nothing sat below 300. The threshold rules out none of the postings live today, but it does stop a body that was genuinely left empty.

A closed posting loses its address. Once a posting moves to draft or closed, its public URL returns 404 while the career home page stays up.

Every open job page is published together with a JobPosting record that machines can read. The record carries the job title, description, publish date, application deadline, employment type, employer and location. When no location is entered it is filled with the country, because an empty location makes the record invalid. Breadcrumb data is emitted as well.

The posting therefore reaches job surfaces such as Google for Jobs in the shape they expect. Whether it is picked up and in what order it appears is up to Google; the promise here is that the data is produced correctly and completely, not that you will rank.

Active postings enter the sitemap one by one, and the sitemap is generated from the live database. A posting published today shows up in the next crawl.

Every posting starts from the same core form: personal details, education, position, salary expectation and start date, file upload, portfolio and LinkedIn links, open ended questions, KVKK consent. A CV is mandatory, it has to be a PDF and it cannot exceed 5 MB. Transcripts and other documents follow the same rules and stay optional.

On top of that you can add posting specific fields. There are five field types: short text, long text, single choice, multiple choice and date. One posting takes at most 20 custom fields, one field at most 50 options. Deactivating a field stops the form from asking it; answers already collected are never deleted.

Answers are not stored on the browser word: the server revalidates every answer against the field definitions active on that posting at that moment. The form is bot protected, and the same email address cannot apply to the same posting twice within 24 hours.

On the KVKK side the data controller is the company that published the posting, not the product. The privacy notice and the explicit consent text are generated in the company name; paste in the wording your own legal team approved and it replaces the generated one. Every consent moment is written onto the application record with its timestamp.

• Field types: short text, long text, single choice, multiple choice, date
• Up to 20 custom fields per posting, up to 50 options per field
• Two fields cannot share a label, an option cannot be listed twice
• CV mandatory, PDF only, 5 MB max
• A second application from the same email to the same posting within 24 hours is blocked

A company that already runs a corporate site may want the application flow to live there. The two are not alternatives: the career page solves the search engine side, the embed solves the flow on your existing site. Both can be on at the same time; a company that will only use the embed switches the career page off, and its career URLs then return 404.

The embed is installed with a single div and a single script tag. Frame height follows the content, so no inner scrollbar appears, and once an application is submitted the host page scrolls to the confirmation screen. Button color is passed with one attribute so it matches the host site.

The embed side also comes with health tracking: every frame load writes a record, and the panel shows the last load time, the last domain, the load count and whether that domain is on the allow list. You see whether the installation works without asking the customer.

The application is saved, the CV and any extra files go to storage, and the candidate receives a confirmation email. That email carries the company logo, color and footer; branding is never baked into the template, it is read from the company record on every send.

The CV analysis then queues in the background. The candidate does not wait for it after pressing submit and sees the confirmation screen right away. When the analysis finishes, the result sits on top of the application in the panel.

The decision mechanism does not change: the system never rejects a candidate, it produces rankings and recommendations, and HR makes the status change.

One note: how many postings you can keep open at once depends on your plan. Moving a posting to Active spends one slot, closing it gives the slot back. If the subscription is suspended, the career page and application intake close with it.