You read it.
Pages of text and links. A hit counter. A guestbook.
Welcome to My Home Page!
Links · Guestbook · Photos
🚧 UNDER CONSTRUCTION 🚧
You are visitor 000417
How it works
How a web engine works
Planned, built and run for you. Here's what's inside, and how we build it.
4 short steps · about 2 minutes
Same business, two websites
Same business. Two websites.
On the left, what we find most often on small-business websites. On the right, the same business as a web engine.
Drag to compare
- Written for your customerLeads with the visitor's problem, in the words they actually search with.
- Built to convertOne primary action, with reviews and the upfront-quote promise right beside it.
- Effortless on a phoneTap-to-call always in reach, three menu items, no slider to fight.
- Open to everyoneHigh-contrast text, 44px tap targets, visible focus and an accessibility menu.
- Readable by AIServices, areas, hours and booking stated plainly — and again in schema for AI.
- Useful from the first tapBuilt to a 90+ PageSpeed target and tested before launch.
application/ld+json
{ "@context": "https://schema.org", "@type": "Plumber", "name": "Your Plumbing & Heating", "telephone": "+1-555-010-0199", "areaServed": [ "Northside", "Lakeview" ], "knowsAbout": [ "Emergency repairs", "Water heaters", "Drain cleaning" ], "potentialAction": { "@type": "ReserveAction", "name": "Book a visit" } }
Answer block
Who can fix a burst pipe near Northside?
Your Plumbing & Heating handles emergency repairs, water heaters and drain cleaning for homes in Northside and Lakeview, gives an upfront quote before work starts, and is open Saturdays. Book a visit online or call.
llms.txt
# Your Plumbing & Heating > Burst pipe or no hot water? Talk to a plumber now. - [Book a visit](/book/) - [Services](/services/) - [Reviews](/reviews/)
Row by row
What changes when a website becomes an engine.
What it affectsTypical websiteWeb engine
Written for your customerOpens with “Welcome to our website” — about the company, not the problem the visitor came with.
Welcome to our websiteLeads with the visitor's problem, in the words they actually search with.
Burst pipe or no hot water? Talk to a plumber now.
Built to convertNo clear next step: a small “Contact us” link and an eleven-field form.One primary action, with reviews and the upfront-quote promise right beside it.
Effortless on a phoneEleven menu items, an auto-rotating slider and the phone number buried in tiny header text.Tap-to-call always in reach, three menu items, no slider to fight.
Open to everyoneLight grey text on white, small tap targets and no visible focus for keyboard users.High-contrast text, 44px tap targets, visible focus and an accessibility menu.
Readable by AIFacts live in images and filler paragraphs, with no structured data for a machine to read.Services, areas, hours and booking stated plainly — and again in schema for AI.
Useful from the first tapHeavy slider images and scripts load before anything useful appears on a phone.Built to a 90+ PageSpeed target and tested before launch.
Read the detailsWhat separates a website that converts from one that just exists
Most small-business websites are built like brochures: a welcome message, a photo slider, a long menu and a contact page. They describe the company. The visitor, meanwhile, arrived with a problem and a phone in their hand, and decides in seconds whether this business can solve it.
Conversion-focused design (CRO) starts from that visitor. The headline names their problem in the words they search with, there is one obvious next step on every screen, the phone number is a tap away, and the proof — reviews and credentials — sits right beside the ask instead of three pages away. Forms ask only for what is needed to start: a name, a phone number and what's going on.
Accessibility is part of the same work. Readable type sizes, strong colour contrast, tap targets large enough for a thumb, visible keyboard focus, real headings and labels, and an accessibility menu make the site usable for more people — older visitors, people on bright screens outdoors, and people using screen readers. The same clean structure is what AI agents and browsers increasingly check when they read a page on someone's behalf.
Machine readability is the last layer. The services, areas, hours and booking path a person sees are also described in schema.org structured data and in short, answer-first paragraphs, so search engines and AI assistants can state the business's facts accurately. Fast managed hosting and light pages make all of it useful on a phone immediately.
“Typical” describes the patterns we find most often when we audit small-business websites; individual sites vary. PageSpeed is measured with Google's PageSpeed Insights, and results vary by page and content.
Look inside a WebEngine page
Looks like a website. Look closer.
Here's an ordinary-looking home page on a phone. Scroll, and we'll take it apart: eight layers, each with one job — helping people find you, trust you and get in touch.
- 01
Mobile-first
Designed for the phone in your customer's hand first.
Thumb-zone buttons · big, easy-to-read text
- 02
Call-or-book layer
Every screen has one clear next step: call, book or ask.
Conversion · sticky call/book bar · one main button · short form · trust beside the ask
- 03
Structure
Every page answers the questions your customers really ask.
AKA framework: Authority → Knowledge → Answer
- 04
Accessibility
Easy to read and use for everyone, including people using screen readers.
Strong contrast · focus states · alt text · 44px tap targets
- 05
AI layer
Hidden labels help Google and AI tools understand who you are and what you do.
Schema (JSON-LD) · llms.txt
- 06
Engine Agent
A friendly helper that answers questions and takes requests, day and night.
Automated assistant · says so · passes every request to your team
- 07
Speed, hosting & security
It opens fast and stays safe: we aim for 90+ on Google's speed test.
Managed hosting · SSL · security updates · locked-down logins · tested at pagespeed.web.dev
- 08
Intelligence
On Growth plans, we check every month what people search for and improve your pages to match.
Engine Intelligence · with your permission · Growth plans
That's why it's not just a website.
Every page is built this way, and sites launch with 90+ pages on average — about two years of blog posts, ready on day one.
See if you qualifyRead the detailsWhat's inside every WebEngine page
Most small-business websites are a picture of the business: a headline, a few photos and a contact form. A WebEngine page looks just as simple to a visitor, but it is built in layers, and each layer has one job. Together they help people find the business, trust it and get in touch — and help search engines and AI assistants understand it.
Mobile-first and conversion. Pages are designed for a phone first: large, readable type, the main buttons where a thumb naturally reaches, and tap targets big enough to hit. Every screen has one clear next step — call, book or ask — with a sticky call-and-book bar, one primary button, short forms and proof such as reviews placed right beside the ask.
Structure. Content follows the AKA framework — Authority, Knowledge, Answer: who you are and what you do, the detail people need to decide, and direct answers to the exact questions they type or speak, in the order they tend to ask them. Sites launch with 90+ pages on average (94 across nine live VIS Mountain builds, depending on services and service areas) — roughly what four blog posts a month add up to over two years. That is what we mean by launching about two years ahead; it is not a promise of rankings.
Accessibility. Text and buttons are designed with strong colour contrast, visible focus states for keyboard users, descriptive alt text on images and touch targets of at least 44 by 44 pixels, so the page is easier to read and use for everyone, including people using screen readers.
The AI layer. Behind the visible page sits structured data in schema.org JSON-LD — the type of business, its name, services, hours, service area and contact details — plus an llms.txt summary file. Visitors never see these labels; search engines and AI assistants read them to understand exactly who the business is. Nobody can guarantee an AI assistant will mention a business; clear, consistent, checkable facts are what we can control.
Engine Agent, hosting, security and speed. Engine Agent is an automated assistant that says so, answers common questions and passes each request to the team. Engines run on fast managed hosting with SSL, updates and security patches, logins and forms protected against bots and break-in attempts, and guardrails for AI agents. Each build is designed to a 90+ PageSpeed target and tested with Google's PageSpeed Insights at pagespeed.web.dev before launch; scores vary by page and content, so 90+ is the target we build to, not a promise for every page.
Intelligence. On Managed + Growth plans, and with your permission, Engine Intelligence reads Google Search Console and Bing Webmaster Tools data every month to see which searches and pages are rising or slipping, and the team fine-tunes titles, answers and pages from it.
Sources: Schema.org · llms.txt proposal · Google PageSpeed Insights
What's inside
What's inside. 14 parts, each with one job.
A web engine has fourteen parts, tuned to your market — some come with the build, some with your plan. Scroll to see what each one does for you.
- 01
Research
We learn what your customers search for before we design anything.
The questions people actually ask, what Google's AI answer and the AI assistants already say, who shows up on the map around you, and how real customers describe the problem.
- 02
Page plan
A page for every service and every place you serve.
Our AKA framework — Authority, Knowledge, Answer: main pages for what you do, guides that teach, and answer pages for the exact questions people type and speak, mapped to every service and every place you serve.
- 03
Phone-first
Big text, fast pages, one clear next step.
Designed for thumbs and phones first, easy to read at any age, with the phone number, the booking button and the reviews and proof always one tap away.
- 04
Fast code
Modern code, served from servers close to your visitors.
Fast, secure and accessible by design — every build is checked for SEO, speed and accessibility before it goes live.
- 05
Labels
Every page labeled so Google and AI know who you are.
Structured data (schema), entities and E-E-A-T signals for your business, services, locations and people, so search engines and AI know exactly who you are, what you do and why you can be trusted.
- 06
Google & Bing
We tell Google and Bing about your site on launch day.
Google Search Console and Bing Webmaster Tools set up and your page list (sitemap) submitted — and on engines we host, IndexNow alerts Bing and other participating search engines whenever a page changes.
- 07
AI-ready
Ready for AI assistants, and the AI helpers that search and book for people.
Clear rules for which AI search bots get in, answers at the top of every page, services, locations and booking paths machines can read, an llms.txt summary file — and readiness for the new ways AI agents will shop and book.
- 08
Intelligence · powered by Engine Intelligence
Your Google and Bing data shows us what to improve next.
With your permission, every month we read Google Search Console and Bing Webmaster Tools to see which searches find you and which pages are rising or slipping, then improve titles, words and answers to match. Your services and the areas you serve are linked to each other, and to answer pages where those exist, with rules that keep the links natural.
- 09
Security
Kept updated, locked tight, and careful with AI.
Updates and security patches for your site's software, and logins and forms protected against bots when we take your site on. AI gets guardrails too: chat agents get a narrow job, any AI we run for you treats what it reads as information — never as orders — and AI search bots are invited where they can mention you and asked to stay out of the rest.
- 10
Engine Agent · powered by Engine Agent
Answers questions and takes new enquiries, day or night.
Engine Agent answers common questions in conversation, saves each enquiry to your CRM (your customer list), which remembers every customer, and hands anything it shouldn't handle to your team.
- 11
Reviews · powered by Bird Local
More reviews. Less effort.
Review requests, review replies and a live review widget on your site — real reviews from your own customers, never filtered to only the happy ones.
- 12
Listings · powered by Branding Signal
Your name, address and phone — the same everywhere.
Kept identical across the listings and directories that maps and AI assistants rely on.
- 13
Conversion · powered by Dash Funnels
Every lead captured and followed up.
Forms, booking and automatic follow-up all flow into one CRM, so no enquiry sits in an inbox nobody checks.
- 14
Pit crew & the Hub · powered by the Hub
Ask any time. Most changes are live within 24 hours.
Open a request in your VIS Mountain Hub — or just email it — any time of day. Every request becomes a tracked ticket the team works from, so requests don't get lost in an inbox, and content, photos, hours, pages and offers stay current.
Read the detailsWhat goes into a web engine, layer by layer
Research comes first. Before design starts we harvest the live search results for your services and area: the People Also Ask questions, what the AI Overview says and which sources it cites, the local map pack, and the competitors around you. That research decides the page plan.
The page plan follows the AKA framework — Authority, Knowledge, Answer. Authority hubs cover each service you offer; knowledge guides explain the topic in depth; answer pages take the exact questions people ask and answer them in the first paragraph, the format search engines and assistants quote. Across nine live VIS Mountain builds the average launch was 94 pages, depending on services and service areas.
Every engine ships with sitewide structured data, technical SEO, accessibility work and speed budgets, and launches through quality gates for titles, metadata, schema, links and performance. On launch day it is submitted to Google Search Console and Bing Webmaster Tools, and on engines we host, IndexNow notifies participating search engines whenever pages change.
The outer layers connect the site to the rest of your presence: Branding Signal keeps your business information consistent across listings and directories, Bird Local runs review requests and responses, and Dash Funnels captures every lead into one CRM with automated follow-up.
Sources: IndexNow · Schema.org · Google Search Central: optimizing for generative AI search
The journey
From your niche to your next customer.
Getting found on Google is planned in from day one, not added later. You see the plan before we build.
- Stage 01
Discover
We learn your business, your goals and how you want to sound.
- Stage 02
Research
What people search, what AI says, who's on the map and the words customers use.
- Stage 03
Blueprint
Every service in every place you serve, in one plan you approve.
- Stage 04
Build
Design, words, photos and code on a private preview you can click through.
- Stage 05
Launch
Final checks, old links pointed to new pages, sent to Google and Bing — live.
- Stage 06
Grow
Changes made for you, reports, and ongoing Google and AI search work as you grow.
Read the detailsHow a WebEngine project runs
Discovery covers the business, the people behind it, the services that matter most, the areas you serve and the voice you want. Research then turns live search data into a plan: the questions customers ask, the answers AI already gives, the competitors that win locally, and the language customers use.
The blueprint is the strategy in one document — a topical map of every service and every location page, how they link, and what each page must answer. Geo SEO is designed in from the first page, whether the engine is a local practice, a multi-location brand, a directory or a store.
The build happens on a private preview so you can click through real pages before launch. Launch includes redirects from any old addresses, quality gates, and submission to Google and Bing. After launch the engine is managed: changes, reporting and, on growth plans, ongoing SEO, AEO and GEO.
Your tools
Works with the tools you already use.
Your website becomes the one true source. Google, maps, AI, listings, reviews, social, payments and your CRM all work from the same facts.
Search & AI
- Google Business Profile
- ChatGPT
- Gemini
- Perplexity
Maps, listings & reviews
- Apple Maps
- Yelp
- Nextdoor
- Foursquare
- Tripadvisor
- BBB
Social
- YouTube
- TikTok
Commerce & payments
- Stripe
- Shopify
- WooCommerce
- Square
- PayPal
- QuickBooks
Tools you already use
- Google Calendar
- Gmail
- Calendly
- Zoom
- HubSpot
- Mailchimp
- Zapier
- Google Sheets
- WordPress
- Webflow
Read the detailsWhich platforms a web engine works with
A web engine sits at the centre of a business's online presence. It works alongside the Google Business Profile, Bing Places and Apple Maps listings that power map results; the review platforms customers check; the social profiles that carry the brand; and the booking, payment, calendar and CRM tools the business already runs on.
Consistency is the point. AI assistants and search engines cross-check what a website says against listings and reviews elsewhere. When the website is the single source of truth — and Branding Signal keeps listings matched to it — the business is described the same way everywhere a customer, or an assistant, looks.
Product names and logos belong to their owners and are shown to indicate the platforms WebEngine works with; they do not imply a partnership or endorsement, except where stated (VIS Mountain is a Google Partner).
Why now
The web keeps changing what a website is for.
You posted on it.
Feeds, profiles and apps. Everyone could post.
social.lybeta
♥ 24
♥ 9
♥ 51
Share this!You were promised you'd own it.
Wallets, tokens and a lot of hype.
Connect wallet
gm · floor 0.42 Ξ · −91%
It works for you.
Read by people. Understood by AI. Ready for the AI helpers that now search and compare for your customers.
Family dentistry, open Saturdays.
Book a visit{ "@type": "Dentist",
"openingHours": "Sa 08:00-13:00",
"potentialAction": "ReserveAction" }Find a dentist open Saturday morningFound one. Opening their booking page…
Read the detailsWhat “Web Engine” means
Web 1.0 was a library: you read pages. Web 2.0 was a stage: everyone posted. Web 3.0 promised ownership and mostly delivered speculation. What has actually changed in the last two years is the reader. A growing share of the people deciding where to eat, which clinic to call or which contractor to hire now start with an AI assistant that reads the web for them.
A web engine is a website built for both readers at once. For people it is fast, clear and obvious about what to do next. For machines it is structured: services, locations, hours, people and prices described in schema markup, summarised in an llms.txt file, published as answer-first pages, and kept consistent with every listing and review profile the business has.
And it does not stand still. A web engine is managed: researched before it is designed, indexed the day it launches, and updated by a team as the business changes.
Questions
Questions about how it works.
Does schema markup help with AI search?
Schema markup states facts about your business — services, locations, hours, people, reviews — in a structured format that search engines read reliably. Google says no special markup is required for its AI features, but well-structured, crawlable pages with accurate structured data are the foundation those features draw on, and consistent facts make your business easier for any system to understand.
What is llms.txt and do I need one?
llms.txt is a proposed convention: a plain-text file at the root of a website that summarises the site for large language models. Be realistic about it — Google Search ignores it, and a 2026 Ahrefs study found most published files get no requests. It costs almost nothing, so every web engine includes one as a courtesy to the tools that do read it (ours is at webengine.io/llms.txt), but the real work is structured, answer-first, consistent content.
Can AI agents book or buy from my website?
Partly, and it is early. AI assistants can already read a well-built site and send customers to its booking or checkout pages, and the big platforms are testing ways for assistants to finish a purchase. A web engine is built with clean, accessible booking and buying paths and structured data, so it is ready as those options mature.
What are SEO, AEO and GEO?
SEO (search engine optimization) helps your pages rank in search results. AEO (answer engine optimization) shapes content so it can be used as a direct answer — in featured snippets, voice assistants and AI Overviews. GEO (generative engine optimization), a term from a 2023 Princeton-led research paper, focuses on being understood and cited by generative AI tools such as ChatGPT, Gemini, Perplexity, Copilot and Grok. Google's own guidance is that optimizing for generative AI search is still SEO — which is why a web engine treats all three as one discipline.
A VIS Mountain company · 20+ years in the industry · Google Partner · 100+ businesses and clinics
Get started
Start your engine.
4 short steps, about 2 minutes. If we're a good fit, you pick a time to talk right away. We work with U.S. businesses.
What happens next
- Answer 4 short steps
- If it's a fit, pick a time
- We come prepared