How to track job applications so the same job never fools you twice: the columns that matter, a simple template, and what 9,988 saved job links showed.
You open your tracker and find two rows for the same company and the same title, with two different links. Did you apply twice? Is it a second opening, or the same job wearing a new address?
It happens to almost everyone past the first few dozen applications. It happened to my own system too, hundreds of times. This guide covers how to track job applications and avoid applying twice: the columns that matter, why one job shows up under several links, and a simple template you can set up tonight.
Most trackers start with company, title and link. The link is the problem. The same job can have several links, so a tracker keyed on links will let repeats in without you noticing.
Track the job's own number instead. Almost every job system gives each role an ID, and it usually sits right in the link.
| Column | Why it matters |
|---|---|
| Company | The first thing you'll search by |
| Job title | Exactly as the employer wrote it |
| Job number | The one thing that stays the same across links |
| Date posted | Old postings deserve less of your time |
| Date applied | So you know when to follow up |
| Where you found it | Tells you which sources work for you |
| Link | Handy, but never the way you check for repeats |
| Status | Applied, heard back, interview, closed |
| Next step and date | One action, with a day attached |
Here is where to find the job number on the systems you'll meet most often:
If you can't find a number, use company plus exact title plus city. It isn't perfect, but it catches most repeats.
I run a service that finds jobs for people and applies for them, so my system saves a lot of job links. In the four weeks before 22 October 2026, it saved 9,988 of them. 844 were a job it had already saved for the same person, under a different link. That's about 1 in 12.
These are the ways one job turned into two links:
| How the repeat happened | Repeats |
|---|---|
| A different path to the same job number (language pages, a title added to the link, location codes) | 559 |
| Extra tracking or search codes added to the same page | 129 |
| The job page and its apply page | 126 |
| The job board and the company's own careers page | 30 |
A few real examples. Amazon shows the same job at /en/jobs/10495000 and /es/jobs/10495000, one in English and one in Spanish. Lever gives a job one link and its application form another, ending in /apply.
A link from a jobs site often arrives with a code like ?ref= on the end. And Samsara's careers page and its Greenhouse board show the same job, number 8112836, at two different addresses.
None of these are tricks. They're just how job sites work. But if you track links, every one of them looks like a new job.
[Illustration idea: one job card in the middle, with four arrows pointing to it from four different-looking links: an English page, a Spanish page, an apply form and a company careers page.]
There's a second kind of repeat that a job number won't catch. Many companies post the same role once per city, and each posting gets its own number.
On 27 October 2026, the company job boards I read listed 14,471 US postings. 1,632 of them were a title the same company had already posted, usually for another city. That's about 1 in 9.
So a software engineer search might show the same role in New York, Seattle and San Francisco as three separate jobs. Often it's one team, one hiring manager and one pile of applications.
In most cases, apply once, to the city you actually want. A second application to the same role in a different city rarely gives you a second chance. It mostly gives the same recruiter a second copy of you.
This is why my own system checks two things before it applies. First, the job number. Second, the company and exact title against everything applied to in the last 60 days. If either matches, it skips the role.
Add a "city" column to your tracker, and before you apply, search your sheet for the company and title. It takes ten seconds.
Often, nothing dramatic. The recruiter may see both applications, and a careful recruiter reads one of them.
Still, applying twice costs you in quieter ways:
If you do apply twice by accident, don't panic and don't send an apology. If you hear back, answer the message and move on.
There's one case where a second application makes sense: when something real has changed. If you've gained a new skill the role asks for, or months have passed and the company reposted the role, applying again is fair. Just make sure it's the new posting, and note the new date in your tracker.
Seeing a job you applied to come back up can sting. It feels like a "no" you never received. The reasons are usually more ordinary than that.
Common reasons a company reposts a job:
What should you do when a job is reposted after applying? Check the posting date first. I wrote a guide on how to see when a job was posted, including a free checker. If the role is the same and only a few weeks have passed, your first application is probably still in the pile.
If it's been a few months, or the new posting has a new number and new details, a second application is reasonable. Log it as its own row, with the new number and the new date.
You don't need special software. A Google Sheets job application tracker does everything above in a few minutes.
That's a working job application tracker template. The repeat check in step 4 does most of the work. It catches every duplicate job number the moment you paste it in.
Then make one habit stick. Before you apply to anything, search your sheet for the company. It's the cheapest ten seconds in your whole search.
[Illustration idea: a screenshot-style mock of the sheet with ten columns, one row highlighted in red because its job number appears twice.]
All of this is what my own system does now, every day, without you keeping a sheet.
Since we switched our check from links to job numbers on 22 October, my scans have saved more than 2,000 new job links, and none of them was a job already saved for the same person. Before Zipply applies, it also checks company and title against the last 60 days.
Every day we read company career pages and search Google for your titles. We score each role against your CV, skip the weak fits and tell you why, apply to the strong ones, and send you one email each morning with everything that went out. It's your tracker, kept for you.
It costs $50 a month, or $550 a year, with a full refund within seven days of the first payment. There is no free trial. It works best in fields with enough open roles, and nobody can promise you a job, including us. You can see if it fits your role here.
When you work out how to track job applications, track the job, not the link.
If you're applying and hearing nothing back, this post on getting ghosted covers the usual reasons.
The most effective way is a simple sheet with one row per job, keyed on the job's own number rather than its link. Add the company, exact title, city, date posted, date applied, status and one next step. A repeat check on the job number column catches the same job arriving under a different link.
Usually nothing serious happens. The recruiter may see both applications, and a careful one simply reads one.
It can look careless if the two differ, so keep the details the same. Don't send an apology. If you hear back, reply as normal and log both rows as the same job in your tracker.
Companies post the same job multiple times to reach new people, to cover more than one city, or because a hire fell through and the role reopened. Some roles stay open all year. Job sites also give one job several links, so a single role can look like many. Check the posting date and job number before you apply again.
Put this into practice
Your personal job search concierge. Zipply watches the market, scores every role against your CV, and applies on your behalf - only when the fit is right.
Get started →