An.htaccess file, hypertext access, is a directory-level configuration file used by the Apache web server to apply configuration directives to the directory in which it is placed and all subdirectories beneath it. Unlike Apache’s main server configuration file, httpd.conf or apache2.conf: which requires server administrator access and a server restart to apply changes an.htaccess file can be placed in any directory accessible to the web server and takes effect immediately, no server restart required.

A 200 OK is an HTTP status code that means a request was received, understood, and successfully fulfilled by the server. It is the standard response for a working web page, the server received the request, found the content, and returned it without any issues.

A 300 redirect is an HTTP status code that indicates a requested resource has more than one possible location, and the client (typically a browser) must choose which one to use. It belongs to the 3xx redirect class of status codes, which all deal with directing requests from one URL to another.

A 301 redirect is a permanent HTTP status code that tells browsers and search engines a URL has moved to a new location, permanently. When someone visits the old URL, they are automatically sent to the new one without any action required on their part.

A 302 redirect is a temporary HTTP status code that tells browsers and search engines a URL has moved to a different location, but only for now. Unlike a 301 redirect, which signals a permanent move, a 302 tells search engines to keep the original URL in their index because it is expected to become active again.

A 303 redirect is an HTTP status code that tells a browser to follow a redirect to a new URL using a GET request, regardless of what HTTP method was used in the original request. It belongs to the 3xx redirect family of status codes and was introduced in HTTP/1.1 specifically to clarify behaviour that the 302 redirect left ambiguous.

A 304 Not Modified is an HTTP status code that tells a browser the resource it requested has not changed since the last time it was fetched. Instead of sending the full response again, the server instructs the browser to load the page from its local cache instead.

A 307 redirect is a temporary HTTP status code that tells a browser to repeat its request at a new URL while preserving the original HTTP method. If the original request was a POST, the browser sends a POST to the new location. If it was a GET, it sends a GET. The method never changes.

A 308 redirect is a permanent HTTP status code that tells browsers and search engines a URL has moved to a new location forever, while strictly preserving the original HTTP request method. If the original request was a POST, the browser sends a POST to the new location. If it was a GET, it sends a GET. The method never changes, and the move is permanent.

A 404 error is an HTTP status code that means the server received a request for a URL but could not find any content at that address. It is the web's way of saying the page does not exist — at least not at the URL that was requested.

A 404 redirect strategy is a systematic approach to identifying URLs that return 404 Not Found errors, pages that no longer exist at their original addresses, and configuring appropriate redirects from those broken URLs to relevant live content. Rather than leaving visitors and search engine crawlers to encounter dead ends the strategy transforms broken link destinations into functioning redirect paths, recovering SEO equity from backlinks pointing to dead URLs and delivering visitors to useful content instead of error pages.

A 410 Gone is an HTTP status code that tells browsers and search engines a page has been permanently removed from the server and will not be coming back. It is a stronger, more explicit signal than a 404 error, where a 404 says the page cannot be found right now, a 410 says the page is gone for good and there is no point looking for it again.

A 500 error is an HTTP status code that means the server encountered an unexpected condition that prevented it from fulfilling the request. It is the web’s generic way of saying something went wrong on the server side, the request was received and understood, but the server failed to process it correctly.

A 503 error is an HTTP status code that means the server is temporarily unable to handle requests. Unlike a 500 error which signals that something went unexpectedly wrong, a 503 carries an important distinction, the word temporarily. It tells browsers and search engines that the server is aware of the problem, the situation is expected to be short-lived, and normal service will resume.

A 508 Loop Detected is an HTTP status code that means the server detected an infinite loop while attempting to process a request. Rather than continuing to process a request that will never resolve, the server stops, returns the 508, and prevents the loop from consuming resources indefinitely.

A base URL is the foundational address from which all other URLs on a website are constructed, the common root that all pages on a site share. In its simplest form the base URL is the protocol and domain combination, https://example.com: that prefixes every page address on the site. https://example.com/products/blue-widget, https://example.com/blog/redirect-guide, and https://example.com/about all share the same base URL, https://example.com: which is the root from which the complete addresses are built by appending paths.

A broken link is a hyperlink that points to a URL that no longer exists, returns an error, or cannot be reached, leaving the visitor who clicks it with an error page rather than the intended destination. When a user follows a broken link they typically encounter a 404 Not Found error, the server confirms the request was received but has no content at the requested URL. Broken links are also called dead links or link rot, the gradual decay of the web’s link graph as pages move, are deleted, or are reorganised without corresponding updates to links pointing to them.

A bulk redirect is the process of creating multiple redirect rules simultaneously rather than configuring them one at a time. Instead of manually entering each source and destination URL individually, bulk redirects allow hundreds or thousands of redirect rules to be defined in a spreadsheet or CSV file and deployed all at once through an import tool or server configuration.

A CAA record, Certification Authority Authorization record, is a DNS record that specifies which certificate authorities are permitted to issue SSL certificates for a domain. It is a security mechanism that allows domain owners to restrict certificate issuance to a specific set of trusted certificate authorities, preventing any other CA from issuing a certificate for the domain even if an attacker somehow convinces them to try.

The Cache-Control header is an HTTP response, and sometimes request, header that provides explicit instructions to browsers, CDN edge servers, reverse proxies, and other caching intermediaries about how to store, serve, and validate cached copies of HTTP responses. It is the primary mechanism through which web servers and applications control caching behaviour across the entire chain of infrastructure between the origin server and the end user, specifying how long a response should be considered fresh, who is permitted to cache it, whether it must be revalidated before serving, and whether it should be stored at all.

A canonical tag is an HTML element placed in the <head> section of a webpage that specifies the preferred, canonical, URL for that page’s content. It is the primary technical mechanism through which website owners communicate to search engines which URL should be indexed, ranked, and credited with accumulated link juice when the same or similar content is accessible at multiple addresses.

A canonical URL is the definitive, preferred URL for a specific piece of content, the single address that search engines should index, rank, and consolidate ranking signals for when the same or similar content is accessible at multiple URLs. When identical or substantially similar content exists at more than one address, through URL parameters, protocol variants, subdomain variations, or multiple domain configurations, the canonical URL is the one the site owner designates as the authoritative version that should appear in search results.

A catch-all redirect is a redirect rule that matches any URL not already handled by a more specific rule and forwards it to a default destination. It is the safety net of a redirect configuration: the rule of last resort that ensures no visitor ever lands on a 404 error regardless of which URL they requested, as long as at least one redirect rule is in place for the domain.

A ccTLD, country code Top-Level Domain, is a two-letter TLD assigned to a specific country or territory based on the ISO 3166-1 alpha-2 standard. .uk for the United Kingdom, .de for Germany, .fr for France, .jp for Japan, .au for Australia, .ca for Canada, .br for Brazil, .cn for China. Every country and many territories have a corresponding ccTLD, there are over 250 ccTLDs in active use worldwide.

A CDN, Content Delivery Network, is a geographically distributed network of servers that delivers web content to users from locations physically close to them, reducing the distance data must travel and therefore reducing latency and improving load times. Rather than serving all content from a single origin server in one location a CDN caches and distributes content across dozens or hundreds of edge servers positioned in major population centres around the world, when a user requests a page the CDN routes the request to the nearest edge server rather than to the distant origin.

A certificate authority, CA, is an organisation trusted to verify the identity of entities on the internet and issue SSL certificates that cryptographically bind a public key to a verified identity. Certificate authorities are the trust anchors of the web’s security infrastructure, they are the entities that browsers and operating systems trust by default, and this trust propagates to every website whose certificate was issued by a trusted CA.

A clean URL is a web address that is human-readable, descriptive, logically structured, and free of unnecessary technical elements, such as query parameters, session identifiers, database IDs, file extensions, and other machine-generated components that obscure the address’s meaning. A clean URL communicates clearly what a page contains, where it sits in the site’s content hierarchy, and why a visitor should click it, all without requiring any technical knowledge to interpret.

A client-side redirect is a URL redirect that is triggered by instructions in the browser rather than by the server. Instead of the server responding to a request with an HTTP status code and a Location header before any content is delivered, as a server-side redirect does, a client-side redirect requires the browser to first receive and begin processing the original page, find the redirect instruction embedded in that page, and then initiate navigation to the destination.

A Cloudflare Worker is a serverless function that executes JavaScript, or other languages compiled to WebAssembly, at Cloudflare’s global edge network, processing HTTP requests and responses at the edge node closest to each user rather than at a centralised origin server. Workers intercept incoming requests to a domain, execute custom logic, reading headers, checking paths, modifying responses, making fetch requests, and return responses directly from the edge without necessarily forwarding requests to an origin server.

A CNAME record, Canonical Name record, is a DNS record that maps one domain name to another domain name rather than directly to an IP address. Instead of pointing www.example.com to a specific server IP address, a CNAME points it to another domain name: proxy.redirect.supply, for example, and the DNS system follows that alias to find the actual IP address.

A company merger redirect is the technical and strategic process of consolidating the web presences of two or more companies, following a business merger, acquisition, or consolidation, onto a single authoritative domain, using permanent redirects to transfer traffic, link equity, and SEO equity from the retiring domains to the surviving domain. When Company A acquires Company B, or two equals merge into Company C, the digital properties of each legacy entity must be unified under the combined brand’s single web presence.

A device redirect is a redirect rule that sends visitors to a different URL based on the type of device they are using to browse. A visitor on a smartphone might be redirected from example.com to m.example.com. A visitor on a tablet might go to tablet.example.com. A visitor on a desktop stays on example.com. The redirect detects the device type from signals in the incoming request and routes visitors to a version of the site built or optimised for that device.

A DNS flush is the process of clearing the DNS cache stored locally on a device, the operating system’s record of recently resolved domain names and their corresponding IP addresses. Flushing the DNS cache forces the device to perform fresh DNS lookups for all subsequent requests rather than serving results from the locally cached copy of previous lookups.

A DNS record is a data entry stored in a DNS zone on an authoritative nameserver that provides specific instructions about how to handle requests for a domain or subdomain. Every domain on the internet is associated with a set of DNS records that define where its web traffic goes, where its email goes, how its SSL certificates are validated, and how other services interact with it.

A DNS resolver is a server that performs DNS lookups on behalf of browsers, applications, and other networked clients. When a browser needs to translate a domain name into an IP address it sends a query to a DNS resolver. The resolver does the work of finding the answer, querying root nameservers, TLD nameservers, and authoritative nameservers in sequence, and returns the result to the browser.

A DNS zone is a distinct portion of the DNS namespace that is managed as a single administrative unit by a specific authoritative nameserver or set of nameservers. It is the container that holds all the DNS records for a domain, the A records, CNAME records, MX records, TXT records, NS records, and all other record types that define how the domain functions.

A domain alias is a configuration that makes one domain name serve identical content to another domain name, the same website, the same pages, the same everything, under a different address. When a visitor navigates to either domain they see the same content without being redirected to the other domain. The address bar shows whichever domain they arrived at. Both domains are active and serving content simultaneously.

Domain change SEO is the discipline of planning and executing a website’s move from one domain to another while preserving as much accumulated SEO equity, organic traffic, and search ranking as possible. When a business rebrands, acquires a new domain name, merges with another company, or for any other reason needs to operate under a different domain address the SEO implications of that change require systematic management, without which the move can cause significant, lasting damage to organic search performance.

A domain name is the human-readable address that identifies a website, email service, or other internet resource. It is the text that people type into a browser, example.com, redirect.supply, google.com: to navigate to a destination on the internet. Behind every domain name is a DNS system that translates it into the numerical IP address of the server hosting the resource, making domain names the readable, memorable layer on top of the numeric addressing system that computers use to communicate.

A domain redirect is a URL redirect that sends all traffic arriving at one domain to a different domain automatically. When a visitor types or clicks a URL on the redirected domain, they are forwarded to the destination domain without any action required. The original domain acts as an entry point receiving the visit and immediately passing it on.

A domain registrar is a company or organisation accredited by ICANN, the Internet Corporation for Assigned Names and Numbers, or by a national registry authority to sell and manage domain name registrations. When someone registers example.com they do so through an accredited registrar, a company like GoDaddy, Namecheap, Cloudflare Registrar, Google Domains, or hundreds of others, that processes the registration, maintains the registrant’s records, and communicates with the relevant TLD registry to publish the domain’s delegation records in the DNS hierarchy.

A domain transfer is the process of moving a domain name registration from one domain registrar to another, changing the company responsible for managing the domain’s registration records, renewal billing, and registrant account while keeping the domain name itself unchanged. The domain name, example.com: remains the same. The registrant, the owner, remains the same. Only the registrar of record changes.

A doorway page is a web page created specifically to rank in search engine results for a particular keyword or query, with the sole purpose of funnelling visitors to a different destination rather than providing genuine value at the page itself. The page is optimised for search engine visibility, stuffed with keywords, structured for rankings, but offers nothing useful to visitors who land on it. Its only function is to intercept search traffic and redirect it elsewhere.

A doorway redirect is a configuration where a page, created specifically to rank for a search query, immediately redirects visitors to a different destination rather than serving them the content that was indexed. The doorway page exists solely as a search engine entry point, its purpose is to capture organic traffic for specific queries and funnel that traffic to another destination. The indexed page serves as a door that users pass through without stopping, hence the name doorway.

A fallback redirect is a redirect rule that activates when no other redirect rule matches an incoming request. It is the default: the rule of last resort that catches any URL not handled by more specific rules and sends visitors to a predetermined destination rather than leaving them on a 404 error page.

A forced redirect is a redirect rule that unconditionally sends every visitor and web crawler from one URL to another with no exceptions, no conditions, and no way to access the original URL directly. Every request to the source URL, regardless of who is making it, what device they are using, where they are located, or how they arrived, receives the same redirect response pointing to the destination.

A forward proxy is a server that sits between client devices and the internet, receiving outbound requests from clients, forwarding them to destination servers on the clients’ behalf, and returning the destination server’s response to the client. Where a reverse proxy acts on behalf of servers, receiving requests intended for backend servers, a forward proxy acts on behalf of clients, sending requests on behalf of user devices.

A geo redirect is a redirect rule that sends visitors to a different URL based on their geographic location. Instead of every visitor arriving at the same destination regardless of where they are in the world, a geo redirect detects where the request is coming from and routes visitors to a version of the site, or a specific page, appropriate for their location.

A global redirect is a redirect rule that forwards all traffic arriving at a domain to a single destination URL regardless of what path or page was requested. It is the broadest possible redirect, a catch-all that treats every URL on a domain identically and sends every visitor to the same place.

A gTLD, generic Top-Level Domain, is a TLD that is not associated with a specific country or territory. Where ccTLDs are two-letter codes assigned to specific nations, .de for Germany, .fr for France, gTLDs are generic identifiers available for registration by anyone worldwide without geographic restriction. .com, .net, .org, .io, .app, .store, .supply: all gTLDs. They define the highest-level category of a domain name without implying any national affiliation.

A hard redirect is a URL redirect implemented through a proper HTTP status code at the server level, specifically a 3xx status code returned in the server’s response before any page content is delivered. The server receives the request, determines a redirect is in place, and responds immediately with the redirect status code and a Location header pointing to the destination. No page content is sent. The browser follows the Location header and loads the destination.

A JavaScript redirect is a client-side redirect that uses JavaScript code executed in the browser to navigate visitors from one URL to another. Instead of the server responding with an HTTP status code and a Location header before any content is delivered, as a server-side redirect does, a JavaScript redirect requires the browser to load the original page, execute the JavaScript code, and then initiate navigation to the destination.

A landing page redirect is an HTTP redirect that routes visitors from a source URL, typically a short, memorable, or campaign-specific address, to a dedicated landing page designed to convert visitors for a specific goal. The source URL is the address distributed in marketing campaigns, printed on physical materials, or shared through specific channels, chosen for its memorability, brand alignment, or contextual appropriateness. The destination is a carefully designed landing page optimised for the conversion goal the campaign is driving, a product purchase, a lead form submission, a webinar registration, a software download, or any other defined action.

A long URL is a web address that extends beyond what is practical for human use, containing extended paths, multiple query parameters, tracking codes, session identifiers, or other components that make the URL unwieldy to read, remember, type, or share. There is no universally defined length at which a URL becomes long, the term is relative, but URLs that run to several hundred characters, that contain machine-generated identifiers, or that include numerous query parameters are generally considered long URLs in contrast to short, clean, human-readable URLs.

A maintenance redirect is a temporary HTTP redirect that sends visitors away from a website, or specific pages, to an alternative destination while maintenance, updates, or repairs are being performed. Rather than presenting visitors with a broken site, server error pages, or partially functioning pages during a maintenance window a maintenance redirect proactively routes traffic to a maintenance notice page, an alternative service, or a simplified version of the site that remains functional while the primary infrastructure undergoes changes.

A masked redirect is a technique that displays content from one URL while keeping a different URL visible in the browser address bar. When a visitor navigates to the original URL, instead of being sent to the destination through a standard HTTP redirect, the original page loads a frame — typically an HTML iframe, containing the destination content. The visitor sees the destination content but the address bar never changes. The original URL stays visible throughout the entire visit.

A meta refresh redirect is a type of URL redirect implemented through an HTML meta tag in the head of a web page rather than through a server-side HTTP response. Instead of the server immediately responding with a 3xx status code and a Location header before the page loads, the server returns the page with a 200 OK and the browser reads the meta tag in the HTML, waits for the specified delay, and then navigates to the destination URL.

A mixed content warning is a browser security alert that appears when a webpage loaded over HTTPS attempts to load resources, images, scripts, stylesheets, iframes, or other assets, over insecure HTTP. The page itself was delivered securely over an encrypted connection but some of its component resources are being requested over an unencrypted channel, creating a mix of secure and insecure content on the same page. This mixing of HTTPS and HTTP content on the same page is what gives the warning its name.

A mobile redirect is an HTTP redirect that detects visitors using mobile devices, smartphones and tablets, and routes them to a mobile-optimised version of a website rather than serving them the same content delivered to desktop browsers. When a mobile visitor requests example.com a mobile redirect detects the mobile user agent and redirects to m.example.com: a separate mobile site, or to a mobile-specific URL pattern, example.com/m/: that serves content formatted and optimised for small screens and touch interfaces.

A multi-domain setup is a configuration where an organisation manages multiple domain names for a single website, application, or infrastructure, serving content, handling redirects, or managing DNS for more than one domain through a unified system. The domains involved may all serve the same content, redirect to a primary domain, target different geographic markets with localised content, or represent different product lines under the same organisational umbrella.

A nameserver is a server that stores DNS records and responds to queries about those records from other servers and clients on the internet. It is the infrastructure layer that makes DNS work, the servers that hold the mappings between domain names and IP addresses and serve those mappings in response to lookup requests.

A nofollow link is a hyperlink that includes the rel="nofollow" attribute, an instruction to search engine crawlers not to follow the link for ranking purposes and not to pass link juice or SEO equity through it to the linked page. Where a standard followed link endorses the destination page and contributes to its authority in search engine ranking algorithms a nofollow link withholds that endorsement, communicating to search engines that the linking page does not want to vouch for the linked destination.

A noindex tag is a directive placed on a webpage that instructs search engine crawlers not to include that page in their search index, preventing it from appearing in organic search results. When Googlebot or another search engine crawler crawls a page and finds a noindex directive it processes the instruction and removes the page from the index, or does not add it if the page was not previously indexed. The page continues to exist and be accessible to visitors but it is invisible to organic search.

A non-www domain is a domain name served directly from the root domain: without the www subdomain prefix. example.com is a non-www domain. redirect.supply is a non-www domain. Any website whose canonical address is the bare domain name, the second-level domain and TLD without any prefix, is using a non-www configuration.

A path-level redirect is a redirect rule that targets a specific URL path or URL pattern and forwards it to a defined destination. Unlike a global redirect that sends all traffic from a domain to a single destination regardless of what was requested, a path-level redirect is precise, it matches a particular path and sends it somewhere specific while leaving all other paths unaffected.

A permalink, a portmanteau of permanent link, is a URL that is intended to remain unchanged and accessible indefinitely, pointing to a specific piece of content at the same address today, next year, and years into the future. The permanence in permalink is a commitment, the URL will not change, break, or disappear as long as the content exists. Anyone who saves, shares, or links to a permalink can rely on it to navigate to the same content at any future time.

A permanent redirect is an HTTP redirect that tells browsers and search engines a URL has moved to a new location forever and will not be returning to its original address. It is the standard method for handling URL changes that are intended to last indefinitely, domain migrations, page restructuring, rebranding, and anything else where the old URL is being retired permanently.

A port number is a 16-bit unsigned integer, ranging from 0 to 65535, that identifies a specific process, service, or application on a networked device. Where an IP address identifies a specific device on a network a port number identifies a specific service running on that device, enabling multiple network services to operate simultaneously on the same device without conflicts. The combination of an IP address and a port number, called a socket, uniquely identifies a specific communication endpoint on the internet.

A premium domain is a domain name that commands significantly higher registration or renewal prices than standard domains due to its perceived value, typically because it is short, memorable, consists of common dictionary words, contains high-value keywords, or has accumulated authority from previous use. Premium domains are distinguished from standard domains by their price point and desirability, the term covers both registry-designated premium names and the broader aftermarket for valuable domain names.

A product discontinuation redirect is a 301 permanent redirect configured from a product page URL to an appropriate alternative destination when a product is retired, discontinued, or removed from a product catalogue. When a business stops selling a product, due to end of life, product line consolidation, supplier changes, or any other reason, the product’s page URL continues to exist in search indexes, backlinks, customer bookmarks, and external references. A product discontinuation redirect ensures that visitors who follow these existing references are delivered to relevant alternative content rather than encountering a 404 error and experiencing a dead end.

A PTR record, Pointer record, is a DNS record that maps an IP address to a domain name. It is the reverse of an A record: where an A record maps a domain name to an IP address, a PTR record maps an IP address back to a domain name. This reverse mapping is what makes PTR records the foundation of reverse DNS lookups, the process of finding the domain name associated with a known IP address.

A query string is the portion of a URL that contains key-value pairs providing additional information to the web server or application, appearing after a question mark ? character at the end of the URL path. In https://example.com/search?q=redirect+management&sort=relevance&page=2 the query string is q=redirect+management&sort=relevance&page=2: the entire portion after the ?. Each key-value pair, q=redirect+management, sort=relevance, page=2: is a URL parameter within the query string, with multiple parameters separated by ampersand & characters.

A redirect chain is a sequence of URL redirects where the browser or crawler must follow multiple hops before reaching a final destination that returns a 200 OK. Instead of URL A redirecting directly to the final destination, URL A redirects to URL B, which redirects to URL C, which finally returns the page. Each intermediate redirect in the sequence is a hop. The total number of hops from the original URL to the final destination defines the length of the chain.

A redirect destination is the URL that a redirect rule sends visitors and web crawlers to when the rule fires. It is the second half of every redirect rule: the address that appears in the Location header of the server’s redirect response, telling the browser where to go next.

A redirect hop is a single step in a sequence of URL redirects: one URL redirecting to another. Every time a browser or web crawler follows a redirect and arrives at a URL that itself returns another redirect rather than a final 200 OK response, that transition from one URL to the next is a hop.

A redirect loop is a configuration error where redirect rules create a circular path that has no exit. URL A redirects to URL B. URL B redirects back to URL A. Or the loop is longer — A redirects to B, B to C, C to D, D back to A — but the result is the same. The browser or crawler follows redirect after redirect, cycling through the same URLs indefinitely, never reaching a final destination that returns a 200 OK.

A redirect source is the URL that a redirect rule is applied to, the original address that triggers the redirect when requested. When a browser or web crawler requests the source URL, the server matches that request against configured redirect rules, finds the source in its rule set, and responds with the appropriate HTTP status code and Location header pointing to the redirect destination.

A regex redirect is a redirect rule that uses a regular expression, commonly abbreviated as regex, to define the URL pattern it matches. Instead of matching a single exact URL or using a simple wildcard asterisk to match any sequence of characters, a regex redirect uses a precise pattern language capable of expressing complex, specific matching logic that wildcards cannot achieve.

A regional redirect, also called a geo redirect or geographic redirect, is an HTTP redirect that routes visitors to different content based on their detected geographic location, determined from their IP address, browser language preferences, or explicit location selection. Where a standard redirect sends all visitors from one URL to the same destination a regional redirect makes routing decisions based on where the visitor is located, sending a visitor from the United Kingdom to a UK-specific version of a page while sending a visitor from Germany to a German-specific version of the same page.

A relative URL is a web address that omits some or all of the scheme and authority components, relying on context to supply the missing parts and resolve to a complete absolute URL. Where an absolute URL like https://example.com/products/blue-widget is fully self-contained, specifying everything needed to locate the resource, a relative URL like /products/blue-widget is incomplete on its own. It must be interpreted in relation to a base URL, typically the URL of the page containing the relative URL, to resolve to the full absolute address.

A render-blocking resource is a file, typically a CSS stylesheet or a synchronous JavaScript file, that the browser must download, parse, and process before it can render any visible content on a web page. When a browser encounters a render-blocking resource while parsing an HTML document it pauses all content rendering, halting the construction of the visual page, until the blocking resource has been fully retrieved from the server and processed. Users see a blank white page during this blocking period, no content is displayed regardless of how much HTML the browser has already parsed.

A request header is a key-value pair included in an HTTP request that provides metadata about the request, communicating information about the client making the request, the content of the request body, the capabilities of the client, and the context in which the request is being made. Request headers accompany every HTTP request, sent by browsers, API clients, crawlers, and other HTTP clients before the request body, providing the server with the information it needs to process the request appropriately and return a suitable response.

A response header is a key-value pair included in an HTTP response that provides metadata about the response, communicating information about the content being returned, instructions for how the browser should handle it, security policies the browser should enforce, and directives for caching infrastructure. Response headers accompany every HTTP response, sent by web servers, CDNs, reverse proxies, and other HTTP infrastructure before the response body, providing clients with the context needed to correctly interpret, display, cache, and secure the returned content.

A reverse proxy is a server that sits between client browsers and one or more backend web servers, receiving incoming requests from clients, forwarding them to the appropriate backend server, and returning the backend’s response to the client. From the client’s perspective the reverse proxy is the web server, the client connects to the reverse proxy’s IP address and receives responses directly from it. The backend servers are hidden behind the reverse proxy, clients never connect to them directly and may not know they exist.

A robots.txt file is a plain text file placed at the root of a website that instructs web crawlers, search engine bots, automated scrapers, and other automated agents, which parts of the site they are permitted to access and which parts they should not crawl. It is the primary mechanism through which website owners communicate crawling permissions to automated agents, providing a voluntary, convention-based protocol for managing how bots interact with web content.

A root domain is the base level of a domain name: the combination of the second-level domain and TLD without any subdomain prefix. example.com is a root domain. google.com is a root domain. redirect.supply is a root domain. Any subdomain added to the left, www.example.com, blog.example.com, app.redirect.supply: is built on top of the root domain but is not itself a root domain.

A secure connection is a network communication channel between a client, typically a browser, and a server that provides three fundamental security properties, encryption, authentication, and integrity. Encryption ensures that data transmitted between the two parties cannot be read by anyone intercepting the traffic. Authentication ensures the client is connecting to the genuine intended server rather than an impostor. Integrity ensures that data cannot be modified in transit without detection. A connection that provides all three properties is considered secure, a connection that lacks any of them has meaningful security gaps regardless of what other protections are in place.

A server-side redirect is a URL redirect that happens at the server level, before any page content is delivered to the browser. When a request arrives at a server for a URL that has a redirect configured, the server responds immediately with an HTTP status code and a Location header pointing to the destination. The browser follows the location and loads the destination page. No content from the original URL is ever rendered.

A short URL is a condensed web address, typically consisting of a domain and a short alphanumeric string, that automatically redirects visitors to a longer destination URL. Where the destination URL might be https://example.com/blog/category/comprehensive-guide-to-redirect-management-for-seo-professionals a short URL equivalent might be https://exmpl.co/r7x2k: a fraction of the length that is easier to type, share, remember, and include in contexts with character limitations.

Site consolidation is the process of merging two or more separate websites into a single unified web presence, combining their content, SEO equity, backlink profiles, and audiences under one authoritative domain. Where domain consolidation specifically refers to combining multiple domains pointing to the same content site consolidation involves the deeper work of combining the actual content, URL structures, and site architectures of distinct websites into one coherent destination.

A soft redirect is an informal term for any technique that sends visitors from one URL to another without issuing a proper HTTP redirect status code, specifically without returning a 3xx status code in the server response. Instead of the server responding with a 301, 302, or other redirect code that browsers and search engines understand natively, a soft redirect uses an alternative mechanism, typically a meta refresh tag, JavaScript navigation, or a page that visually suggests visiting a different URL, to move visitors without the server ever issuing a redirect response.

A subdomain is a label added to the left of a root domain that creates a distinct, separately addressable section within the same domain. www.example.com has the subdomain www. blog.example.com has the subdomain blog. app.redirect.supply has the subdomain app. The subdomain extends the domain name leftward, adding specificity and creating a new addressable hostname that can point to different infrastructure, serve different content, or fulfil a different purpose than the root domain.

A temporary redirect is an HTTP redirect that tells browsers and search engines a URL has moved to a different location for now, but the original URL is still valid and is expected to become active again. Unlike a permanent redirect, a temporary redirect does not tell search engines to update their index or transfer SEO equity to the destination. The original URL is preserved exactly as it is.

A TLD, Top-Level Domain, is the rightmost segment of a domain name, appearing after the final dot. In example.com the TLD is .com. In redirect.supply the TLD is .supply. In bbc.co.uk the TLD is .uk: with .co being a second-level domain within the .uk namespace. TLDs sit at the top of the DNS hierarchy, immediately below the DNS root, and define the highest-level category or geographic association of a domain name.

A trailing slash is the forward slash character, /: that appears at the very end of a URL path. https://example.com/page/ has a trailing slash. https://example.com/page does not. The difference is a single character, but that single character creates two technically distinct URLs that may serve identical content, creating duplicate content issues and splitting SEO equity between two addresses unless explicitly handled.

A TXT record, Text record, is a DNS record that stores arbitrary text data associated with a domain name. Unlike A records that map domains to IP addresses or CNAME records that create domain aliases, TXT records have no specific routing function in DNS. They exist as a flexible mechanism for storing text-based information that other systems, email servers, certificate authorities, domain verification services, security scanners, can retrieve and act upon.

A URI, Uniform Resource Identifier, is a string of characters that identifies a resource. It is the broader category that encompasses both URLs: Uniform Resource Locators, and URNs, Uniform Resource Names, as specific subtypes. Every URL is a URI but not every URI is a URL, a URI only needs to identify a resource, while a URL specifically identifies a resource and provides the means to locate it.

A URL hash, also called a fragment identifier or anchor, is the portion of a URL that follows a # character and identifies a specific section or position within a page. In https://example.com/page#specifications the hash is #specifications: it tells the browser to navigate to the element on the page with the ID specifications after loading the page content. The hash is the mechanism that enables deep linking within a page, sending visitors directly to a specific section rather than to the top of the page.

A URL parameter is a key-value pair appended to a URL after a question mark, ?: that provides additional information to the server or application about how to process the request or what specific content to return. In https://example.com/products?sort=price&colour=blue the parameters are sort=price and colour=blue: each consisting of a key, sort, colour: and a value, price, blue: separated by an equals sign. Multiple parameters are separated by ampersand characters, &.

A URL path is the component of a URL that identifies the specific resource being requested within a domain, the sequence of forward-slash-separated segments that follow the domain name and precede any query string or fragment. In https://example.com/products/widgets/blue-widget the path is /products/widgets/blue-widget: the three-segment sequence that locates the specific page within the site’s content hierarchy.

A URL redirect is a technique that automatically sends visitors and search engines from one web address to another. When someone requests a URL that has a redirect in place, the server responds with an HTTP status code and a Location header pointing to the destination. The browser follows the location automatically and loads the destination page. The visitor rarely notices anything happened.

A URL scheme is the protocol identifier at the very beginning of a URL: the characters before the colon and double slash that specify how the resource should be accessed. In https://example.com/page the scheme is https: instructing the browser to use the HyperText Transfer Protocol Secure to retrieve the resource. In http://example.com/page the scheme is http. In ftp://files.example.com/document.pdf the scheme is ftp. The scheme is the first thing a browser reads in a URL, it determines which protocol to use, which port to connect on by default, and what security and communication characteristics to expect.

A URL shortener is a service or tool that takes a long URL and generates a shorter alias, a compact URL that redirects visitors to the original long destination when clicked. The user submits a long URL, https://example.com/blog/comprehensive-guide-to-redirect-management-for-seo: and the URL shortener produces a short equivalent, https://bit.ly/r7x2k: that is a fraction of the original length but navigates to the same destination through an automatic redirect.

A URL slug is the portion of a URL path that identifies a specific page or resource in a human-readable, descriptive format, the words at the end of a URL that communicate what the page is about. In https://example.com/blog/redirect-management-guide the slug is redirect-management-guide: the unique identifier for that specific page within the blog section. The slug is what distinguishes one page from another within the same section of a site.

A URL, Uniform Resource Locator, is the complete address used to identify and locate a specific resource on the internet. Every web page, image, document, video, API endpoint, and any other accessible resource on the web has a URL, the unique address that browsers, applications, and other clients use to request that specific resource from the server that hosts it.

A user agent is a string transmitted in the User-Agent request header that identifies the software client making an HTTP request, communicating the type of client, its name, version, and often information about the operating system and platform on which it is running. Every HTTP client, web browsers, search engine crawlers, API clients, mobile apps, and automated scripts, includes a user agent string that identifies what it is to the servers it communicates with.

A vanity URL is a custom, human-readable web address created to be short, memorable, and easy to share, typically for a specific campaign, person, event, product, or purpose. Instead of sending someone to example.com/resources/marketing/2024-annual-report-download-page, a vanity URL might be example.com/report2024 or report.example.com. The destination is the same. The address is cleaner, more memorable, and far easier to communicate verbally, print on marketing materials, or include in a presentation.

A web crawler, also called a spider, bot, or web robot, is an automated software program that systematically browses the web by following hyperlinks from page to page, fetching the content of each page it discovers, and processing that content for a specific purpose. Search engine crawlers, Googlebot, Bingbot, Yandexbot, crawl the web to discover, analyse, and index content for inclusion in search results. Other crawlers monitor websites for changes, check for broken links, gather research data, or perform competitive analysis.

A web server is software, and by extension the hardware it runs on, that receives HTTP and HTTPS requests from clients and returns appropriate responses. When a browser navigates to a URL the browser sends an HTTP request to the web server at the address specified by the URL. The web server receives the request, processes it according to its configuration, and returns an HTTP response, which may be the content of a file, a dynamically generated page, a redirect response, an error response, or any other valid HTTP response.

A wildcard domain is a DNS configuration that matches any subdomain under a root domain: routing requests for any subdomain label to the same destination. The asterisk symbol, *: serves as the wildcard character representing any possible subdomain label. A wildcard DNS entry for *.example.com matches anything.example.com, whatever.example.com, random-string.example.com, and any other single-level subdomain of example.com that does not have a more specific DNS record defined.

A wildcard redirect is a redirect rule that uses a pattern, typically represented by an asterisk (*), to match multiple URLs at once and forward them to a destination. Instead of defining a separate redirect rule for every individual URL, a wildcard rule captures an entire group of URLs matching a pattern and handles them all with a single rule.

An A record, short for Address record, is a DNS record that maps a domain name or subdomain to an IPv4 address. It is the most fundamental record in the DNS system: the direct connection between a human-readable domain name and the numerical IP address of the server that hosts it.

An A/B redirect is a redirect rule that splits incoming traffic between two or more versions of a page, sending some visitors to the original version and others to a variation, in order to test which version performs better. Instead of all visitors seeing the same page, a proportion of them are redirected to an alternative URL where a different design, headline, layout, or content is served. The relative performance of the two versions, measured through conversion rates, engagement metrics, or other goals, determines which version wins the test.

An AAAA record, pronounced “quad-A record”, is a DNS record that maps a domain name or subdomain to an IPv6 address. It is the IPv6 equivalent of the A record, where an A record maps a domain to a four-number IPv4 address like 93.184.216.34, an AAAA record maps it to the longer hexadecimal IPv6 format like 2606:2800:220:1:248:1893:25c8:1946.

An absolute URL is a complete, fully specified web address that contains all the components necessary to locate a resource, the protocol, domain, and path, without requiring any additional context to resolve. https://example.com/products/blue-widget is an absolute URL, it specifies the https protocol, the example.com domain, and the /products/blue-widget path. Anyone who has this URL can access the resource it identifies from any context, another website, an email, a printed document, or a command line, without needing to know anything else about the site’s structure or the current page’s location.

An affiliate redirect is a HTTP redirect that routes a visitor through a tracking intermediary before delivering them to a merchant’s website, capturing attribution data that enables the affiliate program to credit the referring affiliate with a commission when the visitor makes a purchase or completes another qualifying action. Rather than linking directly to a merchant’s product page an affiliate link points to a redirect URL that records the click, identifying which affiliate sent the visitor, and then forwards the visitor to the merchant’s destination.

An ALIAS record, also called an ANAME record depending on the DNS provider, is a non-standard DNS record type that provides CNAME record behaviour for root domains where standard CNAME records are prohibited. It allows a domain apex, example.com without any subdomain prefix, to point to another hostname rather than directly to an IP address, while remaining compatible with the DNS specification requirements that make standard CNAMEs impossible at the apex.

An apex domain is a domain name at its root level, without any subdomain prefix. example.com is an apex domain. www.example.com is not, it has the www subdomain prefix. blog.example.com is not, it has the blog subdomain prefix. The apex domain is the base from which all subdomains extend, it sits at the top of the domain’s own namespace, one level below the TLD.

An edge network is a distributed computing infrastructure that positions processing, storage, and content delivery capabilities at locations physically close to end users, at the edge of the internet rather than in centralised data centres. Where traditional web infrastructure centralises computation and data storage in a small number of data centre locations edge networks distribute these capabilities across dozens, hundreds, or thousands of geographically dispersed nodes, each handling requests from nearby users without routing traffic to a distant central location.

An expired domain is a domain name whose registration period has lapsed, the previous owner did not renew before the expiry date and the domain has passed through the grace and redemption periods without being recovered. At the end of this lifecycle the domain is released from the previous registrant’s control and becomes available for anyone to register as if it were a brand new domain, but carrying whatever history, reputation, and accumulated authority it built during its previous registration.

An HTTP status code is a three-digit number that a web server sends back to a browser or client in response to every request. It is the server’s way of communicating the outcome of the request, whether it succeeded, failed, needs to go somewhere else, or ran into a problem, before any page content is delivered.

An IP address, Internet Protocol address, is a numerical label assigned to every device connected to a computer network that uses the Internet Protocol for communication. IP addresses serve two fundamental functions, identifying the device or network interface as a unique entity on the network, and providing the location information needed to route data packets from their source to their destination across the internet.

An MX record, Mail Exchanger record, is a DNS record that specifies the mail server or servers responsible for receiving email addressed to a domain. When someone sends an email to contact@example.com, the sending mail server does not guess where to deliver it, it looks up the MX record for example.com in DNS and finds the address of the mail server that should receive the message.

An NS record, Nameserver record, is a DNS record that specifies which nameservers are authoritative for a domain. It is the record that tells the global DNS system where to find the definitive DNS information for a domain, which servers hold the actual A records, CNAME records, MX records, TXT records, and all other DNS records for that domain.

An origin server is the primary web server that holds the authoritative, original version of a website’s content, the server where the actual application runs, the database is queried, and responses are generated before being sent to users directly or distributed through CDN edge networks and reverse proxies. When a browser requests a web page the origin server is the ultimate source of that page’s content, even when intermediate infrastructure like CDNs, edge networks, and reverse proxies handle the actual delivery to users.

An SOA record, Start of Authority record, is a DNS record that contains essential administrative information about a DNS zone. Every DNS zone has exactly one SOA record, it is mandatory, automatically created by DNS providers, and marks the beginning of authority for the zone. The SOA record identifies the primary nameserver for the zone, provides contact information for the zone administrator, and contains timing parameters that control how the zone’s data is distributed and cached across the DNS system.

An SRV record, Service record, is a DNS record that specifies the hostname and port number of servers that provide a specific service for a domain. Where an A record simply maps a domain name to an IP address, an SRV record is more structured, it identifies not just which server to connect to but which service is being provided, which protocol it uses, on which port it listens, and how multiple servers providing the same service should be prioritised and load-balanced.

An SSL certificate, also called a TLS certificate or digital certificate, is a cryptographic credential issued by a trusted certificate authority that serves two essential purposes, verifying the identity of a website and enabling encrypted HTTPS connections between browsers and servers. The certificate binds a public cryptographic key to a specific domain name, proving that whoever controls the certificate controls the domain, and contains the information browsers need to establish a secure, authenticated connection.

An SSL wildcard certificate is an SSL certificate that covers a domain and all of its single-level subdomains with a single certificate, using an asterisk as a wildcard character in the Subject Alternative Name. A wildcard certificate issued for *.example.com is valid for www.example.com, blog.example.com, api.example.com, shop.example.com, and any other subdomain of example.com: unlimited subdomains covered by one certificate.

An XML sitemap is a structured file in XML format that lists the URLs on a website, providing search engines with a comprehensive map of the site’s content and helping crawlers discover pages that might be difficult to find through link following alone. The sitemap communicates directly with search engines, telling them which URLs exist on the site, when they were last modified, how frequently they change, and in some cases their relative priority compared to other pages on the same site.

Apache HTTP Server, commonly called Apache, is an open-source web server software project maintained by the Apache Software Foundation that has been one of the most widely deployed web servers on the internet since its initial release in 1995. For over two decades Apache was the dominant web server, powering the majority of websites on the internet and establishing the foundational patterns of web server configuration, module architecture, and .htaccess directory-level configuration that shaped web hosting for a generation.

Authoritative DNS refers to the nameservers and the DNS infrastructure that hold the definitive, official DNS records for a domain. When a recursive resolver needs to find the IP address for example.com it ultimately queries the authoritative DNS for that domain, the nameservers that hold the zone data configured by the domain owner. The authoritative nameserver returns the actual record value from the zone file, not a cached copy, not an approximation, but the current authoritative truth.

Bandwidth is the maximum rate at which data can be transferred across a network connection, measured in bits per second and expressed in units of kilobits per second, Kbps, megabits per second, Mbps, or gigabits per second, Gbps. A network connection with 100 Mbps bandwidth can transfer a maximum of 100 megabits of data every second, enabling a 100 megabyte file to be transferred in approximately 8 seconds under ideal conditions.

Browser caching is the mechanism by which a web browser stores copies of web resources, HTML pages, CSS stylesheets, JavaScript files, images, fonts, and other assets, locally on a user’s device after the first visit, so that subsequent requests for the same resources can be served from the local cache rather than fetched again from the server. When a browser has a valid cached copy of a resource it serves the cached version instantly, with zero network latency, rather than making a new HTTP request that must travel to the server and back.

Campaign tracking is the practice of appending identifying parameters to URLs used in marketing campaigns, enabling analytics platforms to attribute website visits, conversions, and revenue to the specific campaigns, channels, and creative executions that drove them. By adding structured parameter strings to destination URLs before distributing them in emails, advertisements, social media posts, and other marketing channels marketers can answer the fundamental marketing question, which campaigns are driving valuable traffic and generating returns?

Certificate renewal is the process of replacing an SSL certificate that is approaching its expiry date with a new certificate, obtaining a fresh certificate from the certificate authority before the existing one expires, installing it on the server, and ensuring continuous HTTPS coverage without any interruption to service. The renewed certificate is a completely new certificate, issued fresh by the CA with a new validity period, rather than an extension of the existing certificate’s validity.

Cloaking is the practice of deliberately presenting different content or URLs to search engine crawlers than to human visitors, showing search engines one version of a page to influence rankings while showing users an entirely different version. A cloaking configuration detects incoming requests, identifying whether they come from a search engine crawler based on IP address, user agent, or other signals, and serves different content based on that detection, giving crawlers optimised, keyword-rich content while directing human visitors to different content entirely.

Cloudflare is a web infrastructure and security company that operates one of the world’s largest edge networks: providing CDN, DDoS protection, DNS hosting, reverse proxy services, edge computing, and security services to millions of websites and internet properties. Founded in 2009 and launched publicly in 2010 Cloudflare has grown from a web application firewall startup into a comprehensive internet infrastructure provider whose network sits between a significant fraction of all internet users and the websites they visit.

CLS, Cumulative Layout Shift, is a Core Web Vitals metric that measures the visual stability of a web page during and after loading, quantifying how much visible page content unexpectedly moves or shifts as the page loads and resources arrive. CLS captures the frustrating experience of trying to read or interact with a page while its layout reorganises around you, text jumping down as an image loads above it, a button moving just as you tap it, an article shifting as an advertisement appears.

Core Web Vitals are a set of specific, measurable web performance metrics defined by Google that quantify key aspects of the user experience on web pages, focusing on loading performance, interactivity responsiveness, and visual stability. Introduced by Google in 2020 and incorporated as confirmed ranking signals in the Page Experience update in 2021 Core Web Vitals represent Google’s attempt to make user experience measurable and actionable, providing website owners with specific, objective targets that correlate with positive user experiences rather than abstract performance advice.

Crawl budget is the number of URLs that a search engine crawler, Googlebot being the most important, will crawl on a website within a given period of time. Search engines do not have unlimited resources to crawl every page on every website continuously, they must allocate their crawling capacity across billions of web pages. The crawl budget for a specific site determines how many of its pages get crawled and how frequently they are recrawled, directly affecting how quickly new content is discovered and indexed and how reliably existing content remains current in the search index.

Crawling is the process by which search engines, and other automated systems, systematically discover and fetch web pages using software programs called crawlers, spiders, or bots. A crawler starts with a set of known URLs, fetches the content of each URL, extracts links from the fetched content, adds those links to its list of URLs to visit, and repeats the process, traversing the web’s link graph in a continuous cycle of discovery and content retrieval.

De-indexing is the process by which a page is removed from a search engine’s index, the database of web pages that search engines query when returning results for user searches. A de-indexed page is invisible in organic search results, it cannot rank for any query, receive any organic search traffic, or contribute its content to search engine understanding of the site. From a search engine perspective a de-indexed page effectively does not exist.

Deep linking is the practice of using a URL that points directly to a specific piece of content, a particular page, section, product, article, or application state, rather than to a homepage or top-level entry point. A deep link navigates users to the exact content they are seeking in a single click rather than requiring them to navigate from a generic entry point to the specific destination.

DNS caching is the process of storing DNS lookup results temporarily so that future requests for the same information can be answered immediately from the stored copy rather than repeating the full lookup process. When a DNS resolver looks up the IP address for example.com and receives the answer it saves that answer, along with an expiry time determined by the record’s DNS TTL: and serves it to any subsequent request for the same record without querying the authoritative nameserver again.

DNS failover is a technique that automatically changes DNS records to redirect traffic from a primary server to a backup server when the primary becomes unavailable. When monitoring detects that the primary server is down, not responding to health checks, returning errors, or experiencing degraded performance, the DNS records pointing to it are automatically updated to point to the backup instead. Visitors who were going to the primary are now routed to the backup without any manual intervention.

DNS hijacking is an attack in which DNS queries are intercepted and redirected to malicious or unauthorised nameservers or IP addresses without the knowledge or consent of the domain owner or the user making the query. Instead of receiving the legitimate answer from the authoritative nameserver the victim receives a fraudulent response, potentially pointing to a fake website designed to steal credentials, serving malware, or simply redirecting traffic to a competitor or a monetisation page.

A DNS lookup is the process of querying the DNS system to translate a human-readable domain name into the information stored in DNS records: most commonly an IP address that a browser or application can use to establish a network connection. Every time a browser navigates to a website, an application connects to an API, an email server delivers a message, or any networked service needs to resolve a hostname, a DNS lookup is performed behind the scenes.

DNS propagation is the process by which changes to DNS records spread across the global network of DNS resolvers, caches, and nameservers after being made on an authoritative nameserver. When a DNS record is updated, changing an A record to point to a new server, adding a CNAME record to connect a domain to redirect infrastructure, or updating an MX record to change email routing, that change does not take effect everywhere simultaneously. It spreads gradually as cached copies of the old record expire and resolvers fetch fresh data from the authoritative nameserver.

DNS TTL, Time To Live, is a value set on each DNS record that specifies how many seconds DNS resolvers should cache that record before discarding it and fetching a fresh copy from the authoritative nameserver. It is the expiry timer attached to every cached DNS response, the clock that determines when a resolver stops serving an old cached value and queries for an updated one.

DNS, Domain Name System, is the internet’s naming infrastructure. It is the system that translates human-readable domain names like example.com into the numerical IP addresses that computers use to identify and communicate with each other. Without DNS, visiting a website would require knowing and typing a string of numbers, 93.184.216.34, instead of a domain name. DNS makes the web navigable by humans.

DNSSEC, DNS Security Extensions, is a suite of specifications that adds cryptographic authentication to the DNS system. It allows DNS resolvers to verify that the DNS records they receive are authentic, that they came from the legitimate authoritative nameserver for a domain and have not been modified in transit or forged by an attacker.

Domain authority, DA, is a proprietary metric developed by Moz that predicts how likely a domain is to rank in search engine results pages based primarily on the strength and quality of its backlink profile. Scored on a logarithmic scale from 1 to 100 domain authority provides a single number that represents the accumulated link-based ranking power of an entire domain, a proxy for the SEO equity that the domain has built through its history of content, links, and online presence.

Domain consolidation is the process of merging multiple domain names: each previously hosting separate content or operating independently, into a single primary domain. Instead of maintaining distinct websites or web properties across multiple domains an organisation chooses one canonical domain and migrates all content, traffic, and accumulated authority from the others to it through permanent redirects, DNS changes, and content migration.

Domain expiry is the point at which a domain name registration period ends, the date on which the domain owner’s paid registration lapses and the domain is no longer exclusively held by that registrant. Every domain registration has an expiry date, typically one to ten years after the initial registration depending on how long the domain was registered for. When that date passes without renewal the domain enters a series of grace periods before eventually being released for anyone to register.

Domain flipping is the practice of purchasing domain names at a low price and selling them at a higher price for profit, the domain equivalent of real estate flipping. A domain investor identifies names with unrealised value, available for standard registration fees or underpriced in the aftermarket, acquires them, and sells them to buyers who need those names for businesses, brands, or projects. The profit comes from the gap between acquisition cost and sale price.

Domain forwarding is the process of automatically sending visitors who arrive at one domain to a different destination domain. When someone types or clicks a forwarded domain the web infrastructure receives the request and immediately passes it on, forwarding the visitor to another address without displaying content at the original domain itself.

Domain migration is the process of moving a website from one domain name to another, transferring all content, functionality, and ideally all accumulated SEO equity and link juice from the old domain to the new one. A company rebranding from oldname.com to newname.com undergoes a domain migration. A business consolidating multiple acquired domains under one primary domain executes a domain migration. An organisation moving from a ccTLD to a gTLD: or from .com to a new TLD: performs a domain migration.

Domain parking is the practice of registering a domain name and holding it without hosting an active website at that address. The domain is registered, paid for and associated with the registrant in the domain registrar’s records, but no meaningful content is served at the domain. Instead the domain either displays a placeholder page, forwards visitors to another destination through a redirect, or simply sits unused waiting for a future purpose.

Domain privacy, also called WHOIS privacy, privacy protection, or domain proxy, is a service that replaces a domain registrant’s personal contact information in public WHOIS records with the contact details of a privacy proxy service. Instead of a domain owner’s name, home address, personal email address, and phone number being publicly visible to anyone who performs a WHOIS lookup the record shows generic contact information belonging to the privacy service, protecting the registrant’s personal details from public exposure.

Domain rebranding is the process of moving a website, and the brand identity associated with it, from one domain name to a new domain name that reflects a changed or updated brand. When a company renames itself, merges with another organisation, repositions its brand identity, or simply determines that its current domain no longer accurately represents what it does a domain rebrand replaces the old domain with a new one, transitioning all web traffic, brand recognition, and accumulated SEO equity from the old address to the new.

Duplicate content is identical or substantially similar content that appears at multiple URLs, either within the same website or across different websites. When search engines crawl the web and find the same content at two or more addresses they face a fundamental challenge, which URL should be indexed, which should appear in search results, and how should the link juice and SEO equity from backlinks pointing to any version be attributed.

Dynamic DNS, commonly abbreviated as DDNS, is a service that automatically updates DNS records when the IP address associated with a hostname changes. Where standard DNS configuration involves setting a fixed IP address in an A record that remains static until manually changed, dynamic DNS continuously monitors the current IP address and updates the DNS record automatically whenever the address changes, keeping the domain name pointed at the correct destination at all times.

Edge computing is a distributed computing paradigm that moves data processing, application logic, and storage capabilities away from centralised data centres and toward the edges of the network, locations physically close to the users and devices that generate and consume the data being processed. Rather than sending every computation to a distant central server edge computing performs processing at the nearest available node, reducing the distance data must travel and therefore reducing latency, bandwidth consumption, and dependence on central infrastructure.

ERR_TOO_MANY_REDIRECTS is a browser error that appears when a browser gets stuck following a chain of redirects that never reaches a final destination. The browser follows redirect after redirect, each one pointing to another URL, until it hits its internal limit, gives up, and displays the error to the visitor.

Forced HTTPS is the practice of automatically redirecting all HTTP requests to the corresponding HTTPS version, ensuring that every visitor to a website connects securely regardless of whether they typed http:// or https:// in their browser, clicked an HTTP link, or arrived from an HTTP bookmark. When forced HTTPS is in place no HTTP version of any page is ever served, every HTTP request receives a redirect response pointing to the HTTPS equivalent.

Googlebot is Google’s automated web crawling system, the software infrastructure responsible for discovering, fetching, and processing web content for inclusion in Google’s search index. Googlebot continuously crawls the web, following links, processing redirects, reading robots.txt directives, and gathering the signals that Google’s indexing and ranking systems use to understand and evaluate web content. Without Googlebot’s crawl no page can appear in Google Search results, the crawl is the necessary first step in Google’s pipeline from web content to search result.

HSTS, HTTP Strict Transport Security, is a web security policy mechanism that instructs browsers to connect to a domain exclusively over HTTPS for a specified period, eliminating HTTP connections entirely rather than relying on server-side redirects to upgrade them. Once a browser receives an HSTS header from a domain it remembers that the domain requires HTTPS and automatically upgrades all future HTTP requests to HTTPS before they leave the device, without making any network request over HTTP at all.

HTTP caching is the mechanism by which web browsers, CDN edge servers, reverse proxies, and other intermediaries store copies of HTTP responses, reusing stored responses for subsequent requests rather than fetching fresh content from the origin server every time. By serving cached responses caching reduces latency for users, who receive responses from nearby or local caches rather than from distant origin servers, reduces bandwidth consumption, the same content is not repeatedly transmitted from origin to user, and reduces load on origin servers, which handle only requests that cannot be served from cache.

HTTP preconnect is a browser performance hint that instructs the browser to establish a network connection to a specified origin, completing the DNS resolution, TCP handshake, and TLS negotiation, before any resources from that origin have been explicitly requested. By completing these connection establishment steps early, during idle time or in parallel with other work, preconnect eliminates the connection setup overhead when the browser later needs to actually fetch resources from the preconnected origin.

HTTP to HTTPS migration is the process of moving a website from serving content over unencrypted HTTP connections to serving it over encrypted HTTPS connections, implementing TLS encryption across the entire site, obtaining and installing SSL certificates, configuring permanent redirects from all HTTP URLs to their HTTPS equivalents, and updating all internal references to use the new HTTPS addresses.

HTTP/2 is the second major version of the HTTP protocol, the communication standard that governs how browsers and web servers exchange data. Released as a formal standard in 2015 HTTP/2 introduced fundamental changes to how HTTP requests and responses are transmitted, addressing performance limitations that had accumulated in HTTP/1.1 over its nearly two decades of dominant use. The core changes, multiplexing, header compression, server push, and binary framing, deliver measurably faster page load times particularly for pages that load many resources from the same server.

HTTP/3 is the third major version of the HTTP protocol, the communication standard governing data exchange between browsers and web servers. Standardised in RFC 9114 in June 2022 HTTP/3 represents the most fundamental architectural change in HTTP’s history, replacing the TCP transport layer that HTTP has used since its inception with QUIC, a new transport protocol built on UDP. This transport layer replacement addresses the one significant performance limitation that HTTP/2 could not solve, TCP head-of-line blocking, while preserving and extending all of HTTP/2’s multiplexing, header compression, and performance improvements.

HTTP, HyperText Transfer Protocol, is the foundational communication protocol of the World Wide Web. It defines the rules by which browsers and web servers communicate, how a browser requests a resource, how a server responds, what headers accompany those requests and responses, and how different types of content are identified and transferred. Every time a browser loads a web page, fetches an image, submits a form, or makes an API call it is using HTTP, or its secure variant HTTPS: to communicate with servers.

HTTPS, HyperText Transfer Protocol Secure, is the secure version of HTTP, the protocol used to transfer data between web browsers and servers. HTTPS encrypts the data exchanged during a web session using TLS: Transport Layer Security, ensuring that information transmitted between a visitor’s browser and the web server cannot be intercepted, read, or modified by third parties on the network path between them.

Indexing is the process by which search engines discover web pages, analyse their content, and store the information in a searchable database, the search index, so that pages can be retrieved and ranked in response to user queries. A page that has been indexed exists in the search engine’s database and is eligible to appear in search results. A page that has not been indexed, regardless of how good its content is or how many backlinks it has, cannot appear in organic search results at all.

INP, Interaction to Next Paint, is a Core Web Vitals metric that measures the responsiveness of a web page to user interactions, specifically the time from when a user interacts with a page to when the browser next paints a visual update in response to that interaction. INP replaced First Input Delay, FID, as the third Core Web Vital in March 2024, providing a more comprehensive assessment of interaction responsiveness throughout the entire page visit rather than only the first interaction.

IPv4, Internet Protocol version 4, is the fourth and historically dominant version of the Internet Protocol, the fundamental communication standard that governs how data is addressed, routed, and delivered across the internet and other IP networks. Standardised in RFC 791 in September 1981 IPv4 has been the backbone of internet communication for over four decades, the protocol that made the modern internet possible and that still carries the majority of internet traffic today despite the gradual transition to its successor IPv6.

IPv6, Internet Protocol version 6, is the most recent version of the Internet Protocol, the fundamental communication standard governing how data is addressed and routed across the internet. Developed by the Internet Engineering Task Force and standardised in RFC 2460 in 1998, later updated by RFC 8200 in 2017, IPv6 was designed primarily to solve the address exhaustion problem of IPv4 by providing a vastly larger address space while simultaneously improving routing efficiency, security, and network configuration.

A language-based redirect is an HTTP redirect that routes visitors to content in their preferred or most appropriate language, determined by analysing the visitor’s browser language settings, geographic location, or explicit language preference, rather than serving all visitors the same language version regardless of their language background. Where a regional redirect routes primarily based on geographic location a language-based redirect routes primarily based on linguistic preference, the distinction matters because geography and language do not always align perfectly.

Latency is the time delay between an action being initiated and its effect being observed, in web infrastructure specifically the time between a browser sending an HTTP request and beginning to receive the server’s response. Measured in milliseconds latency is one of the most fundamental performance metrics in web infrastructure, it determines how quickly users begin to see responses to their requests and directly affects user experience, engagement, conversion rates, and SEO rankings.

Lazy loading is a web performance technique that defers the loading of non-critical resources, images, videos, iframes, and JavaScript modules, until they are actually needed rather than loading everything simultaneously when the page first loads. Resources that are not immediately visible to the user, below the fold, outside the current viewport, or not needed for initial interaction, are withheld from loading until the user scrolls them into view or explicitly triggers them. The result is a faster initial page load, fewer resources compete for bandwidth and processing during the critical loading window, and reduced overall bandwidth consumption when users do not scroll through the entire page.

LCP, Largest Contentful Paint, is a Core Web Vitals metric that measures the time from when a page begins loading to when the largest content element visible in the viewport has fully rendered. LCP captures the moment at which a user perceives the main content of a page to have loaded, the point when the most visually significant piece of content becomes visible and the page feels substantially complete rather than still loading.

Let’s Encrypt is a free, automated, and open certificate authority that provides SSL certificates to anyone who controls a domain, at no cost and with no manual process beyond proving domain control. Launched in 2016 by the Internet Security Research Group, ISRG, Let’s Encrypt was created with a single mission, to make HTTPS the default for the entire web by removing the two biggest barriers to SSL adoption, cost and complexity.

Link juice is an informal SEO term describing the ranking power, or SEO equity: that passes from one webpage to another through hyperlinks. When a webpage links to another page it passes some of its authority, trust, and ranking potential to the destination, the linked page receives a portion of the linking page’s accumulated ranking signals. This transfer of ranking power through links is what the term link juice captures, authority flowing like liquid from one page to another through the connections between them.

Link preservation is the practice of maintaining the accessibility and value of hyperlinks over time, ensuring that URLs referenced in external content, internal navigation, bookmarks, marketing materials, and search engine indexes continue to deliver users and crawlers to relevant, functioning destinations rather than returning errors. Link preservation recognises that every URL shared, linked to, or indexed represents an investment, in user trust, in SEO equity, in marketing effectiveness, and that this investment is protected only if the URL continues to function correctly regardless of changes to the underlying site structure.

Link rot is the gradual deterioration of hyperlinks over time as the pages they point to move, are deleted, are reorganised, or become inaccessible, leaving behind broken links that lead visitors to error pages rather than the intended content. The term captures the organic, inevitable quality of this decay, like physical rot that slowly degrades material over time, link rot quietly erodes the web’s interconnected structure as URLs that once pointed to valuable content increasingly point to nothing.

Load balancing is the process of distributing incoming network requests across multiple servers, ensuring that no single server bears the full burden of handling all traffic and that the workload is spread efficiently across the available server capacity. A load balancer sits in front of a pool of servers and routes each incoming request to one of the available servers according to a distribution algorithm, preventing any individual server from becoming a bottleneck while ensuring that the application remains responsive and available even when individual servers fail or are taken offline for maintenance.

Minification is the process of removing unnecessary characters from source code, whitespace, comments, line breaks, and redundant syntax, without changing the code’s functionality, to reduce file size and improve the speed at which files are downloaded by browsers. A minified JavaScript file containing the same logic as its original source might be 30-70% smaller, transmitting faster over the network and parsing more quickly in the browser.

mTLS, mutual TLS, is an extension of the standard TLS protocol in which both the client and the server authenticate each other using SSL certificates: rather than the standard TLS model where only the server presents a certificate to the client. In standard TLS the client verifies the server’s identity through its certificate but the server accepts connections from any client without verifying the client’s identity. In mTLS both parties present certificates, the server proves its identity to the client and the client proves its identity to the server, before the encrypted connection is established.

Nginx, pronounced engine-x, is an open-source web server, reverse proxy, load balancer, and HTTP cache that has become one of the most widely deployed pieces of web infrastructure in the world. Created by Igor Sysoev and first publicly released in 2004 Nginx was designed specifically to address the C10K problem, the challenge of handling ten thousand simultaneous connections on a single server, a problem that Apache’s process-based architecture struggled to solve efficiently.

Page authority, PA, is a proprietary metric developed by Moz that predicts how likely a specific web page is to rank in search engine results based primarily on the strength and quality of the backlink profile pointing to that individual URL. Where domain authority measures the ranking potential of an entire domain as a unit page authority measures the ranking potential of a single page, https://example.com/specific-page: based on the links pointing specifically to that URL rather than to the domain as a whole.

Page speed is a measure of how quickly a web page loads and becomes usable for visitors, encompassing the time from a user initiating a navigation to the point at which the page content is fully loaded, visually rendered, and interactive. Page speed is not a single number but a collection of measurements, different metrics capture different aspects of the loading experience, from how quickly the first content appears to how long until the page responds to user input.

PageRank is a link analysis algorithm developed by Google founders Larry Page, after whom it is named, and Sergey Brin while they were PhD students at Stanford University. Published in their 1998 paper “The Anatomy of a Large-Scale Hypertextual Web Search Engine” PageRank introduced the foundational idea that the importance of a web page can be measured by the quantity and quality of other pages linking to it, treating links as votes of confidence where votes from more important pages carry more weight than votes from less important pages.

Prefetching is a browser performance technique that speculatively loads resources, web pages, assets, or data, before the user explicitly requests them, anticipating that the resources will be needed in the near future and loading them during idle time so they are immediately available when the user does navigate to them. Where normal resource loading is reactive, the browser fetches what is needed when it is needed, prefetching is proactive, the browser fetches what might be needed before the user asks for it.

Preloading is a browser performance technique that instructs the browser to fetch specific resources needed for the current page as early as possible, before the browser would normally discover and request them through its regular parsing and rendering process. Where prefetching speculatively loads resources for future navigations preloading prioritises resources for the current page, ensuring critical assets are available sooner in the loading sequence than they would otherwise be.

Recursive DNS is the process by which a DNS resolver takes on the full responsibility of resolving a domain name query on behalf of a client, querying multiple servers in the DNS hierarchy until it finds the definitive answer and returns it. When a browser asks a recursive resolver to look up example.com the resolver does not simply say “I don’t know, ask someone else”, it performs all the necessary queries itself, working through root nameservers, TLD nameservers, and authoritative nameservers in sequence until it has the answer.

SEO equity is the accumulated ranking power, authority, and trust that a website or specific URL has built over time through its history of backlinks, content quality, user engagement, and technical performance signals. It represents the sum of all positive ranking signals associated with a domain or URL, the hard-won authority that enables pages to rank for competitive queries and that persists as an asset even as content is updated, designs change, and strategies evolve.

Serverless is a cloud computing execution model in which the cloud provider dynamically manages the allocation and provisioning of servers, developers write and deploy code without configuring, managing, or maintaining the underlying server infrastructure. The name is somewhat misleading, servers absolutely exist and run serverless code, but from the developer’s perspective the servers are invisible. The developer writes a function, deploys it to the serverless platform, and the platform handles everything else, provisioning compute capacity, scaling up under load, scaling down during quiet periods, applying security patches, and managing availability.

SNI, Server Name Indication, is a TLS extension that allows a client to specify which domain it is connecting to at the beginning of the TLS handshake, before the server has presented its SSL certificate. This allows a single server with a single IP address to host SSL certificates for multiple different domains, presenting the correct certificate for whichever domain the client is connecting to.

SSL termination, also called TLS termination, is the process of decrypting HTTPS traffic at a specific point in the network infrastructure before passing it onward to backend servers. The encrypted connection that a browser establishes with a server is terminated, ended, at a designated component, a load balancer, reverse proxy, CDN edge node, or dedicated SSL termination device, rather than being maintained all the way to the application server that ultimately handles the request.

SSL, Secure Sockets Layer, is a cryptographic protocol that establishes encrypted, authenticated connections between clients and servers over the internet. Originally developed by Netscape in the mid-1990s SSL created the foundation for secure web communication, enabling browsers to connect to servers with confidence that the connection was private, that the server was who it claimed to be, and that data transmitted could not be intercepted or modified in transit.

A 301 redirect and a 302 redirect are the two most commonly used HTTP redirect status codes on the web. Both send visitors and web crawlers from one URL to another automatically and invisibly. But they communicate fundamentally different things to browsers and search engines, and using the wrong one has real consequences for both user experience and SEO.

A 301 redirect and a 308 redirect are both permanent HTTP redirects that tell browsers and search engines a URL has moved to a new location forever. Both pass SEO equity to the destination. Both cause search engines to update their index over time. Both are cached by browsers.

A 302 redirect and a 307 redirect are both temporary HTTP redirects that tell browsers and search engines a URL has moved to a different location for now, while keeping the original URL intact. Both are treated as temporary redirects by search engines. Both leave the original URL in the search index. Neither transfers SEO equity to the destination.

The HTTP Location header is a response header sent by a server to tell a browser or client where to find a resource at a different URL. It is the mechanism that makes URL redirects work, without it, a 3xx status code would tell a browser that a redirect is happening but give it nowhere to go.

Thin content is web content that provides little or no genuine value to users, pages that exist without delivering meaningful information, unique insights, or substantive answers to the questions they purport to address. The term captures the shallow, insubstantial quality of these pages, they have the form of content without its substance, words on a page that do not meaningfully inform, help, or engage the visitor.

TLS, Transport Layer Security, is the cryptographic protocol that secures communication between clients and servers over the internet. It provides three fundamental security properties, encryption that prevents eavesdropping, authentication that verifies the server’s identity, and integrity verification that detects tampering. TLS is the technology that makes HTTPS possible, the S in HTTPS stands for Secure and that security is delivered entirely by TLS.

Traffic routing is the process of directing incoming web requests to appropriate destinations, servers, content variants, geographic locations, or entirely different URLs, based on attributes of the request, the requesting client, or configured business rules. Every web request that arrives at a network infrastructure component, a DNS resolver, a CDN edge node, a load balancer, a reverse proxy, or a web server: is subject to routing decisions that determine where it goes next.

TTFB, Time to First Byte, is a web performance metric that measures the duration from when a browser sends an HTTP request to when it receives the first byte of the server’s response. TTFB captures the combined latency of the network connection establishment, server processing time, and network transmission time for the response to begin arriving at the client. It is the foundational server-side performance metric, the time the browser spends waiting before any response content begins to arrive.

Uptime is the proportion of time that a system, a server, website, service, or infrastructure component, is operational, available, and responding correctly to requests. Expressed as a percentage uptime measures reliability, a system with 99.9% uptime is unavailable for approximately 8.7 hours per year, while a system with 99.99% uptime is unavailable for only approximately 52 minutes per year. The difference between these two figures, 99.9% and 99.99%, seems small but represents nearly an eightfold improvement in availability that matters significantly for production web infrastructure.

URL canonicalization, also spelled canonicalisation in British English, is the process of selecting a single preferred URL for content that is accessible at multiple addresses and then enforcing that preference through technical signals that consolidate search engine attention, link juice, and SEO equity to the chosen canonical form. When the same or substantially similar content can be reached at several different URLs the canonicalization process establishes which one is definitive, the canonical URL: and implements the mechanisms that communicate this preference to search engines and redirect users from non-canonical addresses to the canonical one.

URL encoding, also called percent encoding, is the process of converting characters that are not permitted or have special meaning in URLs into a safe format that can be transmitted across the internet without ambiguity or corruption. When a character cannot appear directly in a URL, because it is reserved for a specific structural purpose, because it falls outside the ASCII character set, or because it has no defined URL representation, URL encoding replaces it with a percent sign followed by the two-digit hexadecimal code representing the character’s value in the ASCII or UTF-8 encoding scheme.

URL forwarding is the process of automatically sending visitors from one web address to another. When someone types or clicks a URL that has forwarding set up, they are taken to a different destination without any action required on their part. The original URL acts as a pointer: it receives the visit and immediately passes it on.

URL masking is a technique that displays content from one URL while keeping a different URL visible in the browser address bar. When a visitor navigates to a masked URL, the page loads content from a completely different destination, but the address bar never changes. The original URL remains visible throughout the entire visit regardless of what content is actually being displayed.

URL structure is the format, organisation, and hierarchy of web addresses, the pattern and conventions that determine how URLs are constructed across a website. It encompasses the choice of protocol, domain, subdomain or subdirectory organisation, directory depth, slug format, parameter usage, and all other elements that shape what a site’s URLs look like and how they communicate the organisation of the site’s content.

UTM tracking, Urchin Tracking Module tracking, is a standardised method of appending identifying parameters to URLs that enables web analytics platforms to attribute website visits to specific marketing campaigns, traffic sources, and channels. When a user clicks a URL containing UTM parameters the analytics tracking code on the destination page reads the parameter values and records the session with the corresponding campaign attribution, allowing marketers to measure how much traffic, how many conversions, and how much revenue each campaign, source, and channel generates.

Website migration is the process of making significant changes to a website’s technical infrastructure, moving it to a new domain, switching to a different content management system, restructuring its URL architecture, changing its hosting environment, or any combination of these, while preserving as much accumulated SEO equity, organic traffic, and search ranking as possible. A migration is distinguished from routine site maintenance by its scope and risk, migrations involve coordinated changes to multiple systems simultaneously and carry meaningful risk of SEO disruption if not executed correctly.

WHOIS, pronounced “who is”, is both a protocol and a database system that stores and provides publicly accessible information about domain name registrations. When a domain is registered the registrant’s contact information, registration dates, nameserver details, and domain registrar information are recorded in WHOIS databases maintained by registrars and registries. Anyone can query these databases to find out who registered a domain, when it was registered, when it expires, and how to contact the domain owner.

www, World Wide Web, is a subdomain prefix that has been conventionally placed before domain names to indicate a website address since the early days of the internet. In www.example.com the www is a subdomain of example.com: technically identical in DNS terms to any other subdomain like blog.example.com or shop.example.com: but carrying the historical convention that this subdomain hosts the public-facing website.