Page Headings Structure

Headings help organize a page so people can quickly understand what it covers and find the section they need. A well-structured page uses headings to break content into clear sections and show how ideas relate to one another. Good headings make long pages easier to scan and easier to manage.

 

Use headings to organize content

Headings should divide the page into meaningful sections. They help users move through the content without having to read every paragraph from top to bottom.

 

A page with good headings is easier to use when it includes:

  • several topics on one page

  • longer explanations

  • instructions with multiple parts

  • grouped resources or details

  • content that users may want to scan quickly

 

If a page only has a short amount of content, a main heading may be enough. Longer pages usually need a clear heading structure.

 

Start with one main heading

Every page should begin with one main heading. That heading introduces the page topic. The sections below it should support that topic, not compete with it.

 

After the main heading, use section headings to break the page into clear parts. If one section needs smaller parts underneath it, use subheadings.

 

A simple pattern looks like this:

  • main page heading

  • section heading

  • subheading when needed

 

The goal is to show users how the page is organized.

 

Keep headings in order

Headings should follow a clear order. Do not jump around between heading levels.

 

For example:

  • use the main heading first

  • then use section headings

  • then use subheadings only when they belong under that section

 

Do not skip from a main heading straight to a smaller subheading level just because it looks better visually. The heading level should reflect the structure of the content, not just the appearance. The live page already calls this out as a key rule, and that should stay.

 

Make headings match the content below them

A heading should clearly describe the section that follows. Users should not read a heading and then feel surprised by the content underneath it.

 

Less helpful

  • Information

  • Details

  • Resources

  • Other

 

Better

  • Application deadlines

  • Required documents

  • Contact information

  • Parking and transportation

 

The heading should give users a clear idea of what they are about to read.

 

Keep headings short and natural

Write headings in a way that feels clear and human. They should be easy to scan and easy to understand.

 

Avoid headings that are:

  • too broad

  • too long

  • overly formal

  • packed with extra wording

 

Less effective

  • Important information regarding the required materials that must be submitted as part of the application process

 

Better

  • Required application materials

 

Shorter headings are usually easier to scan.

 

Use sentence case

Headings usually work best in sentence case. That means only the first word and proper nouns are capitalized.

 

Use

  • Required application materials

  • Student support services

  • Campus parking map

 

Avoid

  • Required Application Materials

  • STUDENT SUPPORT SERVICES

  • Campus Parking Map

 

The current live page already recommends sentence case, and that guidance fits well here.

 

Do not use headings just to make text look bigger

Headings are for structure, not decoration. Do not apply a heading style just because you want text to appear larger or bolder.

 

If text is not actually introducing a section, it probably should not be a heading.

 

This is one of the most important habits to get right because it affects how the whole page is organized. The live page already includes this rule, and it is worth keeping in plain language.

 

Use task-based headings when helpful

If a section helps users do something, the heading can reflect that task directly.

 

Examples:

  • Submit your documents

  • Check your application status

  • Request an appointment

  • Contact the department

 

This can make the page feel more direct and easier to act on, especially for service or process pages.

 

Avoid links inside headings

Headings should label sections, not act like navigation links. Keep links in the body content, callout areas, or next-step sections instead of placing them inside the heading itself. The live page includes this rule, and it is a good one to keep because linked headings can make pages harder to scan and maintain.

 

Keep related content together

If a section has several subtopics, group them under one clear section heading instead of scattering similar content across the page.

 

For example, instead of mixing deadlines, required documents, and contact information in random order, group them into separate sections with clear headings. This makes the page easier to follow and easier to update later.

 

Before publishing

Use this quick review before adding or approving page headings:

  • The page has one clear main heading.

  • Headings are used to organize real sections of content.

  • The heading order is logical and not skipped.

  • Each heading matches the content below it.

  • Headings are short, clear, and easy to scan.

  • Sentence case is used consistently.

  • Headings are not being used just for styling.

  • Links were not placed inside headings.

 

Related guidance: Main page heading (H1), Page Title, Content Development, and Define the Purpose of Page.