Ventall already had real HVAC projects: ventilation and air conditioning for apartments, houses, and commercial properties. But the legacy WordPress site worked like a brochure: the business entity, services, answers, and navigation context were almost invisible to AI/search. Requests arrived without structure, preliminary estimates could take days, and the team spent expert time on manual clarification.
IndexDock rebuilt this into a production-ready visibility system. The new site gives Ventall an AI-readable business foundation, structured service architecture, answer-ready content, real proof through cases, and a pricing calculator that qualifies requests before the first conversation. Customers now get preliminary pricing direction in minutes, AI/search can correctly read the business, and the team works with qualified data instead of raw requests.
What changed
01
From invisible business to AI-readable entity
Before
The old site had basic SEO, but no machine-readable business foundation: 0% JSON-LD/schema coverage, no Organization, LocalBusiness, Service, FAQPage, HowTo, or Breadcrumbs. AI/search could not reliably understand who Ventall was or what the company offered.
After
Ventall now has an AI-readable foundation: the business entity, services, FAQ, HowTo content, navigation context, and local business signals can be understood by search engines, AI search, and crawlers.
02
From service list to premium delivery system
Before
The website described isolated services: ventilation, air conditioning, installation, and equipment. This made the offer look like a list of tasks and did not explain why a full HVAC solution can justify a higher-value project.
After
Ventall is now presented as a complete HVAC delivery cycle: consulting, design, supply, installation, commissioning, and service. This supports premium positioning and explains the value of the integrated approach.
03
From raw leads to qualified demand
Before
Requests arrived raw: "I need ventilation." The team had to manually clarify object type, area, system choice, scenario, complexity, and budget direction.
After
Requests now arrive with context: object type, area, rooms/zones, system choice, and scenario are captured before the first conversation. The team receives a qualified commercial signal, not just a contact form.
04
From slow estimate cycle to pricing direction in minutes
Before
A preliminary estimate could take days, especially when the starting data was incomplete. Customers waited while managers and engineers spent expert time on clarification.
After
The pricing calculator gives customers preliminary budget direction in minutes. The team starts from structured data instead of manual discovery.
05
From portfolio content to proof and answer layer
Before
Cases, articles, and answers existed as separate content pieces, but they did not work as one system for trust, explanation, and AI/search understanding.
After
Cases now work as the proof layer, FAQ and articles as the answer layer, and video/documents as trust assets. This helps both people and AI/search understand Ventall's experience, scenarios, services, and evidence.
06
From one-time website to controlled visibility foundation
Before
There was no clear foundation for control: it was hard to understand which requests were qualified, how visibility was changing, or where the system needed improvement.
After
Ventall now has a controlled visibility foundation: structured intake, measurable pricing flow, AI/search readiness signals, and a basis for ongoing monitoring and improvement.
What IndexDock delivered
01
Blueprint and visibility strategy
A strategic foundation that turned Ventall’s business, services, demand, and answer structure into a clear AI/search visibility system.
02
Production implementation
A React / Next.js rebuild with localized uk/en structure, new routing, service pages, cases, articles, FAQ, and conversion paths.
03
Pricing qualification
A guided pricing flow that captures key project context before the first conversation with the team.
04
AI discovery foundation
Structured data, metadata, canonical URLs, hreflang, sitemap, robots, video sitemap, answer-ready content, and business entity signals.
05
Trust and proof layer
Cases, real project evidence, media, documents, and answer content supporting high-value HVAC decisions.
06
Control foundation
A controlled visibility foundation with structured intake, measurable pricing flow, AI/search readiness signals, and a basis for ongoing monitoring and improvement.
01 Strategy / Blueprint
Strategy and business clarity
IndexDock started with the Blueprint to turn Ventall’s business into a structure that customers, Google, AI search, and crawlers could understand. The old site had services and content, but no controlled AEO/GEO/SEO foundation connecting the business entity, services, answers, proof, and conversion paths.
The Blueprint organized Ventall around a clear commercial model: a full HVAC delivery cycle — consultation, design, supply, installation, commissioning, and service. This became the foundation for the service architecture, case layer, FAQ, articles, pricing calculator, and structured data.
Instead of producing another set of pages, the Blueprint defined the commercial structure of the new visibility system: what users should understand first, what proof they should see, and how the site should guide them toward the right next step.
02 Business model
Business model and product structure
Ventall moved from a site about separate HVAC services into a clear commercial system. Customers no longer see only ventilation, air conditioning, or installation — they see a complete path from understanding the task to implementation, commissioning, and service.
This model now shapes the digital experience: services explain the offer, cases prove experience, FAQ and articles answer questions, the calculator gives preliminary budget direction, and contact paths move users toward a qualified request.
03 Implementation
Implementation scope
IndexDock replaced the legacy WordPress setup with a React / Next.js system built for speed, structured content, localization, and AI/search readability.
The new implementation brought together uk/en routing, service pages, portfolio and case pages, articles, FAQ, pricing calculator, contact paths, metadata, schema foundation, sitemap, robots, and video sitemap. Ventall now has a production website that supports discovery, qualification, and ongoing improvement.
Pricing and qualification
Pricing qualification and customer intake
The Ventall calculator is not an AI estimate and not a decorative feature. It is an engineering qualification layer: formulas, rules, pricing data, property scenarios, and the team’s practical HVAC knowledge work together in a controlled system that can be updated through the admin panel.
Before, customers arrived with unclear requests, and the team spent days clarifying area, property type, system choice, zones, and budget direction. Now the calculator captures the key context before the first conversation and gives customers preliminary pricing direction in minutes.
For customers, this means faster budget understanding. For the Ventall team, it means less manual chaos, protected engineering time, and requests that arrive with prepared data instead of raw messages.
Highlights
- Captures pricing intent
- Protects engineering time
- Qualifies requests upfront
- Admin-managed pricing logic
04 Trust and answers
Trust, proof, and answer layers
For high-value HVAC decisions, trust must be part of the system. Cases, documents, certificates, photos, and videos became the proof layer: they show Ventall’s real experience and support the customer’s decision.
FAQ and answer content are built around real customer questions. They address common doubts before contact and give Google, AI search, and crawlers structured answers.
Articles, cases, and media now work as one system of trust, explanation, and discovery — for customers and for AI/search.
05 Schema and discovery
Technical discovery foundation
Visibility in Google and AI search depends not only on text, but on whether systems can correctly read the business. IndexDock created the technical discovery layer: schema, metadata, canonical URLs, hreflang, sitemap, robots, and video sitemap.
The new structure describes Ventall as a business entity, local HVAC business, service provider, answer source, knowledge publisher, media owner, and structured navigation system. It replaced the old state of 0% JSON-LD/schema coverage with a machine-readable system.
As a result, customers, Google, AI search, and crawlers can understand who the company is, what it offers, where it operates, what answers it provides, and what proof supports its experience.
Signals implemented
- Organization / LocalBusiness
- Service
- FAQPage / HowTo
- Article
- VideoObject for video pages
- Breadcrumbs
- Canonical / hreflang
- XML sitemap / video sitemap
- Robots configuration
06 Migration
Migration and release control
The move from the legacy WordPress site to the new system was handled as a controlled release, not just a page replacement. IndexDock preserved the crawl and discovery foundation with redirects for legacy URLs, clean URL structure, robots/sitemap, canonical signals, and post-launch validation.
This reduced the risk of losing accumulated Google signals and gave Ventall a stable launch for the new AI-ready system.
Covered
- Legacy URL transition
- Redirect control
- URL cleanup
- Indexation protection
- Release validation
- Post-launch correction
07 Control mode
Measurement and ongoing control
Launch was not the endpoint. Ventall received the foundation for control mode: the system became measurable, reviewable, and improvable after release.
Control covers the key areas: request quality, pricing flow performance, AI/search visibility, technical availability, schema/discovery signals, and migration stability. This allows the team to see where the system needs correction instead of guessing what works.
Ventall now has a controlled visibility system that can be reviewed, measured, and improved over time.
Controlled areas
- Request quality
- Pricing flow performance
- AI/search visibility
- Technical availability
- Schema/discovery signals
- Migration stability
- Ongoing improvement
Operational value
Business value for Ventall team
The system was built not only for Google and AI. It changed how the Ventall team works: customers arrive with context instead of raw “I need ventilation” messages, and initial qualification happens before the first conversation.
This protects expert time, reduces manual clarification, and makes sales preparation stronger. The team sees property type, project scale, system choice, and budget direction earlier — so it can separate typical requests from complex projects faster.
Key outcomes
- Engineering time protected
- Less manual clarification
- Better sales preparation
- Qualified requests for the team