Understand Web fundamentals
Start with a page you know. Separate its address, the software reading it and the exchanges needed to display it. This avoids looking for a domain problem in page copy or confusing a downloaded file with an HTML page.
21 concepts to explore with definitions and practical advice.
Search the full glossary
A reading path
1. Identify the resource
Record the full URL, path and useful parameters. A deep link should reach the intended information without requiring a homepage visit.
- URL
Uniform Resource Locator: address identifying a resource location and the protocol used to access it.
- Domain name
Hierarchical name identifying an Internet destination, such as example.fr. It differs from a complete URL, hosting and a trademark; management should remain with the appropriate registrant. Separate domain, subdomain, path and parameters when comparing addresses; a similar name does not establish common ownership.
- Deep link
Link leading directly to a particular page, view or section without starting at the homepage. On the web, a fragment such as #hours can identify part of a page. The destination should provide enough context to understand it and enforce the same access rights as ordinary navigation.
2. Read the exchange
The browser requests a resource and receives a response. Status helps describe the result; content and type indicate what can be displayed or downloaded.
- Browser
Software that requests web resources, interprets their content and presents pages or applications to users. Its engine, settings and extensions can affect observed behavior. A browser differs from a search engine: the former is used to visit the latter, among other services.
- HTTP
Protocol for exchanging messages between clients and servers through requests and responses. HTTP defines methods, headers and statuses; HTTPS protects transport using TLS. The same URL can produce different responses depending on method, headers or permissions. Inspect the complete exchange before concluding that a service failed.
- HTTP status code
Numeric HTTP response code describing request handling. Read it with the method and context; a visually correct page can return an incorrect status. Distinguish the returned status from displayed content: a “not found” message accompanied by 200 still announces success at protocol level.
- MIME type
Identifier for a resource format transmitted notably through HTTP, such as text/html, image/webp or application/json. The type differs from the filename extension. Check Content-Type in the actual response, especially when a JSON download returns an HTML error page.
3. Check the journey
Try the link from another entry point, then a missing address. An error page should help recover a resource while keeping an appropriate status.
- Permalink
Address intended to identify content over time, even when its presentation or technical storage changes. Stability depends on site management: “permanent” does not prevent deletion or broken links. When content moves, an equivalent destination or explicit removal status preserves an understandable route.
- Error 404
HTTP response indicating that the requested resource was not found. It does not itself distinguish temporary from permanent absence; a useful page can offer recovery paths.
- User agent
Software acting for a user during a Web request, such as a browser, crawler or screen reader.
Useful distinctions
Domain name / URL
A domain identifies part of an address; a URL can also contain a path, query and fragment. Changing pages does not necessarily change the domain.
Browser / Server
The browser uses the response to present the page; the server supplies requested resources. A display defect and an unavailable resource require different observations.
Use the vocabulary to make a decision

Situation
An old shared link no longer shows the expected record.
Before deciding
Record its URL and status before concluding that content has disappeared. Compare the destination with a genuinely available equivalent record.
A concrete check
Test the direct link and return to the section; note whether visitors can resume their journey.
Read the response before fixing the link
Visible text alone does not describe the server response. In browser developer tools, the Network panel shows the requested address, redirects and final status.
- Requested addressWhich link did the visitor open?
- Received responseWhich status and destination?
- Usable pageCan they find the expected information?
On a narrow screen, scroll the table horizontally to read all three columns.
| Observed signal | What to check | What it means |
|---|---|---|
| 200 with a “not found” message | Compare the content with the HTTP status. | The server reports success for an absent resource; status and content should agree. |
| 301 to the homepage | Check whether a replacement answers the same need. | A permanent redirect does not establish the relevance of its destination. |
| 404 for an old page | Look for an equivalent page; otherwise provide helpful navigation. | A genuine absence can retain a 404 status while helping the reader. |
Next step : Update internal links to replaced addresses, then test direct access and navigation from the parent section.
Technical reference : MDN — HTTP response status codes. The scenarios and numerical examples above are educational, not measurements of this website.
The domain alone does not describe the destination
Fictional teaching case. Open each interpretation to examine its scope; there is no score or professional assessment.
- Exact base
- Reference resolved
- Destination compared
On https://example.org/offres/, two links are contact/ and /contact/. They share the domain, but do not interpret the starting path in the same way.
Which difference should be examined?
A useful next step : Compare resolved URLs before blaming the domain. These reserved addresses are examples, not links to test.
Reference to explore : MDN · Resolving relative references · Consulted .
All concepts in this topic
Links open the full definition on its alphabet page. Acronyms and synonyms remain searchable in the main glossary.
Frequently asked questions
Does a readable address guarantee a good page?
No. It helps identify a resource but proves neither availability, relevance nor content security. Check the address and response separately.
Can an error page contain useful content?
Yes. It can offer search, sections and contact while explaining that the requested resource is missing. Useful wording should not conceal the technical state.
Primary reference documents
These documents explain technical concepts. Reading paths and examples are editorial methods to adapt to your project.