Mohd Shad Mirza Declaring something best practice, no matter the authority, does not make it right. The MDN documentation is rather empty on supporting evidence: You should only use one <h1> per page. Using more than one will not result in an error, but using only one is seen as a best practice. It makes logical sense — <h1> is the most important heading, and tells you what the purpose of the overall page is. You wouldn't have a book with more than one title, or a movie with more than one name! Having a single top-level title is also arguably better for screenreader users, and SEO.

Mohd Shad Mirza Is the H1 the title of the publication or the individual article? What about main feed that shows the last 5 posts; Should those be H1s? Suppose it's a home page for some company like atlassian; would the H1 be "Atlassian" or maybe "Jira" then a second H1 "BitBucket"? I guess what I'm getting at is there's no real reason to avoid a second H1 as long as it makes semantic sense. YEARS ago there was an article that said google penalized for multiple H1; but that has long since been the case. When I researched using multiple H1s a year or so ago, that was the single empirical datapoint. No standard, guideline, or publication had any meaningful justification for avoiding multiple H1s other than the defunct Google ranking algorithm. Screen readers support it.

What's wrong with multiple H1 elements?