What Is an H1 Tag? Titles, Heading Structure and WordPress Checks
Published:
Last Updated:
Category: SEO & Content
Authors: Shusaku Yosa
An H1 is the main heading of a page. It helps a reader understand the subject; it is not simply a way to make text large. Distinguish its role from the document title, then review the hierarchy and the output that the page actually provides.
An H1 communicates the page’s main subject
A useful H1 communicates what the page covers. For a setup guide, identify the system and task rather than using only a site name or “Helpful information.” Readers should be able to decide whether the page addresses their problem.
Headings also help people who navigate with assistive technology. The W3C heading guidance explains their structural role. Visual size and semantic meaning are different concerns.
A single clear main subject is a practical editorial convention, not a scoring formula. Do not judge rankings or content quality by counting H1 elements alone. Review whether the document has an understandable subject and a logical structure.
Distinguish the title element, H1 and Google’s title link
Item | Role | Relationship |
|---|---|---|
Title element | Document title, also used in browser tabs | May match the H1, but need not |
H1 | Main heading in the page content | Communicates the subject to readers |
Google title link | Heading generated for a search result | May differ from either element |
In a fictional article, the title could be “Check WordPress search visibility | Site name,” while the H1 is “Check WordPress search visibility.” The article reader may not need the site name repeated in the main heading.
Google can use information from the title element, main heading and other sources to generate a title link. Its official title-link guidance explains that the submitted string is not guaranteed to appear unchanged. If a search title differs, check whether the page’s prominent heading and document title describe the same subject.
Build a logical hierarchy around the content
Treat headings as a content outline. An H1 identifies the article, H2 headings group major sections, and H3 headings explain smaller parts within them. The goal is a meaningful relationship, not the maximum possible number of heading levels.
Level | Fictional setup-guide heading | Purpose |
|---|---|---|
H1 | Check WordPress search visibility | Overall subject |
H2 | Prepare for the review | Major section |
H2 | Inspect the public page | Another major section |
H3 | When the page requires login | A branch within the inspection |
H3 | When a noindex directive appears | Another branch in that section |
Changing an H2 to an H4 merely to make it look smaller can make the outline confusing. Handle presentation separately from the content hierarchy. A short list also does not need every bullet promoted into a heading.
Rewrite vague and keyword-stuffed headings
Weak wording | Possible rewrite | Reason |
|---|---|---|
About SEO | SEO basics and your first checks | Defines a useful scope |
SEO ranking WordPress optimization | A WordPress search visibility checklist | Replaces a keyword pile with a task |
Plan A | Plan A features and eligibility | Explains the decision available |
The complete fix | Checks for common measurement failures | Replaces a guarantee with an inspectable task |
These are fictional editing examples, not accounts of ranking improvements. The test is whether the heading accurately describes what the page delivers. A heading promising a price comparison needs actual comparison conditions and a reliable way to verify prices in the body.
Adjust length around meaning. Preserve the main subject and reader task instead of adding popular phrases until an arbitrary character target is reached. A short heading can be vague, and a longer one can still be clear.
Check WordPress post titles and body headings
A WordPress theme may output the post title as an H1. Adding the same main heading to the first line of the body can therefore duplicate the subject. Inspect the published output rather than relying solely on the editor’s visual appearance.
Check | Possible observation | Decision |
|---|---|---|
Post title | Already rendered as H1 | Reconsider repeating it in the body |
Section headings | H2 sections and H3 branches | Check their semantic relationship |
Theme styling | Appearance differs from element level | Do not judge by size alone |
Document title | Different wording, same subject | Check for contradictions or exaggeration |
If changes to a theme or custom output are required, involve someone who can review their impact. Avoid altering unrelated logo or navigation structures simply to satisfy a heading count. Record which output you inspected so future template changes can be assessed.
Audit the page outline and readability
Read the headings in order without relying on the paragraphs. Do they identify the topic, scope and path through the explanation? Then check whether readers can use them to locate the answer they need.
- Does the H1 match the body’s main subject?
- Are sections unnecessarily repeated?
- Can the parent-child relationship of H2 and H3 be understood?
- Are important conditions hidden behind an overconfident heading?
- Do related-link labels agree with their destinations?
A change in time spent on the page after a rewrite does not, by itself, prove a ranking effect. Start by checking that the body fulfills the heading’s promise. Keep readability observations and search-performance observations separate when reviewing the result.
