11 min read
Your portfolio is strong. Your contact row has a mail icon, a phone icon, and a chain-link glyph where the URL used to be. You upload to iCIMS, the preview shows your name and email. The portfolio line vanished. Recruiters never click what they can't see in plain text, and parsers won't reconstruct a URL you didn't spell out.
You're not alone if a designer resume template caused this. Links don't break ATS because hyperlinks are forbidden. They break because parsers read linear text and your design hid the string. If you can't Ctrl+F the domain in the parsed preview, neither can the system scoring your file. Check your resume for free on the export PDF before you blame the tool. You're confirming whether URL characters survived parse, not whether the Word file looked pretty.
US corporate uploads punish clever layout. You don't need a design degree. You need contact lines recruiters can copy and project URLs that stay attached to the bullet they prove. That's the whole game: visible strings, boring layout, scan the PDF you'll actually submit.
Below: what readable links look like in parsed text, five teardown pairs across roles, what broken versions share, and a copy-paste contact block. When links parse clean, generate a cover letter that names one portfolio piece so the upload package points to the same URL twice on purpose.
Quick Wins
- Label plus plain URL on one line: Portfolio: yourname.dev
- Project links after the deliverable name inside the bullet, not in a footer.
- Scan the PDF you'll upload; if the URL string is missing, parsers won't invent it.
What parsers need from a link line
Parsers credit URLs they can read as characters, in order, on one line. Workday, Greenhouse, Lever, and Taleo don't click your links. They strip or keep the text. A glyph with a hidden anchor often becomes nothing. A table cell with three URLs jammed together becomes one mangled string.
Recruiters behave the same way on a phone screen. They copy a portfolio URL into a browser. If they have to right-click and guess, they move on. Readable beats pretty every time on US corporate applications.
The standard you're judged against is boring: Name on line one, contact block with email, phone, city and state if relevant, then one labeled URL per line with the full domain visible. No pipes cramming four links into one row unless you're sure your export still parses that way.
File format matters after layout. A text-based PDF from Word usually keeps URL strings. Image-heavy exports treat links as decoration. Test the artifact the portal receives, not the template you designed at midnight.
HTTPS prefix is optional on US resumes when the domain is obvious. github.com/handle parses the same either way. Skip query strings and tracking parameters in contact lines. Clean paths beat analytics clutter.
Email addresses are links too. Plain text [email protected] survives every parser I've tested in corporate uploads. Mailto buttons wrapped in buttons do not.
Five before-and-after link teardowns across roles
Teardown 1: Contact block for a marketing coordinator
Before: Header row with envelope icon linked to email, phone icon, and LinkedIn icon only. No visible URL strings.
After: Alex Rivera · [email protected] · 312-555-0142 · Chicago, IL · Portfolio: alexrivera.work · Profile: linkedin.com/in/alexrivera-mktg
Teardown 2: Software engineer with GitHub proof
Before: Footer band: "Links: GitHub | Portfolio | Blog" with hyperlinks on each word.
After: Contact: github.com/jchen-dev · jchen.dev. Project bullet: "Shipped payments retry service (github.com/jchen-dev/pay-retry) cutting failed charges 18% in Q2."
Teardown 3: UX designer portfolio in a two-column template
Before: Portfolio URL inside a left sidebar text box. Parser merges sidebar into contact and drops the box.
After: Single column. Summary ends with Selected work: morganlee.design/case-studies. Case study URL repeated once in the Projects bullet it supports.
Teardown 4: Nurse with certification verification link
Before: "Verify credentials here" hyperlinked with no visible board URL.
After: Certifications: RN, Illinois · License lookup: idfpr.illinois.gov (license number on request). Plain state board path, no click-here wrapper.
Teardown 5: Sales rep with published deck sample
Before: Bit-style short URL in Skills: "Pitch deck: [short link]"
After: Bullet: "Built enterprise pitch deck for logistics vertical (slides at parker-sales.com/deck-logistics) used in 12 late-stage opps." Full path on your domain, tied to the outcome line.
I've opened Greenhouse previews where the only portfolio signal was an icon row. The human resume on disk had URLs. The parsed view didn't. Fix the string, not the color palette.
Copy-paste block: ATS-safe contact lines
Your Name City, ST · phone · [email protected] Portfolio: yourdomain.com Code: github.com/yourhandle Writing sample: yourdomain.com/sample-title (only if posting asks) Project bullet pattern: [Outcome verb] [deliverable] ([full URL path]) [metric].
Edge case: the employer forbids external links in the application form but allows a resume upload. Put one primary portfolio URL in contact. Drop extra project URLs unless the posting requests writing samples or repos.
Edge case: your name is common and the clean URL is taken. Use a middle initial or role slug in the path: james-park-analytics.dev reads better than a string of random numbers. Still spell it out in full.
Upload issues often look like link problems but are really file problems. See resume upload mistakes that instantly disqualify you when the portal rejects the file before parsing starts.
Academic CVs sometimes carry ten publication URLs. US corporate one-page resumes aren't that format. Pick the two publications the posting's research area would care about and cite them in a Publications line with full DOI or journal paths spelled out.
Creative roles get pressure to make the resume itself a portfolio piece. Keep the proof link in contact and let the PDF layout stay boring. The work sample site is where you show taste. The resume is where you show parse survival.
Government and federal resume builders sometimes auto-insert link fields. If the builder exports a blank link row, delete the row entirely. An empty labeled field can push real contact lines off the first parser screen.
What broken link rows share
They hide the URL string behind design. Icons, buttons, and "click here" anchors look fine in Word. Parsed text often shows an empty line or a lone word with no domain.
They stack too many links in one table cell. Parsers read left to right and drop separators. Three URLs in one pipe-delimited row become unreadable mush in Taleo previews.
They park proof links in Skills. A GitHub URL in Skills without a repo named in Experience tells recruiters nothing about what you shipped. Tie the URL to a bullet with a deliverable and a date.
They trust the editable file over the upload PDF. Hyperlinks survive in Word and vanish in export. Always scan the PDF you'll attach to the portal.
Before: Icon header, footer link bar, short redirect URLs, no parser test.
After: Labeled plain-text URLs in contact, one project URL per bullet, custom domain paths, PDF scanned before apply.
This won't fix a portfolio that contradicts your bullets. It stops a qualified file from losing the one line recruiters needed to verify your work.
Platform-specific upload quirks matter after links parse. Read iCIMS resume upload issues US formatting guide if your URLs look fine locally but the iCIMS preview still strips the contact block.
QR codes on resumes look modern and parse terribly. Recruiters on desktop won't scan them. Parsers read them as images. Delete the square and type the URL.
Before: Contact row uses blue underlined hyperlinks only, no visible characters in the URL field.
After: Same links as plain gray text with labels, one per line, then optional hyperlink on the URL string for email applications only.
Watermarked portfolio hosts sometimes inject long tracking URLs when you copy a share link. Open the public view, copy the browser address bar, and trim parameters before you paste into contact. Recruiters shouldn't need a login to see your sample.
If you maintain separate writing and design portfolios, pick one primary URL for contact and mention the second only when the posting asks for that medium. Two home pages split recruiter attention and double the parse risk.
Test the export before upload
Run the PDF through HireFlow's free ATS resume checker . Confirm URL strings appear in the parsed contact section and that project links stayed inside Experience bullets, not orphaned at the bottom.
If you're rebuilding from a broken template, build your resume in a single-column layout so contact lines export in reading order.
Do this now: Replace icon contact rows with labeled plain URLs, move project links into bullets, export PDF, scan once, apply to one role with a portfolio line that survives parse.
What to fix tonight
How to format links on a resume without breaking ATS comes down to visible URL strings, labeled contact lines, and project paths inside the bullets they prove. Strip icons, test the PDF, and keep the link count small. When a recruiter can copy your portfolio line from the preview without opening another menu, you've done it right.
Build a five-line contact template once and reuse it across applications. Name, phone, email, city, one portfolio URL. Add a second profile URL only when the role is public-facing and the posting names that platform. Everything else belongs in a bullet with context.
After you fix links, don't touch the layout again unless a scan fails. Repeated exports from design tools are how good URL strings disappear between applications. One clean PDF beats five prettier drafts.
- Rewrite contact as plain text: label, colon, full domain.
- Move repo and deck URLs into the supporting bullet.
- Export single-column PDF and scan before upload.
- Drop redirect links that hide the destination.
Open your last export. Run a free ATS check , confirm URLs survived parse, and re-upload once with readable lines.
Read more
Frequently asked questions
For US portal uploads, plain text URLs on their own line or after a label win most of the time. Hyperlinks behind icons or inside tables often strip on parse. If you email the resume directly to a hiring manager, a clean hyperlink on the URL string itself is fine. Always scan the exact PDF you'll upload.
Contact block for your primary portfolio and profile URLs, one per line with a short label. Project-specific URLs belong in the bullet they prove, spelled out in full after the deliverable name. Don't bury six links in a footer band parsers read last or skip.
Avoid them on US corporate uploads. Short links look like opaque strings to parsers and recruiters, and some security filters flag them. Use a short custom path on your own domain instead: yourname.dev/case-study reads cleaner than a random redirect token.
The PDF matters more than the link type. A text-based PDF exported from Word with visible URL strings usually survives. Scanned images, Canva-style graphics, or links drawn on shapes vanish. Run a parser preview on the upload file, not the design draft.
Two to four total for most roles: email, phone, one profile URL, one portfolio or project proof link. Add a second project URL only when the posting asks for a writing sample or code repo. More than that and parsers start dropping lines from the contact block.