Professional Web glossary
Understand the language of the Web, from A to Z.
SEO, SXO, artificial intelligence, hosting, servers, cloud, development, analytics and digital marketing: this bilingual reference library explains the terms used to build, promote, secure and improve a website.
Each definition is concise enough to be scanned quickly and precise enough to clarify a brief, a quotation, a technical discussion or a content strategy.
→
420 terms explained
420terms explained
26letters available
11topic families
2French and English
Browse the glossary
Browse the glossary
Each definition is concise enough to be scanned quickly and precise enough to clarify a brief, a quotation, a technical discussion or a content strategy.
420 terms displayed
No term matches these criteria.
C30 terms displayed
Cache→
Cache-Control→
Call to action→
Canonical URL→
CAPTCHA→
CDN→
Chatbot→
Click depth→
Click-through rate→
Client→
Cloud computing→
CLS→
CMS→
CNAME→
Compression→
Consent Mode→
Content gap→
Content marketing→
Conversion→
Conversion funnel→
Conversion rate→
Cookie→
Core Web Vitals→
Crawl budget→
Crawler→
CRM→
CSP→
CSS→
Customer journey→
Cybersecurity→
S37 terms displayed
SaaS→
Schema.org→
Search engine→
Search engine optimization→
Search intent→
Search operator→
Search volume→
SEM→
Semantic HTML→
SEO→
SEO audit→
SEO ranking→
SERP→
Server→
Server-side rendering→
Serverless→
Session→
Session replay→
SFTP→
Sitemap XML→
SLA→
Slug→
SMTP→
Social media marketing→
Soft 404→
Source code→
Spam→
SQL→
SSH→
SSL/TLS→
SSL/TLS certificate→
Staging→
Static site→
Streaming→
Structured data→
Subdomain→
SXO→
Editorial method
Definitions written for people, structured for machines.
The entries are editorially reformulated in plain language, connected to stable URLs and represented with DefinedTerm structured data. They provide orientation, not a substitute for official standards, legal advice or vendor documentation.
FAQ
Questions about the glossary
The glossary covers the vocabulary used to plan, create, publish, promote, measure, host and secure websites. Its categories include Web fundamentals, content, accessibility, user experience, development, infrastructure, cloud services, cybersecurity, search optimisation, paid search, analytics, artificial intelligence and digital business. Terms were selected because they appear in project discussions, proposals, documentation and professional tools. The catalogue is broad but not exhaustive, and one term may belong to several fields. Definitions focus on the meaning most useful in a website context; a specialist discipline may use a narrower or more technical interpretation. Aliases and related wording support discovery, while the category pages and alphabet provide different ways to explore the collection.
Yes. The main glossary index searches names, aliases and categories across all entries directly in the browser. A query can therefore find a concept even when the preferred term begins with a different letter. On an individual letter page, the search is limited to that part of the catalogue, and the alphabet links return to other sections. Search text is not sent to a third-party engine. If no result appears, try a shorter expression, an English or French equivalent, an acronym or a broader concept. The index is intended for orientation rather than full-text research inside every definition, so a neighbouring term may also contain the explanation needed.
No. They are concise editorial explanations designed to help readers understand a brief, quotation, technical discussion or content strategy. Some terms have a formal definition in a standard, law, protocol or provider documentation; others are industry shorthand whose meaning changes with context. When accuracy is important, the linked or named primary documentation remains authoritative. Legal, security, accessibility and infrastructure decisions may also require a qualified professional assessment. The glossary aims to explain what a term usually means, why it matters and how it relates to a website, without replacing normative text, contractual documentation or specialist advice. Definitions should be reviewed when technologies and usage evolve.
Yes. The main index and every alphabet page have a French counterpart connected through the language selector and hreflang metadata. The two versions are editorial adaptations rather than automatic word-for-word translations. A technical term may keep its English name in French practice, use an established French equivalent or require both forms to avoid ambiguity. Aliases help readers find these variations. Because professional usage differs between countries and communities, the surrounding explanation prioritises clarity and may provide a different example in each language while preserving the same underlying concept.