SEO Resume

An SEO resume is not a biography. It is a proof-of-concept page. You are supposed to convince the person reading it that you understand how search engines work, that you can move a number, and that you know how to prioritise. The best way to do that is to show, not tell.

I learned this the hard way. My first resume said “SEO Specialist with 5 years of experience managing on-page optimisation and link building.” That sentence told nobody anything. I rewrote it to: “Increased organic traffic by 40% for a SaaS client in 6 months using technical audits and content restructuring.” That got me a call back from two agencies within the same week. The difference is a single number.

Your resume summary should be a short paragraph (3–5 sentences) that opens with a metric. After that, list your experience in reverse chronological order, but for each job you pick the 3–4 achievements that had the biggest business impact. Do not list duties. No one cares that you “performed keyword research.” They care that you found a set of 120 keywords that drove 15,000 visits a month.

ATS (applicant tracking systems) are the gatekeeper. I have run my resume through a plain-text scanner and seen it fail because I used a two-column layout. Now I use a single column, standard headings (Experience, Education, Skills), and a font like Arial. I save as PDF. And I mirror the job description’s keywords — if the ad says “technical SEO,” I use that phrase exactly, not “on-site optimisation.” But I do not stuff keywords. One natural mention per bullet is enough.

If you are a [freelance SEO](/freelance-seo/) consultant, your resume often becomes your portfolio. I link to case studies and include a line like “client work available on request.” That is often enough to convert a browse into a meeting.

An SEO resume matters every time you are not the only candidate. For most [SEO jobs](/seo-jobs/), you are competing against dozens of people who all claim to know the same things. The resume is the filter. I have been on the hiring side twice, and I can tell you: I spent about 30 seconds on each resume. If I did not see a number in the first three lines, I moved on.

It matters most when:

• You are applying for a role in an agency or in-house team that already has an SEO function. The hiring manager knows the jargon and will spot generic language instantly.
• You are a [freelance SEO consultant](/seo-consultant/) pitching to a client who has been burned before. They want proof that you can deliver, not promises.
• You are early in your career and need to compensate for limited experience. A well-structured resume with a single strong metric can outweigh years of experience.

It matters less when:

• You are being headhunted or referred internally. Even then, I still send a tailored resume because the recruiter has to submit something to HR.
• The role is a junior position where the employer expects to train you. In that case, your resume’s job is to show you have the foundational skills and can learn fast.

I track my own response rate. Before I started tailoring, I got one interview per ten applications. After I introduced the metric-first summary and keyword mirroring, it went to one in four. That is a 150% improvement. If you are coming from a different field, your resume is your only chance to prove you can think like an SEO. Spend the time on it.

I also use the job description to decide which skills to highlight. If the ad mentions Google Analytics and SEMrush, I make sure those appear in my skills section and in a bullet under a relevant role. But I do not list every tool I have ever touched. I even removed Ahrefs once because the job used Moz. That seems small, but it signals to the ATS that you are a match for that specific stack.

I got a lot wrong. First, I used to write a generic objective statement like “Seeking a challenging role where I can utilise my SEO skills.” That is meaningless. I now write a summary that states what I have already achieved, not what I hope to do.

Second, I used to list every tool I had ever touched — including ones I used once in a training course. That dilutes the signal. Now I only list tools I have used in production for at least three months, and I only include them if they match the job description. I also learned that tools change; the ATS does not care about your proficiency level in a tool that is no longer used.

Third, I used to think longer resumes were better. I had a two-page resume with every project I had ever touched. That was a mistake. For most roles, one page is enough. The only exception I have seen is for senior roles where you need to show progression. I now keep it to one page unless I have more than 10 years of experience or am applying for a [SEO manager](/seo-manager/) position.

Fourth, I buried my strongest results in the middle of bullet points. I assumed the recruiter would read the whole thing. They do not. Now I open every bullet with the metric: “Drove 30% increase in organic traffic by…” not “Responsible for SEO which resulted in…”. The latter is safer but invisible.

Fifth, I ignored the formatting for ATS. I used tables, columns, and even a pie chart once. All of those got stripped and the resume became a jumble of text. I now use a standard template with no columns, no graphics, and simple section headings. I test it by copying the text into a plain text editor to see if it reads logically.

Finally, I used to send the same resume to every job. That is like sending the same meta description to every page. It works for none of them. I now have a master resume with all my achievements, and I cut and paste the most relevant 3–4 bullets per role. That takes 20 minutes per application, but it tripled my callback rate. If you are serious about a [career in SEO](/career-in-seo/), that is time well spent.