Website jargon, translated into plain English

Every industry has jargon. Website projects can be especially confusing because the people buying and managing a site are rarely the people building it. A good technical partner should make the choices easier to understand, not hide behind terminology. Here are the terms you are most likely to hear, what they mean in plain English, and why they might matter to you.

Where your website lives

• Domain: your address on the internet, like itbonsai.com. You rent it annually from a registrar. Whoever controls the registrar account controls your website, so make sure that account belongs to you, not your vendor.
• DNS: the internet's phone book. When someone types your domain, DNS tells their browser where to find your site. DNS changes are also a common source of outages when a website moves between vendors.
• Hosting: the service that stores your website and makes it available online. Basic hosting may be enough for a small site, but the right plan also depends on traffic, security, support, and how the site is built.
• Server: the computer and software that receive requests and deliver your website. When someone says there is a server problem, they usually mean something in that hosting environment rather than an issue with your content.
• CDN: a network of copies of your site stored around the world so it loads quickly everywhere. Like keeping stock in local warehouses instead of shipping everything from one building.
• SSL / HTTPS: the padlock in the browser. It encrypts traffic between your visitor and your site. It is essential and is usually included with reputable hosting. If it appears as a separate charge, ask what service is included.

How it gets built

• Front end: everything visitors see and touch. Buttons, layouts, animations.
• Back end: everything behind the curtain. Databases, logins, the machinery that saves a form submission.
• CMS: content management system. The tool your team uses to edit pages without a developer. WordPress is the famous one. If your team dreads using yours, that is a fixable problem, not a fact of life.
• API: a way for two pieces of software to talk to each other. When your website sends form fills to your CRM, an API is doing it.
• Framework: a pre-built foundation developers build on so they do not start from zero. You mostly care about one question: is it common enough that the next developer can pick it up?
• Staging: a private copy of your website where changes can be tested before the public sees them. If changes are made directly on the live site, ask how they are tested and how the team would roll them back if something goes wrong.

How it stays fast

• Cache: a saved copy of something so it does not have to be rebuilt for every visitor. Caching is why a page loads faster the second time. Also why you sometimes cannot see a change until it is "cleared."
• Page weight: how much data a page makes visitors download. Heavier pages load slower, especially on phones. Large images, video, and third-party scripts are common causes.
• Core Web Vitals: Google's three measurements of how a page feels: how quickly the main content appears, how promptly the page responds, and how stable the layout is while loading. They are useful because they can reveal frustrating experiences for visitors. Google also uses them as one of many signals related to page experience.
• Lazy loading: waiting to load things (usually images) until the visitor scrolls near them. A standard trick for making pages feel faster.

How people find it

• Crawling: search engines send software to discover and read pages across the web. If they cannot crawl your pages, they may not be able to include them in search results.
• Indexing: being added to the search engine's library after crawling. A page can be crawled and still not indexed, which is one of the first things a technical SEO checks.
• Ranking: where a page appears in search results for a particular query. Useful content and a strong reputation matter most, but technical issues can still hold a good page back.
• Metadata: information in the page code, most often the title tag and meta description. It helps search engines understand the page and can influence how it appears in results, although search engines may choose different text for a particular search.
• Redirect (301): a forwarding address for a web page. It sends visitors and search engines from an old URL to its replacement. A redirect plan is especially important during a redesign or migration, when many URLs may change at once.
• Canonical: a tag that tells search engines which version of a page you prefer when similar or duplicate versions exist. If it points to the wrong URL, the page you want people to find may be left out of search results.
• Structured data: standardized labels in your page's code that describe things such as articles, products, events, or business details. It helps search engines understand the content and can make some pages eligible for richer search results, but it does not guarantee them.

You do not need to memorize this list. Keep it nearby, and feel free to pause a conversation when a term is unfamiliar. Ask what it means for your site, your budget, or the decision in front of you. A good technical partner will be glad to explain. Clear communication is part of the work.