← Back to blog

Writing a Technical Blog in Markdown and Optimizing SEO: The Complete Workflow

Markdown blogtechnical blog SEOstatic site generatorAstro blogsitemap xmlJSON-LD structured data

Writing a Technical Blog in Markdown and Optimizing SEO

Writing a technical blog in Markdown is the most efficient approach, but to make search engines like it, you still need to complete the SEO “standard moves.” Here is a workflow you can put into practice.

1. Content as data: frontmatter-driven SEO

Declare the title, description, keywords, and date for each post with YAML frontmatter:

title: "Article title"
description: "A one-sentence summary that appears in search results"
keywords: ["keyword one", "keyword two"]
pubDate: 2026-07-25

These fields are automatically injected into <title>, <meta name="description">, and <meta name="keywords"> — no manual HTML editing required.

2. The three SEO foundations

FoundationPurpose
sitemap.xmlTells crawlers which pages exist
robots.txtGuides crawlers and points to the sitemap
JSON-LDDescribes the article with structured data (author, publish time, keywords)

3. Social sharing cards

Configure Open Graph and Twitter Card so articles get a nice preview image when shared on WeChat, X, Telegram, and more.

4. Speed is ranking

Static sites ship zero runtime JS by default and load instantly — a natural SEO advantage. Combined with a CDN/edge network (such as Cloudflare Pages) for global acceleration, Core Web Vitals are easily met.

5. Content managed with Git

Blog posts are just .md files in the repo:

  • Edit content = edit a file + open a PR
  • Publish = merge and auto-deploy
  • History = Git commit log

This “content as code” approach makes a technical blog both easy to write and easy to maintain.

This very blog is built with this approach — the source is on GitHub.