Case study · 2026

Vardão Máquinas website

The institutional website of the company where I work, Vardão Máquinas, an authorized Husqvarna dealer and service center in Limeira, Brazil. It presents the company, the workshop and the product lines so customers find us on Google and take the conversation straight to WhatsApp, bringing more sales to the store. It complements Vardão Central, which runs the operation from the inside.

Open the website
Home page of the Vardão Máquinas website, with the store front and the reasons to buy from Vardão

The problem

Vardão is a Gold-level Husqvarna dealer, with its own workshop and genuine parts at the same address. But people who want a chainsaw, a lawn tractor or a repair search on Google before going to the store. A company without a complete website does not show up in that search, and visitors need to understand quickly who the company is, what it sells, whether it repairs what they already own and how to reach someone.

The solution

A complete institutional website: the company's story and numbers, the service workshop explained, the product lines, customer reviews and a contact option on every page. It is about 200 pages generated from typed data, with the right title, description and structured data for search, and a button that takes the visitor to a salesperson with the message already filled in.

What the site does

Presents the company

The About page tells who the company is: an authorized Husqvarna dealer at Gold level since 2020, with store, workshop and genuine parts at the same address, how Vardão works and how to get there.

Shows the service workshop

A page of its own for the authorized workshop: what the service covers, factory warranty preserved and a free quote approved before any work.

Presents the product lines

Garden, forestry, robotics, family farming and battery, in pages that show the recommended use and lead to the specialist, so customers do not have to hunt for a contact.

Gathers social proof

Public customer reviews from Google, for people who do not know the store yet to see what others say.

Helps customers choose

37 comparison and buying-guide articles, calculators, search inside the site and a guide to parts and accessories by model, so customers decide with confidence before talking to a salesperson.

WhatsApp with context

Eleven kinds of pre-filled message, depending on what the customer was looking at, so the salesperson joins the conversation already knowing the topic.

Screens

Decisions

Pages generated from data

Products, articles and the company pages live in typed TypeScript data files, and a single template page generates each route at build time. Adding a new product means filling in an object, and the sitemap, title, structured data and navigation follow on their own. The gain is consistency: none of the 200 pages depends on someone remembering to configure SEO.

WhatsApp with the question already asked

Every call to WhatsApp carries what the customer was looking at: the product, the category, the article or the service workshop. That replaces "hi, how are you?" with a conversation that already starts on the topic, and the salesperson knows which page the contact came from.

Cookies with real consent

Google Analytics and the Google map only load after the visitor accepts, and consent starts as denied. Declining takes nothing away from the site. The choice is saved in the browser and can be changed later from a link in the footer.

Security in the headers

The site sends a content security policy that allows only what it really uses, plus protection against being embedded in other pages and against file-type sniffing. One limit is documented in the code: Next injects scripts without its own identifier, so the policy has to accept inline scripts. In development it is more permissive than in production.

The right part, or none

The parts and accessories guide follows the same principle as the counter in Vardão Central: suggest only when there is certainty. For tractors and zero-turn mowers, for example, matching is done only by model code, never by name similarity. I would rather show no accessory than the wrong one.

Numbers

202addresses in the sitemap
9institutional pages (home, About, service workshop, contact, reviews and others)
136product and category pages
37published articles
21accessory pages
11kinds of contextual WhatsApp message
~24klines of TypeScript and TSX

Counted on the live site's sitemap and in the code on 10/31/2026.

Stack