Twenty-four terms, explained plainly

Glossary of website, app and AI builder terms

This AI website builder glossary explains the words you meet when you build a site with AI, get it indexed, publish an app to the stores or hand the code to a developer. Each entry is short and says what the term changes for your project.

How to use this AI website builder glossary

Go straight to your word

The terms are sorted alphabetically. Open the one that brought you here instead of reading the whole list. Rendering questions start at pre-render, and store questions start at App Store review and closed testing.

What each entry tells you

Each entry defines the term in a few sentences, then explains what it changes for your site or app. When Eqlo handles the point for you, the entry says so.

Acceptance

The check that a site or app really does the job it was built for, on real cases rather than on a demo. An AI builder tends to show the happy path: sign in, book, pay. Acceptance covers the rest, such as a fully booked slot, a declined card or a form sent empty. Write down what must work before you start, then test each point before launch.

App Store review

Apple's check before an iPhone app goes live, carried out partly by people and partly by software. Reviewers look for an app that works, a login they can use and a privacy label that matches the data you collect. Eqlo fills in the store listing from your site and generates the App Privacy declaration. On the Plus plan, it also sends the signed build to TestFlight. Apple makes the final call.

Canonical

A tag that tells search engines which address is the official one for a page, when the same content can be reached at several. Without it, a preview address and your real domain can compete with each other in results. Every page Eqlo publishes declares its canonical address. Once you connect your own domain, that domain is the address to look for in the tag.

Client-side rendering

The server sends an almost empty page, and the browser runs JavaScript to fetch the text and build the layout. This works well for an app behind a login. It is risky for a public page you want found on Google, because a crawler that keeps the first response keeps an empty shell. The fix is to send HTML that already contains the words. See pre-render and SSR.

Closed testing

A Google Play test track where a list of testers installs your app before it goes public. New personal developer accounts must run one with at least 12 testers for 14 days before releasing to everyone. On the Plus plan, Eqlo sends the signed Android build to the internal testing track, and you then manage testers in your Play Console. Apple uses TestFlight, which follows its own rules.

Core Web Vitals

Three Google measurements of how a page feels on real devices: loading speed (Largest Contentful Paint), response to taps (Interaction to Next Paint) and visual stability (Cumulative Layout Shift). A heavy video or images without set dimensions can fail on a phone even when the page looks fine on a laptop. Eqlo converts photos to WebP files of 200 KB or less and hosts its fonts itself.

Crawlability

Whether a search engine robot can reach a page and follow its links. A robots.txt rule, a login wall, a noindex tag or a menu that only appears after JavaScript all get in the way. A sitemap helps robots find pages, but it does not override a block in robots.txt. To check a page, load it with JavaScript turned off, then open robots.txt and the sitemap on the same domain.

Data residency

The country or region where data is supposed to stay, under a contract or a legal requirement. It is close to hosting but more of a legal notion. A data protection officer asks about residency, and a host answers with the location of a data center. GDPR compliance alone does not fix a storage location, since the regulation sets rules for processing. Ask any provider where your data is actually stored. On Eqlo, each project has its own region, EU, US or UK, set at the moment you create it.

Design system

The visual rules a brand follows: fonts, colors, spacing, and components such as buttons and forms. Without them, each new page tends to invent its own style. Eqlo offers 21 visual styles and 44 fonts. You can also give it the address of a site you like, or a screenshot, and it reuses the colors, fonts and corner shapes without copying any text or logo.

GitHub sync

A two-way link between a project and a Git repository you control on GitHub. Eqlo sends the full Next.js code, in React and TypeScript, to your repository. Whatever you push there returns to Eqlo as a fresh version. When a tool only offers a one-way export, or charges extra for it, you depend on that tool for every change.

hreflang

A tag that tells search engines which URL serves which language or country. It is useful when the same content exists in, say, English and French, and both versions must point to each other. An Eqlo site is written in one language, English or French, and declares that language in its tags. Hreflang only matters if you publish a second version in the other language.

Hydration

The step where JavaScript takes over a page the server has already sent, so that buttons, calendars and carts respond. When the HTML already holds the text, visitors and crawlers see it right away. Trouble starts when hydration is the only way the text appears. On an Eqlo site, forms work even with JavaScript turned off, file uploads included.

Indexation

The moment Google stores a page in its index, which allows it to show the page in results later. It is different from crawling, which is the visit, and from ranking, which is the position. A page can be crawled and still not indexed, and Search Console tells you why. No builder can promise indexation, because a page needs real content first.

llms.txt

A plain-text file at the root of a site that points AI assistants to the pages worth reading. It is a proposal rather than a standard with the weight of robots.txt, and it cannot make up for empty HTML. Eqlo generates an llms.txt file each time you publish, alongside the sitemap and robots.txt.

Multi-tenant

One application used by many customers whose data stays separate, so company A never sees the records of company B. Most software sold by subscription works this way. Eqlo does not provide this separation between client companies: each member has an individual account, and building it falls to a developer working from the exported code. Separation is hard to add later, so plan for it from the first version. Before launch, sign in with two different customer accounts and confirm that neither can see the other's data.

noindex

An instruction, in a meta tag or a server header, that asks search engines not to keep a page in their index. It is the right choice for a thank-you page or a test site. It is a serious problem on a homepage that someone forgot to switch back after launch. A page that carries noindex should not appear in your sitemap either.

Pre-render

Building the HTML of a public page in advance, so the first response already contains the title, the H1, the text and the structured data. This is the main difference between an AI site that Google can read and an empty shell. Eqlo publishes complete HTML pages and refuses to publish a page that does not display without JavaScript.

Prompt

The sentence or the messages you give an AI model. A useful prompt names your trade, your town, the pages you need and what you do not offer. A vague request such as "modern and premium" pushes the model to invent services. In Eqlo, the "Improve my request" button rewrites your text without adding facts, and leaves what is missing in square brackets.

Repo export

Leaving with your project as ordinary files in a Git repository, rather than as a theme locked inside a tool. For an Eqlo site, that means Next.js code in React and TypeScript. For an app, the Expo and React Native source project can be downloaded as well. Every plan includes code export, Free too, so you can host the result elsewhere.

Sitemap

An XML file, usually at /sitemap.xml, that lists the pages you want search engines to find. It must use your live domain and stay up to date as you add or remove pages. Submit it in Google Search Console to speed up discovery. Eqlo creates the sitemap on every publish and stops the publish if it is missing.

SSR

Short for server-side rendering: the server builds the HTML of a page when it is requested, then sends it. Pre-rendering does the same work once, at publish time, for pages that look the same to every visitor. Both put the text in the first response. People often search "SSR vs CSR" when an AI-built site looks finished but Search Console reports empty pages.

Structured data

Information added to the code of a page, usually as JSON-LD, that tells search engines what the page describes: a business, a product, a price. It must match what visitors can see on the page. Eqlo adds business or local business data to the homepage, and product and price data to each product page in the store.

Vibe coding

Describing software in plain language and guiding an AI model by looking at the result, rather than reading each line of code. Andrej Karpathy coined the phrase in February 2025. It can produce a first version the same afternoon. It does not replace acceptance testing, or a review of what the code does before real users arrive.

White label

Delivering a site or app under your own brand, without showing the name of the tool used to build it. Agencies often ask for it, because their clients buy the agency's work and name. White label should never hide who bills what. Before you deliver, tell your client which tool you use and who pays the subscription.

If a word is missing

Start from the closest entry. Rendering questions are covered by pre-render, client-side rendering, SSR and hydration. Store questions are covered by App Store review and closed testing. Ownership questions are covered by repo export, GitHub sync and white label. The AI website builder glossary stays at twenty-four terms so that each one can be explained properly. If you need another term, send it to us through the contact page.

Frequently asked questions

Do I need to know these words before I start?

No. To start, you only need to describe your business, your town and what you offer. The terms help later, when you face a decision such as publishing, getting indexed or releasing an app.

Why does this AI website builder glossary have only twenty-four entries?

Each definition needs room to be useful. These twenty-four terms are the ones that come up most often when people build and publish a site with AI. If a word is missing, send it through the contact page.

Can I quote a definition?

Yes. The page is published as a set of defined terms that search engines can read. If a definition looks wrong, send us the term and the correction through the contact page, and we date the change.

You know the words, now build the site

You get five free projects, with no card. Describe your business in one sentence and Eqlo builds the pages, ready to publish.