Technical Writing and SEO Growth on a Portfolio

Strong technical writing does two things at once:

1. It documents decisions in a way your future self can audit.
2. It improves discoverability when done with the right structure.

When I started adding technical writeups to this portfolio, I set three goals:

• Keep the authoring experience inside the repository.
• Keep metadata explicit for search engines.
• Keep each post technically useful, not marketing-focused.

Why this works

Search engines care about context signals. On a portfolio, that usually means:

• Page-level metadata (title, description, canonical URL).
• Publication date and stable URL structure.
• Internal links between related ideas.
• Content that resolves practical questions around implementation choices.

MDX is useful here because it lets you document architecture and code examples in the same place as your products.

Practical framing

For each post, I start from one prompt:

• What decision did I make?
• Why did I make it?
• What changed because of it?

That rhythm gives each writeup a reusable pattern for both readers and my own search engine indexing.

If you are building a public engineering presence, your content should help you get found and help future teammates move faster.