The Web Design & Development Glossary

A 301 is a permanent server-side redirect that sends both visitors and search engines from an old URL to a new one. When a page or whole domain moves, a proper 301 passes along the link authority the old URL earned, so bookmarks, inbound links and rankings follow you to the new address instead of dying in a 404.

A DNS record that maps a domain name to an IPv4 address — the line that says “example.com lives at this server.” (Its IPv6 cousin is the AAAA record.) Change the A record and you change where the whole world’s browsers go when they type your name.

The part of a page a visitor sees before scrolling. The term is borrowed from newspapers. It still matters: your headline, your promise and a clear next step should live up here, because a large share of people decide whether to stay in the first few seconds.

Designing and building so that people with disabilities — visual, motor, auditory, cognitive — can actually use your site. Good accessibility (screen-reader support, keyboard navigation, sufficient contrast) is both the right thing to do and, increasingly, a legal expectation. It also tends to make a site better for everyone.

The written description attached to an image (alt="..."). Screen readers read it aloud, search engines use it to understand the picture, and it’s what shows if the image fails to load. Describe what the image communicates, not just what it literally is.

The visible, clickable words of a link. “Click here” tells a search engine nothing; descriptive anchor text (“our Shopify setup guide”) tells both people and Google what’s on the other end.

Application Programming Interface — a defined way for two pieces of software to talk to each other. When your contact form sends mail through SendGrid, or your store pulls live shipping rates, it’s happening over an API. APIs are how modern sites stitch services together instead of building everything from scratch.

Accessible Rich Internet Applications — a set of HTML attributes (role, aria-label, aria-expanded…) that describe interactive widgets to assistive technology. The first rule of ARIA is to use native HTML where you can and reach for ARIA only when you can’t.

Everything that runs on the server, out of the visitor’s sight: databases, application logic, APIs, authentication. The backend decides what data to show; the frontend decides how it looks.

A link from another website to yours. Search engines treat them as votes of confidence: the more relevant, trustworthy sites that point to you, the more authority you tend to accumulate. A handful of links from respected sources beats a thousand from junk.

The amount of data transferred between your site and its visitors over a period of time. Traditional hosts meter and bill it; modern static platforms like Cloudflare Pages don’t cap it at all, which is one reason a fast static site can absorb a traffic spike without a surprise invoice.

The share of visitors who land on a page and leave without interacting further. A high bounce rate isn’t automatically bad — someone may have gotten exactly the answer they needed — but on a sales page it usually signals a mismatch between what you promised and what they found.

More than a logo. It’s the consistent system — mark, colors, typography, voice and the feeling people get — that makes your business recognizable and trustworthy across every touchpoint, online and off.

The small “Home › Blog › This Post” trail near the top of a page. It helps visitors understand where they are and gives search engines a clear picture of your site’s structure.

A screen width at which a responsive layout changes — say, where a three-column grid collapses to one column on a phone. Good breakpoints are chosen by where the content starts to break, not by chasing specific device sizes.

A stored copy of content kept close to where it’s needed so it doesn’t have to be regenerated or re-fetched every time. Browsers cache assets, servers cache pages, and CDNs cache your whole site at the edge. Caching is the single biggest lever for perceived speed.

The practice of serving those stored copies. On WordPress a caching plugin turns dynamic PHP pages into static HTML so visitors aren’t waiting on the database every load; on a static or CDN-backed site, caching is essentially built in.

The specific thing you want a visitor to do next — “Get a quote,” “Add to cart,” “Book a call.” Every meaningful page should have one obvious, primary CTA. If everything is emphasized, nothing is.

The single “official” address for a piece of content when several URLs could show the same thing. A <link rel="canonical"> tag tells search engines which version to credit, preventing your own pages from competing with each other.

The broader process of collapsing the many possible forms of a URL (with/without www, with/without a trailing slash, http vs https) down to one standard form. Without it, example.com and www.example.com can be treated as two different sites splitting the same authority.

Content Delivery Network — a fleet of servers spread around the world that each keep a cached copy of your site. A visitor in Sydney is served from a nearby node instead of waiting on a server in Virginia. Cloudflare runs one of the largest; it’s why edge-hosted sites feel instant everywhere.

Cumulative Layout Shift — a Core Web Vital that measures how much your page jumps around as it loads. The annoying moment when you go to tap a button and an ad shoves it down? That’s CLS. Reserving space for images and embeds keeps it near zero.

Content Management System — software that lets non-developers create and edit site content without touching code. WordPress is the best-known, but the category ranges from Shopify (for stores) to headless systems that feed content to a custom front end.

A DNS record that points one name at another name rather than an IP address — e.g. www as an alias of your apex domain, or a custom domain pointed at a pages.dev host. Handy, with one classic gotcha: a strict CNAME isn’t allowed on a bare apex domain (providers like Cloudflare work around it with “CNAME flattening”).

Shrinking files before they’re sent. Text assets are squeezed with Gzip or Brotli; images with formats like WebP. Less data over the wire means faster loads — often the easiest performance win available.

The moment a visitor takes the action that matters to you — buys, books, subscribes, fills out the form. Everything else on the site exists to make conversions more likely. Define yours before you measure anything.

The percentage of visitors who convert. If 1,000 people visit and 25 buy, that’s a 2.5% conversion rate. Doubling it is usually cheaper than doubling traffic, which is why design and copy quality pay for themselves.

Google’s trio of real-world experience metrics — loading (LCP), interactivity (INP) and visual stability (CLS). They factor into rankings and, more importantly, into whether visitors stick around. A well-built site passes them comfortably.

The control panel many traditional hosts use to manage websites, email, databases and DNS. cPanel manages a single account; WHM is the reseller/admin layer above it that creates and manages those accounts. Powerful, but a reminder that you’re on shared, server-managed infrastructure.

An automated program that visits and reads web pages — Googlebot being the famous one. Crawlers follow links, index what they find, and build the database that powers search. Your job is to make their path clear with clean links, a sitemap and sensible robots.txt rules.

Cascading Style Sheets — the language that controls how a site looks: layout, color, type, spacing, animation. HTML is the structure; CSS is the styling laid over it. Clean, well-organized CSS is the difference between a site that’s easy to evolve and one that fights every change.

See Call to Action. The single most important — and most often neglected — element on a page.

An organized store of your site’s data — posts, products, users, orders. WordPress uses MySQL/MariaDB; every query to it takes time, which is why database-driven sites lean on caching and why a purely static site (no database to query) is inherently quicker.

Distributed Denial of Service — an attack that floods a site with bogus traffic from many machines at once to knock it offline. Sitting behind a network like Cloudflare is the standard defense; it absorbs and filters the flood before it reaches your server.

To publish your code or content to the live environment so the public can see it. Modern workflows let you deploy in seconds and roll back just as fast — a far cry from the days of dragging files over FTP and hoping.

A generic HTML container (<div>) used to group and lay out content. It’s the workhorse of page structure — but reach for semantic elements (<header>, <nav>, <main>, <article>) first; they tell browsers and screen readers what a section actually is.

The Open Directory Project — the first large, human-edited web directory. It shaped early SEO and shut down in 2017. We list it because you’ll still bump into references to it in old advice; treat that advice with suspicion.

Domain Name System — the internet’s phone book. It translates the human name you type (wandzilakwebdesign.com) into the numeric IP address machines use. When you “point a domain” somewhere, you’re editing DNS records. Changes can take minutes to hours to propagate.

A third-party score (popularized by Moz) that estimates how likely a site is to rank, based largely on its backlink profile. It’s a useful relative gauge, not a Google metric — don’t mistake the speedometer for the engine.

Your address on the web — the name people type to reach you. You don’t buy it outright; you register it (lease it) through a registrar, typically by the year. It’s one of the few assets you should guard jealously and always control yourself.

Selling goods or services online. It spans everything from a single “Buy” button to a full catalog with inventory, payments, tax and shipping. The platform you choose — Shopify, WooCommerce, custom — should follow from how you actually sell, not the other way around.

Servers positioned geographically close to users (“the edge”) rather than in one central data center. Running your site — and even your code, via edge functions — at the edge is what makes globally fast, resilient sites possible.

The tiny icon that appears in browser tabs, bookmarks and history. A small thing that quietly signals polish; a missing favicon makes a site feel unfinished.

A Web Application Firewall inspects incoming traffic and blocks malicious requests — SQL injection, bad bots, known exploits — before they reach your site. It’s a core layer of a sensible security posture, and a managed network can run one for you.

Adobe (formerly Macromedia) Flash brought animation, sound and interactivity to the early web. Browsers killed it off for good in 2020 over security and performance. Anything Flash once did is now done better with HTML5, CSS and JavaScript — if you have Flash content lingering, it’s long past time to replace it.

Flash of Unstyled Content — the brief flicker (often a white flash) when a page’s raw HTML paints before its CSS loads. A reliable old fix is to set the background on the html element itself so the right color is painted first; modern build pipelines and inlined critical CSS prevent it more thoroughly.

A pre-built foundation of code and conventions you build on top of, instead of starting from a blank file. On the front end, React; for styling, Tailwind; on the back end, Laravel or Rails. Frameworks trade a learning curve for speed, structure and a community of solved problems.

Everything that runs in the visitor’s browser — the HTML, CSS and JavaScript that make up what they see and touch. “Front-end development” is the craft of turning a design into a fast, accessible, interactive interface.

File Transfer Protocol — the old way of moving files to a web server with a client like FileZilla. It still works, but plain FTP is insecure and manual; modern teams deploy through Git and automated pipelines, with SFTP for the rare hand-edit.

Comfortable across the whole spectrum — frontend, backend, databases, deployment. A full-stack developer can carry a feature from the database query all the way to the button you click.

Google Analytics 4 — the current version of Google’s analytics, built around events rather than the old pageview-centric model. It tells you where visitors come from, what they do, and which channels actually produce conversions. Privacy-first alternatives exist, but GA4 remains the default.

Tailoring content, ads or SEO to a specific place — a city, region or radius. Essential for local businesses: a roofer in Denver wants to be found by people searching in Denver, not nationwide.

The version-control system professional developers use to track every change, work in parallel and roll back mistakes. Paired with a host like GitHub, it’s also how modern sites deploy: push your code, and the site rebuilds. If your site isn’t in version control, you’re working without a safety net.

WordPress’s block editor, introduced in 2018 — the default way content is built in modern WordPress, assembling a page from stackable “blocks” (paragraph, image, columns, etc.) rather than one freeform text area.

The main heading of a page (<h1>) — the title of its content. There should be exactly one, and headings should descend in order (H1, then H2, H3…) like an outline. It helps both readers skimming and screen-reader users navigating.

A content system that manages your content but doesn’t dictate how it’s displayed — it serves the content over an API to whatever front end you build. “Headless” buys flexibility and speed at the cost of more up-front engineering.

The large, attention-grabbing area at the top of a page — usually a bold headline, a supporting line and a primary call to action, often over an image or animation. It sets the tone and makes the promise the rest of the page keeps.

The service that stores your website’s files and serves them to visitors. Options run from cheap shared hosting to VPS, managed platforms and edge networks. The right host shapes your speed, reliability and security as much as your code does.

HyperText Markup Language — the foundational language of every web page. It defines structure and meaning: headings, paragraphs, links, images, forms. CSS styles it and JavaScript animates it, but HTML is the skeleton everything hangs on.

The secure version of HTTP, encrypting traffic between browser and server with TLS so it can’t be read or tampered with in transit. It’s now the baseline — browsers flag plain HTTP as “Not Secure,” and certificates are free. There’s no excuse not to have it.

The process by which a search engine stores and organizes the pages it has crawled so they can appear in results. A page can be crawled but not indexed; if it isn’t indexed, it effectively doesn’t exist in search.

An architecture built on pre-rendered markup served from a CDN, with dynamic bits handled by JavaScript and APIs. In plain terms: ship fast static files and call services only when you need them. It’s the philosophy behind a lot of modern, edge-hosted sites.

The programming language of the browser — it makes pages interactive: menus, sliders, form validation, live updates, whole applications. With Node.js it also runs on servers. Powerful, but worth using deliberately: too much JavaScript is a leading cause of slow sites.

A word or phrase people type into search. Modern SEO is less about stuffing exact keywords and more about thoroughly answering the intent behind them — but knowing the terms your customers actually use still guides what you write.

A focused page built around a single goal and usually a single offer, often the destination of an ad or campaign. Strip away distractions, make one promise, ask for one action. Specialized landing pages routinely outconvert sending traffic to a homepage.

Deferring the load of off-screen images, videos or iframes until the visitor scrolls near them. The page becomes interactive sooner and wastes no bandwidth on things never seen. Native browser support (loading="lazy") makes it nearly free.

Largest Contentful Paint — a Core Web Vital marking when the biggest element in view (usually the hero image or headline) finishes rendering. It’s a good proxy for “when does this page feel loaded?” Aim for under 2.5 seconds.

Optimizing to be found by nearby customers — claiming and tuning your Google Business Profile, earning local citations and reviews, and targeting location-based searches. For brick-and-mortar and service-area businesses, it’s often the highest-ROI marketing there is.

Malicious software that can infect a site — to steal data, redirect visitors, mine crypto or spread further. Out-of-date plugins are the usual entry point on WordPress. Updates, least-privilege access, a firewall and clean backups are the defense.

The CSS feature (@media) that applies styles only under certain conditions — most often a screen width, but also things like dark mode or reduced-motion preferences. Media queries are the mechanism that makes responsive design work.

The short summary of a page (~150–160 characters) that search engines often show beneath your title in results. It doesn’t directly affect rankings, but a sharp, benefit-led description meaningfully changes how many people click.

Stripping the comments, whitespace and unnecessary characters out of CSS and JavaScript so the files download faster. The code still works identically; it’s just smaller. A standard step in any production build.

Model-View-Controller — a way of structuring an application by separating concerns: the Model handles data, the View handles presentation, and the Controller handles the logic connecting them. Keeping these apart makes large codebases far easier to reason about and maintain.

The DNS servers that hold the authoritative records for your domain. Pointing your domain’s nameservers at a provider (say, Cloudflare) hands them control of your DNS — the first step in putting a domain behind their network.

A fast, efficient web server (and reverse proxy) that powers a huge share of high-traffic sites, often paired with or in front of other software. Like Apache, it’s part of the plumbing your site sits on — invisible when it’s doing its job.

A link attribute (rel="nofollow") that tells search engines not to pass authority through a link. It’s used for paid, untrusted or user-generated links. Most everyday internal and editorial links should be regular (“followed”) links.

The set of og: meta tags that control how your page looks when shared on social platforms — the title, description and preview image. Get them right and a shared link looks deliberate and clickable; ignore them and you get an ugly, blank card.

A visual site builder for WordPress that outputs notably lean markup and gives developers fine control, without the bloat some page builders add. A favorite for performance-minded WordPress work — though it ties the build to that ecosystem.

A drag-and-drop tool for designing WordPress pages without code — Elementor, Beaver Builder, Divi, Oxygen and others. They lower the barrier to editing; the tradeoff is that some add markup and scripts that can weigh a site down if used carelessly.

How quickly a page loads and becomes usable. It affects rankings, bounce rate and revenue in measurable ways. Speed comes from many small disciplines — caching, compression, image formats, lean code — and it’s a core reason to consider a static or edge-hosted build.

The service that securely processes card and digital payments on your store — Stripe, PayPal, Shopify Payments and the like. It handles the sensitive part of a transaction so you don’t have to touch raw card data. Fees and supported methods vary, so it’s worth choosing deliberately.

The server-side programming language WordPress is written in, and a long-time backbone of the web. It runs on the server to assemble pages before they’re sent to the browser. Mature and ubiquitous, if no longer fashionable.

An add-on that extends a platform’s features — a WordPress contact form, an SEO toolkit, a backup tool. Plugins are WordPress’s superpower and its biggest liability: each one is third-party code that can slow, break or expose your site, so fewer and well-chosen beats many.

The accredited company you register (lease) a domain through — GoDaddy, Namecheap, Cloudflare Registrar and others. They’re not all equal on price, renewal cost or honesty about upsells; the registrar that hooked you cheaply may not be the one you want to keep the name with.

Building one site that adapts fluidly to any screen — phone, tablet, laptop, big monitor — rather than maintaining separate versions. Since most traffic is mobile, “responsive” isn’t a feature anymore; it’s the baseline expectation.

A common, conventional style of web API that uses standard HTTP verbs (GET, POST, PUT, DELETE) against addressable resources. Most services you’d integrate — including WordPress itself — expose a REST API; it’s the lingua franca of system-to-system communication.

A plain text file at your site’s root that tells crawlers which areas they may or may not access. It’s guidance, not a lock — sensitive pages need real protection — but it’s how you keep bots out of admin paths and point them at your sitemap.

Structured data (usually JSON-LD) added to your pages so search engines understand exactly what they describe — a product, a business, an FAQ, a review. It can earn you rich results (stars, prices, FAQ dropdowns) that make your listing stand out and click better.

Using HTML elements for their actual meaning — <nav> for navigation, <button> for buttons, <article> for self-contained content — instead of a sea of generic <div>s. Semantic markup is more accessible, more SEO-friendly and easier to maintain, all at once.

Search Engine Optimization — the ongoing practice of earning visibility in organic (unpaid) search by making your site fast, well-structured, genuinely useful and trustworthy. It’s a compounding investment, not a switch; done right, it pays back for years.

Search Engine Results Page — what you see after a query. “SERP management” is the discipline of shaping how and where you appear there, across the organic listings, local pack, images and rich results. The whole point of SEO is to win real estate on it.

Running code without managing servers yourself — you write a function, the platform runs it on demand and scales it automatically. Cloudflare Workers and similar services let dynamic logic run at the edge, close to users, billed only when it actually runs.

The cheapest tier of traditional hosting, where many sites share one server’s resources. Fine for small, low-traffic sites; the catch is that a neighbor’s spike or security lapse can affect you, and performance is capped by what you’re sharing.

A hosted e-commerce platform that handles the storefront, checkout, payments, hosting and security for you, for a monthly fee. It’s the fastest reliable way to launch a serious store — the tradeoff is monthly cost, transaction fees if you skip Shopify Payments, and working within its ecosystem.

Organizing a site so that closely related pages link tightly to each other and form a clear topical cluster. Done well, siloing helps both visitors and search engines see you as a focused authority on a subject rather than a scattered collection of pages.

A file (usually sitemap.xml) listing your site’s important URLs so search engines can discover and prioritize them. It doesn’t guarantee indexing, but it’s a clear, machine-readable map you hand to Google.

Structured Query Language — the language used to read and write data in relational databases like MySQL. Every time WordPress loads a post, SQL queries run behind the scenes. (Unsanitized input near SQL is also where “SQL injection” attacks happen — hence the emphasis on secure code.)

Static Site Generator — a tool (Eleventy, Hugo, Astro, Next.js and others) that builds your site into plain HTML files ahead of time. You get the editing convenience of templates and content files, plus the speed and security of static output. Our favored approach for content sites that don’t need a live database.

The credential that enables HTTPS, verifying your site’s identity and encrypting traffic. Once a paid annual purchase, certificates are now free and auto-renewing via services like Let’s Encrypt and Cloudflare. If anyone tries to sell you one as a must-buy add-on, be skeptical.

A private copy of your live site where changes are built and tested before going public. It’s the difference between trying a risky update in front of customers and trying it where only you can see the breakage.

A site served as pre-built HTML, CSS and JavaScript files with no database or server-side processing per request. Because there’s nothing to assemble on the fly, static sites are exceptionally fast, cheap to host, and have almost no attack surface. Ideal for marketing sites, portfolios and blogs.

A prefix on your domain that can host separate content — blog.example.com, shop.example.com, dev.example.com. Subdomains are created in DNS and are handy for staging environments, stores or apps that live alongside the main site.

Scalable Vector Graphics — images defined by math rather than pixels, so they stay razor-sharp at any size and usually weigh very little. Perfect for logos, icons and illustrations; they can even be styled and animated with CSS.

A utility-first CSS framework: instead of writing custom stylesheets, you compose designs from small, single-purpose classes right in your markup. It makes building consistent, responsive interfaces fast — once you’re past the initial “that looks busy” reaction.

The package that controls a site’s appearance and layout — on WordPress, Shopify and beyond. Also called a template or (in older parlance) a skin. A theme is a starting point; the value is in how well it’s adapted to your brand and content.

The <title> of a page — what shows in the browser tab and, crucially, as the bold blue headline in search results. It’s one of the strongest on-page SEO signals and your first pitch to a searcher. Make each one unique and specific.

User Interface — the concrete visual and interactive layer people touch: buttons, forms, menus, spacing, type. UI is part of UX. Beautiful UI on top of confusing UX is lipstick on a maze.

The percentage of time your site is reachable. “99.9% uptime” sounds perfect but still allows ~8.7 hours of downtime a year; the architecture you choose (single server vs. distributed edge) largely determines how close to truly always-on you get.

User Experience — the overall feel of using your site: how easily someone can find what they need and accomplish their goal. Good UX is mostly invisible; bad UX is the friction that quietly sends people to a competitor.

HTML and CSS that conform to the standards for the document type, with no structural errors when checked against a validator like the W3C’s. Valid code renders more predictably across browsers and devices and is easier to maintain. We validate as part of every build.

The visible area of a web page on a given device. The <meta name="viewport"> tag tells mobile browsers to render at the device’s real width instead of pretending to be a desktop — the small line that makes responsive design behave.

A real person viewing your site, as opposed to a bot crawling it. In analytics this is usually counted as a “session” — a group of interactions within a time window. Distinguishing human visits from automated traffic matters when you’re judging what’s actually working.

Virtual Private Server — a slice of a physical server with resources dedicated to you, more powerful and isolated than shared hosting and cheaper than a whole machine. It offers control and consistency, at the cost of needing someone who can manage it.

See Firewall. The shield that filters malicious requests before they reach your site.

Web Content Accessibility Guidelines — the internationally recognized standard for accessibility, organized into levels A, AA and AAA. “WCAG 2.1 AA” is the common target for compliance and the benchmark most accessibility laws point to.

The software (Apache, Nginx, Cloudflare’s edge) that receives requests and sends back your pages and files. It’s the layer between a visitor’s browser and your site’s files — usually invisible, always essential.

An automated message one service sends another when an event happens — “an order was placed,” “a form was submitted.” Where an API is you asking for data, a webhook is the data showing up the moment it’s ready. It’s how systems react to each other in real time.

A modern image format that delivers the same quality as JPEG or PNG at noticeably smaller file sizes, with transparency and animation support. Converting images to WebP (with AVIF close behind) is one of the simplest, highest-impact speed upgrades available.

A low-fidelity, deliberately plain blueprint of a page — boxes and labels, no colors or polish — used to settle structure and priority before any visual design. It’s far cheaper to move a box in a wireframe than to rebuild a finished page.

The free e-commerce plugin that turns WordPress into a full online store. It’s deeply customizable and you own everything, but you’re also responsible for hosting, security, performance and updates — the classic WordPress tradeoff applied to selling.

The open-source CMS that powers roughly 43% of all websites — by far the most popular way to build a site. It’s flexible and well-supported, with a vast plugin and theme ecosystem; the flip side is that it needs maintenance, and its strengths can become liabilities if it’s left untended.

A small piece of code that runs on a CDN’s edge network, close to your visitors, rather than on a central server. Cloudflare Workers can handle forms, redirects, authentication and whole APIs with near-zero latency — the engine behind a lot of fast, modern sites (including parts of this one).