10 min read
You added the keywords. The checker lit up green on skills. Workday still shows a garbled import or auto-rejects you before a human opens the file. That's not a density problem. It's a layout problem wearing a keyword mask, and it won't fix itself if you keep tweaking the Skills list.
Check your resume for free on the exact PDF you'll plan to upload. A free ATS resume checker should flag layout failures that keyword tweaks cannot fix: columns read out of order, contact info trapped in headers, creative section titles the parser doesn't map. Fix those before you rewrite bullet three again.
Below: the symptom when formatting breaks import, three causes with before and after fixes, how to tell which cause is yours, what broken files share, and what to run before the next application. Job searching is draining enough without fighting a template that looked fine in Word.
This isn't a font aesthetics guide. It's what I see when a qualified file dies in Greenhouse because the parser read the right words in the wrong order. If you've only been tuning keywords, you're fixing the wrong layer.
Most candidates don't find out until silence stacks up. You won't get an email that says "nice skills, bad columns." You'll get nothing. The checker plus plain-text export catches it before upload.
Quick Wins
- Export plain text after every save; scrambled order means layout fix, not more keywords.
- Move email and phone out of headers into the body top block.
- Rename creative section titles to Work Experience, Education, Skills.
- Drop tables, text boxes, and skill bar graphics; use bullets instead.
Green keywords, broken import
The symptom looks like a paradox. Your checker or a keyword highlighter says Python and SQL are present. The employer portal shows missing dates, employers stacked wrong, or Skills empty. You assume the ATS hates you. Often the parser never mapped your sections correctly.
What a formatting failure actually means: the file imported, but section boundaries landed in the wrong buckets. Recruiters searching "Work Experience" won't find bullets that parsed under a sidebar or a text box labeled "Impact."
I've opened Workday profiles where the candidate clearly had the skills on the PDF, but Experience showed one jumbled paragraph because a two-column Canva export read left column then right column. Keyword scans on the raw PDF still found the words. The structured profile did not.
Read why manual resume review is almost gone for the filter stack. This page is the layout layer beneath keyword tuning.
Edge case: some portals re-OCR scanned PDFs and turn letters into noise. That's a file-type problem, not a wording problem. Edge case: a DOCX with tracked changes still on can insert hidden characters. Accept all changes and save clean before upload.
How this differs from a keyword miss: a keyword miss shows up as a gap on a job match report against the posting. A layout miss shows up as scrambled plain text or empty Experience in the ATS preview while the PDF looks perfect to your eye. Run both checks. They answer different questions.
Free ATS resume checker: three layout causes and quick fixes
Cause 1: Multi-column layout scrambles read order
Parsers often read down column one, then column two. Skills in a right rail can attach to the wrong job. Dates beside titles in a table can detach entirely.
Before: Two-column resume: left column has Experience bullets; right column has Skills and certifications in a shaded sidebar.
After: Single column: name and contact on line one, Work Experience with Month Year dates inline, Skills as a simple list below Education.
Before: Table grid for each job: company logo cell, title cell, date cell, bullets in merged cells.
After: Plain lines: Company Name | Job Title | 03/2022 to 06/2024, then hyphen bullets underneath. No merged cells.
Fix: Rebuild in a single column at 11-point Calibri or Arial. Export plain text. If Skills appear after Education in the text dump, reorder in Word until they land where you expect.
Cause 2: Contact info and dates trapped in headers or footers
Many templates put email and phone in a header block because it looks clean. Workday and iCIMS often skip header/footer zones on import. Recruiters see a name with no way to reply.
Before: Phone and email only in the PDF header; body starts with Summary.
After: First lines of body: Full Name, City ST, [email protected], (555) 123-4567, linkedin.com/in/handle.
Before: Page numbers and "Confidential" in footer; last job dates only in footer on page two.
After: Dates beside each role in the body. Remove decorative footers entirely.
Fix: Double-click header/footer in Word, cut contact lines, paste at document top. Re-export and confirm plain text shows phone and email in the first ten lines.
Cause 3: Non-standard section labels hide Experience
Creative headings like "Where I've Made Impact" or "Professional Journey" do not map to the Experience field in most ATS profiles. Bullets sit in an unsearchable blob.
Before: Section title: Career Highlights. Content: three jobs with bullets.
After: Section title: Work Experience. Same bullets, standard label.
Before: Section title: Tech Stack with icon fonts for Python, AWS, Docker.
After: Section title: Skills. Lines of text: Python, AWS, Docker, PostgreSQL.
Fix: Rename sections to Education, Work Experience, Skills, Certifications. Keep creativity inside bullets, not headings.
Cause 4: Graphics, skill bars, and text boxes drop content
Infographic templates hide words inside shapes. Parsers read text layers, not colored rectangles. Skill bars show five dots for Python but import as blank space.
Before: Skills section uses horizontal bar charts at 80% for JavaScript and 60% for React.
After: Skills section lists JavaScript and React on separate lines; proof lives in bullets under Work Experience.
Before: Summary inside a shaded text box with a border graphic.
After: Summary as normal paragraphs under a plain Summary heading, no box drawing.
Fix: Delete charts, icons, and text boxes. Type the skill names. Move proof into Experience bullets where recruiters actually search in Workday.
Edge case: Canva and similar exports often flatten to images. Re-type the resume in Word or Google Docs even if it looks less flashy. Edge case: hyphen bullets copied from the web sometimes import as odd Unicode characters. Re-type bullets natively in your editor.
How to tell which cause is yours
Column scramble: Plain-text export shows Skills or certs between two jobs that should be separate. Cause one.
Missing contact: Plain text has no email in the body. Cause two.
Unmapped sections: ATS preview shows one big paragraph under "Other" or blank Experience. Cause three.
Blank skill graphics: Plain text skips skill names but shows odd symbols or empty lines where bars were. Cause four.
Edge case: image-based PDFs from design tools pass visual inspection but fail text export entirely. Re-save as text PDF or DOCX. Edge case: hyperlinks only in icons do not parse as URLs; spell the link in text if it matters.
Copy-paste formatting reset checklist
1. Single column, no text boxes or tables for layout
2. Contact block in body lines 1 to 4
3. Headings: Work Experience | Education | Skills | Certifications
4. Dates: Month Year to Month Year beside each role
5. Bullets: standard round dots, not custom Wingdings
6. Save DOCX, export PDF, run plain-text export and read order aloud
Work through the list top to bottom on the file you already have. Pair with how to tailor a resume to a job description after layout is clean. Tailoring scrambled sections wastes time.
Platform note: Taleo and iCIMS can be pickier about tables than Greenhouse on some configs. The fix is the same: single column, standard headings, text contact block.
What scrambled imports share
Chasing keyword density on a broken template. Adding SQL five more times does not fix a sidebar that parsed under Education.
Trusting the Word preview alone. Word looks fine. Plain text tells the truth. Always export both before you apply.
Using design-tool PDFs for corporate portals. Pretty gradients often mean image layers. Corporate ATS wants boring text.
Mixing date formats. Jan '22, 2022, and 01/2022 on the same file confuse timeline sort. Pick Month Year and stick to it.
Hiding must-have certs in graphics. A badge image does not search. Type the cert name and issuer as text.
Re-uploading the same broken PDF with new keywords. Log file version and plain-text export. If order did not change, layout did not change.
Using light gray text for secondary details. Some parsers drop low-contrast text. Stick to black on white for body copy.
Nesting jobs inside summary paragraphs. Each role needs its own employer line and date range. Paragraph-style career stories do not sort in Taleo.
Scan before you tailor again
Run the rebuilt file through the free ATS resume checker before you touch keywords for the next req. Confirm section order and gate terms parse in the right buckets. A human rewrite on a clean template beats a third keyword pass on a two-column export.
Then score your job match on one target posting. Use the gap list on Experience bullets only after import looks correct. Applying with a scrambled profile wastes a good match score.
For roles that ask for a letter, generate a cover letter after layout passes. A clean letter on top of a broken resume still fails when they download the PDF from the portal.
Save checker output with the file name and date. When silence continues after layout fixes, you can rule out parser failure and focus on fit or timing instead.
Build a before-and-after habit: keep the broken export as v1, the fixed single-column file as v2. When a friend asks why you're not hearing back, show the plain-text diff instead of guessing.
Layout first, keywords second
A free ATS resume checker earns its keep when it catches layout failures keyword tweaks cannot fix. Columns, headers, and renamed sections break import while your Skills list still looks full in preview. Fix the skeleton, then tailor the muscles.
Open your last upload. Export plain text. If the story reads out of order, rebuild single column tonight before you add another keyword. Run the checker on the new file. Log the version. Apply with proof the parser and the recruiter see the same story.
Keywords without structure are noise in the wrong drawer. Structure without keywords is an empty drawer. You need both, in that order.
If you're on a timeline, block one hour for layout only. No job boards, no new postings. Rebuild single column, run plain text, run the checker, save v2. Tomorrow you can tailor keywords on a file that actually imports. That's the sequence that sticks.
The free ATS resume checker is a parse mirror, not a score to brag about. Confirm formatting errors are gone, then move on to fit and timing.
Read more
Frequently asked questions
Yes. Keyword tools read text you typed. Workday and Greenhouse read layout first. A two-column template can dump your Skills block under Education while still showing SQL in a side panel preview. Fix column order and plain-text export before you add another keyword.
Use DOCX when the portal accepts it; parsers often handle Word structure more predictably. PDF is fine when it is text-based, single-column, and exports cleanly to plain text. If plain-text export scrambles sections, switch format before you reapply.
They often do. Rating bars and font icons are graphics, not words. Replace them with a simple Skills list or proof bullets in Experience. The checker should show the skill as text, not a rectangle.
Export plain text from your PDF. If your phone number or email only appears once at the very top or bottom and missing from the body, the parser likely read header/footer zones only. Move contact lines into the main document body.
No. Layout gets you a faithful import. Tailoring still belongs in bullet one and gate terms from the posting. Run layout fixes first so keywords land in the sections recruiters search.
