Forty public projects you can open, fork and reshape with a few sentences.
Browse templatesSeparate client workspaces, white label, and the Git repo handed over at the end of the engagement.
See the programmePaste a URL. In thirty seconds you see exactly what Google receives before any JavaScript runs.
Check a URLTwenty-four terms that show up when you search for how AI sites are built, indexed, shipped to stores, or handed to a developer. Each entry is written for English queries. It is not a translation of a French list.
The index is alphabetical by the words people type. Open the one you landed on. If you came from a comparison page, start at pre-render, repo export or data residency. If you came from an app brief, start at App Store review and closed testing.
It is not a promise that using the word will make a page rank. It is not a legal memo. Acceptance, residency and store review still have rules you must read at the source. Eqlo uses these terms the way this glossary states them.
The written test a stranger can fail. In an AI build, the model will show a happy path: sign in, book, pay. Acceptance is the rest: sold out, a reviewer login, a tenant who must not see another tenant's rows. If you cannot name the fail, you have a demo. A prompt that never mentions acceptance will keep adding screens instead of finishing one job.
Apple's human and automated check before an iPhone app goes live. Common first-time failures are a binary that is only a website, a login the reviewer cannot use, and a privacy label that does not match the data you collect. Eqlo can block an obvious wrapper and prepare a signed build. It cannot stand in the queue. The listing sits on your developer account.
The URL you tell search engines is the one true address for a document. A self-canonical on the live page keeps preview hosts from splitting the signal. A canonical that points at staging wastes the crawl. After you attach a domain, the preview must not remain the canonical. Check the link element in the first HTML.
The server sends a shell. The browser runs JavaScript, then fetches the copy, then paints the page. Fine for a logged-in app. Fragile for a public page you want indexed. A crawler that stores the first response stores the shell. The fix is a first HTML file that already contains the words. See pre-render and SSR.
Google Play's required test track before a new personal developer account can go to production. Testers install a marked build and you collect the hours Google asks for. Eqlo can produce the Android package. You still run the track on your Play Console. Apple's TestFlight is a different programme with different rules.
Google's field metrics for loading, interactivity and visual stability: Largest Contentful Paint, Interaction to Next Paint, Cumulative Layout Shift. A huge hero video or unsized images will fail on a phone even if the desktop preview looks calm. Pre-rendering helps the document start. It does not shrink a four megabyte slideshow.
Whether a bot is allowed to fetch the URL and follow what it finds. robots.txt, login walls, noindex, and a menu that only exists after JavaScript all reduce crawlability. A sitemap helps discovery. It does not override a disallow. Check: fetch the URL without scripts, then open robots and the sitemap on the same hostname.
The country or bloc where the project's data sits at rest. Eqlo asks you to pick the European Union, the United States or the United Kingdom when you create the project. Teams under GDPR or UK GDPR usually need the region named before the first personal row lands. Residency is not legal advice. It is the first question procurement will ask.
The named tokens and components a team already uses: colour, type, space, buttons, forms. An AI builder that ignores the system will invent a second brand that looks like every other generated UI. Bring the tokens if you have them. Eqlo will not invent a second library on top of one you already named.
A two-way link between the project and a repository you control. A commit you make at 23:00 is in the project in the morning. Preview deploys follow the branch. If sync is one-way, or export is a paid extra, you are closer to a rental. Eqlo treats the repo as yours.
Annotations that tell search engines which language or region URL is the counterpart of another. They must be reciprocal. A page with no counterpart must not invent an alternate. Pointing every alternate at a homepage is a common self-inflicted duplicate. Two locales with the same paragraph are two URLs that compete, not a strategy.
After the server has sent real HTML, the browser attaches event handlers so the page becomes an application. Done well, the visitor already saw the words. Hydration is not the enemy of SEO. Hydration instead of a document is. If you disable JavaScript and the copy vanishes, you client-rendered.
Google has stored the URL as a document it may show. It is not a ranking. A page can look finished and never be indexed if the stored file is empty. AI builders that promise "we submit to Google" are describing a sitemap ping, not a place in the results. See crawlability and pre-render.
A proposed plain-text file at the origin that tells AI assistants which pages to read. It is not a standard with the weight of robots.txt, and it will not repair an empty first HTML. Eqlo generates one on publish. You still decide which URLs belong in it.
One application, many customers, with rows scoped so company A cannot see company B. For a SaaS MVP this is not a later hardening. Eqlo scopes data to a workspace from the first version when you ask for accounts. If you build a single-user app and split it later, you will rebuild the queries.
A robots meta tag or header that tells engines not to store the URL. Correct on a thank-you page or a staging host. Fatal on a homepage you forgot to flip after launch. Check the live head of the first HTML. A sitemap that lists a noindexed URL is a mixed message.
The public page is turned into HTML at publish time, so the first response already contains the title, the H1, the copy and the structured data. This is the main difference between an AI site that can be indexed and a client-rendered shell. Eqlo pre-renders marketing pages. Verify it: disable JavaScript, reload, read the words.
The sentence or brief you give the model. A useful prompt names the user, the job, the pages, a real example, and what must not appear. After the first pass, change one thing at a time. A transcript is not a specification. See vibe coding.
You leave with a Git repository of ordinary files, not a locked theme. For Eqlo that means React and TypeScript, and React Native when the project is an app. You can host it elsewhere. If export is missing or formatted so only the vendor can run it, you rented the result.
An XML list of URLs you want discovered, usually at /sitemap.xml. It is a hint. It must list the live hostname, not the preview, and stay in sync when you add or retire a page. Submit it in Search Console. If it is absent, the crawler is guessing.
Server-side rendering: the server composes the HTML for this request, then sends it. Related to pre-render, which often happens at build time for pages that do not change per visitor. Both put words in the first response. For a public brochure, pre-render is usually enough. People search "SSR vs CSR" when an AI site looks finished and Search Console disagrees.
Machine-readable JSON-LD that names the page as a Product, FAQPage, LocalBusiness or HowTo. It must match what a human can see. A LocalBusiness block on a site with no address is a lie. Eqlo writes structured data that follows the page type. You still correct the facts inside it.
Describing software in natural language and steering a model by running the result, rather than by reading every diff. Andrej Karpathy named the habit in February 2025. It enables a first version the same afternoon. It does not replace acceptance, a repo you can leave, or a first HTML a crawler can read. Eqlo uses the loop and still produces files a reviewer can reject. The longer page on this site is the encyclopedia, not this entry.
The preview or the shipped site does not announce the builder's name. Agencies ask for this when procurement wants the studio's brand. White label is not a hidden second invoice. Eqlo does not bill your client unless you add them as a payer. Ask who the customer sees before you send the Thursday URL.
Start from the closest entry and follow the related page. Rendering problems live under pre-render, client-side rendering, SSR and hydration. Store problems live under App Store review and closed testing. Commercial problems live under repo export, white label and data residency. The vibe coding page is the practice. The SEO page is the ranking argument. This list stays at twenty-four so each definition can be long enough to use. If you needed a twenty-fifth word, write to contact and say which English query it should serve.
Because a hundred thin definitions help nobody. These twenty-four match English searches we actually see around AI builders. The French glossary is a different list, written for French queries, not a copy of this one.
Yes. The page publishes a DefinedTermSet. If a definition is wrong, write to contact with the term and the correction. We will date the change.
No. The useful work is still a fetchable document, which is pre-render and crawlability. A separate marketing acronym did not earn a slot over those two.
Five free projects, no card. Open view-source on the preview if the term you came for was pre-render.