標題: It’s possible that searchers might [打印本頁] 作者: 5bybpbc3f4 時間: 2024-2-18 18:56 標題: It’s possible that searchers might Feel a little duped or confused after clicking through to this page, so it’d probably make sense to stick with a consistent angle. PRO TIP If your website has many pages, sort the report in Ahrefs’ Site Audit by organic traffic to prioritize changes. There’s little point worrying about mismatched titles and H1s if your page doesn’t get any organic traffic in the first place. Use an H1 tag on every important page Given that your page title should be wrapped in an H1 tag, it goes without saying that you should use a H1 on every important page. After all, every page has a title. If you want to find pages with missing or empty H1s: Sign up for a free Ahrefs Webmaster Tools account Crawl your website in Site Audit Go to the On page report Scroll to the “H1 setup” chart Click on the red area in the pie chart.
You can see above that some of our pages are missing H1s. Is this best practice? Not really. But it’s also cell phone numbers list unlikely to be a huge deal because these pages aren’t particularly important from an SEO perspective. They’re just blog homepages and archive pages that are only likely to attract branded traffic anyway. So while our developers could “fix” this in minutes, it’s probably not worth wasting their time as the pages look perfectly fine for visitors—and that’s all that matters here. Use only one H1 per page Google’s John Mueller says using multiple H1s per page is fine. If you’re using HTML5, this is strictly true.
There’s nothing technically wrong with using multiple H1 tags in different sections. For example, this HTML5 page has four H1 tags and is technically fine. <body> <h1>Apples</h1> <p>Apples are fruit.</p> <section> <h1>Taste</h1> <p>They taste lovely.</p> <section> <h1>Sweet</h1> <p>Red apples are sweeter than green ones.</p> </section> </section> <section> <h1>Color</h1> <p>Apples come in various colors.</p> </section> </body> Pretty much all modern browsers will render this correctly, and will display H1 tags in nested <section> elements according to their nesting level.
