Method · Process · Ownership · Data

Beautiful on the surface. Engineered underneath.

That line is our craft signature, and this page is what it means in practice. EzWebBuilds works in four steps — scope, design, build, care — with one design sign-off gate, a documented visibility methodology applied to every build, and a simple ownership rule: everything we make is yours. Below is the whole method, including how we handle your data and how our own site treats AI crawlers.

The method is tested on our own machinery first — including an 80+ page island platform we run as a visibility laboratory.

01The Four Steps
04How We Work

Scope

We learn the business and agree exactly what is being built and what it costs.

Design

Clean, on-brand interfaces, settled before a line of code is written.

Build

We build, connect it to your tools, and test it against real use.

Care

Hosting, renewals, and updates handled so it keeps running without you thinking about it.

02The Visibility Method, In Plain Words

How do you make a website visible to AI search?

Honestly: nobody can guarantee it — anyone who promises rankings or AI citations is selling weather. What can be engineered is eligibility: clean structure, self-contained answers, consistent facts, and machine-readable labels that let Google and AI assistants read and verify a property. We wrote a 25-chapter, evidence-tagged framework on exactly this, and every build inherits it.

Evidence-tagged

Every claim in our framework is labeled verified, inferred or unverified — the same discipline our audit reports use. We don't dress guesses as facts, in our documents or on your website.

Tested on ourselves

Our own island travel platform is the laboratory. Structural experiments run there first; only what survives becomes part of client builds.

Applied everywhere

This site practices what it sells: structured data on every page, a machine-readable index at /llms.txt, and a documented crawler policy — the same treatment your build gets.

How this site treats AI crawlers

Our robots.txt welcomes search and citation crawlers — the ones that can send guests your way — and declines training-only crawlers, which take content without returning visibility. Every allow and block is a documented decision, we don't claim the file is enforcement (it's a published preference), and we revisit the policy as the crawler landscape changes. Your build gets the same deliberate treatment, decided with you.

03Ownership & Trust

You own everything

Domain, code, content, design files, analytics, the assistant's knowledge files — all registered to you or handed over at launch. No builder lock-in, no hostage pages.

Fixed scope, fixed price, in writing

Every project starts with a written scope: what's included, what's excluded, what it costs in USD and MVR, and what happens if scope changes — a mini-quote before work, never a surprise line item.

The clock starts at content receipt

Timelines are counted from the day your photos and details arrive, not the day we shake hands. We send the checklist on day one and help you chase it.

No token surprises

AI running costs are explained before launch: expected monthly range, a usage cap if you want one, and an approval threshold past which nothing scales without your sign-off.

04Data Handling, Summarized

What data do we hold, and what do we refuse to hold?

We store what a project needs: your contact details, project files and website content, with named providers and stated retention. We do not store guest personal data in AI knowledge bases, we train staff never to paste passport or payment details into tools, and payments on client sites are handled by your booking engine — never by us. The full policy is in Privacy, and a project-specific data-handling document comes with every AI build.

05How We Report

How do you know a result is real and not marketing?

Because we tag it. Every number we publish carries its status, so you can tell a measurement from an estimate at a glance — the same discipline we apply to a client's data, applied to our own claims. This page describes how we build; this section describes how we report.

Measured vs projected

A measured figure traces to a named third-party source — Booking.com's extranet, Google Analytics, a published study. A projection is a studio estimate, labelled as one and visually distinct. We never dress an estimate as a measurement.

We publish the trade-offs

On the Proof page we show the numbers that got worse — a 16% drop in room nights, a rank of 27th of 44 on volume — next to the ones that got better. A result you can't see the cost of isn't a result. It's an advertisement.

We won't guarantee outcomes

No honest studio guarantees bookings, rankings or AI citations — they depend on weather, season and algorithms nobody controls. We guarantee the machinery: the eligibility, the structure, the evidence. What you do with it, and what the market does with you, stays honest.

Unmeasured is not "passed"

If we don't have a number, we say we don't have it — we don't round a gap up to a win. The same rule governs our audits, our case studies and every claim on this site.

06Start Where It's Easy

Work with someone who shows the engineering.

Tell us about the property on WhatsApp — you'll get a written scope and a fixed price. No surprise line items.

What happens next: you message → we ask five questions → you get a one-page plan with a fixed price within 48 hours.