Blog topic
Behind the Build
Case studies of real sites built with PolyDraft, including this one.
This topic is the open notebook: real builds documented in full, including the decisions, the constraints and the things that had to be corrected — starting with the site you are reading.
What this topic covers
Marketing pages describe what a product does. This topic shows the work: what was actually researched, which pages were planned and why, what the automated quality gate flagged, and which decisions were reversed. The point is that a claim you can inspect is worth more than one you have to accept.
Why the log is public
This website was built with PolyDraft, which makes it the one case study nobody has to take on trust — every page, every piece of structured data, every internal link and the llms.txt file are on the same domain you are reading, and can be viewed, validated and criticised directly. Writing the build up honestly means including the parts that needed a second pass, not only the parts that worked first time.
What a build log contains
- The brief and the verified facts — what the agent was given, and what it was forbidden to invent.
- Research and planning — the competitors studied, the keyword decisions, and the one money keyword assigned to each page.
- What shipped — the page set, the SEO and GEO layer applied, and the structured data emitted.
- What was corrected — quality-gate findings and the fixes, which is usually the most useful part for anyone doing the same work.
Related reading
Documented customer sites live on the showcase, each with the brief, what was researched and what shipped. The how it works page describes the same sequence in the abstract, and about covers the honest-content principles these write-ups are held to.
Frequently asked questions
- Was this website really built with PolyDraft?
- Yes, and it is deliberately verifiable rather than asserted. The pages, structured data, internal-link dictionary, sitemap and llms.txt file are all on this domain and can be inspected or validated with any third-party tool, and the full build is written up in the log in this topic.
- Do these write-ups include the mistakes?
- Yes. A build log that only records what worked is marketing, not documentation. The write-ups include what the automated quality gate flagged and what had to be corrected afterwards, because that is the part that is actually useful to someone doing the same work.
- How is a build log different from a case study?
- A case study summarises an outcome; a build log records the sequence and the reasoning, including decisions that were later reversed. Customer case studies live on the showcase page and cover the brief, the research and what shipped, without invented metrics or client quotes.
AI builds it. You own it.
Building a complete, researched website costs nothing — you pay only to publish.