src config blog.config.ts
1 /**
2

Build. Publish. Scale.

3 *
4

The modern blog template built for speed, SEO, and developers who ship.

5 */
6
7 export default {
8 framework: 'Astro 5',
9 content: 'MDX + Markdown',
10 styling: 'Tailwind CSS',
11 types: 'TypeScript strict',
12 features: [ 'SEO', 'i18n', 'search', 'RSS', 'dark mode'],
13 config: 'site-config.json',
14 };
Get Pro Free on GitHub

Open source · MIT License · Kevin Gabeci

Outline

Everything you need. Nothing you don't.

Built-in features that just work, and the dependency list that backs them.

features.ts 11 exports
1 export const features = {
2

seo

: 'sitemap, meta tags, Open Graph, Twitter cards, structured data',
3

darkMode

: 'system preference detection, persisted, smooth transitions',
4

cms

: 'built-in editor for posts, authors and content, no database',
5

fileBased

: 'everything lives in your repo, no external services',
6

search

: 'client-side full-text search with keyboard navigation',
7

mdx

: 'Markdown with components and syntax highlighting',
8

performance

: 'static-first output, optimized images, code splitting',
9

i18n

: 'multi-language routing and translations, RTL capable',
10

feeds

: 'RSS, XML sitemap and feed discovery, generated',
11

typescript

: 'strict mode throughout, typed props, IDE autocomplete',
12

zeroConfig

: 'works out of the box, nothing to wire up first',
13 };
package.json 19 dependencies
"dependencies": {
"@astrojs/markdoc": "^0.15.5",
"@astrojs/mdx": "^4.3.4",
"@astrojs/node": "^9.4.3",
"@astrojs/react": "^4.3.0",
"@astrojs/rss": "^4.0.12",
"@astrojs/sitemap": "^3.5.1",
"@astrojs/tailwind": "^6.0.2",
"@tailwindcss/typography": "^0.5.16",
"astro": "^5.13.5",
"astro-seo": "^0.8.4",
"clsx": "^2.1.1",
"direction": "^2.0.1",
"gray-matter": "^4.0.3",
"lodash": "^4.17.21",
"lodash.debounce": "^4.0.8",
"marked": "^16.2.1",
"satori": "^0.28.0",
"sharp": "^0.34.3",
"tailwind-merge": "^3.3.1",
}

Free to start. Pro when you mean it.

Ship free. Grow on Pro.

The engine is open source and yours forever. Upgrade to the Pro edition when you want the automation that grows your traffic and your revenue on autopilot.

Free

Open source, MIT licensed.

  • Full blog with a built-in CMS
  • 12+ languages, dark mode, search
  • SEO meta and structured data
  • The stock look plus one free template
Start free on GitHub
Pro

Pro Blog

$69.99 one-off, lifetime.

  • Instant IndexNow submission on publish
  • Auto internal linking and smarter related posts
  • Ad, sponsored and affiliate slots
  • Dynamic branded OG social cards
  • Redirect manager for clean migrations
Get the Pro Blog

Premium templates

Reskin the whole blog with a look pack. Drop in a folder, change one line. $19.99 each.

Browse templates
Terminal

Clone. Build. Ship.

Six commands to launch.

Terminal npm
01

Clone and install

git clone https://github.com/kevingabeci/astro-seo-blog-template.git
npm install
02

Customize

edit public/data/settings/site-config.json
npm run dev
03

Ship

npm run build
npm run start
Get Started

Free and open source · MIT License

Folded

FAQ

Common questions answered.

faq.md 6 regions
Is this template really free?

Yes. It is completely free and open source under the MIT License. Use it for personal projects, commercial work, or modify it however you see fit.

Do I need to know Astro?

Basic knowledge helps, but you can start immediately by editing the configuration file and writing posts in Markdown or MDX. The documentation walks through the rest.

Can I customize the design?

Yes. The template uses Tailwind CSS wired to CSS custom properties, so colours, fonts, spacing and layout are all yours. Installed templates re-skin the whole blog by redefining those tokens.

Where can I deploy this?

Anywhere that runs Node.js. Vercel, Netlify, Railway, DigitalOcean or any VPS. The documentation includes deployment examples.

Does it support multiple languages?

Yes. The template is i18n ready with automatic routing, translated content directories and RTL capability. Add a language and the interface adapts.

How do I get support?

Check the documentation on GitHub, open an issue if you find a bug, or start a discussion for questions.