All guides

Extension guide

Find out which skills actually pay before you learn one

How a research search and the Keywords page turn the jobs your searches already found into an answer about what to learn next.

September 14, 2026 · 5 min read

The question this answers

Every freelancer eventually asks which skill to pick up next. The usual answers are anecdote: a thread, a friend, a course landing page. None of them know what the jobs in your corner of Upwork are actually asking for, or what those jobs pay.

The Keywords page answers it from your own data. Every job your saved searches find already arrives carrying its skill tags, its budget, and how many people have bid. Counting those is arithmetic over rows you already have, not a new thing to scrape.

Two kinds of saved search

A lead search is what you already run: a narrow, filtered Upwork search whose results you intend to apply to. Its jobs land in the inbox, can be auto-drafted, and are pushed to you.

A research search is the same scan pointed at one broad word — typescript, say — and its results go nowhere except the count. No inbox row, no draft, no notification. You can hold one at a time, and it spends one of your three saved searches.

Set it when you add the search: under "What is this search for?", choose Research instead of Finding work. The saved row is badged Research so you never mistake it for a search that feeds your inbox.

Keeping it inside the same three is deliberate. A fourth URL means more requests per hour against Upwork from the same browser, which is the thing worth being careful about. Counting is free; scanning is not.

Why the ranking is not a frequency list

Sorting keywords by how often they appear puts javascript at the top and teaches you nothing. Common and valuable are different properties, and the most common skills are usually the ones with the most people already bidding.

So a keyword is ranked on its median budget divided by how many proposals those jobs attract. Volume still counts, but damped — seen more often is better evidence, not a proportionally better opportunity. A narrow, well-paid, lightly-contested skill beats a crowded cheap one even on a fraction of the job count.

Read the change column, not the snapshot

A single day tells you what is common. Two days tell you what is moving. The change column compares against the previous counted day, and it only appears once there is a previous day to compare with — before that it is blank rather than invented.

Rising is the signal worth acting on. A skill that has held the same count for a month is a market you can already see; one that has climbed for three weeks is one you can still get ahead of.

Know what it cannot tell you

The numbers come from the jobs your own searches found. That is a corpus, not a market. A skill that none of your three searches reach will never appear on the page however common it is on Upwork — the table will look objective and will be silent about everything outside your own field of view.

That is the reason to spend a slot on a broad research word. A filtered search only ever shows you words adjacent to what you already do. One wide word is how something genuinely new gets into the count at all.

  • One of your three searches is a broad single word, not a filtered search.
  • You have let it run for more than one night, so the change column has something to compare.
  • You are reading the ranking, not the raw job count.
  • You know which skills your searches cannot see.

Next read

Back to the full guide library.

Use the guide index to choose the next operating improvement.