大网数据广告活动
网站运营与故障问答

Effects of converting literal ampersand to HTML Entity

· 52CE 我爱测

I'm working on a site that has main/parent category names which include a literal ampersand & character, such as " Things & Stuff ". This has been working fine for many years, even though it should probably have originally been c…

问题原文

原帖链接 · SnakeDoc · CC BY-SA 3.0

I'm working on a site that has main/parent category names which include a literal ampersand & character, such as "Things & Stuff".

This has been working fine for many years, even though it should probably have originally been created using the HTML Entity & instead, such as "Things & Stuff" (they both render the same on-page as "Things & Stuff").

Now, the site wants to integrate with a 3rd party company to do some product related stuff. Their system chokes up on the literal ampersand & characters, and they have asked the site to convert them into the proper HTML Entity &.

What ramifications are there for this change? Will Google et al view the before and after as the same, or is there a negative SEO impact since main category page titles will be changing.

已采纳解答

原帖链接 · Simon Hayter · CC BY-SA 3.0

When Googlebot visits your site it sees both the source and the end results, markup plays little to no role in rankings because why should it; your visitors don't care about your markup and neither do search engines.

It's important to note that older html documents you needed to use such HTML codes because the UNICODE didn't support the symbol. Now with HTML5 and onwards we don't need silly little codes.

  • & is exactly the same as &
  • & is exactly the same as &
  • & shares the same meaning with and

摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。

资料来源与适用范围

资料来源
Webmasters Stack Exchange
适用范围
以原帖系统、软件版本与发布日期为准(2017-01-26)
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY-SA 3.0

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。