SEO technical writing refers to creating content about complex or specialized topics—software documentation, medical guides, engineering explanations, legal topics—while optimizing that content for search engines. Technical SEO is the practice of optimizing website infrastructure: crawl budget, XML sitemaps, robots.txt, structured data, page speed, mobile-friendliness, and indexing issues. They're different disciplines that sometimes intersect. A technical writer focused on SEO needs to balance subject-matter accuracy with keyword research, search intent, and readability for non-experts. They structure content with proper heading hierarchy, answer People Also Ask questions, and write meta descriptions that drive clicks. The challenge is avoiding keyword stuffing or oversimplification that damages credibility with expert audiences. For example, writing API documentation that ranks for "how to integrate X payment gateway" requires both developer-level precision and beginner-friendly explanations. Technical SEO specialists, meanwhile, rarely write long-form content. They audit site architecture, fix canonical tag issues, optimize JavaScript rendering for Googlebot, configure server headers, and improve Core Web Vitals scores. At Ottawa SEO, we see clients confuse the two when they hire a technical writer expecting someone who can fix their site speed or schema markup—those are completely different skill sets. The overlap happens when technical SEO practitioners write documentation about their work (migration guides, audit reports) or when technical writers need to implement structured data markup for their how-to articles. A strong technical content strategy needs both: someone ensuring the content is discoverable and renders properly (technical SEO), and someone making that content valuable and accurate (SEO technical writing). If you're hiring, clarify what you need. A technical writer with SEO skills won't diagnose why Google isn't indexing your category pages. A technical SEO won't write a 3,000-word guide explaining complex SaaS features. Agencies like ours maintain both capabilities separately because the expertise doesn't naturally overlap—one requires engineering and analytics skills, the other demands subject expertise and editorial judgment.