Skip to content

Conversation

@stevenjoezhang
Copy link
Contributor

@stevenjoezhang stevenjoezhang commented Mar 14, 2020

References:

Multiple H1 Headings: How to Handle Them for SEO & Accessibility?
https://www.youtube.com/watch?v=zyqJJXWk0gk
https://www.youtube.com/watch?v=WsgrSxCmMbM

According to google, multiple h1 on the page will not negatively affect seo.
Tests have shown that if all pages are required to have one and only one h1, then brand.swig cannot be cached, which results in an ~8% slowdown in hexo g.

<span class="site-title">{{ title }}</span>

{%- if is_post() or is_page() %}span{% else %}h1{%- endif %}

@stevenjoezhang stevenjoezhang merged commit bd2ee2e into master Mar 21, 2020
@stevenjoezhang stevenjoezhang deleted the seo branch March 21, 2020 05:16
Guoye added a commit to Guoye/hexo-theme-next that referenced this pull request Apr 22, 2020
* 'master' of https://github.com/theme-next/hexo-theme-next: (99 commits)
  Optimize main-menu & sidebar-nav style
  Optimize dark mode blockquote style
  Use fixed-width icons in copy-btn
  Fix exturl title
  Fix Font Awesome path and font-family
  Fix Font Awesome class name
  Migrate to Font Awesome 5 (theme-next#1438)
  Release v7.8.0
  Optimize dark mode button color
  Fix theme-next#1424: Dark mode footer color of scheme Mist
  Optimize dark mode colors
  Combine .content and .posts-expand
  Optimize mobile_layout_economy
  New Crowdin translations (theme-next#1413)
  Some minor fixes
  Revert theme-next#1124: Class name for pages
  Run lebab
  Trigger search after loading is complete
  Simplify footer.powered settings (theme-next#1432)
  Remove `seo` option in `_config.yml` (theme-next#1414)
  ...

# Conflicts:
#	_config.yml
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants