Home
Service hero, editable roofing services, trust guidance, project proof, service-area summary, FAQ, and contact.
Start from a six-page roofing site with editable services, project proof, service-area guidance, FAQs, and a public inquiry form. On a Forms-enabled plan, published requests go to Form Submissions without inventing licenses, warranties, financing, reviews, prices, or estimate promises.
The live preview uses fictional demo details. The page tree and components come from the same canonical Roofing Site Template factory that creates the user's site.
The template stays inside normal Cogo Site pages and components, so every section can be changed after creation.
Service hero, editable roofing services, trust guidance, project proof, service-area summary, FAQ, and contact.
A service catalog that starts from repair, replacement, inspection, or the services entered during setup.
A safe starting point for real completed work without fabricated locations, materials, warranties, or results.
Business story and trust content that stays neutral until verified facts are added.
Coverage guidance that asks visitors to confirm whether a specific address can be served.
A public service-inquiry form for Name, Email, Phone, and Message, plus direct phone or email contact when supplied.
The existing Local Service setup can carry a business name, phone, primary service area, and service list into the first SiteConfig. There is no separate contractor profile or roofing runtime.
Change copy and imagery, add real project proof, adjust layouts and theme tokens, reorder sections, preview, and publish through the normal Cogo Site workflow.
The created site includes a structured public service inquiry Form and keeps phone or email contact when supplied. On a Forms-enabled plan, published requests can reach Form Submissions. It does not calculate estimates or claim licenses, insurance, warranties, financing, prices, ratings, availability, or response times unless you add facts you can verify.
The Roofing template connects the public Contact page to Cogo Site Forms from the first site creation. On a Forms-enabled plan, that gives the published site a real inquiry-to-inbox path without adding booking or estimate semantics.
When this Roofing site is created, Cogo Site provisions and publishes the Form behind the Contact page instead of leaving a visual-only placeholder.
On a Forms-enabled plan, the published form collects Name, Email, Phone, and Message as a service inquiry. It does not calculate an estimate or promise that a job is available.
With Forms enabled, the owner can open Form Submissions and read the captured details after a visitor submits the form, then decide the next step.
No. It includes a structured public service inquiry Form for Name, Email, Phone, and Message. On a Forms-enabled plan, published requests appear in Form Submissions; the form does not calculate a roofing estimate.
Yes. The Projects page is designed for real project photos and descriptions you can substantiate. The starter does not invent project locations, materials, warranties, or outcomes.
No. Credentials, insurance, warranties, reviews, prices, and financing remain neutral until you add accurate business facts.
No. Roofing only selects the initial SiteConfig. The resulting website uses the same editor, renderer, preview, and publishing path as other Cogo Site sites.
Open the live preview, then create the Roofing site through the normal signup flow. The Contact form is part of 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