Shared vocabulary for describing entities, content and relationships in a structured form understood by several search engines. Choose a type matching the described object, then suitable properties. A valid vocabulary does not guarantee that every search engine uses every property.
Use of HTML elements according to their role: headings organise documents, links lead to destinations and buttons trigger actions. Meaning does not depend only on appearance. Correct semantics aids interpretation but still requires usable labels and behaviours.
In practice: start with the questions a page answers and any crawl barriers before changing tags.
Guide: Validate structured data on a website→Also searched as : référencement naturel optimisation moteurs seo search engine optimization Référencement naturel Search engine optimization referencement-naturel
Results page presented by a search engine in response to a query. It may combine links, images, advertisements or other features depending on the engine and context. An observed position belongs to that particular search and does not necessarily represent what every user sees.
In practice: record the query, date, language and search context when examining a result. Compare its title and description with the destination page; an isolated screenshot is insufficient to measure a visibility trend.
Software or a system handling client requests and providing responses. Server availability differs from business-operation success: a responding page may still show an application error.
Timestamped record of requests or events processed by a server, used for diagnosis, security and crawl analysis. Record format, time zone and observed layer. Proxy and application logs may describe different stages of the same request.
Production of HTML on the server before sending it to the browser. Initial content can be read without waiting for JavaScript to construct it. This can coexist with client-side interactions; it does not alone guarantee speed, accessibility or fresh data.
Script separate from the page, running in a secure context and able to handle certain requests within its scope. It can serve cached resources. Its installation and activation lifecycle requires testing older open pages, updates and errors; it does not automatically create reliable offline use.
Context linking requests to a continuing interaction, often using an identifier stored in a cookie. Sign-in, renewal, expiry and logout have distinct effects. Validity and permissions need server-side checks; a cookie’s presence does not establish continued access.
Browser key-value storage associated with an origin and a page session in a tab. It normally survives a page reload and ends with that tab’s page session.
File transfer protocol using encrypted SSH transport, with server and user authentication according to configuration. It supports sending and retrieving remote files. It differs from FTPS, which protects FTP using TLS; similar names do not make their settings interchangeable.
In practice: confirm the protocol, host and permitted directory, then transfer a sample file and check its destination. Verify server identity and restrict the account to required operations; file access is distinct from administrator access.
Image offered to platforms to accompany a page link in a sharing preview. Open Graph metadata can provide its address and alternative description. Each platform controls rendering and caching, so including the tag does not guarantee identical display everywhere.
In practice: test a specific page with its title, image and description. Check that the visual remains understandable when cropped and its URL is reachable; an old preview may persist in a platform’s cache after replacement.
File listing important website URLs and able to provide search engines with discovery or update information. Include useful canonical URLs and justified modification dates. A sitemap helps discovery without requiring the engine to index the pages.
HTML indication of an image’s expected display width when srcset uses width descriptors. It helps the browser select a file for the stated conditions. It does not set CSS image width; an inaccurate hint can cause unnecessarily large transfers.
Service Level Agreement: contractual commitment defining a level of service, availability or response time.
Apply this term to a comparison
Check covered events, interventions, measurement and request handling. Compare identical commitments before prices; an advertised percentage does not describe all support.
Readable part of an address identifying content, often derived from its title, such as workshop-hours. A slug forms part of a complete URL alongside the domain and any directories. Changing it can break existing links, so changing a title need not automatically change the address.
In practice: choose a short, explicit and durable label before publishing. When a change is necessary, check internal links and the previous address; retain a relevant redirect to equivalent content rather than sending everything to the homepage.
Page that appears missing or useless in its content while returning a successful HTTP status instead of a true 404 error. Compare the HTTP status with actual rendered content. An empty page or one announcing missing content can be treated as an error despite a 200 response.
Structured inventory of software components and dependencies used to track versions, licenses and vulnerabilities. Tie the inventory to a precise release and generation scope. A valid document proves neither completeness nor absence of vulnerabilities.
Rule determining the sequence of items in a list, such as date followed by name. When several items share a value, a stable additional criterion avoids unpredictable movement. Without explicit ordering, the order returned by a database query should not be treated as guaranteed.
In practice: test several records sharing a date, then move to the next page. Check that items are neither skipped nor repeated, ascending or descending direction is clear, and ordering survives filter changes.
Email authentication mechanism through which a domain publishes servers authorised to use its SMTP envelope identities. It does not guarantee delivery or alone validate the visible From domain.
HTML attribute offering alternative image files with width or density descriptors. The browser selects according to context. Candidates should represent a consistent image and declare actual dimensions; providing more files does not guarantee a better selection.
Digital certificate associating a domain name with a public key and enabling a browser to verify a server’s technical identity during a TLS connection. Validity, the trust chain and server configuration matter together. A valid certificate does not establish that content is truthful or a business trustworthy.
In practice: check every hostname used, the expiry date and automatic renewal. Also test resources loaded by the page: a page reached over HTTPS may still request elements through HTTP addresses.
Minimum amount attached to an actually available, described scope. Without a reference case and exclusions, it can misleadingly appear comparable to other offers.
Apply this term to a comparison
Find the exact scope behind the starting price, then the items required by the real project. Do not copy a promotional amount as full cost when duration, options or conditions remain unclear.
A site whose main responses come from files prepared in advance. It can still run JavaScript and call services; static does not mean free of forms or external dependencies.
Media transmission allowing playback while data arrives. It can serve live or recorded content; startup delay, buffering interruptions and delay behind a live event are separate concerns.
Data embedded in page code according to a defined vocabulary to make entities and properties explicit to machines. Match declared values to content available to visitors. Describing a price, review or date does not remove the need to verify its source.
Check of syntax, expected properties and consistency between structured markup and visible content. Distinguish vocabulary conformance from eligibility for a search feature. An error-free test guarantees neither rich display nor indexing.
Part before a domain distinguishing a service or area, such as shop.example.fr. Its use can need separate DNS settings, a certificate and access rules.
A message reporting a submission outcome. Its wording should match the established state, such as received or pending; a displayed screen alone does not prove email delivery.
Mechanism allowing the browser to compare a loaded resource with an expected hash before use. Modified content can be rejected. Matching confirms expected bytes, not freedom from vulnerabilities in that version; an update may require a new hash.
Text displayed in time with media. Accessibility captions convey speech and meaningful sounds; a separate transcript does not provide the same function during playback.
Monitoring through automated scenarios run at defined times and locations. It can detect repeatable regressions and complements user observation without reproducing every usage condition.
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.
