Anda menghabiskan waktu berjam-jam untuk membuat halaman WordPress yang sempurna. Kontennya solid. Kata kuncinya sudah ditempatkan. Plugin SEO Anda menunjukkan tanda centang hijau.
But open your browser’s developer tools and inspect the heading structure, and you’ll see something that can quietly kill your organic traffic: a broken heading hierarchy. Two H1s. A site title wrapped in `＜h1＞`. Sections jumping from H2 straight to H4. Or worse — no H1 at all.
This isn’t a kesalahan pemula. It’s a masalah struktural baked into how WordPress, themes, page builders, and the Gutenberg editor interact — and most site owners never know it’s happening.
This guide exists to fix that. Whether you’re a WordPress site owner managing your own content, or an agency building sites for dozens of clients, you’ll leave here knowing exactly how to mengaudit, mendiagnosis, dan menyelesaikan secara permanen masalah urutan heading di WordPress.
Apa Itu Tag H1 dan Mengapa Itu Penting di WordPress?
An H1 tag (＜h1>) is the top-level HTML heading element. In semantic HTML, it signals to browsers, search engines, and assistive technologies: “This is the primary topic of this page.”
Anggap tag heading sebagai kerangka dokumen:
H1 – Main page title (only one per page)
├── H2 – First major section
│ ├── H3 – Subsection
│ └── H3 – Another subsection
├── H2 – Second major section
│ ├── H3 – Subsection
│ │ └── H4 – Detail within subsection
└── H2 – Third major sectionSkip a level — jumping from H2 to H4 — and you break the outline. Use two H1s and you create structural ambiguity. Use H3 tags for visual styling and you introduce ghost headings that confuse crawlers.
In WordPress specifically, this gets complicated fast. Unlike a static HTML page where you write every tag manually, WordPress generates heading markup from at least four different sources simultaneously: the theme’s header template, the post title, the editor content, and any widgets or page builder modules you’ve added.
Apa yang Sebenarnya Dikatakan Google Tentang Tag H1
Let’s settle the perdebatan peringkat lebih awal.
In July 2026, Google’s Gary Illyes addressed this directly during the SEO Office Hours podcast: arranging headings in semantic order is genuinely helpful for accessibility (especially screen reader users), but it doesn’t significantly impact Google’s ranking algorithms. John Mueller has also stated that multiple H1 tags on a page don’t confuse crawlers and have zero direct SEO impact.
Jadi, apakah semua ini penting?
Yes — but not for the reason most SEO guides say.
Alasan sebenarnya untuk memperhatikan struktur heading di WordPress adalah:
- Kepatuhan aksesibilitas — WCAG 2.1 success criterion 1.3.1 requires information and relationships to be programmatically determinable. Broken heading hierarchies fail this.
- Kemampuan perayapan dan sinyal konten — While Google can parse messy markup, a clean H1 gives the clearest possible signal about page topic, which matters in ambiguous cases.
- Pengalaman pengguna dan waktu tunggu — Readers scan headings. A logical hierarchy helps them navigate and stay longer — both indirect ranking signals.
- Kebersihan audit teknis — For agencies, heading issues surface in every audit tool (Screaming Frog, Ahrefs, SEMrush, Rank Math, Yoast). Client-facing reports look bad even if the direct ranking impact is debated.
Bagaimana WordPress Menghasilkan Tag Judul: Empat Sumber Konflik
Memahami Mengapa Kerusakan struktur judul WordPress memerlukan pemahaman dari empat tempat pembuatan judul.
Source 1: The Theme’s Header Template
Most WordPress themes output the site title in the header area. Older and poorly coded themes wrap this in an ＜h1> tag — on every single page. This means every page on your site starts with the same H1: your brand name.
Kemudian, ketika halaman atau judul postingan dirender (yang sebaiknya menjadi H1), maka akan menjadi H1 kedua atau diturunkan menjadi H2.
Here’s what this looks like in a broken theme’s header.php:
php
// Broken — site title as H1 on every page
＜h1＞＜?php bloginfo('name'); ?＞＜/h1＞
＜h2＞＜?php the_title(); ?＞＜/h2＞ // Post title wrongly demotedSeperti apa tampilannya:
php
// Correct — site title is a link or span, post title is H1
＜p class="site-title"＞＜a href="＜?php echo home_url(); ?＞"＞＜?php bloginfo('name'); ?＞＜/a＞＜/p＞
＜h1＞＜?php the_title(); ?＞＜/h1＞This is one of the most common WordPress H1 issues and it’s entirely invisible unless you inspect the page source. You can have an SEO plugin, a green readability score, and konten yang sempurna — and still be outputting duplicate H1s on every page.
Sumber 2: Editor Blok Gutenberg
The WordPress block editor introduced deliberate changes to H1 behavior. By default, Gutenberg de-emphasizes the H1 option in the Heading block — the assumption is that the post title is already rendering as H1, so content-area headings should start at H2.
Dalam praktiknya, hal ini menimbulkan dua masalah:
Masalah A: Beberapa tema melakukannya tidak output the post title as H1. If your theme renders the title in a ＜div> or ＜h2> for stylistic reasons, and Gutenberg has hidden H1 from the heading block options, you end up with zero H1 tags on the page.
This is exactly the situation flagged in a long-running GitHub issue in the Gutenberg repository — users requesting the ability to remove the H1 option entirely for enterprise and agency setups where the H1 is controlled at the template level. The issue highlights real confusion: the editor’s default behavior and the theme’s template need to be explicitly coordinated, but WordPress provides no automated check for this.
Masalah B: Content editors can still select H1 in the block editor by changing the heading level. If your theme already outputs the post title as H1, an editor adding another H1 block inside the content area creates a duplicate — and no warning appears.
Sumber 3: Pembuat Halaman (Elementor, Divi, Beaver Builder)
Pembuat halaman adalah satu-satunya sumber terbesar kekacauan hierarki judul di WordPress.
Here’s why: page builders give you granular visual control. You can drag a text element anywhere, style it any way, and assign any heading level. This is powerful for design. It’s disastrous for structure.
Masalah judul pembuat halaman pada umumnya terlihat seperti ini:
- Bagian pahlawan: H1 (benar) ✓
- Feature section title: H3 (skipped H2, chosen because it “looks better”) ✗
- Judul area widget: H2 (tampak seperti judul bagian, namun hanya judul widget sidebar) ✗
- Judul Testimonial : H4 (tidak ada H3 diatasnya) ✗
- Judul CTA: H2 (kembali ke level yang lebih tinggi, sekarang garis besarnya sepenuhnya non-linier) ✗
The result is a heading structure that’s visually coherent but semantically meaningless. Screen readers and crawlers parsing this get a content outline that jumps around like a broken table of contents.
InspectWP’s documentation identifies this pattern explicitly: authors and page builder users choose heading levels based on how they Lihat rather than their logical meaning — if H3 is the right visual size, they select H3, even with no H2 above it.
Sumber 4: Widget dan Komponen Tema
WordPress widget areas — sidebars, footers, header modules — often output their own headings. A “Recent Posts” widget might render as H2. A promotional banner built into the theme might use H3. None of these are part of the content outline, but they appear in the page’s heading structure.
This creates heading “noise” that inflates the apparent complexity of the outline and can push content headings out of their correct hierarchical position.
5 Masalah Hirarki H1 dan Heading WordPress Paling Umum
Masalah 1: Judul Situs Dibungkus H1 di Setiap Halaman
Seperti apa: Every page on your site has two H1s — your site name and your post title.
Siapa yang terpengaruh: Sites using older themes, poorly built premium themes, or any theme where the developer used ＜h1> for the site branding.
Cara mendeteksinya: Right-click any page → Inspect → search for ＜h1 in the Elements panel. If you see your site name wrapped in H1 in the ＜header> section, you have this problem.
Cara memperbaikinya:
Opsi 1: Pengeditan tema anak (pendekatan pengembang) In your child theme’s header.php, find the site title output and change it from ＜h1> to ＜p> or ＜span> with appropriate classes:
php
＜p class="site-title"＞
＜a href="＜?php echo esc_url(home_url('/')); ?＞" rel="home"＞
＜?php bloginfo('name'); ?＞
＜/a＞
＜/p＞Opsi 2: CSS + aria-label (solusi tanpa kode) If you can’t edit theme files, use CSS to reset the H1 styling on the site title:
css
.site-header h1.site-title {
font-size: inherit;
font-weight: inherit;
margin: 0;
}Catatan: ini menyembunyikan visual H1 problem but doesn’t fix the structural issue. The H1 tag remains in the markup.
Opsi 3: Beralih ke tema yang terstruktur dengan baik Themes following WordPress coding standards (Twenty Twenty-Four, Kadence, GeneratePress, Astra) handle this correctly out of the box. If your current theme has this issue and you’re not a developer, switching is often the most reliable fix.
Masalah 2: H1 Hilang di Beranda
Seperti apa: Your homepage has zero H1 tags. SEO plugins report “No H1 found.”
Siapa yang terpengaruh: Sites that use a logo image for branding (hiding the site title), sites using a static front page with no title visible, or sites where the theme’s homepage template doesn’t call the_title().
This is a real and recurring issue in the WordPress support forums. The cause is typically this sequence: the site title is set to display in the header, but the user hides it (or replaces it with a logo), removing the only H1 from the page. Since the homepage often doesn’t have a “post title” in the way a blog post does, there’s no automatic H1 generated.
Cara memperbaikinya:
Khusus untuk beranda: Tambahkan H1 ke bagian pahlawan atau templat halaman Anda. Ini bisa berupa:
- A visible heading (“Your Business Name | Service Category”) that also functions as the H1
- H1 yang tersembunyi secara visual ditambahkan melalui CSS (
position: absolute; clip: rect(0 0 0 0);) yang memberikan penanda semantik tanpa mengganggu desain visual
Di Gutenberg: Tambahkan blok Heading di bagian atas konten beranda Anda, atur ke H1, dan jadikan itu bagian dari pesan pahlawan Anda.
Masalah 3: Tingkat Judul yang Dilewatkan dalam Konten
Seperti apa: Struktur konten melompat dari H2 langsung ke H4, atau dari H1 langsung ke H3.
Siapa yang terpengaruh: Siapa pun yang menulis konten berdurasi panjang yang menggunakan judul untuk gaya visual, bukan struktur semantik.
Mengapa ini penting: As InspectWP notes, skipping heading levels happens when authors choose levels based on appearance — the H3 looks right, so they use H3, regardless of whether an H2 precedes it.
Cara mendeteksinya di Gutenberg: Klik ikon info (ⓘ) di toolbar atas editor blok. Panel Kerangka Dokumen memperlihatkan setiap judul secara berurutan dan bendera yang dilewati tingkatnya dengan peringatan.
Cara memperbaikinya:
- Audit struktur judul Anda menggunakan Kerangka Dokumen sebelum dipublikasikan
- Set a content style guide for your team: H2 for major sections, H3 for subsections, H4 for sub-subsections — never skip levels
- Use Yoast SEO or Rank Math’s content analysis — both flag heading structure issues
Masalah 4: Beberapa Tag H1 Dari Pembuat Halaman
Seperti apa: A page built with Elementor or Divi has three or four H1 tags because each major section has its own hero-style “H1” headline.
Cara memperbaikinya:
In Elementor: Edit each heading widget → check the HTML Tag setting → set only the primary page title to H1, and change all others to H2 or H3 as appropriate.
In Divi: Edit heading modules → under Advanced → HTML Tag → change to the correct semantic level.
In Beaver Builder: Each heading module has a “Heading Tag” setting in the Style tab. Audit each one.
Masalah 5: Masalah Visibilitas Gutenberg H1
Seperti apa: Your theme doesn’t output the post title as H1, and Gutenberg has hidden the H1 option in the Heading block. Your pages have no H1.
Cara memperbaikinya:
For developers managing a site where the H1 must be placed inside the content area, you can restore the H1 option using a filter in your theme’s functions.php:
php
// Allow H1 in the Heading block
add_filter( 'allowed_block_types_all', function( $allowed_blocks ) {
return $allowed_blocks;
});Alternatively, switch to the “Edit as HTML” view for the Heading block and manually set ＜h1> in the markup.
Untuk penyiapan agensi di tempat yang Anda inginkan mencegah editor dari menambahkan H1 (karena templat mengontrolnya), gunakan block_editor_settings_all filter untuk membatasi level judul di editor.
Cara Mengaudit Struktur Heading WordPress Anda (Langkah demi Langkah)
Metode 1: Plugin Gratis SkySEOManager
Gunakan Plugin SkySEOManager inbuild SEO Analyzer untuk menemukan semua masalah terkait Judul.
Baca panduan lengkapnya: cara mengaudit situs wordpress Anda menggunakan SkySEOManager untuk semua Masalah SEO
Metode 2: Gunakan Analis SEO Siteskyline gratis
Kunjungi Keluar Penganalisis SEO gratis dan masukkan URL Anda dan klik analzye sekarang.
It’ll Show you all issue with your headline tags.
Hirarki H1 WordPress: Daftar Periksa Agensi
If you’re building or maintaining WordPress sites for clients, heading structure needs to be part of your pre-launch and ongoing audit process. Here’s a repeatable checklist:
Pada Tingkat Tema:
- Site title in header is NOT wrapped in ＜h1> (use ＜p>, ＜span>, or ＜div>)
- Post/page title renders as ＜h1> in ＜article> or ＜main> on all post types
- Homepage has exactly one ＜h1> — either from the site title or the hero section
- Archive pages (category, tag, author) have a descriptive ＜h1>
- 404 page has an ＜h1>
Pada Tingkat Konten:
- Each page has exactly one ＜h1> in the content area (or zero if the theme handles it via the title)
- Major sections use ＜h2>
- Subsections use ＜h3> nested within ＜h2> sections
- Tidak ada level judul yang dilewati
- Judul tidak digunakan untuk penataan visual saja
Di Tingkat Plugin/Pembuat:
- Elemen judul Elementor/Divi/Beaver Builder memiliki pengaturan Tag HTML yang benar
- Widget areas don’t output accidental H1 or H2 tags
- Peringatan plugin SEO H1 teratasi di semua halaman utama
The Correct WordPress Heading Hierarchy — By Page Type
One pattern doesn’t fit every WordPress page type. Here’s the correct structure for each:
Postingan Blog / Halaman Postingan Tunggal
H1: Post Title (output by theme automatically)
H2: First major section
H3: Subsection
H3: Another subsection
H2: Second major section
H3: Subsection
H4: Detail
H2: Third major sectionBeranda (Halaman Depan Statis)
H1: Primary value proposition or page headline
H2: Service category or feature group
H3: Individual service or feature
H2: Testimonials or social proof section
H2: Call to action sectionHalaman Produk WooCommerce
H1: Product name (output by WooCommerce template)
H2: Product description heading
H2: Reviews
H2: Related productsKategori / Halaman Arsip
H1: Category name (e.g., "WordPress SEO Articles")
H2: Post title within loop (if posts are displayed with headings)Kesalahan Umum yang Merusak Struktur WordPress H1
Kesalahan 1: Menggunakan tag heading untuk menata teks If you want large bold text that isn’t a section heading, don’t use H2. Add a CSS class to a ＜p> or ＜div> and style it visually. Using heading tags for aesthetics pollutes your structural outline.
Kesalahan 2: Membiarkan editor memilih tingkat judul berdasarkan pandangan Tanpa panduan gaya konten, editor secara alami akan tertarik pada level judul itu Lihat right. A brief internal guide — “H2 for sections, H3 for subsections, never use H1 in content” — prevents most issues.
Kesalahan 3: Memasang tema WordPress tanpa memeriksa struktur judul Tidak semua tema WordPress premium menghasilkan markup judul yang benar. Sebelum berkomitmen pada suatu tema, periksa postingan demo: apakah judul postingan ditampilkan sebagai H1? Apakah judul situs menghindari H1 di halaman dalam?
Kesalahan 4: Dengan asumsi plugin SEO Anda mencakup semuanya Yoast and Rank Math check the post you’re editing. They don’t catch heading issues introduced by your theme’s header template, footer widgets, or archive page templates. A manual audit or Screaming Frog crawl is still necessary.
Kesalahan 5: Memperbaiki tampilan visual alih-alih struktur HTML The most common “fix” for the site title H1 problem is adding CSS to make it look smaller. That hides the problem visually but leaves the broken markup in place. Fix the HTML tag, not just the style.
