Why technical SEOs keep the CV in plain text
If you spend your week in crawl exports, log files and rendering diffs, a word processor is an odd place to keep your own document. Markdown keeps it diffable and portable, and the export is deterministic.
What hiring managers screen for
Technical SEO is the most engineering-adjacent branch of the discipline, and the screen is looking for someone who can hold a credible conversation with a developer.
Crawling and indexing, diagnosed. Not “improved indexation” but what was wrong — orphaned pages, faceted navigation generating millions of URLs, a noindex shipped in a release, canonical tags pointing at redirects — how you found it, and what happened after.
Rendering. Whether the site was client-side rendered and what that cost in indexation, and what you changed: SSR, dynamic rendering, hydration fixes. This single topic separates technical SEOs from generalists faster than anything else.
Migrations. Domain, platform, or information architecture. State the size, the redirect strategy, and the traffic retained. A migration that held 95% of organic traffic is a strong, verifiable claim.
Core Web Vitals, honestly. LCP, INP and CLS before and after, and what you actually changed. Reviewers know the difference between a real fix and a lab-score screenshot.
Technical vocabulary these screens require
- Crawl and index: crawl budget, log file analysis, XML sitemaps, robots.txt, canonicalisation, pagination, faceted navigation, index bloat
- Rendering and performance: JavaScript SEO, server-side rendering, hydration, Core Web Vitals, LCP, INP, CLS
- Structure: site architecture, internal linking at scale, hreflang, structured data, schema.org
- Tools: Screaming Frog, Sitebulb, Search Console, BigQuery, Python, Botify or OnCrawl
- Collaboration: working with engineering, writing tickets, QA on staging, release review
What undercuts a technical SEO résumé
Audit counts. “Completed 40 technical audits” measures output, not impact. What got fixed, and what changed as a result?
Findings with no shipped fix. The hard part of this job is getting engineering to prioritise the work. A résumé that lists diagnoses without deployments describes half the role.
No numbers on scale. Technical SEO on a 500-page site and a 5-million-page site are different jobs. Say which one you have done.
Avoiding the tooling question. Comfort with Python, SQL or BigQuery for log and crawl analysis is increasingly a baseline expectation at senior level.
Frequently Asked Questions
Is this technical SEO resume template free? +
Yes. Edit it in your browser and export to PDF, DOCX, or HTML with no account, no watermark, and no usage limit.
What sets a technical SEO resume apart? +
Depth on the engineering side of search: migrations, indexation, Core Web Vitals, and structured data — with the metrics they moved. The sample bolds each result.
Should I show coding skills? +
Yes, if you have them. Python, log-file analysis, and JavaScript SEO signal you can work directly with dev teams — a major advantage for technical SEO roles.