SEO, performance, and hosting · Lesson 1 of 8 · 7 minutes

SEO, performance, and hosting: Unique page titles

A page title should describe this page rather than repeat the same vague label across the site.

Open the lab Course map

Mastery 0/3Run itExplain itApply it

Current edit

PreviewNo external resources

Your objectives

Hints are always available. Wrong turns never cost XP.

1
Build unique page titles
Build this first target: <head>; <title> inside <head> containing “Workshop”. Inspect the structure before checking the lesson.
Hint & worked example
A page title should describe this page rather than repeat the same vague label across the site.
The requested elements, attributes, content, and hierarchy exist outside comments.
```
<head><title>Workshop</title></head>
```
Common mistake to avoid: A visual appearance alone guarantees the intended HTML meaning.
2
Extend the unique page titles example
Extend your file to include: <head>; <title> inside <head> containing “Linux permissions workshop | Library Lab”. Inspect the structure before checking the lesson.
Hint & worked example
A page title should describe this page rather than repeat the same vague label across the site.
The requested elements, attributes, content, and hierarchy exist outside comments.
```
<head><title>Linux permissions workshop | Library Lab</title></head>
```
Common mistake to avoid: Replacing semantic elements with generic divs automatically improves accessibility.
3
Verify the complete unique page titles pattern
Finish the pattern with: <head>; <title> inside <head> containing “Linux permissions workshop | Library Lab”; <meta> inside <head> (name="description", content="Practice reading and changing file permissions in the library workshop."). Inspect the structure before checking the lesson.
Hint & worked example
A page title should describe this page rather than repeat the same vague label across the site.
The requested elements, attributes, content, and hierarchy exist outside comments.
```
<head><title>Linux permissions workshop | Library Lab</title><meta name="description" content="Practice reading and changing file permissions in the library workshop."></head>
```
Common mistake to avoid: A visual appearance alone guarantees the intended HTML meaning.

Understand the pattern

A page title should describe this page rather than repeat the same vague label across the site.

Misconceptions to reject

A visual appearance alone guarantees the intended HTML meaning.
Replacing semantic elements with generic divs automatically improves accessibility.

The preview is a sanitized subset, not a full browser compatibility test.

Worked example and expected result

<head><title>Linux permissions workshop | Library Lab</title><meta name="description" content="Practice reading and changing file permissions in the library workshop."></head>

A page title should describe this page rather than repeat the same vague label across the site.

Try a variation

Adapt the final example to a different project name while retaining its structure and relationships. A different context still needs a real browser and accessibility check.

Explain it

Which statement correctly explains unique page titles?A page title should describe this page rather than repeat the same vague label across the site.A visual appearance alone guarantees the intended HTML meaning.Replacing semantic elements with generic divs automatically improves accessibility.

Apply it elsewhere

You reuse unique page titles in a different project. What must still be verified?Nothing; passing a single exercise guarantees every future use.Only whether the source code has the same number of lines.The meaning, relationships, and accessible names in the new document.

Keep the momentum.

Complete the lab, then explain and apply the pattern.

Next: SEO, performance, and hosting: Meta descriptions Try an incident drill

Anonymous lesson and mastery progress lasts for this session. Sign in to keep synced lesson XP between sessions; mastery stays device-local. No speed bonus, lost lives, or hint penalties.

Keep learning

MDN: HTML structure