11 min read
You've got strong repos and a polished PDF. Then Workday imports your file and your GitHub link vanishes. That's not rare. Parsers often drop hyperlinked-only URLs while they keep plain text on its own line. The fix isn't more repos. It's one visible profile URL in contact info plus one project bullet that repeats the full repo path in plain text.
Check your resume for free after you export. You'll often see a green Skills match while the parsed contact block never captured github.com at all.
Below: why links strip, five steps with before/after pairs, two edge cases, mistakes, a copy-paste contact block, and FAQ. You shouldn't lose credit for work recruiters would happily click if the parser had kept the URL.
Quick Wins
- Contact line: GitHub: https://github.com/yourhandle (plain text, own line).
- One project bullet with full repo path and posting stack keywords.
- Paste export into Notepad; confirm github.com appears intact.
- Remove icon-only GitHub glyphs from sidebar Skills rows.
What parsers do to GitHub links on import
Applicant tracking systems read text in rough top-to-bottom order. Contact blocks usually survive. Hyperlinks wrapped in anchor text often don't. The parser stores Portfolio or GitHub as a word and discards the destination URL behind it.
The pattern: a composite backend developer uploads a two-column Canva resume. The GitHub icon sits in a sidebar. Greenhouse imports React and Python from Skills but never attaches a URL to the candidate record. Recruiters who ctrl-f github see nothing even though the PDF looked fine on screen.
Plain text URLs on their own line fix most of this. So does repeating one repo path inside a dated project bullet where Experience parsers already look. You don't need a separate Portfolio section with six links. You need one profile URL recruiters can click and one repo they can open when the role is technical.
Read PDF resume vs DOCX resume which works better for ATS when your export format keeps breaking URLs across line wraps.
This guide is about parsing survival, not whether GitHub belongs on every file. For that decision, treat the posting as the gate. If the req lists a public code sample or stack you prove in repos, include GitHub using the format below.
Parsers also struggle when URLs carry tracking parameters or shortener domains. Use the canonical github.com path only. Strip UTM strings and bit.ly wrappers before they land on the resume.
Workday, Greenhouse, Lever, and Taleo all import differently, but the failure mode is the same: anchor text survives, destination URL does not. Plain text on its own line is the lowest-common-denominator fix across employers.
Because contact blocks parse early, putting GitHub there gives you the best shot even when later sections scramble. A project bullet with the repo path is backup insurance when the header import strips one character from the URL.
Five steps to include GitHub without parsing issues
Step 1: Add a plain-text profile URL in contact info
Put your name, phone, city, and email first. On the next line, type GitHub: https://github.com/yourhandle. No hyperlink anchor. No icon-only glyph. The full string should copy cleanly from Notepad.
Before: Header shows a blue linked word Portfolio pointing at GitHub.
After: Contact block lists GitHub: https://github.com/yourhandle on its own line under email.
Step 2: Choose one repo that matches the posting
Open the job description. Circle three stack terms. Pick the repo where you actually used two of them in production-quality code you can walk through live. Forks you never touched don't count.
Step 3: Write one project bullet with the full repo path
Under Projects or your latest employer strip, write one bullet: verb, stack, scope, outcome, then the full URL. Parsers that miss the header link often still capture URLs inside Experience or Projects paragraphs.
Before: Projects section lists Inventory App with a hyperlink labeled repo.
After: Built inventory REST API in Node.js and PostgreSQL for 3 warehouse clients; cut stock sync errors 18% in Q2 2025; https://github.com/yourhandle/inventory-api
Step 4: Run the Notepad import test
Export PDF or DOCX. Paste into Notepad on Windows or TextEdit plain mode on Mac. Search github.com. You should see at least two intact URLs: profile and project. If a line break splits the path, fix wrapping before upload.
Pair for frontend role: Before: GitHub icon in sidebar; React in Skills only.
After: Contact URL plus bullet: Shipped React component library used by 4 internal apps; cut UI bug backlog 22% in H1 2025; https://github.com/yourhandle/ui-kit
Step 5: Checker pass against the target req
Upload to a free checker with the posting text. Confirm parsed contact includes github.com and project terms land in body text, not only a footer. Tweak bullet wording if stack terms parse as disconnected tokens.
Pair for data role: Before: GitHub URL only in LinkedIn field on the application form, not on resume.
After: Resume contact lists profile URL; bullet names Python ETL repo with row volume and delivery window; full path in plain text.
Edge case: career-change bootcamp graduate
When work history is thin, place two bootcamp repos under a Projects heading with URLs and stack, not under a fake employer name. Keep employer strips honest. Parsers flag invented companies faster than they flag extra project lines.
Edge case: senior engineer with many repos
Link the profile in contact and one flagship repo in bullet one under your current role. Mention other repos in interview, not as six URLs on page two. Recruiters rarely open more than two links before the phone screen.
Copy-paste contact and project block
Copy-paste: Your Name | City, ST | phone | email | GitHub: https://github.com/yourhandle | Projects or Latest Role bullet: [Verb] [stack from posting] [scope] [outcome]; https://github.com/yourhandle/repo-name | Second bullet optional only if second repo proves a different must-have from the same posting.
Example: Built CI/CD pipeline in GitHub Actions for 12 microservices; cut deploy time from 45 to 12 minutes in Q3 2025; https://github.com/yourhandle/deploy-pipeline
Read what keywords does ATS look for when project bullets still pass parsing but keyword gates miss stack terms.
After GitHub is visible in parsed output, mirror one repo metric in a cover letter only if the field is optional. The resume still carries the proof recruiters ctrl-f first.
For mobile-first templates, preview the PDF on a phone before upload. Some builders wrap long URLs at narrow widths. If github.com breaks across two lines on mobile export, widen the contact column or shorten the handle line so the path stays intact.
Bootcamp grads should pin one capstone repo with tests and a short demo script in the README. Hiring managers forgive thin employment history faster when the linked repo runs locally without a scavenger hunt through issues.
Staff-plus candidates can skip listing every open-source contribution. Name the profile URL, link one repo that shows system design scope, and mention broader OSS work in the phone screen. Parsing favors clarity over volume on links too.
Link formats that fail screening
Hyperlinked anchor text without visible URL. Portfolio as a blue word imports as a word, not a link.
Icon-only GitHub logos in a sidebar. Parsers skip graphics. The URL never enters the database.
URL shorteners and tracking query strings. Some imports truncate at the question mark. Use canonical github.com paths.
Six repo links and no contact profile URL. Clutter without a clear front door makes recruiters give up.
GitHub only on the application form, not the resume. Screeners often open the file attachment first. If the URL isn't there, they may never check the extra field.
Listing GitHub under Skills without a bullet that proves usage. Skills echo tools. Bullets prove you shipped with them.
Two-column headers that wrap URLs mid-string. github.com/yourhandle split across lines fails Notepad test every time.
Private repos you can't share on a screen share. If the req asks for public samples, link public work or omit until you have one.
QR codes replacing typed URLs. Scanners do not feed ATS databases. Type the path.
GitHub gists as the only code sample. Fine for scripts; weak when the posting asks for application architecture. Link a repo with folders and tests when you have one.
I've screened developer batches where the PDF showed a clean GitHub button and the parsed record had zero URLs. The candidate assumed visual design equaled ATS readability. It didn't.
Verify parsed output before you apply
Run a free ATS check with the target posting. Confirm github.com appears in parsed contact or project text before you batch similar dev reqs.
Build your resume in a single-column layout if your current template hides contact links in a graphic header bar.
Plain text GitHub URLs beat pretty hyperlinks
How to include GitHub on your resume without parsing issues comes down to two visible strings: profile URL in contact, repo path in one project bullet. Everything else is optional polish that parsers may ignore.
Tonight: fix contact line, rewrite one project bullet with stack and full path, export, Notepad test, checker pass, then apply. You shouldn't need a redesign to keep credit for repos you already built.
When parsing looks clean and screens stay quiet, check seniority fit and bullet-one alignment next. GitHub fixes visibility. It doesn't override every gate.
Save a master dev resume with contact URL and two project bullets ready to swap per posting. Change repo path and stack terms per req instead of rebuilding headers each week.
If a teammate says their GitHub link looks fine in Word, ask them to paste the export into Notepad and search github.com. When the URL is missing there, the ATS record probably missed it too. Fix plain text before you chase more repos.
Technical screeners often open one repo before the call. Make that repo match the posting stack and include a README with setup steps. Parsing gets you into the database. The README gets you past the first human glance.
Read more
Frequently asked questions
Use plain text for the profile URL in contact info: GitHub: https://github.com/yourhandle. Hyperlinked anchor text like Portfolio often strips on import into Workday or Greenhouse. One project bullet can repeat the full repo path in plain text so parsers and recruiters both see it.
Place the profile URL on its own line in the contact block under phone and city. Add one featured repo as a bullet under Projects or under your latest role with stack and outcome. Avoid burying the only URL inside a Skills icon row or a footer column the parser reads last.
One profile URL in contact plus one or two repo paths in project bullets is enough. More than three full URLs clutter the import and rarely raise your score. Pick repos that match the posting stack and that you can explain on a phone screen.
For non-coding roles, skip GitHub unless the posting asks for code samples or you have repos that prove automation relevant to the job. For software, data, and DevOps reqs, a missing URL when peers include one looks like a gap. Match the posting, not every template on the internet.
Both can work when URLs are plain text on their own lines. PDF exports from design tools sometimes break URLs across lines; DOCX hyperlinks sometimes vanish on upload. Paste the resume into Notepad after export. If github.com does not appear intact, fix formatting before you apply.