How to answer “Include a link to your GitHub profile and/or website” on Upwork
Updated
The client is not just asking for a URL. They’re checking whether your public work supports the proposal you just wrote. For developer jobs, your GitHub profile, portfolio site, case study page, or live demo helps them answer one question fast: can this person actually build the thing I need?
A good answer gives the link, then tells the client exactly what to look at. Don’t make them click around and guess which repo matters. Point them to the most relevant project, explain your role, name the stack, and connect it to their job.
What the client is really checking
- Proof of skill: They want evidence beyond your cover letter. For coding work, that may be source code, commits, tests, documentation, or a deployed app.
- Relevance: A React client cares more about your React work than a random Python script. A Shopify client wants to see storefront, app, theme, or integration work.
- Taste and judgment: Clean README files, sensible folder structure, useful commit messages, and clear portfolio pages show how you communicate when nobody is watching.
- Ownership: They want to know what you personally did. If the site was a team project, say which parts were yours.
- Risk: Broken links, empty profiles, old demo sites, and unexplained private work make the client wonder what else will be difficult.
Include a link to your GitHub profile and/or website.
New freelancer
Here’s my GitHub: {{github_url}}. The most relevant repo is {{repo_name}}, where I built {{short_project_description}} using {{stack}}. For this job, I’d suggest looking at the README, the component structure, and the way I handled {{specific_feature}}. I’m newer on Upwork, but this sample shows the type of clean, documented work I’d bring to your project.
Experienced
GitHub: {{github_url}}. Portfolio: {{website_url}}. The best match for your project is {{project_or_repo_name}}, which includes {{relevant_feature_1}}, {{relevant_feature_2}}, and {{relevant_feature_3}}. My role was {{your_role}}, including {{specific_responsibility}}. For your {{client_project_type}}, the most relevant part is {{specific_area}}, because it’s close to the workflow you described.
Agency
Our website is here: {{agency_website_url}}, and our public GitHub is here: {{github_url}}. For this job, please review {{case_study_or_repo_name}}. It shows our work on {{similar_project_type}}, including {{relevant_system_or_feature}}. The team members who would work on your project are {{roles}}, and our part in the sample was {{agency_scope}}. Some client repositories are private, but we can share more detail about architecture and process on a call.
Why these answers work
Each answer does more than paste a link. It tells the client where to click, what to inspect, and why it matters. That matters because many clients skim screening answers before they read the full proposal. A clear answer makes your proof easy to verify.
For technical jobs, match the link to the job type. A JavaScript job should point to JavaScript work if you have it. A React developer proposal should be backed by a React app, component library, or frontend case study. A Python developer proposal should point to Python code, automation, API work, data scripts, or a relevant backend project.
What makes this answer get skipped
- Only saying “See my GitHub.” That makes the client do all the work. Add one sentence about the most relevant repo or project.
- Sending a broken, private, or empty link. Test it in a logged-out browser before you send the proposal.
- Linking to unrelated work. A calculator app may not help much if the job is for a complex SaaS dashboard, unless you explain the relevant part.
- Hiding behind NDAs with no alternative. “All my work is private” is weak by itself. Add a public sample, anonymized case study, or describe the architecture you built.
- Overloading the answer with every link you own. One strong GitHub link and one strong portfolio link are usually better than ten weak links.
- Not saying what you did. If the work was from a team, clarify your contribution. Clients are wary of portfolios that don’t show ownership.
- Using a messy portfolio site. If your site is slow, outdated, full of broken images, or hard to navigate, send the cleaner GitHub repo instead.
How to adapt your answer to the job
- 1
Pick one primary link
Choose the link that best supports this specific job. If the job is backend-heavy, don’t lead with a design portfolio. If the job is UI-heavy, don’t lead with an API repo unless it’s the closest match you have.
- 2
Name the exact project to review
Don’t rely on the client to scan your whole GitHub profile. Say, “The most relevant repo is X,” or “The closest case study is Y.”
- 3
Translate the sample into client value
Connect the sample to the job post. For example: “This is relevant because your app also needs role-based dashboards and Stripe billing.”
- 4
Explain your role in plain language
Use direct wording: “I built the frontend,” “I wrote the API,” “I handled deployment,” or “Our agency handled design and development.”
- 5
Handle private work honestly
If your best samples are private, don’t apologize for it for three paragraphs. Give the best public proof you can and explain the private work at a high level.
Most of my closest client work is in private repositories, but here’s a public sample: {{github_or_website_url}}. The most relevant part is {{specific_feature_or_section}}, because your project also needs {{client_requirement}}. On similar private projects, I handled {{your_responsibility}} using {{stack_or_tools}}.Use this when you have strong work you cannot show publicly.
Here’s my portfolio: {{website_url}}. Please start with {{case_study_name}}, which is closest to your project. It covers {{feature_1}}, {{feature_2}}, and {{feature_3}}. My role was {{your_role}}, and I’d approach your project with a similar focus on {{client_priority}}.Use this when your website explains the work better than GitHub does.
Quick check before you send
- Open your GitHub or website in an incognito window.
- Make sure the project name in your answer matches the page you linked.
- Check that the README, screenshots, demo, or case study are understandable without a call.
- Remove any confidential client details you’re not allowed to share.
- Add one job-specific sentence that repeats the client’s actual need.
If you answer lots of Upwork screening questions, keep a few versions of this response ready: public GitHub, private-work explanation, agency case study, and portfolio-first. Then customize the first two sentences for each job.
BidGrow can help by scoring new jobs with rules you can read, then drafting proposal and screening-question answers from your own templates. You still review everything and press send yourself. It does not submit proposals or log in to Upwork for you, and it isn’t affiliated with or endorsed by Upwork.
Questions
Should I link to GitHub if my profile is not impressive?
Yes, if there is at least one relevant repo with readable code or a clear README. If not, use your website, portfolio, case study, or a small public sample built for the type of work you sell.
What if all my best code is private?
Say that briefly, then offer a public sample or sanitized case study. Clients understand private repositories. They just need some proof that connects to their project.
Should I include both GitHub and a website?
Include both if they help. Lead with the one that proves the job requirement best, then mention the second as supporting context.