Website & Technology Terminology

CATEGORY 1 — Website Basics

Accessibility: Design and coding practices that make a website easier to use for people with disabilities. Examples include readable contrast, keyboard navigation, descriptive labels, and proper heading structure.
Back End: The behind-the-scenes part of a website or service. It may process forms, send email, store data, manage logins, or perform other work that visitors do not see directly.
Content Management System (CMS): Software that lets authorized users edit website content through an administrative screen instead of changing code directly. A CMS is useful when non-technical staff need to update pages, posts, images, or other content.
Dynamic Website: A website that creates or changes pages using server-side software, a database, or a content management system. WordPress is a common example of a dynamic website platform.
Favicon: The small icon associated with a website. It commonly appears in browser tabs, bookmarks, and some search or device interfaces.
Front End: The part of a website that visitors see and use in their browser — the layout, text, images, menus, buttons, forms, and other visible elements.
Responsive Design: A way of building a website so it automatically adapts to different screen sizes. A responsive site should remain usable on desktop computers, tablets, and mobile phones.
Source Code: The editable files used to create a website or application. Keeping source code organized and backed up makes future changes, troubleshooting, and recovery much easier.
Static Website: A website made from finished files that are delivered directly to a visitor’s browser. Static sites usually do not need WordPress or a database to build each page on demand, which can make them fast, secure, and easier to host.
Webpage: One individual page within a website, such as a Home, About, Services, or Contact page. Each page normally has its own web address, or URL.
Website: A collection of pages and files that people reach through a web address. A website can contain text, images, forms, documents, videos, and other information or tools.
Website Stickiness: The ability of a website to keep visitors interested and encourage them to spend more time exploring its pages or return again later. Useful information, easy navigation, interactive tools, related content, and regularly updated resources can all make a website more “sticky.”
WordPress: A widely used content management system. It can be very flexible, but it also requires regular updates to WordPress itself, themes, and plugins, and it usually depends on a database and server-side software.

CATEGORY 2 — Hosting, Deployment & Source Control

Build: An automated process that prepares website source files for production use. A build may organize files, optimize assets, compile code, and create the final version that is deployed.
Cloud Hosting: Hosting that uses cloud-based infrastructure rather than relying on one traditional web server. It can provide flexible deployment, distribution, and reliability options.
Cloudflare Pages: A hosting and deployment service used for static websites and related web functions. A site can be connected to a source-code repository so approved changes are automatically built and published.
Commit: A saved checkpoint in version control. A commit normally groups one or more related changes with a short description of what was changed.
Content Delivery Network (CDN): A network of servers in different locations that stores and delivers copies of website files from a location closer to the visitor. A CDN can help pages load faster, reduce load on the main hosting service, and improve resilience.
Deployment: The process of taking an approved website change and publishing it so visitors can see it. A deployment may be automatic after a GitHub update or may be started manually, depending on the setup.
Development / Preview Site: A private or temporary version of a website used to review changes before they are placed on the live domain. This reduces the risk of testing unfinished work on the public site.
GitHub: An online service used to store and manage source code. It provides a history of changes and can connect directly to hosting platforms for automated deployment.
Production Site: The live version of a website that the public reaches at the normal domain name.
Repository: A project folder in a source-control system such as GitHub. It contains the website files and a history of approved changes.
Version Control: A system that records changes to website files over time. It helps identify what changed, who changed it, and allows earlier versions to be recovered when necessary.
Web Hosting: The service that makes website files available on the internet. Different types of hosting are suited to different website platforms and levels of complexity.

CATEGORY 3 — Domains, DNS & Web Addresses

301 Redirect: A permanent redirect. It tells browsers and search engines that an old address has permanently moved to a new address.
404 / Not Found: The response shown when a requested page or file does not exist. A proper 404 helps visitors and search engines understand that the address is not valid.
A Record: A DNS record that points a name to an IPv4 address. It is often used to direct a domain or subdomain to a web service.
Apex / Root Domain: The domain without a prefix such as www. For AmeriHost, the apex domain is amerihost.com.
CNAME Record: A DNS record that makes one hostname act as an alias for another hostname. It is commonly used for services such as www or hosted platforms.
DNS (Domain Name System): The internet’s addressing system. DNS tells computers where to find a website, where to deliver email, and how other domain-based services should be reached.
DNS Record: An individual instruction in DNS. Different record types tell internet services where websites, email, verification information, and other services are located.
Domain Name: The easy-to-read internet name for a website or email system, such as amerihost.com. A domain name is separate from the website hosting itself.
Domain Registrar: The company through which a domain name is registered and renewed. The registrar maintains the registration record, while DNS may be managed at the registrar or through another provider.
HTTPS: The secure version of the web protocol used between a visitor’s browser and a website. HTTPS encrypts information in transit and is now the normal standard for public websites.
MX Record: A DNS record that tells the internet which mail servers receive email for a domain. MX records should not be changed casually because doing so can interrupt incoming email.
Nameservers: The servers that are authoritative for a domain’s DNS records. Changing nameservers can move DNS management from one provider to another, so it must be done carefully to avoid disrupting websites or email.
Redirect: An instruction that sends a visitor from one web address to another. Redirects are useful when pages move, domains change, or www and non-www addresses need to be standardized.
SSL/TLS Certificate: A digital certificate that allows a website to use HTTPS and helps prove that the browser is communicating with the intended domain. Modern hosting platforms often manage these certificates automatically.
Subdomain: A name added before the main domain to identify a separate service or section, such as support.example.com or shop.example.com.
TTL (Time to Live): A DNS setting that tells other systems how long they may keep a DNS answer before checking again. Lower or higher TTL values can affect how quickly DNS changes are noticed across the internet.
TXT Record: A DNS record that stores text information. TXT records are commonly used for email security, ownership verification, and service configuration.
URL (Web Address): The complete address of a page or file on the internet. For example, https://amerihost.com/contact/ is the URL for the AmeriHost Contact page.
www: A common subdomain used for websites. Many sites are configured so www.example.com automatically redirects to example.com, or the reverse, so visitors consistently use one preferred address.

CATEGORY 4 — Business Email & Email Authentication

Business Email: Email that uses a company’s own domain, such as [email protected], rather than a free consumer address. It presents a consistent company identity and can be managed separately from the website.
DKIM: An email-authentication method that adds a digital signature to outgoing messages. Receiving systems can use DNS information to confirm that the message was authorized by the domain.
DMARC: An email policy that works with SPF and DKIM. It tells receiving mail systems how to handle messages that fail authentication and can provide reports about possible misuse of a domain.
Email Alias: An additional email address that delivers to an existing mailbox. An alias normally does not have its own separate inbox unless the provider specifically configures one.
Email Forwarding: A rule that automatically sends mail received at one address to another address.
IMAP: A common method for reading and synchronizing email across multiple devices. Messages generally remain stored on the mail server so the mailbox stays consistent on phones, computers, and webmail.
Mail Server: A system that sends, receives, or stores email. A company’s website and its mail server can be hosted by completely different providers.
Reply-To: An email setting that tells a recipient where a reply should go. For a website form, the message can come from the website’s authorized sending address while Reply-To is set to the visitor’s address.
SMTP: The standard method used to send email between systems. Websites and applications may use an SMTP service or an email API when they need to send messages.
SPF: An email-authentication DNS record that identifies which systems are allowed to send mail for a domain. It helps receiving mail systems detect unauthorized senders.
Transactional Email: Automated email sent because of an action on a website, such as a contact-form notification or confirmation message. It is usually handled separately from normal employee-to-employee business email.
Webmail: A browser-based way to access email without installing a separate email program.

CATEGORY 5 — Forms, Security & Behind-the-Scenes Services

API (Application Programming Interface): A defined way for one software system to communicate with another. For example, a website can use an API to send an email or verify a security check.
API Key: A private code used to authorize access to a software service. API keys should be stored securely and should never be exposed publicly in website source that runs in the browser.
Application Allowlisting: A security approach that allows approved programs and processes to run while blocking unknown or unauthorized ones. It is a different strategy from relying only on lists of known malware.
Bot / Spam Protection: Measures designed to reduce automated form submissions, fake requests, and other unwanted activity. Common techniques include security challenges, rate limits, validation, and hidden fields.
Cloudflare Pages Function: A serverless function that runs alongside a Cloudflare Pages website. It can process forms, validate requests, call other services, and perform work that should not be exposed in browser code.
Cloudflare Turnstile: A website security check used to distinguish legitimate visitors from automated abuse. Depending on its mode and the visitor’s risk level, it may run quietly or display a visible verification widget.
Endpoint Security: Security software and policies that protect business computers and other endpoints from malicious or unauthorized activity. Endpoint security is separate from website security, although both are parts of a broader security plan.
Environment Variable: A configuration value stored outside the normal website code. Environment variables are commonly used for email addresses, settings, and other values that may differ between development and production.
Form Validation: Checks that make sure submitted information is present and in an expected format. Good validation occurs in the browser for convenience and again on the server for security.
Honeypot Field: A form field that normal visitors do not see and should leave empty. Automated bots sometimes fill it in, which can help a website identify and reject spam submissions.
Malware: Software intentionally designed to damage systems, steal information, disrupt operations, or gain unauthorized access.
Secret: A protected configuration value such as an API key or private token. Secrets are intentionally hidden from public code and should be handled as confidential information.
Server-Side Processing: Work performed away from the visitor’s browser on a trusted server or cloud service. This is where sensitive tasks such as sending email or validating security tokens should normally occur.
Serverless Function: A small piece of back-end code that runs only when needed, without requiring a traditional always-running server. It is well suited to tasks such as processing website forms.
Web Form: A set of fields on a website that lets a visitor send information, such as a contact request. A secure form normally validates the information and sends it through a protected server-side process.

CATEGORY 6 — Search, SEO & Site Organization

Breadcrumb: A small navigation trail that shows where a visitor is within the site, such as Home > Services > Website Design. Breadcrumbs can help both visitors and search engines understand site structure.
Canonical URL: The preferred address for a page when similar or duplicate addresses could exist. A canonical tag helps search engines understand which version should be treated as the main one.
Core Web Vitals: A set of Google measurements related to real-world page experience, including how quickly important content appears, how responsive the page feels, and whether the layout shifts unexpectedly.
Google Search Console: A Google service that helps website owners verify ownership, submit sitemaps, inspect indexing, and review how Google sees a website in search.
Indexing: The process by which a search engine analyzes a webpage and adds information about it to its searchable database. A page can be publicly available before it has been indexed.
Internal Link: A link from one page of a website to another page on the same website. Useful internal links help visitors move through related information and help search engines understand how pages are connected.
Meta Description: A short summary placed in a webpage’s code. Search engines may use it as descriptive text in search results, although they can choose different text when they believe it better matches a search.
Open Graph Metadata: Information in a webpage’s code that helps control how the page may appear when shared on social networks or messaging platforms, such as its title, description, and image.
Page Title / SEO Title: The title associated with a webpage in browser tabs and search-engine results. A good title describes the page clearly and helps distinguish it from other pages on the site.
Robots.txt: A small file that gives search-engine crawlers instructions about areas of a website they should or should not crawl. It is guidance for crawlers, not a password or security system.
Search Engine Crawler: Automated software used by search engines to discover and read webpages. Crawlers follow links, inspect site files, and collect information that may later be used in search results.
SEO (Search Engine Optimization): The practice of organizing website content and technical details so search engines can understand the site and people can more easily find relevant pages in search results.
Sitemap.xml: A machine-readable list of important website URLs. It helps search engines discover the pages a site owner wants them to know about.
Structured Data / Schema: Machine-readable information added to a webpage to describe things such as an organization, breadcrumb trail, product, event, or other content in a standardized format that search engines can understand.

CATEGORY 7 — Maintenance, Reliability & Recovery

Backup: A separate copy of important website files, databases, or configuration that can be used if the working version is lost, damaged, or corrupted.
Cache: A temporary stored copy of website data that helps pages load faster. Because cached information can remain for a period of time, a recent website or DNS change may not appear everywhere immediately.
Cutover: The point at which traffic is switched from an old website or service to the new one. DNS changes are often part of a website cutover.
Migration: Moving a website, domain, email service, or other system from one platform or provider to another. A good migration plan considers DNS, email, redirects, testing, and rollback options before the cutover.
Monitoring: Automated or manual checks used to watch the health, availability, performance, or security of a website or online service.
Propagation: The period during which a DNS change is being noticed by resolvers and networks across the internet. Different users may temporarily receive different answers until cached records expire.
Recovery: The process of restoring a website or service after a failure, accidental change, security event, or data loss.
Uptime: The amount of time a website or service is available and operating normally.