# ATS-friendly Google Docs CV template

> Google Docs is free, works everywhere, and its built-in CV templates are mostly a trap. Here is the structure to build instead (ten minutes, no add-ons) and the export settings that keep it parseable.

- **URL**: https://www.fitmycv.link/google-docs-cv-template

---

## How to build an ATS-friendly CV in Google Docs

Build a single-column, parse-safe CV in Google Docs and export it correctly.

1. **Start from a blank document.** Do not use the built-in CV templates. Several use two-column tables and place contact details in the page header.
2. **Set margins and type.** 2cm margins all round, a standard font at 10 to 11pt for body text, and 1.15 line spacing.
3. **Build the sections in order.** Contact details, summary, experience, skills, education. Each heading styled as Heading 2 using the standard vocabulary.
4. **Write bullets with the list tool.** Use the real bulleted-list button rather than typing dashes, so the structure survives extraction.
5. **Export as PDF.** File -> Download -> PDF Document. Never print to image, and never use File -> Print -> Save as PDF from a browser preview.

## Why not just use the built-in templates

Google Docs ships several CV templates and they are a reasonable starting point visually. The problem is structural: some use a **two-column table** for the layout and put the name and contact block in the **page header**. Those are the two most reliable ways to lose information during parsing: reading order interleaves, and header content is routinely skipped entirely.

Ten minutes from a blank document gives you something that looks nearly identical and parses correctly.

## The structure to build

1. **Page setup.** File -> Page setup. Margins 2cm on all sides. Keep the page size as A4 or Letter to match where you are applying.
2. **Contact block: in the body.** First lines of the document, not the header. Name at 16 to 18pt bold, then a single line: target job title | city | phone | email | LinkedIn URL.
3. **Section headings.** Use the Heading 2 style (not just bold text) for Summary, Experience, Skills, Education. Real heading styles give the document structure that survives export.
4. **Experience entries.** One line per role: Employer - Job Title (Mar 2022 to Present). Then three to six bullets using the bulleted-list button, never typed dashes.
5. **Skills.** Two or three grouped lines of plain text. No tables, no columns, no rating graphics.
6. **Export.** File -> Download -> PDF Document (.pdf). Open the result and try to select a line of text. If you cannot, something went wrong.

> **The one thing not to do**
>
> Do not use Insert -> Table to put two things side by side. If you need a job title on the left and dates on the right, put them on one line separated by an en dash or a pipe. Tabs and right-alignment are also safe; tables are not.

## Checking it worked

1. Open the exported PDF and select all, then paste into a plain text editor.
2. Read what arrives: sections in order, contact details present, bullets intact.
3. If anything is scrambled or missing, the culprit is almost always a table or a header.
4. Then score the content against a real posting with the [free ATS resume checker](/ats-resume-checker).

## Where Google Docs runs out

It is genuinely fine for building and storing a master CV. What it cannot do is the per-application work: duplicating the file, rereading the posting, remapping which bullets lead, and rewriting the summary for each role. That is twenty to forty minutes each time, and it is the step almost everyone abandons around application twelve.

|  | Google Docs | FitMyCV |
| --- | --- | --- |
| Build a master CV | Yes | Yes |
| Free | Yes | Free to build; paid to tailor |
| Switch layout without retyping | No | Yes, 24 templates |
| Read a job posting URL | No | Yes |
| Rewrite bullets against a posting | No | Yes |
| Matching cover letter | No | Yes |

If the Google Docs route is enough for you, the structure above is all you need. If the per-application editing is what is stopping you, the [CV templates](/cv-templates) page covers the 24 built-in layouts and [tailoring from a job link](/tailor-cv-from-job-link) covers the part Docs cannot do.

## Next step

- [Skip the setup](/cv-templates)
- [How to write a CV](/how-to-write-a-resume)

## Related

- [CV templates](/cv-templates): 24 ATS-safe layouts with no setup and no table traps.
- [How to write a resume](/how-to-write-a-resume): What goes in each section once the document is set up.
- [ATS resume checker](/ats-resume-checker): Score your exported PDF against the posting you are applying to.

## FAQ

### Are the built-in Google Docs CV templates ATS-friendly?

Mostly not. Several of the stock templates use two-column tables for layout and place the name and contact details in the page header, the two changes most likely to scramble or lose information when the file is parsed. Start from a blank document instead.

### How do I make a CV in Google Docs?

Start blank, set 2cm margins, use Heading 2 for standard section names, write experience bullets with the real list tool, and export with File -> Download -> PDF Document. The full structure is laid out on this page and takes about ten minutes.

### Should I send my CV as a Google Docs link?

No. Send a PDF attachment unless the application explicitly asks otherwise. A share link can be permission-blocked, is not archivable by the employer's system, and tells them when you opened it.

### Does exporting from Google Docs keep the text layer?

Yes, if you use File -> Download -> PDF Document. That produces a proper text-based PDF. Printing to an image, screenshotting, or exporting from a browser print preview can strip or degrade the text layer.

### What font should I use in a Google Docs CV?

Any standard system font at 10 to 11pt for body text and 14 to 18pt for your name. Avoid decorative or recently added Google Fonts, which can embed with non-standard character maps and produce garbled text on extraction.

### Can I tailor a Google Docs CV to each job automatically?

Not within Google Docs. You would duplicate the file and edit it by hand each time, which is twenty to forty minutes per application. That is the specific limitation this site exists to remove.