AlbertaWeb.Design

Blog

Services · Strategy

Rebuild the site, or add a knowledge layer?

· 6 min · AlbertaWeb.Design

If people can already quote and book, you may only need schema, /llms.txt, and a service map. If they cannot, a brochure retrofit will not save the funnel.

Most Alberta sites we see fail in one of two ways. Humans cannot finish a job — no phone, no price band, no booking. Or humans can finish, but a crawler gets an empty shell. Those are different repairs.

Choose the retrofit when

  • The design is acceptable and the phone rings from the current URL.
  • Pages already name services and cities in HTML.
  • You need LocalBusiness / Service schema, /llms.txt, /services.json, and a WCAG patch list — not a new brand.

Choose the rebuild when

  • The homepage is a slideshow with no next step.
  • The stack cannot server-render text for crawlers.
  • You need an instant scope, calendar hooks, and service pages that match how you actually sell.

We will not bolt a chat widget onto a site that cannot state hours or prices. That is how you get an assistant that invents a name and says it is not available.

The sequence we sell

Scan the public URLs. Pay $299 if you want live assistant prompts. Retrofit or rebuild. Add automation only after intake has somewhere to land. Full inclusions and prices.

Clinics, restaurants, retail, firms, home services, and trades all use the same two journeys: customer → quote → book, and assistant → verify → recommend. The pages change. The architecture does not.

Scan a live website