We built this site with agents. We check their work.
Copy, code, screenshots and browser checks. This is how we get website changes ready to review without asking the owner to coordinate every step.
A real page revision, start to finish
When Jim reviewed the first case-study draft, he wanted a page a business owner could scan and act on. The draft was too dry, the proof was buried and there was no clear next step.
- Use the feedback. The agent rewrote the opening around the result, shortened the story and added contact buttons.
- Prepare the real evidence. A supplied Shopify screenshot became the visual proof. Monetary values were removed from the image itself, including the chart's dollar scale.
- Build and check. The revised page was built, checked in desktop and mobile browsers, and tested through to the contact form. No enquiry was sent during that check.
- Put the preview in front of the owner. Jim reviewed the actual page. The production domain was not switched, and the client-approval gate stayed in place.
That is the kind of complete job we want agents to help deliver. The writing is one part. Preparing the image, changing the layout and checking the buttons matter just as much.
What this means for your website
- You review a page, not a technical specification. See the proposed change before deciding whether it should go live.
- Useful context stays with the work. Your audience, offers, approved claims and corrections guide the next revision.
- The team checks the release. We look at real routes, images, mobile layout and enquiry paths, not just whether the code builds.
For your technical team
Astro builds static HTML served by Cloudflare Workers. Reading an ordinary page does not call a language model. The contact form has its own validated endpoint and durable storage.
Content rules prevent unapproved case studies from entering the production build. Separate review builds can expose selected drafts with noindex and an approval warning. Previous Cloudflare deployments remain available for rollback.
Client identity, claims, access and publication still need the appropriate human approval. Open-source tools and portable content help us change the underlying technology without discarding the work.
Build your own version
A content-led business site can be small, fast and inexpensive to host. Astro generates HTML ahead of time; Cloudflare serves the files. This is not a substitute for Shopify checkout, a booking system or an application that needs a database on every page.
1. Start with a repository and a working page
Install a supported Node.js release, then run npm create astro@latest. Choose a minimal project, install its dependencies and run npm run dev. Put pages in src/pages/, shared layouts in src/layouts/ and public assets in public/. Keep the code and lockfile in your own Git repository. Keep credentials out of it.
Set Astro's site to your intended canonical domain and decide your trailing-slash convention. Start with static output. Use Astro's installation guide for current prerequisites rather than copying an old runtime version.
2. Give content a clear review path
Store articles as Markdown with titles, descriptions, dates and source records. Use content schemas to reject missing required fields. Keep draft status and client approval separate. An agent can prepare a change on a branch, but an owner should review the preview, claims and affected links before merging.
3. Build and deploy an isolated preview
Run npm run build and inspect the generated dist/ directory. Configure Cloudflare Workers Static Assets to serve that directory, then deploy to an isolated workers.dev preview before attaching a production domain. Follow the Static Assets guide for the configuration and routing rules.
Block preview indexing, keep preview and production build settings explicit, and test both. Use access controls if the preview contains confidential material: noindex is not a password.
4. Connect forms and measurement deliberately
Static HTML cannot safely hold an email API secret. Send enquiries to a server-side endpoint with validation, spam protection, durable storage and delivery monitoring. Test the record and notification, not just the thank-you page. Keep newsletter consent separate from sales enquiries. This site uses Buttondown for newsletter subscriptions and its own enquiry endpoint for business enquiries.
Choose analytics and consent settings before launch. Verify page views, a controlled enquiry and the intended conversion event. Keep source-page attribution separate from campaign UTMs; decide which campaign fields you need and how long you retain them.
Migrate the addresses, not just the pages
A fast rebuild can still lose useful search traffic or break customer journeys. Before replacing an existing site:
- Inventory the old URLs. Combine the sitemap, a crawl, CMS exports, Search Console, analytics and known campaign links. Include files and forms, not only articles.
- Choose each outcome. Keep useful pages at their existing addresses. Redirect only to a relevant replacement. Explicitly review retirements; do not send everything to the homepage.
- Build the redirect map. Test expected status and destination for every old address, including slashless variants. Avoid chains and loops.
- Check the new site. Verify canonical paths, internal links, media, forms, structured data and a sitemap containing only intended indexable pages. Find orphaned retained pages through a separate homepage discovery crawl.
- Rehearse the launch. Test a production-like build locally. Search its output for staging hostnames. Confirm analytics, consent and enquiry delivery, and record a working rollback point for the old site.
- Approve the cutover. Release the approved build, attach the production domain and verify apex, www and HTTPS behaviour. Remove preview noindex only from intended production pages. Check the deployed robots.txt and sitemap before submitting the sitemap in Search Console.
- Monitor and keep a way back. Recheck old URLs, form errors, indexing and conversion data after launch. Keep the old system recoverable until the verification window closes.
Our seven migration checks and domain migration guide cover the search and customer-journey risks in more detail.
Keep running costs and responsibility visible
Cloudflare currently lists static-asset requests as free and unlimited. Worker execution, storage, email, domains, AI use and maintenance have their own limits or costs. A free hosting tier is not a promise that operating a business website is free. Review Cloudflare's current pricing and limits before selecting a plan. Platform guidance checked 10 September 2026.
Monitor uptime, broken links, failed forms and stale content. Keep deployment identifiers and source revisions together so you can restore a known-good version. Database changes need a separate recovery plan: rolling back static files does not restore deleted records.
Build it yourself, or bring us the next step.
If you have a working Astro site, we can discuss whether AIVA onboarding or an agent-operated website workflow fits. We agree eligibility, scope and costs before implementation. You can also keep the guide and run the site yourself.