Home
Service hero, editable landscape services, trust guidance, project proof, service-area summary, FAQ, and contact.
Start from a six-page landscaping site with editable lawn, design, hardscape, maintenance, or other services, a Projects page, and a structured public inquiry Form. On a Forms-enabled plan, requests reach Form Submissions without inventing prices, booking slots, project estimates, payments, or guaranteed availability.
The preview uses fictional demo facts, while its page structure, service sections, Projects page, and components come from the same canonical Site Template factory used at creation.
The template is image-forward where useful but stays entirely inside the normal Cogo Site editing and publishing model.
Service hero, editable landscape services, trust guidance, project proof, service-area summary, FAQ, and contact.
A flexible list for lawn care, design, hardscape, cleanup, maintenance, or services entered during setup.
A safe starting point for real outdoor project photography and accurate project descriptions.
Business story and trust content that does not invent awards, years in business, reviews, or results.
A page for the actual communities or regions served, with address-level availability confirmed by contact.
A public landscaping inquiry Form for Name, Email, Phone, and Message, plus direct phone or email contact when supplied.
Business name, phone, primary service area, and offered services can flow through the existing Local Service setup into ordinary editable SiteConfig content.
Use the normal editor to replace images, edit project and service copy, change layouts and theme tokens, reorder sections, preview, and publish without a landscaping-only editor.
The created site includes a structured landscaping inquiry Form and keeps phone, email, service-area, and project-proof content when supplied. On a Forms-enabled plan, published requests can reach Form Submissions. It does not calculate estimates, book appointments, take payments, measure properties, create proposals, or promise availability.
The Landscaping template uses the same canonical Cogo Site Forms path as the other proven Local Service sites. It pairs project proof and service-area context with a short inquiry without turning the website into an estimating or field-service system.
Site creation provisions and publishes the canonical Form behind the Contact page, then binds the returned Form definition id instead of leaving a visual-only quote box.
On a Forms-enabled plan, the published Form collects Name, Email, Phone, and Message so a visitor can describe the property and project need. It does not calculate an estimate or reserve a schedule.
The owner can read the submitted landscaping inquiry in Form Submissions and decide how to scope, price, schedule, or decline the work outside the Form itself.
No. The created site includes a structured landscaping inquiry Form; on a Forms-enabled plan, visitors can submit Name, Email, Phone, and Message and the owner can review the request in Form Submissions. The Form does not calculate estimates, reserve appointments, or take payments.
Yes. The Projects page is made for real project evidence. Replace demo imagery and add only descriptions, locations, or results that are accurate and appropriate to publish.
Yes. The service list is editable during setup and again in the normal visual editor.
No. The industry template only chooses the initial SiteConfig; rendering, editing, preview, and publishing use the existing shared product path.
Open the live preview, then create the Landscaping site through the normal signup flow. The Contact Form belongs to the created starting site; Form Submissions becomes the published inbox path when Forms is enabled for the workspace.
We use cookies
We use cookies to enhance your browsing experience and analyze site traffic. By clicking 'Accept', you consent to our use of cookies. Learn more about our cookie policy