The SEO Checklist Every Dev Blog Needs in 2026
Most SEO guides are written for marketers. This one is for developers who want their blog to rank.
Technical SEO (Do This Once)
These are the foundations. Get them right and forget about them.
✅ Sitemap
Your sitemap tells Google what pages exist on your site. With Astro:
npm install @astrojs/sitemapAdd it to astro.config.mjs:
import sitemap from '@astrojs/sitemap';
export default defineConfig({
site: 'https://blog.yourdomain.com',
integrations: [sitemap()],
});Astro generates /sitemap-index.xml automatically at build time.
✅ RSS Feed
RSS feeds get you indexed faster and help aggregate sites like Feedly surface your content.
✅ Canonical URLs
Every page should have a <link rel="canonical" href="..." /> tag. This prevents duplicate content issues if you cross-post to Dev.to or Hashnode.
✅ Open Graph Tags
When someone shares your article on Twitter/LinkedIn, OG tags control the preview card. Missing OG tags = ugly, unclickable shares.
<meta property="og:title" content="Your Title" />
<meta property="og:description" content="Your description" />
<meta property="og:image" content="https://yourblog.com/og-image.png" />✅ Core Web Vitals
Google uses page experience as a ranking signal. Aim for:
- LCP (Largest Contentful Paint): < 2.5s
- CLS (Cumulative Layout Shift): < 0.1
- FID/INP: < 200ms
Astro ships with near-perfect scores by default.
Content SEO (Ongoing)
Target Long-Tail Keywords
“JavaScript tutorial” has millions of competing pages. “how to debounce input in JavaScript vanilla” has hundreds. Target the specific.
Use Ahrefs Keyword Explorer or the free Google Keyword Planner to find keywords with:
- Volume: 100–1000/mo (not too competitive)
- Difficulty: Under 30 (you can actually rank)
Write Complete Articles
Google rewards topical depth. If your article about “React hooks” only covers useState, you’ll lose to an article that covers all hooks with examples.
Aim for articles that answer every obvious follow-up question.
Update Old Posts
Updating old articles with new information and a fresh updatedDate in your frontmatter signals freshness to Google. A 20-minute update can double an old post’s traffic.
Distribution (The Multiplier)
Getting indexed is step one. Getting read is step two.
| Platform | Strategy |
|---|---|
| Dev.to | Cross-post with canonical link back to your site |
| Hacker News | Submit to Show HN for strong posts |
| r/webdev, r/programming, r/learnprogramming | |
| Twitter/X | Thread key takeaways, link to full post |
| Works well for career/architecture content |
The One-Month Plan
- Week 1: Set up Technical SEO, submit sitemap to Google & Bing
- Week 2: Publish first 3 posts (pre-write before launch)
- Week 3: Cross-post to Dev.to and Hashnode with canonical URLs
- Week 4: Share on Reddit and Hacker News, check Google Search Console for impressions
After 3 months of consistent publishing, you’ll start to see compounding organic traffic. Patience is the real SEO strategy.