Croftweaver case study: its own website, week by week

This case study follows croftweaver.com, built with Croftweaver, from its launch on . It is a log, not a finished story: each change says what was asked, links the pull request, names the checks that ran, and is followed by the next measurement. The zeros stay in.

Last updated . A movement after a change is something we saw, not proof that the change caused it. For a site that is months old, see one site, measured.

Do AI assistants name it?

Croftweaver's weekly AI check asks AI assistants two questions that do not name Croftweaver, with web search and without. On , with web search, 0 of 22 answers from 5 assistants named it, and croftweaver.com was among the sources returned in 0 of 22. Without web search, 0 of 24 named it.

Day With search: named croftweaver.com among the sources Without search: named
0 of 22 0 of 22 0 of 24
0 of 22 0 of 22 0 of 24

“Among the sources” counts answers whose returned sources include croftweaver.com; for some assistants the check cannot tell whether the answer's text uses them, so this page does not call it a citation. No question, setting or route changed between these days, and no assistant reported a different model. Counts only: the answers themselves are not published.

The log

A change is dated by the day its pull request was merged. It goes live when the site is next published, which can be a few days later.

  1. · Change

    Saying plainly that it works on a site you already have

    Asked: Answer “Can it improve a website I already have?” on the home page, and say the same on genai-wednesday.de, the page Gemini was citing.

    Pull request: karero/croftweaver-site#107. Checks: 312 and 298 tests; review by two outside models, 1 round.

    Next measurement: the next weekly check.

  2. · Change

    The same, on genai-wednesday.de

    Asked: Add “Already have a website?” to the Croftweaver page on genai-wednesday.de, in English and German.

    Pull request: GenAI-Wednesday/GenAI-Wednesday.de#53. Checks: 298 tests; reviewed together with the change above.

    Next measurement: the next weekly check.

  3. · Observation

    14 of 15 pages indexed by Google

    Google has indexed 14 of the 15 pages it knows about.

    Source: Google Search Console, page indexing report, read on 20 October.

  4. · Observation

    Asking the assistants again

    Four more questions that do not name Croftweaver, asked in the ChatGPT app and through Perplexity’s API, and six in the Gemini app: 0 of 14 answers named it. Asked by name, Gemini said Croftweaver cannot improve an existing website; it was citing genai-wednesday.de, which never said that it can.

    Source: a one-off run, signed in, a different method from the weekly check below.

  5. · Change

    The roadmap says when it was last read through

    Asked: Show the date and release the roadmap was last checked against, and add a contents line to the page for established sites.

    Pull request: karero/croftweaver-site#102. Checks: 312 tests; review by two outside models, 2 rounds.

    Next measurement: the next weekly check.

  6. · Change

    The ranking answer on the home page

    Asked: Keep the headline “Weave websites that rank.” and answer “Will it rank my site?” without a promise; say on the About page how AI is used.

    Pull request: karero/croftweaver-site#105. Checks: 312 tests; review by two outside models, 1 round.

    Next measurement: the next weekly check.

  7. · Observation

    Bing indexing requested

    Indexing of the home page was requested in Bing Webmaster Tools. The outcome is pending.

    Source: Bing Webmaster Tools.

  8. · Change

    README: the first paragraph matches the home page

    Asked: Open the README with the home page’s definition, and say exactly which assistants were tested from start to finish.

    Pull request: karero/croftweaver#355. The checks are in the pull request.

    Next measurement: .

  9. · Observation

    Bing could not crawl the home page

    Bing Webmaster Tools listed the home page as discovered but not crawled: its fetch failed. Cloudflare’s security log for the week shows no request from Bing that was blocked.

    Source: Bing Webmaster Tools, URL inspection; Cloudflare security events, last 7 days, read on 20 October.

  10. · Change

    README: who maintains it, and what works on a live site

    Asked: Say who maintains Croftweaver and which parts work on a site that is already live, near the top of the README.

    Pull request: karero/croftweaver#284. The checks are in the pull request.

    Next measurement: .

  11. · Change

    An About page with a note from the maintainer

    Asked: Add a page that says who is behind Croftweaver and how to reach the maintainer.

    Pull request: karero/croftweaver-site#75. The checks are in the pull request.

    Next measurement: .

  12. · Observation

    A first AI check, run by an outside reviewer

    An outside review asked ChatGPT and Perplexity (with web search) and Gemini (without) six questions that do not name Croftweaver: 0 of 18 answers named it.

    Source: a one-off run through the assistants’ APIs, a different method from the weekly check below.

  13. · Observation

    The site goes live

    croftweaver.com is live on Cloudflare Pages, built with Croftweaver from its starter. The first Google impressions arrive the same day.

    Source: the site launch; Google Search Console, daily figures above.