Rebuilding My Website with Astro: Structure, SEO, and an AI-Friendly Workflow

Last week, I rebuilt my personal website with Astro. The goal was not just to give the site a fresh look. I wanted a setup that was easier to maintain, faster to load, more deliberate about SEO, and much easier to work on with AI.

This rebuild gave me a chance to rethink both the structure of the site and the way content is published. I wanted a setup where content, performance, SEO, and maintenance all worked together.

Why I moved to Astro

My website is relatively simple on the surface: a homepage, a projects section, and a blog. But even simple sites benefit from a clean architecture. I wanted a stack that would let me keep the site mostly content-driven without shipping unnecessary JavaScript.

One of the biggest reasons I chose Astro was how well it fits the way I want to build and maintain things now. I used AI to help build the site, and I want to keep maintaining it with AI as well. That means I can ask an agent to add a new section, update content, adjust a component, or refine a layout, and it can work directly inside a clean codebase, create a PR, and let me review the change before it goes live.

I prefer that workflow much more than managing a traditional CMS. Instead of logging into a dashboard, clicking through settings, or making scattered manual changes, I can treat the website like a proper project: structured files, version control, reviewable changes, and automatic deployment.

Astro was a good fit for a few reasons:

• Static by default. Pages are pre-rendered, which keeps the site fast and reduces moving parts.
• Content-first workflow. Blog posts live as Markdown files, so writing and publishing feels straightforward.
• Flexible structure. I can keep reusable components, content collections, and SEO logic organized without overengineering the project.
• AI-friendly maintenance. The project is easy for both me and an AI agent to understand, update, and improve safely.

For a personal site, that balance matters. I do not need a heavy runtime for every page. I need a site that is pleasant to maintain and quick for visitors to use.

How I structured the site

I kept the project organized around a few clear responsibilities.

The main layout and UI building blocks live in reusable components and layouts. That keeps design decisions centralized instead of scattered across pages. Content that changes often, like site metadata, project listings, and blog posts, lives in dedicated data or content files.

For the blog specifically, Astro’s content collections helped keep things tidy. Each post sits inside src/content/blog/ with validated frontmatter for title, description, publish date, tags, and draft state. That gives me a predictable publishing flow and reduces mistakes.

The biggest benefit is that the structure is easy to understand. Writing a new post is mostly creating one Markdown file. Adding a new section does not mean rewriting the whole site. And because things are organized clearly, it is also easier to ask an AI agent to make updates without breaking unrelated parts.

That matters to me a lot. I want to be able to describe a change, review the PR, merge it, and see it go live without turning every small update into manual work.

What I improved for SEO

A rebuild is a good time to fix SEO properly instead of treating it as a final checklist item. I focused on a few areas that make a real difference.

1. Better metadata structure

Each page and blog post now has clearer title and description handling. For blog posts, the metadata is specific to the article instead of relying on generic site-wide defaults. That helps search engines and link previews understand the content more accurately.

2. Cleaner content organization

When blog content is structured consistently, it becomes easier to generate supporting SEO outputs such as RSS feeds, sitemaps, and alternate machine-friendly formats. Astro makes this easier because content and routing are predictable.

3. Performance as an SEO advantage

Fast pages are not just nicer for users. They also support discoverability. Because Astro ships very little client-side JavaScript by default, the site has a better starting point for performance than many JavaScript-heavy setups.

4. Sharable pages and blog posts

I also made the blog friendlier for social previews and external sharing. Good Open Graph data, clear descriptions, and dedicated blog URLs make posts easier to distribute across LinkedIn, X, or developer communities.

What I like most about this setup

The biggest improvement is clarity and speed.

I know where content lives. I know how a new post gets added. I know how the site is built and deployed. I can ask an AI agent to make a content change or a design tweak, review the PR, merge it, and let Vercel deploy it automatically. That kind of simplicity matters more to me over time than choosing the trendiest stack.

Astro gives me a setup that feels modern without being noisy. It keeps the site lean, but still gives me enough structure to grow the blog, improve SEO, and ship updates confidently. More importantly, it matches how I actually want to work in the AI era.

Final thoughts

Rebuilding a personal website is rarely just about design. It is usually a chance to improve the system behind the design.

For me, moving to Astro was about creating a site that is easier to write for, easier to maintain, better prepared for search and sharing, and much easier to evolve with AI-assisted workflows. I like being able to describe a change, review the PR, merge it, and see it go live automatically. In many cases, that feels better than maintaining a CMS or manually editing everything myself.

That makes the site a better home for the kind of things I want to publish: development lessons, AI work, experiments, and practical engineering write-ups.

If you are planning a personal site rebuild, I think Astro is worth a serious look, especially if you want strong performance, a clean content workflow, SEO foundations that do not feel like an afterthought, and a setup that works well with modern AI-based development habits.