← Insights

Aaron Charlton · November 17, 2026

Opening the Black Box of AI Website SEO

SEO transparency, consistency, and control for AI websites.

Pen-and-ink drawing of a robot inside a black box making websites on a conveyor belt, with a large pile of website pages at the end.

SEO transparency, consistency, and control for AI websites.

AI can now build a complete website from a conversation. But what happens when you ask a simple question about its SEO?

Which pages are excluded from the sitemap? Where are the canonical URLs defined? If you ask the AI to redesign the site, will it preserve your titles, redirects, and indexation decisions?

The agent may know the answers. Or it may have to search through the project to find them. It might have implemented SEO carefully the first time, or it might not have considered some of these details at all. And a later edit can quietly change things that were working.

That uncertainty is the problem I want to solve.

WordPress has a familiar way to manage SEO

For years, WordPress users have had a mature ecosystem of SEO plugins. Yoast, Rank Math, and other tools provide a recognizable place to manage titles, descriptions, indexation, sitemaps, schema, and redirects. The plugins differ in features and complexity, but the underlying idea is familiar: SEO settings should be visible and controllable.

WordPress doesn’t automatically give you good SEO. You still need good content, internal links, useful information, and reasons for other sites to cite or recommend yours. But the management layer is well established.

AI-generated static websites have a different problem. They can produce excellent, fast, crawlable HTML. Yet their SEO settings may be scattered among page files, templates, configuration files, and deployment settings. Sometimes two different parts of the system can contradict each other.

A capable coding agent can manage all of this. But unless we establish consistent rules, each new request or refactor can become another chance to change the behavior unintentionally.

SEO shouldn’t be a black box

I want three things from the sites I manage:

This isn’t content optimization. It doesn’t decide which keywords to target, write a better page, or build authority. Those are separate jobs, whether the site runs on WordPress or is assembled by AI.

And low-quality, mass-produced content isn’t an AI-static-site problem alone. You can publish spam on WordPress, too. This is about the technical controls underneath the content.

Introducing Bare Bones SEO for static sites

I’ve released Bare Bones SEO for static sites, a free, openly licensed collection of standards that you can give to an AI coding agent when building or maintaining a website.

It isn’t a plugin you install or another dashboard you log into. You copy a short prompt into the AI tool you’re already using. The agent reads the standards, adapts them to the site’s existing framework and hosting platform, and implements the controls in the site’s own build process.

The standards establish a single source of truth for intentional metadata and indexation settings, encourage schema to be generated from real page data, preserve existing redirects and URLs, and call for checks against the actual built output. They also instruct future agents to act as a conversational SEO dashboard: ask for a report on ten pages, see which URLs are noindexed, or review redirects without manually searching through code.

These checks are intended to be advisory, not roadblocks to building or publishing. And they aren’t a guarantee that an AI agent will never make a mistake. The point is to make the system understandable and give the SEO practitioner a dependable way to inspect and direct it.

You can copy the instructions and read the standards at BareBonesSEO.com. The project is free to use, including commercially, under an attribution-based license.

The same idea started on WordPress

This is the second branch of Bare Bones SEO. The first is my free, open-source WordPress plugin, built around the essential technical settings rather than keyword scores, upsells, or a sprawling marketing toolkit.

I’m also testing an upgrade to the WordPress plugin using the WordPress Abilities API, so compatible AI tools can discover and manage its SEO controls through conversation. Tools such as WPVibe already connect AI assistants to WordPress and can expose abilities registered by compatible plugins. That integration is in testing, not a feature I’m claiming is available in the current public Bare Bones release.

The implementation differs between WordPress and static sites, but the principle is identical: the software should expose its SEO settings and respect deliberate decisions. The person responsible for SEO should remain in control.

AI has made website creation dramatically easier. Managing the resulting website shouldn’t become harder to understand.

That’s what Bare Bones SEO is for.