SiteAgain takes the business website you already own, rebuilds it on a fast static foundation, and hands you a way to change it in plain language — with a preview and your approval in front of every publish.
operator-console.png
The operator console mid-session: the request on the left, the diff and the passing checks on the right, Approve and publish in reach.
2000×1500 px · 4/3
Your existing site is the input. There is no blank canvas and no import wizard.
Plain files you own outright. No database on the request path, no plugin to patch.
Measured after the fact, on your own property — never a score we invented.
SiteAgain is a website operator. It takes the business website you already have, rebuilds it on a fast static foundation without losing the URLs and content you already rank for, and then lets you change it by describing the change in plain language. Every request is built in a sandbox, previewed, checked against a set of quality gates, and held until a person approves it.
The site itself is usually fine. What costs you is the distance between deciding to change something and that change being live.
Five days
to change one line
You spot a wrong price. You email the agency. You wait for a quote, then for staging, then for someone to be back from holiday. The edit takes four minutes; the round trip takes a week.
18 plugins
nobody wants to update
Somewhere in there is a page builder, a form handler, a cache layer and a theme that was customised in 2019. Every update is a coin flip, so nothing gets updated, so the risk compounds.
€150
per routine change
Routine content work is billed at the same rate as the work that actually needs a specialist. The invoice does not distinguish between changing a phone number and rebuilding a template.
None of that is solved by a better content editor. It is solved by removing the queue — and by making the change safe enough that removing the queue is not reckless.
Nothing here asks you to trust a process you cannot see. Every stage produces an artifact — findings, a preview, a contract, a change set, a report — and you decide whether the next one happens.
A bounded crawl reads the site you already run and reports what it observes: metadata coverage, canonical integrity, real-device load times, structured data, and what it costs you to change a page today.
OutAssessment — findings with evidence, and a supported / review-required / unsupported verdict
assessment-findings.png
The assessment view: findings ranked by impact, each one showing the observed evidence it was drawn from.
1920×1200 px · 16/10
Before money changes hands, the highest-impact page is rebuilt as a private preview. You judge the method on your own content instead of on a portfolio of somebody else's.
OutFirst-page proof — your page, side by side with the original
first-page-proof.png
Split view: the live page on the left, the rebuilt preview on the right, with every material difference annotated.
1920×1200 px · 16/10
Every legacy URL gets a destination decision. Every form, script, embed and analytics tag is inventoried and tested with real events. The plan is priced from that inventory, not from a guess.
OutMigration contract — URL matrix, integration inventory, fixed price
migration-contract.png
The URL matrix at full size: hundreds of rows, each marked preserve, redirect, remove or human-review.
1920×1200 px · 16/10
Describe the change the way you would describe it to a colleague. SiteAgain writes it in a sandbox, builds a preview, runs the checks, and shows you the result. Nothing reaches the public until you press the button.
OutChange set — sandboxed branch, preview URL, passing gates, your approval
change-set-review.png
A change set awaiting approval: the visual diff, the code diff, and the quality gates that passed.
1920×1200 px · 16/10
Search Console data feeds a weekly decision report — not a metrics dump. Proposals arrive with evidence, a confidence level and the window they should be judged in. Shipped changes are measured against that window and kept or reverted.
OutWeekly report — proposals in, measured outcomes out
weekly-report.png
The weekly decision report: three proposals to accept or dismiss, and last week's shipped changes with their measured direction.
1920×1200 px · 16/10
A request goes in as a sentence. What comes back is a change set: a branch, a preview, a diff, and the gates it had to pass. You approve it or you do not.
Add the new continuous care service to the homepage at €149 a month, and put an FAQ under it answering how fast changes go live.
Change set chg_7d31c0 is ready on a preview branch. Five gates ran; all five passed.
<section id="services">- <h2>Our services</h2>+ <h2>Our services</h2>+ <article class="service">+ <h3>Continuous care</h3>+ <p class="price">€149 / month</p>+ </article> </section>chg-7d31c0.preview.siteagain.com
Anything on this sheet is a sentence, not a ticket. Anything that is not on it, the assessment will tell you plainly before you sign.
Turnaround describes when the change is ready for your review, not when it is published. Publication happens when you approve it, which is usually the slow part.
Before anything is signed, your highest-impact page is rebuilt as a private preview. You compare the two yourself. If it is not obviously better, there is nothing to discuss.
proof-source.png
Full-page capture of the customer's live page, exactly as it is served today.
1600×1200 px · 4/3
proof-preview.png
The same page rebuilt: same content and structure, new foundation. Captured at the same viewport for an honest comparison.
1600×1200 px · 4/3
| Measure | Source | Preview |
|---|---|---|
| Platform | WordPress + 14 plugins | Static Astro, no runtime |
| Largest Contentful Paint | 4.1 s | 0.9 s |
| Page weight | 2.4 MB | 184 KB |
| Title & canonical | Bakery — Home | Est. 1998 | Bakery — Home | Est. 1998 |
| Contact form | Plugin handler | Same fields, tested |
| Entity markup | None | Organisation + Service |
Builders are for sites that do not exist yet. If yours already brings in work, the interesting problem is not generating a new one — it is changing the one you have without breaking what it already earns.
| Wix, Lovable, Framer, v0An AI website builder | SiteAgainA website operator | |
|---|---|---|
| 01 | Starts from a prompt on an empty canvas | Starts from the site you already run |
| 02 | Produces a new site with no history behind it | Preserves the URLs, content and search history you have |
| 03 | Each prompt is a fresh draft; context resets | Remembers your services, tone and every past change |
| 04 | Your existing URLs, rankings and copy are out of scope | Legacy URLs are a contract, not an afterthought |
| 05 | Publishing is immediate — review is your problem | Preview, quality gates and approval before every publish |
| 06 | Export is a zip file you now have to host | A live Git repository you own and can walk away with |
| Right tool when there is nothing there yet. | Right tool when the site already earns you money. |
An agent that can change your website quickly is a liability unless the same system can refuse a bad change and undo a published one. These four rails are enforced in code, not in a policy document.
A lost URL, a missing title, a broken canonical: these do not produce a warning you can click past. They fail the quality gate and the change does not ship.
Every edit is generated in a sandbox against a Git branch and becomes a change set. Sandbox, preview, evidence, approval, deploy — in that order, with no shortcut.
Every production change keeps a known-good rollback target. Rollback runs from the console in under a minute, without anyone editing a database by hand.
Your site is a plain static Astro repository. You can export it and its assets and walk away. Cancellation is never used as technical leverage.
The SEO contract is the one thing that separates this from a website builder, so it is a build failure and not a notification you can dismiss.
Every one of these is routinely sold. None of them is inside anyone's control, so none of them is ours to sell. What is left is what we can actually engineer — and that is the part written into the contract.
Nobody controls the ranking. Anyone who sells you one is selling a coincidence with an invoice attached.
Estimates ship with their assumptions, a confidence level, and the window they should be judged in — or they do not ship.
We make your site clear enough to be cited. Whether an engine cites it is the engine's decision, not ours to sell.
The assessment has no single number. Missing evidence is reported as missing, never quietly rounded down to a zero.
What we do commit to is narrower and checkable: your URLs survive, your approval gates every publish, every deploy keeps a rollback target, and the repository leaves with you if you go.
If your site matters to the business but is nobody's full-time job, this is pointed at you.
Keep services, hours, pricing and reviews accurate without opening a ticket with anyone.
Publish a case study the week it happens, not the quarter after.
Ship the page yourself instead of queuing behind an engineering backlog.
Test positioning, fix the copy, launch the landing page — between two meetings.
Hand routine maintenance and change requests to the operator; keep the strategy work.
No tiers to compare and nothing withheld behind a higher plan. The safety rails — approval, rollback, export — are not features, so they are never something you can be upsold.
Limited to a small number of businesses while the product is being refined.
Your existing site is assessed, rebuilt, launched and then operated through SiteAgain — with a person reachable throughout the pilot.
Not a feature Regression guards, approval before publish, rollback targets, repository export and data deletion are on every account, in every billing state.
These answers are also published as structured data, so an assistant asked the same question can quote them.
No. Your current website stays online while SiteAgain prepares the new version. Nothing changes until you have reviewed the result and approved the cutover.
No. You describe what you want in normal language. There is no code to write, no Git to learn and no CMS to configure.
Every change is previewed and approved before publication by default. Controlled automatic improvements can be enabled separately, once you are comfortable with them.
Yes. Your existing domain is connected to the new site at cutover, and the change is rehearsed before it is made.
Every deployment keeps a known-good rollback target. The site can be returned to a previous working version from the console in under a minute.
Business and marketing websites are supported today. Complex web applications and large ecommerce stores are assessed case by case, and the assessment says plainly when something is out of scope.
You export the repository and its assets and host them anywhere. The output is a plain static Astro project; cancellation is never used as technical leverage.
A bounded crawl, findings with the evidence they came from, and a plain verdict — supported, review required, or not a fit. It costs nothing and it does not touch your live site.