If you write online and you aren’t using Markdown yet, you’re spending too much time formatting and not enough time writing. Markdown is a tiny set of plain-text conventions that turn into clean HTML—no mouse, no toolbar, no fighting with a WYSIWYG editor that randomly inserts <span> tags everywhere. Once you know fifteen characters, you can publish anywhere from GitHub to Ghost to Notion to your own static site without changing tools.
This post is two things: a cheat sheet you can bookmark, and a short guide to using Markdown well in a blogging context where SEO and reader experience actually matter.
The Core Syntax
Headings use #. One hash for H1, two for H2, six for H6. Always leave a space between the hashes and the text.
# Page title
## Section
### SubsectionBold is **text**, italics is *text*, and you can combine them with ***text***. Strikethrough uses ~~text~~. Inline code uses backticks: `code`.
Links are [anchor text](https://example.com). Images are the same with a leading exclamation point: . Always write meaningful alt text—it’s good for accessibility and good for image search.
Lists are even simpler. Hyphens or asterisks for bullets, numbers for ordered:
- First
- Second
- Nested
- Third
1. Step one
2. Step twoBlockquotes use >:
> This is a quote.And horizontal rules are three dashes on their own line: ---.
Code Blocks
Triple backticks open and close a fenced code block. Add a language name on the opening line for syntax highlighting:
```javascript
const greet = (name) => `Hello, ${name}`;
```Most static site generators and modern CMSs support this out of the box. If yours doesn’t, that’s a sign to upgrade.
Tables
Tables in Markdown look intimidating but they’re just pipes and dashes:
| Tool | Purpose | Free? |
|------|---------|-------|
| Markdown | Writing | Yes |
| HTML | Rendering | Yes |The colons in the dashed line control alignment: :--- left, :---: center, ---: right. You don’t need to make the columns line up perfectly in your source—Markdown only cares about the pipes.
Why Markdown Wins for Blogging
Three reasons.
First, it’s portable. A Markdown file is just text. It opens in any editor on any operating system, it diffs cleanly in Git, and if your CMS shuts down tomorrow, your content is still readable. Try saying that about a WordPress export.
Second, it’s fast. No mouse trips to a toolbar. No dropdown menus. You stay in flow because your hands stay on the keyboard. Writers who switch to Markdown almost universally report writing more, not less.
Third, it forces clean structure. Because formatting options are limited, you can’t lean on color and font tricks to fake hierarchy. You write headings because you need headings. That happens to be exactly what search engines want—a clear H1, descriptive H2s, scannable lists. Markdown gives you good SEO almost by accident.
Markdown Habits for Better Blog Posts
A few things I’ve learned the hard way.
Use one H1 per post, and make it match your title tag. Use H2s for major sections so readers can scan and so search engines can build sitelinks. Don’t skip levels—going from H2 straight to H4 confuses both screen readers and crawlers.
Keep paragraphs short. Markdown rewards short paragraphs because the line breaks are visible in the source. If a paragraph in your editor looks like a wall of text, it’ll feel like one to a reader on a phone.
Link out generously. Markdown link syntax is so easy that there’s no excuse not to cite sources, link to related posts, and reference tools. Internal links are huge for SEO and Markdown makes them effortless.
Always write alt text for images.  is a missed opportunity every single time.
Migrating Existing Content
If you’ve got a backlog of posts in HTML—maybe exported from an old blog, or copied out of Google Docs—you don’t have to rewrite them by hand. Converting HTML to Markdown is mostly mechanical, and a good converter will preserve your headings, links, lists, and code blocks while stripping out the junk inline styles.
After converting, skim the output once. Converters generally do a great job with structure but occasionally trip over nested tables or weird inline styles. A two-minute review per post catches almost everything.
Common Gotchas
A few things that bite people new to Markdown.
Blank lines matter. Two paragraphs need a blank line between them. A list item without a blank line before it might get pulled into the previous paragraph.
Underscores in URLs and filenames can sometimes get interpreted as italics. If you see weird formatting, escape them with a backslash: file\_name.md.
Markdown doesn’t have a centered-text syntax, or font colors, or custom fonts. That’s a feature, not a bug. If you find yourself wanting those, ask whether you really need them—or whether your CSS should handle it instead.
Wrapping Up
Markdown is one of those rare technical investments where the payoff is immediate and lasts forever. An hour of practice and you’ll never want to go back to a rich-text editor. A week and you’ll start composing entire blog posts in your terminal because it’s actually faster.
Bookmark this page, keep a converter open in a tab, and let Markdown handle the formatting so you can focus on the writing.