Skip to content
UX Atlas
Plate WRT·007 · UX writingGrid F2 · Rev. 2026-08-14

SEO for Content Products

Making content findable by search engines, which overlaps almost entirely with making it good for people.

UX writingCraft conventionIntermediate

Definition

Search optimisation for content products is largely a matter of clear structure, honest metadata, fast pages and stable URLs. The techniques that conflict with user experience are also the ones search engines penalise.

Craft convention. True because the industry converged on it. Breaking it costs familiarity, not correctness.

On this plate
  1. 1Definition
  2. 2What matters, in rough order
  3. 3What actually moves visibility
  4. 4In practice
  5. 5Local chart
  6. 6Sources
  7. 7Continue from here

Reach for this when

  • Building a content-led product.
  • Planning a redesign or migration.
  • Structuring a growing resource library.
  • Content is being restructured, or a site is being rebuilt on new addresses.

Common mistakes

  • URLs changed without redirects.
  • Duplicated titles and descriptions.
  • Heading levels chosen for appearance.
  • Content written for crawlers rather than readers.

What matters, in rough order

  1. 1.Content that answers the question someone actually typed.
  2. 2.Correct heading structure, which serves both screen readers and crawlers.
  3. 3.Stable, readable URLs. Changing them without redirects is the most common self-inflicted traffic loss.
  4. 4.Unique title and meta description per page, describing the specific content.
  5. 5.Fast loading and stable layout, since Core Web Vitals are a ranking input.
  6. 6.Internal linking between related content, which distributes authority and helps readers.
  7. 7.Structured data where a recognised schema applies, such as articles, FAQs and breadcrumbs.
  8. 8.Canonical URLs where the same content is reachable by several paths.

What actually moves visibility

Do

  • Answer the question the search was asking, near the top of the page.
  • Use one clear h1 and a real heading structure, which serves readers and crawlers alike.
  • Keep URLs stable, and redirect properly when they must change.
  • Make the content reachable without JavaScript where you can.

Do not

  • Write for a keyword rather than for the question behind it.
  • Ship a redesign that changes every URL with no redirect map.
  • Hide the answer below a wall of preamble.
  • Treat metadata as a substitute for content that answers something.

In practice

  1. i.

    The redesign that lost the traffic

    URLs

    A relaunch with a new URL structure and no redirects dropped organic traffic sharply and took months to recover. The design was better. The addresses were the asset nobody had listed.

Local chart

WRT·007 · Region III · Grid F2

This entry and the entries it is stated to connect with. Each line is labelled with what the connection means.

LighthouseTOOL·031 · OFTEN USED WITHMatomoTOOL·028 · OFTEN USED WITHWebflowTOOL·005 · OFTEN USED WITHFixing a Search That Returned NothingCASE·006 · PRACTICAL EXAMPLEPre-Launch ChecklistCHK·009 · CHECK YOUR WORKWeb UX ChecklistCHK·011 · CHECK YOUR WORKCanonical URLTERM·130 · SHORT DEFINITIONMetadataTERM·013 · SHORT DEFINITIONSEOTERM·129 · SHORT DEFINITIONStructured DataTERM·131 · SHORT DEFINITIONAlt TextA11Y·007 · RELATED CONCEPTHeading StructureA11Y·006 · RELATED CONCEPT

Sources

Where a source establishes something narrower than the popular reading of it, the note says so.

  1. [1]

    Google Search Essentials

    Google Search Central

Continue from here

Each link says what the connection is, so you can tell a principle from an alternative from a thing people mix this up with.

Often used with

These usually appear in the same screen or the same decision.

Practical example

A worked decision where this was the deciding factor.

Check your work

Review passes that test whether this was done properly.

Short definition

The one-paragraph version, for when that is all you need.

Related concept

Connected closely enough to change how you apply this.