Créez un site web de nettoyage qui explique vos services et tarifiez correctement vos missions

Build a mobile-first website for my cleaning business. Make it clear, welcoming and easy to use. Help customers understand the service, get an estimate when my rules support one, and request a visit.

MY DETAILS
- Business name and background: [REAL NAME AND FACTS]
- Country, website language, currency and size unit: [COUNTRY / LANGUAGE / CURRENCY / SQUARE METRES OR SQUARE FEET]
- Services: [ONLY WHAT I OFFER, WITH INCLUSIONS, EXCLUSIONS AND WHO SUPPLIES MATERIALS]
- Service area: [ACTUAL TOWNS / POSTCODES / BOUNDARIES]
- Contact and hours: [PHONE / EMAIL / HOURS / TIME ZONE]
- Verified trust claims: [ACTUAL INSURANCE, CHECKS, QUALIFICATIONS OR GUARANTEE TERMS; OMIT UNSUPPORTED CLAIMS]
- Pricing rules: [MY RATE TABLE OR FORMULA, MINIMUM CHARGE, EXTRAS, FIRST-VISIT AND REPEAT-VISIT RULES, DISCOUNTS IF ANY, TAX/FEE TREATMENT AND ROUNDING; OR QUOTE REQUEST ONLY]
- Manual-review cases: [SERVICES, PROPERTY CONDITIONS OR SIZES I CANNOT PRICE AUTOMATICALLY]
- Example jobs: [INPUTS AND EXPECTED ESTIMATES I HAVE CALCULATED]
- Existing request/scheduling tool: [SUPPORTED FORM/LINK, OR NONE]
- Response window and cancellation terms: [MY ACTUAL REVIEWED TERMS, OR OMIT]

PAGES
Home: service area, selected services, click-to-call and "Get an estimate" or "Request a quote", matching the flow actually available.
Services: a checklist of what each service includes and excludes. Show durations only when supplied; distinguish first-time, regular and specialist work.
Estimate or quote request: ask only the factors my pricing uses, such as property size, bathrooms, selected service, condition, frequency and extras. Use my size unit consistently. Do not apply a domestic room formula to commercial or post-renovation jobs unless I supplied a valid rule.
About: my real background and verified claims. No invented badges, reviews, team size or guarantees.
Contact: real contact details, hours and service-area information. Add FAQs using only supplied facts.

ESTIMATE RULES
Calculate from my supplied rules, not AI guesses. Apply discounts, fees, minimums and taxes only as specified, and ask me to resolve missing or conflicting rules. If a range is supported, show its basis and assumptions; do not invent a percentage buffer. Distinguish first-visit and ongoing prices. Show mandatory charges clearly with the result and use my reviewed tax treatment.
For missing rules, unsupported jobs or out-of-area addresses, explain the limitation and offer a manual enquiry without a misleading price. Label an estimate as provisional; explain that scope, final price and availability need confirmation. Do not suggest that this label overrides an accepted quote or local consumer rights.

REQUEST FLOW
Collect name, preferred contact, area/postcode, selected service and preferred timing. Do not ask for keys, alarm codes, identity documents or card details. Save the request privately with inputs, result, currency, price-rule version and timestamp. Recalculate on the server rather than trusting a submitted total. Notify me through a supported configured service. Validate inputs, prevent duplicate requests on retry and add spam protection. Show success only after saving; handle notification failure without losing the request. Do not display fake appointment availability or confirm a recurring booking.

DESIGN AND HANDOFF
Use real team/work photos or neutral placeholders. Never generate fictional cleaning results or before-and-after images. Improvements to my real photos can adjust lighting, crop or colour without changing the actual result. Publish client-home photos and genuine reviews only with permission; hide unsupported sections.
Let me edit services and pricing in an owner-only admin. Use accessible labels, accurate page titles and mobile layouts; support RTL for Hebrew. Prepare privacy/terms drafts for review from my actual country and tools. List missing setup. Test my example prices, boundary cases, form saving, notification delivery and owner-only access. Report anything untested.