Why build a website for search and AI visibility
A website that nobody finds earns nothing. This page makes the case, for the person who decides, that search and AI visibility belong in the build and under test, not on a list of settings to get to later.
The evidence so far
One site, measured: genai-wednesday.de, launched on .
- Speed and search basics. PageSpeed Insights on a simulated phone, 4 October 2026: 99, 100, 100 and 100 out of 100 for performance, accessibility, best practices and SEO.
- Clicks from Google. From 3 in the 28 days that include the launch (18 March 2026 to 14 April 2026) to a best 28 days of 99 (16 June 2026 to 13 July 2026), and 50 in the latest 28 days (2 September 2026 to 29 September 2026).
- AI assistants. On 8 October 2026, 16 of 18 answers given with web search named the site, and 0 of 24 given from memory. Google AI Mode and Google AI Overview were not run that day. The proof page says why the second number is zero.
It is one site, and it belongs to the maintainer of Croftweaver. Clicks have fallen from their best, and the cause is not established. The proof page has the sources, the daily numbers and what the figures do not show.
The recommendation, in three reasons
Choose a tool that is built for being found, not one that merely permits it.
Built in from the first build
Search basics, trust signals and readability for AI assistants are part of every page by default. Tests check what a machine can check, such as metadata, internal links and structure, before each push and on each pull request.
Improved after launch
Real search data replaces guesswork about keywords. When there is enough of it, it helps pick two or three edits a week to look into.
Owned, with no platform fee
A static site in your repository, on your domain. Croftweaver is MIT-licensed and charges nothing.
The difference is what the tool is for
A tool can hand you every control and still leave the work to you: knowing what to do, doing it on every page, keeping it done. When a check depends on someone remembering it, a new page can miss it.
A tool built for being found does that work by default and tests what can be tested. The result is meant to hold on the hundredth page, two years later.
None of this is a case against design. Being found helps people arrive; design helps them stay. Both matter. If you use a website builder and like it, keep it, and ask what the site earns you in search.
What is built in
Search basics
Titles and descriptions within set limits, structured data that says what each page is, a sitemap, internal links that resolve.
Trust signals
Croftweaver builds the structure that carries your experience, expertise, authority and trust: named authors, profile links, legal pages, sources. It cannot earn the reputation for you.
AI answers
Pages are structured so that an AI assistant can read and quote them, and every site ships a file that maps it for assistants.
Shared links
Every content page gets its own share card at the size messengers accept, and a content page without one fails a test. The home page and the legal pages share a default card.
The test gate, suite by suite says what is checked and what a pass does not prove.
What happens after launch
Google Search Console collects data only from the day a site is verified, so that is done at launch. From then on the skills read the data and point at edits:
- Searches with an average position around 8 to 20. Candidates to look at first.
- Pages seen but rarely clicked. The skill checks the real results page before it suggests a new title or description.
- Whether AI assistants name you. An optional weekly check, run with your own API keys.
Runs of the tracker are recorded, so you can see what moved. On a Mac, an optional weekly schedule runs it for you. Every edit goes back through the same tests.
What you own
- Plain files. The site is built once and served as static pages. There is no database to wait for or to keep alive.
- No content system to run. Content is text files in your repository; the default setup has no login and no plugins. If someone needs an editing screen, an optional editor adds one. It runs on your own computer by default, and the content stays in the repository.
- Room for a second language. It can be added later without moving the addresses you already have.
- No fee to Croftweaver. The licence is MIT. Your domain, your hosting and your AI assistant can still cost money.
How it goes: four steps, and you decide at each
1. Brief
A few questions about your audience, your offer and your tone.
2. Build
Positioning first, then content, pages and metadata.
3. Check
12 test suites: accessibility, search, tone, links, images.
4. Launch
Live on your own domain, as static pages.
How long it takes depends on how much content you have and how fast the decisions are made. There is no honest number to print here.
Where it fits
Croftweaver suits content sites: event and community sites, landing pages for a startup, expert and personal profiles, resource hubs, the site of a small studio or agency. For a shop, a booking platform or a web application, another kind of tool serves you better, and so does a managed builder if you want no code at all. Croftweaver and its alternatives says which. If you already run a large site, the parts that work on established sites are listed in the order to use them.
Start this week
- Install an AI coding assistant and build one site from the starter prompt.
- Verify the site in Search Console on the first day. It collects no history before that.
- Read the first weekly report together, then decide whether to continue.