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

SEO, performance, and hosting: Canonical paths

A canonical link identifies the preferred URL for duplicate content; it is not a redirect or an indexing guarantee.

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 canonical paths
Build this first target: <head>; <title> inside <head> containing “Log workshop”. Inspect the structure before checking the lesson.
Hint & worked example
A canonical link identifies the preferred URL for duplicate content; it is not a redirect or an indexing guarantee.
The requested elements, attributes, content, and hierarchy exist outside comments.
```
<head><title>Log workshop</title></head>
```
Common mistake to avoid: A visual appearance alone guarantees the intended HTML meaning.
2
Extend the canonical paths example
Extend your file to include: <head>; <title> inside <head> containing “Log workshop”; <link> inside <head> (rel="canonical", href="/workshops/logs/"). Inspect the structure before checking the lesson.
Hint & worked example
A canonical link identifies the preferred URL for duplicate content; it is not a redirect or an indexing guarantee.
The requested elements, attributes, content, and hierarchy exist outside comments.
```
<head><title>Log workshop</title><link rel="canonical" href="/workshops/logs/"></head>
```
Common mistake to avoid: Replacing semantic elements with generic divs automatically improves accessibility.
3
Verify the complete canonical paths pattern
Finish the pattern with: <head>; <title> inside <head> containing “Log workshop”; <link> inside <head> (rel="canonical", href="/workshops/logs/"); <a> (href="/workshops/logs/") containing “Log workshop”. Inspect the structure before checking the lesson.
Hint & worked example
A canonical link identifies the preferred URL for duplicate content; it is not a redirect or an indexing guarantee.
The requested elements, attributes, content, and hierarchy exist outside comments.
```
<head><title>Log workshop</title><link rel="canonical" href="/workshops/logs/"></head><a href="/workshops/logs/">Log workshop</a>
```
Common mistake to avoid: A visual appearance alone guarantees the intended HTML meaning.

Understand the pattern

A canonical link identifies the preferred URL for duplicate content; it is not a redirect or an indexing guarantee.

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>Log workshop</title><link rel="canonical" href="/workshops/logs/"></head><a href="/workshops/logs/">Log workshop</a>

A canonical link identifies the preferred URL for duplicate content; it is not a redirect or an indexing guarantee.

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 canonical paths?Replacing semantic elements with generic divs automatically improves accessibility.A canonical link identifies the preferred URL for duplicate content; it is not a redirect or an indexing guarantee.A visual appearance alone guarantees the intended HTML meaning.

Apply it elsewhere

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

Keep the momentum.

Complete the lab, then explain and apply the pattern.

Next: SEO, performance, and hosting: Viewport metadata 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