Weave websites that rank.

Four AI assistants scored a site built with Croftweaver

The Builder Lab at GenAI Wednesday gave four AI assistants the same prompt about genai-wednesday.de on 20 August 2026. SEO is how well Google can find and read a site. GEO, short for generative engine optimization, is how well AI assistants such as ChatGPT, Perplexity or Gemini can read and quote it. GEO has no official scorer, and the SEO scores here are the assistants' own opinions too, not a Google metric. They are not rankings, they vary from run to run, and they do not show that an assistant would recommend the site. The site belongs to the maintainer of Croftweaver.

Scores out of 10, as the Builder Lab shows them (read on 8 October 2026). Gemini (Antigravity) answers out of 100 and the Lab shows it out of 10. The Lab warns that scores are not comparable between assistants, so read the average as a rough guide. GEO ranges from 6.5 to 9.2.

Try it on your own site

Paste this into your own AI assistant and replace the part in brackets with your site's address. Your scores will differ from these: they are opinions. The Lab's own prompt is on More proof.

Score genai-wednesday.de for SEO and GEO, with one sentence of reason for each score. Then do the same for [your site's address].

Measured, not scored. On 4 October 2026, Google's PageSpeed Insights gave three sites built with Croftweaver, all of them the maintainer's own, scores of 99 to 100 out of 100 across its four categories. More proof has the figures, and how the same four assistants score trust. On 8 October 2026, 16 of 18 answers from AI assistants with web search named genai-wednesday.de; without web search, 0 of 24 did. One site in depth has the counts and the site's clicks from Google. The case study follows croftweaver.com itself, change by change.

From someone who built her own site

“The first version of my website is live. Without the [Croftweaver] Builder it wouldn’t have been possible — especially not with all the small but important details that, as a non-professional, you don’t think about at all. Many thanks for this great project.”

Every change waits on someone else

Many sites start from an old page nobody dares to touch, or from nothing at all. Every update means asking someone else: a brief, a wait, often a bill. So changes pile up, and the site falls behind.

The work that gets a site found is the first to go. A description goes missing, a link breaks, a share card shows the wrong picture, and nothing tells you.

So when someone hears your name and looks you up, the site makes a weaker case than you would yourself. And the people who do not know you yet have a harder time finding you.

Croftweaver takes the other route. Your assistant starts with your positioning, what you offer and for whom, and from then on a test keeps your pages on it: Positioning first. It can also tell the home page as your visitor's story. Then you and your assistant make the changes, the search and AI work is done by default, and the tests check it by default. Why build for search and AI visibility makes the full case, for the person who decides.

Three steps to a site people can find

1. DescribeSay new website to your assistant and answer its questions. It works out what the site says before it writes a word.
2. Build and checkYour assistant builds the pages with the search and AI work done by default, and 14 test suites check every change by default.
3. Publish and keep improvingPublish on hosting you control, such as Cloudflare's free plan. Once you connect Google Search Console, your own data points to the next edit, week by week.

Rebuilding an old site? Tell your assistant what the old site says. There is no automatic import yet; the roadmap says what is missing.

What changes for you

A change, start to finish. You tell your assistant: make the opening line of the About page shorter. It edits the page, the test suites check the change, and you publish it yourself. There is no brief to write and no one to wait for.

What Croftweaver is, and what people ask

Croftweaver is a free, open-source suite of website skills for search and AI visibility, made for AI coding assistants. It turns an assistant such as Claude Code into a careful website builder: fast, accessible Astro sites, built to rank on Google and show up in AI answers, in a repository you own.

The search and AI work is the part that gets skipped when a site has to go live fast. Croftweaver does that work by default, and by default the tests check it. The proof is above. More proof and one site in depth are measured and dated.

Do I need to code?

Not to start. You work with your assistant in plain language, and the starter prompt asks it to explain every command and to install a tool only when the site needs it.

Will it rank my site?

Ranking is the aim, but Croftweaver is a tool, so the result depends on how you use it. What it gives you is a steady habit: say what you offer, keep every page true to it, check each week, and fix what the check shows. That gives each page a fair chance. How far it rises still depends on your content, how unique it is, and your competition.

Can it improve a website I already have?

Yes, without rebuilding it. The checks and measurements work on a live site on any stack: Search Console insights, the weekly AI check, the SEO audit, the positioning check and the facts check. The ready-made test suite and the two link audits need the Croftweaver starter, the facts check does not run a page's JavaScript, and there is no automatic import of an existing site yet. Croftweaver for established sites.

What does it cost?

Croftweaver itself is free and MIT-licensed, a GitHub account and a Cloudflare account are free to open, and Cloudflare's free plan hosts the site. You still pay for your domain. Your AI assistant can cost money, and so can the optional weekly AI check.

Is it safe to install?

The skills are plain text instructions and small scripts in a public repository, so you or your assistant can read every one before you install it. You can check that a download arrived intact, and the one-line installer does that check for you. In its default settings, Claude Code asks before it runs a command. The site it builds is static files, with no database and no user accounts.

Can my site have a contact form?

Yes, and ours works differently on purpose. The visitor fills in a few fields, and their own email program opens with the message written, ready to send. It comes from their own address, so it reads like a personal note, and you answer with Reply. Their email program keeps a copy in their Sent folder, as it does for any email, so they can see that it left. There is no form service to pay for or look after, nothing for a spam bot to fire off, and no message stored on a server. A visitor without an email program copies the address shown under the form.

Built in from the first build, checked on every change

You do not switch any of this on. The skills build it into every page:

• Titles and descriptions kept within set length limits.
• Structured data (schema.org JSON-LD) on every page, so a search engine can tell what the page is.
• An llms.txt file that maps your site for AI assistants. It does not guarantee that an assistant reads it.
• A sitemap, clean addresses and internal links that all resolve.
• A share card for every page, sized so messengers show a proper preview.
• Accessible markup and colours, in light and dark.

Every Croftweaver site also carries its own tests: 14 test suites. By default they run before every push, and again on GitHub for every pull request. A change that breaks a rule fails there, so by default it does not reach your visitors.

A green run proves that the tests passed, nothing more. The positioning test, for example, proves that this page carries its key term in its title, description and opening, not that the positioning is good. The test gate, suite by suite, says what each suite checks and what a pass does not prove. How the positioning itself is worked out, before any copy: Positioning first.

After launch, the next edit, tested

Knowing where you stand is the easy part: Search Console shows how you do on Google, and plenty of tools check whether AI assistants name you. What moves a site is the next change to it. Once you connect Google Search Console and it has data on your site, the skills read it and point at the two or three edits most worth making this week:

• Searches where you sit just below the first page of results.
• Pages that people see in the results but rarely click.
• An optional weekly check, run with your own API keys, that asks AI assistants the questions your customers ask and counts how often they name you.

Your assistant makes the edit with you, and the same tests run on it, by default before every push and on every pull request. The skills cover the whole life of a site:

1. BuildBrief, positioning, content, design.
2. VerifyThe test suites, then a two-pass review.
3. LaunchPublish, and register with Search Console.
4. GrowRead the data, make the edits, weekly.

From Grow, every edit returns to Verify.

The site is yours

Your code sits in your repository, your domain is in your name, and your pages are static files that any host can serve. Croftweaver is MIT-licensed. It has no account and no subscription, and nothing runs on our servers.

Install guides cover Claude Code, Codex and Antigravity. Croftweaver is developed and used with Claude Code; Codex and Antigravity have each been tested with it from start to finish on one site.

A croft is a small farm in the Scottish Highlands, worked by the family that lives on it: a modest piece of ground that feeds the people who tend it. Croftweaver offers the same deal for the web, on ground you own. The weaver is your AI assistant. The plot stays yours.

A good first AI project, alone or with your team

AI stops being abstract when it works on your own site. You know what it should say, you see each change take shape, and you decide what stays. In my experience it is a real learning curve, and a happy one. Questions along the way? I am glad to help. Write to hello [at] croftweaver [dot] com.

Daniel Melter, maintainer of Croftweaver

Who maintains Croftweaver

Croftweaver has one maintainer, Daniel Melter. He co-founded M-Squad in 2001 and leads it today, and he has worked in product development for mobile and telecom for more than 20 years. M-Squad GmbH, in Munich, operates this site. He co-built the community GenAI Wednesday and still co-organizes it in Munich, and Croftweaver grew out of its website, genai-wednesday.de.

His profile is on M-Squad's team page. The code is on GitHub under the MIT licence, and the imprint has the company's address. A note from him is on the About page.

Where Croftweaver fits, and where it does not

A contact form or one live widget is fine: the output supports a single serverless function when a site truly needs one.

Croftweaver and its alternatives says when another kind of tool is the better choice, and the roadmap says what is still missing.

You pay nothing for hosting

Build your site with your AI assistant, then run it on two free accounts.

• Your site's files live in your own GitHub account. About GitHub.
• Cloudflare hosts the site on its free plan. Cloudflare says it proxies about 20% of the web. What Cloudflare is.
• You still pay for your domain, and for your AI assistant if you use a paid plan.

Rebuilding a site you already have? Before you cancel the old hosting plan, check what else runs on it: your domain and your email. Three checks before you cancel.

Cloudflare's free plan has limits, and its own page lists them. GitHub's free plan is on GitHub's plans. Both pages and Cloudflare's 20% figure were read on 12 October 2026.

Quickstart

The easy way is one prompt. The starter prompt asks your assistant to do the typing, explain every command and install a tool only when the site needs it.

1. Install an AI coding assistant, such as Claude Code, and open it. You also need a free GitHub account and a computer (what you need).
2. Paste the starter prompt and send it.
3. Answer its questions. It builds the site from your answers.

Or install by hand

1. Clone the repository and run the installer. This one is for Claude Code:

git clone https://github.com/karero/croftweaver.git
cd croftweaver && ./scripts/install.sh

2. Restart your assistant, then open it in a new, empty folder.
3. Say: new website. The interview and the pipeline take it from there.

The full quickstart has the starter prompt in full, the plugins for Claude Code and Codex, the one-line installer, the installers for Codex and Antigravity, and the six questions the assistant asks.