Search
Enter at least two characters without personal information.

    LibraryArticles & FAQ Your projectRequest a quote
    LanguageEN
    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.

    People reviewing documents and layouts on a table 660 terms explained
    660terms explained
    26letters available
    11topic families
    10available languages

    Explore the glossary by topic

    A reading path · Useful distinctions · Use the vocabulary to make a decision.

    Several devices displaying web pages

    Understand Web fundamentals

    URL, browser, HTTP, domain and status: connect Web vocabulary to a page that can actually be visited.

    21 concepts linked to their definitions

    Notebook, brochure and tablet before campaign notes

    Understand marketing and acquisition

    Audience, campaign, landing page and conversion: connect a promise with an action that is actually useful.

    48 concepts linked to their definitions

    Two people working on a laptop

    Understand development and code

    HTML, scripts, APIs and failure states: connect website components to verifiable behaviour.

    101 concepts linked to their definitions

    Security token and backup drive

    Understand security and privacy

    Identity, permissions, protections and recovery: connect security terms to actual website journeys.

    63 concepts linked to their definitions

    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.

    660 terms displayed

    Explore by decision

    Where to begin in each subject.

    The alphabet helps you find a word; these subject routes help you connect a definition with a real check or decision.

    Web fundamentals

    Understand what the browser requests, receives and displays before diagnosing a page.

    • Does the address return the intended resource?
    • Does the HTTP status accurately describe the outcome?

    Start with : URL · HTTP status code

    SEO, search and visibility

    Connect search, crawling and page usefulness without reducing the work to a score or tag.

    • Does the page answer an identifiable need?
    • Is an obstacle preventing discovery or reading?

    Start with : AI discoverability · Crawl budget

    Marketing and acquisition

    Choose a promise and next action that match what the visitor needs.

    • Does the page fulfil the promise that led to the click?
    • Does the measured action represent real progress?

    Start with : Landing page · Conversion

    Content and communication

    Structure content that the team can classify, find, review and maintain.

    • Does a new entry have a clear category?
    • Who reviews information as it ages?

    Start with : Taxonomy · Content lifecycle

    Design, UX and accessibility

    Design journeys that make sense with or without a mouse and across screen sizes.

    • Can someone find the right information?
    • Do controls announce their purpose clearly?

    Start with : Information architecture · Accessible name

    Development and code

    Distinguish a page’s native structure from behaviour added by scripts.

    • Does the HTML describe elements correctly?
    • What remains usable if a script fails?

    Start with : HTML · JavaScript

    Hosting and infrastructure

    Identify the services that make a site available and who owns each change.

    • Which functions depend on a DNS record?
    • Is the cache serving the correct content version?

    Start with : DNS · Cache-Control

    Security and privacy

    Connect protections to the actual journeys, components and data in use.

    • Does a rule block a legitimate function?
    • How does someone recover an account?

    Start with : CSP · Passkey

    Data and measurement

    Define useful measures and their limits before making decisions from a dashboard.

    • Does the event match a real action?
    • Does the measure describe real visitors or a lab test?

    Start with : Event tracking · Field data

    Artificial intelligence

    Evaluate generated answers against sources, examples and success criteria.

    • Can important facts be verified?
    • Does the test cover real cases and errors?

    Start with : Grounding · AI evaluation

    Project, product and business

    Turn a project idea into a testable result before committing to every feature.

    • Who accepts the result and through what test?
    • What minimum version verifies the hypothesis?

    Start with : Acceptance criteria · MVP

    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

    It explains Web content, design, development, infrastructure, security, measurement, search and AI terminology. Definitions are grouped by topic and letter, with aliases, practical examples and references where available. Use a term’s permanent link to return directly to its explanation.

    Yes. The main index searches the catalogue across letters and can be narrowed by category. On a letter page, filtering applies to the definitions displayed there. Check the result count and clear the filter if needed. Alphabet links and definitions remain available without JavaScript.

    No. These are editorial explanations for understanding a project or discussing a deliverable. The cited specification or publisher remains the source for exact syntax, requirements and current behaviour. A practical example illustrates a limited case; it is not a complete implementation or evidence of compliance.

    Yes. French and English pages are connected through the language selector, alongside the site’s other languages. Labels can differ because professional usage varies. Aliases help connect common forms; the explanation and context matter more than assuming that one translated word has exactly the same scope everywhere.