· 01:56
Sure! Here’s a podcast-style summary of the article "Alternative to H1 for Website Title" from Dev.to:
🎙️ Welcome back to The Practical Developer Podcast! Today, we’re tackling a question that often confuses web developers: What’s the best element for your website title when you already have an H1 for your blog posts?
Traditionally, best practice suggested using only one <h1>
per page. But modern HTML5 semantics and accessibility guidelines allow multiple <h1>
elements when used correctly within different landmarks, like a <header>
for the site and an <article>
for the post. The big question is: Is this the right approach for SEO and accessibility? In this discussion, we’ll break down alternatives and recommendations from the Dev.to community.
Multiple <h1>
elements?
<h1>
tags is valid if structured properly. <header>
, while a blog post title inside <article>
can also use <h1>
.Alternative elements for the website title:
<h1>
for your blog article, some alternatives for your site’s name include: <p>
styled like an <h1>
<span>
with CSS styles <h2>
or <h3>
for hierarchy, depending on page structureSEO & Accessibility Considerations:
Screen readers rely on proper heading structures. A site-wide <h1>
can improve navigation for visually impaired users.
Google can handle multiple <h1>
tags, but it's still safer to ensure clear document structure.
So what’s the best practice? If your page has a blog article, using <h1>
for the post title is a good idea, but structuring your website name inside a <header>
with an <h2>
or <p>
is a workable solution.
That’s all for today’s episode! Have thoughts? Hit us up on social media! And as always, keep coding, keep learning! 🚀
Link to Article
Listen to jawbreaker.io using one of many popular podcasting apps or directories.