Guides
How we write and check this
Appliora publishes CV examples, ATS guides and cover-letter examples. This page says who writes them, what we do and do not claim, and what we do when we get something wrong. It is short on purpose - everything on it should be checkable.
Who writes it
The Appliora editorial team. There is no individual byline on these pages because the work is not done by one person: drafts are written and reviewed inside the team that builds the product, and the same people maintain the parser and scoring model the ATS content describes.
We do not publish a fictional expert. If you see a named reviewer with a credential on an Appliora page, that person is real, the credential is real, and they read that page. Today no page carries one, so no page claims one.
The standard a page has to meet
Content on this site is generated from a structured source, and a page that does not clear these is not published - it does not become a thin page and it does not become a noindex page.
- Role-specific material, not a general article with a job title substituted in. A sentence that would be equally true of a nurse and a DevOps engineer does not belong on either page.
- At least eight before-and-after experience bullets, most of them carrying a concrete figure.
- A complete worked example, as readable text rather than only as a picture.
- Three professional summary variants, by career level.
- Notes on machine readability that name real checks from the product, not invented ones.
- Two to four recommended templates, each with a reason. Never all of them.
- Links to genuinely related pages that resolve.
- No page ships with a filler phrase from a banned list, and no page ships with an em dash - this site writes short hyphens.
The rules live in content/schema.mjs in the site's source, and the check runs on every build.
The example CVs and letters are fictional
Every named person, employer and figure in an example on this site is invented. They are there to show a shape you can copy, and the numbers are specifically not there to be copied - a figure on your CV has to be one you can defend in an interview.
We never publish a real user's CV, a real user's data, or a real company's internal numbers. Appliora processes an uploaded CV in the browser for the free checker; nothing from it reaches this content.
Statistics, and the ones we refuse to repeat
Career advice recirculates a handful of numbers whose original source nobody can produce: how many seconds a recruiter spends on a CV, what share of applications an ATS rejects, what percentage of large employers use one. You will not find them on this site, and their absence is deliberate rather than an oversight.
When a number matters, we prefer one we generated ourselves and can show the method for. The CV parsing benchmark is that: one CV through every layout, the same parser, the method written out, the raw results in the repository, and a result that does not flatter us.
Product facts
Numbers about Appliora itself - how many templates there are, how many ATS checks are published, how many languages a CV can be written in - are derived at build time from the code that defines them rather than typed into prose. Today that is 20 templates, 14 checks and 20 CV languages, and a page that said something else would fail a test rather than reach you.
What we claim about applicant tracking systems
Dates, updates and review
Each page shows when it was last updated. That date moves when the content actually changed - it is not bumped to make a page look fresh, and a year in a title does not change on its own in January.
Pages that quote anything outside Appliora - a competitor's pricing, a third-party product's feature - carry the date the claim was last verified and the source it came from, and there is an internal report that lists which of them are overdue for a re-check. We would rather show you a stale date honestly than a current-looking price we have not looked at since last year.
When we are wrong
Tell us: hello@appliora.io. If something on a page is factually wrong we correct it and move the updated date. If a page is wrong in a way that changed what a reader did, we say what changed rather than editing it quietly.
We have removed our own content before for this reason. The blog once carried invented reader comments with names and dates; they were deleted, and there is now a test that fails the build if anything like them comes back.
How Appliora makes money
Building a CV, the live preview, the ATS checker and everything on these pages is free and needs no account. Appliora charges when you download the finished PDF. That is the whole model, and it is why the CTA on a content page is an offer to use a tool rather than a sign-up wall in front of the advice.