Astro, WordPress and AI Agents: Constantin Malanciuc on Choosing the Right Website Stack

The rise of AI coding agents has changed how websites are planned, built and maintained. Constantin Malanciuc has worked with conventional content management systems and page-builder workflows, but now increasingly chooses Astro for content-driven local business websites.

He is also clear that no framework is automatically the right answer. In this interview, he discusses the real shift behind agentic website building, where WordPress still wins and why human judgement has become more important as production gets faster.

What changed when AI agents became capable of working across an entire website?

Constantin Malanciuc: The biggest change is scale. A normal assistant might help write a paragraph or a piece of code. An agent can inspect a project, understand the structure, edit several files, run a build, see an error and try to correct it.

That changes the job from assembling every detail manually to directing a system. I can define a component once and apply it across dozens of pages. I can ask for an audit of titles, internal links or structured data across the whole website. But I still need to review the result because the agent can be confidently wrong.

Why are many home-service websites unnecessarily complicated?

Constantin: Because the default answer has been to install another tool. Need a form? Add a plugin. Need redirects? Add a plugin. Need structured data? Add a plugin. Need speed? Add a caching plugin to fix the weight created by the other plugins.

That can work, but the site slowly becomes a negotiation between different pieces of code. For a local service business that mainly needs information, proof and contact routes, the machinery can become heavier than the job.

Why do you increasingly choose Astro?

Constantin: It gives me a clean, code-first base. Most of the page can be delivered as static HTML, and interactivity can be added only where it is needed. That fits content-driven websites well.

I also like the control. The templates, components, metadata and content structure are visible in the project. Changes are tracked in Git. The site can be deployed globally without requiring a database to build the same service page for every visitor.

The result can be very fast and stable, but I am careful with the language. Astro does not prevent bad decisions. You can still build a slow Astro site. You can still create security problems through forms, third-party scripts or poor account management. It reduces certain kinds of complexity. It does not abolish reality.

Can a static website still be edited by a normal business owner?

Constantin: Yes, if the editing workflow is planned.

Decap CMS can provide a familiar interface while storing content in the Git repository. Sanity can provide a more structured content platform with its own editing environment and APIs. There are other options too.

The important question is not "Can I add a CMS?" It is "Who needs to edit what, how often and with what level of control?" Some clients only need a monthly article or a price update, and a developer-managed workflow may be perfectly reasonable. Others need several editors publishing every day. That changes the answer.

Does Astro automatically produce better SEO?

Constantin: No. It can give you a strong technical starting point, but SEO still depends on the architecture, content, internal links, crawlability, reputation and usefulness of the website.

I prefer to build SEO into the components. A service template should handle headings, metadata, structured data, internal links and conversion elements consistently. A location template should require real local information instead of allowing somebody to generate fifty empty city pages.

The system should make the right action easier, but somebody still has to provide the evidence and judgement.

When would you recommend WordPress instead?

Constantin: When its ecosystem solves more problems than it creates.

If a project needs mature ecommerce, memberships, an LMS, a complex editorial team or specific integrations that already work well in WordPress, I would seriously consider it. Many people know the dashboard, and clients can find support easily.

WordPress can also be built cleanly by developers who understand performance, security and architecture. My criticism is not that WordPress cannot work. It is that people often use a full CMS and a large plugin stack for a website that only needed a dozen well-built templates and a clear content workflow.

How do AI agents change project timescales?

Constantin: They can compress the production stage dramatically. Once the business data, content and design direction are available, an experienced person can get from architecture to a complete working build much faster than before.

But the launch process still includes testing. Forms need to deliver. Analytics must record the right events. Mobile layouts need checking. Redirects, privacy, accessibility, metadata and structured data need review. AI can help with all of those tasks, but the person responsible cannot simply assume the agent did them correctly.

What skills does someone need to manage this workflow?

Constantin: They need basic web development knowledge, an understanding of Git and deployment, and the ability to read what the agent changed. They do not need to memorise every line of code, but they cannot rely on guesswork.

They also need marketing judgement. A technically elegant website with the wrong offer, weak proof and a confusing call to action is still a bad website.

Can one consultant now do work that previously required a larger team?

Constantin: In some cases, yes. One experienced person can now research, plan, build, write, test and analyse at a level that once required several handoffs.

That does not make specialists irrelevant. A strong designer, developer, photographer, copywriter or analyst can still improve the result. AI reduces the cost of coordination and repetitive production. It does not turn one person into the world's best specialist at everything.

What are the main risks of relying too heavily on AI-generated code?

Constantin: Hidden complexity, invented solutions, inconsistent patterns, security mistakes and a false sense of confidence. If nobody understands the project, small changes can become dangerous.

I use version control, review changes, run builds, test the rendered pages and keep the architecture simple. The agent should work inside a clear system, not improvise the entire business on every prompt.

What will website development look like over the next few years?

Constantin: More websites will be built through conversation and agent workflows, but the strongest ones will still come from people who can define the right system.

Basic production will become cheaper. Strategy, evidence, original content, design judgement and measurement will become more valuable. The question will move from "Can you build a website?" to "Can you build the right website, prove that it works and keep it under control?"

That is a much better question.

About Constantin Malanciuc

Constantin Malanciuc is an SEO and Digital Marketing Consultant working across website strategy, local SEO, paid media, attribution, social content and original photography. He focuses on practical systems that help local and service-based businesses turn visibility into qualified enquiries and revenue. Connect with him on LinkedIn and follow@constantin_seo on X.