1. LandOffer
  2. Blog
  3. All articles
  4. Upwork Specialized Profiles Are Gone: Rebuild Your Main Profile for the Work You Want

Job search

Upwork Specialized Profiles Are Gone: Rebuild Your Main Profile for the Work You Want

Rebuild a focused main Upwork profile after Specialized Profiles retired, using retained work records, original positioning and public-safe portfolio evidence.

9 min readLandOffer team

If you are looking for your old Upwork Specialized Profiles, the removal has already happened. Upwork retired them on May 28, 2026. Rebuilding now starts with your main profile, the evidence still available there, and any copies you already own.

For a developer who once separated API work from website work, the next task is explaining those services coherently in the main profile. Start by accounting for the material you have, then write around the work you want next. This guide uses public documentation checked on October 22, 2026; both worked examples are fictional, unsaved exercises. If you are also considering employment, explore LandOffer.ai separately from this freelance-profile rebuild.

A developer curates preserved project sheets into one open portfolio while two smaller folios remain closed.

What disappeared, and what Upwork says remains

According to Upwork's retirement notice, portfolio items, earnings, work history and reviews from specialized-profile jobs were incorporated into the primary profile. Specialized titles, overviews and skills did not transfer automatically. The retired profiles and their content cannot be retrieved by you or customer support.

The notice also describes the full profile appearing to clients, with relevant experience highlighted according to a search or job. That is Upwork's description, not a measured result from testing this guide. Its statements about rankings and improved hiring should not become a promise about your account.

Some wording on the same page still recommends copying content before deletion. That deadline has passed. The old-proposal visibility window, through June 28, 2026, has passed too. Neither is a current recovery instruction. Use an existing personal copy if you have one; otherwise write fresh text from evidence you can verify.

Account for your material before rewriting

A private inventory helps you avoid recreating items you already have or making unsupported claims to replace wording you lost. Compare the current main profile with your own approved samples and records. A missing paragraph and a missing contract record are different problems; record what you actually see without diagnosing an account issue from a general announcement.

For each item, separate existence, ownership and permission. A screenshot in your files establishes that a file exists. It does not establish that you may display the customer's data. A visible work-history entry establishes a record on the profile. It does not automatically authorize publishing the underlying code or naming internal systems.

Write the inventory locally first. For an uncertain screenshot, record “excluded: customer identifiers present; permission unknown,” rather than “check later.” Avoid an open-ended instruction to restore everything. The aim is enough reliable evidence for your next service, rather than a perfect reconstruction of every past presentation.

Worked rebuild: Priya chooses API integration work

Priya is a fictional developer who wants small backend integration assignments. Her former positioning mixed APIs, landing pages and database maintenance. In this exercise, she has inspected her main profile and her own files; the observations below are stipulated examples, not findings about a real Upwork account.

Material What Priya has in this example Rebuild decision
Completed API contract Main-profile work-history entry and review visible Retain the record; do not rewrite the customer's review
Earnings history Existing main-profile history visible Leave it intact; do not duplicate totals in marketing copy
Integration portfolio item Existing item visible; description names her contribution accurately Keep after checking its displayed content
Old specialized overview No personal copy Write a new overview; mark old wording unavailable
Old specialized skill list A dated private note, not a current platform field Use as a prompt; verify each proposed skill against current work
Client dashboard screenshot Local file with customer identifiers; sharing permission unknown Exclude; create an independent fictional demonstration instead

The inventory supports a focused offer: implementing and testing API connections for existing applications. It does not support calling Priya a full-service cloud architect. Her web-layout experience can remain in her history without occupying the opening sentence.

Her new title draft is: “Backend Developer | API Integrations and PostgreSQL.” This is an original editorial example, not a tested search formula.

Her complete overview draft reads:

I connect existing applications to external APIs and make their data flows easier to maintain. My focus is backend integration work using Python and PostgreSQL, with clear handling for retries, validation and handoff documentation.

On a previous team project, I implemented the import endpoint and its validation tests. A separate infrastructure engineer owned deployment and monitoring. My portfolio describes the integration work I contributed and includes an independent demonstration built with fictional records.

I can help scope an API connection, implement an agreed data mapping, test failure cases and document how the integration works. Before estimating, I need the API documentation, expected input and output, authentication requirements and the boundaries of the existing application.

I am currently looking for integration implementation and maintenance assignments. For projects needing production infrastructure ownership, we should establish who handles that responsibility before work begins.

Notice the boundary around deployment. A client can see what Priya would deliver and which responsibility needs another owner before discussing an estimate. She has not padded the profile with a performance percentage or claimed that a team result was entirely hers.

Her proposed skill shortlist is Python, API Integration, PostgreSQL, RESTful API and Backend Development, subject to the options actually offered in the editor. She would remove any label she could not explain through her own work. The old note helps her remember; it does not certify present competence.

Edit the main profile in a deliberate order

Upwork's profile essentials guide directs freelancers to their profile-picture menu and Your profile. Title and overview edits use their respective pencil controls, followed by Save. The guide says roughly the first 250 overview characters appear in search results, so make that opening useful on its own.

Prepare your text separately before entering it. Read only the proposed title and first sentence together: do they describe the same service? Then check the rest against actual work. If the opening promises API integration but the next paragraph offers unrelated services, decide which work the profile should lead with.

Select skills through the current picker rather than pasting an old list indiscriminately. There is a documentation conflict: the dedicated skills page says up to 20 skills, while the essentials page says 15. Check the limit offered in your account; this guide did not inspect an authenticated editor. A focused shortlist avoids making either number an optimization target.

Before saving a real change, review the complete text for inaccurate scope and contact details. Upwork's essentials guide prohibits misleading information, claiming others' work and including personal contact information. Keep a dated private copy of the wording you deliberately choose now, so a later edit can be compared with a known version.

Hands select original demonstration sheets and technical diagrams while a separate client document remains covered.

Worked portfolio: Tomas replaces a broad claims list

Tomas, another fictional developer, wants React interface implementation work. He also has testing experience. His problem is selecting evidence, rather than recovering a lost paragraph. Here is his completed selection record:

Candidate sample Evidence and exposure issue Decision
Independent task-board demo Tomas wrote the interface, tests and fictional records Include as a personal demonstration
Customer billing screen Real account balances and internal navigation; permission unclear Exclude from public materials
Team design-system release Tomas wrote two components; another person designed the system Retain an accurate history description; do not claim system ownership
Old static homepage exercise His work, but weak evidence for the requested interaction work Leave out of the selected examples

His finished portfolio item draft is:

Title: “React task-board demo with keyboard-friendly controls”

Role: “Frontend developer: interface implementation and component tests”

Description: “Independent demonstration using fictional task records. I built the React interface, keyboard interactions and component tests for creating and filtering tasks. The screenshots show the same sample dataset used in the demo. This is personal work, not a client engagement, accessibility certification or production performance claim.”

Proposed skills: React, JavaScript, CSS, Front-End Development and Software Testing, using the closest accurate options available in the editor.

The description gives the sample a purpose without pretending it represents paid work. It also keeps a useful distinction: demonstrating keyboard interactions does not establish that an entire application meets an accessibility standard.

For a hypothetical interface-implementation posting, Tomas's unsent emphasis sentence is: “My task-board demonstration shows the React interaction work I would discuss when scoping your interface, including keyboard controls and component tests.”

For a hypothetical testing-focused posting, his alternative unsent emphasis sentence is: “The same demonstration includes component tests around task creation and filtering; I would first confirm whether your assignment needs test maintenance, new coverage or interface changes.”

These sentences point to different evidence within one truthful service description. They are not two published profiles or actual proposals. Tomas would still read the real requirements before using either approach. If a posting needs backend load testing, neither sentence supplies evidence of that competence.

Keep portfolio review separate from client-visible changes

Upwork's portfolio instructions distinguish saving a draft from publishing: drafts are not visible to clients. The documented limits are 70 characters for the title, 100 for the role and 600 for the description, plus up to five skill tags. Preview the actual item before deciding to publish it.

Linking an item to a previous Upwork contract can notify the client and invoke a review process. That is a consequential step, not a silent way to organize your private inventory. Review the current instructions and your permission to share the material before linking real work. No contract was linked or client notified for this guide.

Check the files themselves as well as their captions. The portfolio guidance prohibits contact details in portfolio materials and linked sites. Review screenshots, documents and destination pages for exposed information; an innocuous thumbnail can lead to a page containing much more.

For Tomas's demo, the review decision is straightforward: fictional records, his own contribution, no customer data and a description that matches the displayed sample. For the billing screen, removing a customer's name alone would not resolve the unexplained permission question. He excludes it rather than assuming redaction grants permission.

Judge the rebuild by clarity before judging traffic

Upwork's profile examples guidance recommends original, client-focused wording and relevant evidence. Use other profiles to notice how clearly they explain a service, then write from your own experience. Copying a compelling paragraph can import claims you cannot support.

A useful final review is to read the title, opening, one portfolio description and work history as a single story. Ask what work you offer, which sample supports it and which responsibilities need clarification. If the answers conflict, fix that conflict before adding more keywords.

After a real update, keep the edit date and the wording you changed. If you later review invitations or proposal responses, record the jobs, timing and other changes too. A change in activity alone cannot isolate the effect of a rewritten profile, and it cannot validate a promised ranking boost.

Start your rebuild with one supported service and one sample you can explain confidently. If you are comparing freelancing with employment, browse recent roles on LandOffer.ai as a separate search. For this migration, start with your available work records, choose the service those records support, and draft one opening that explains it to a client.

Sources and Further Reading