: Effects of converting literal ampersand to HTML Entity I'm working on a site that has main/parent category names which include a literal ampersand & character, such as "Things & Stuff".
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.
More posts by @Martha676
1 Comments
Sorted by latest first Latest Oldest Best
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
Terms of Use Create Support ticket Your support tickets Stock Market News! © vmapp.org2024 All Rights reserved.