I think semantics improves the maintainability of the project. The w3c specification recommends that we separate structure, performance and behavior. Semantic tags play such a role. Most of the semantic tags have their own styles, which can be reduced to a certain extent. It reduces the amount of code and forms a unified style, such as first-level headings and second-level headings, etc. It also makes our WYSIWYG header content and steps clear at a glance, shortening the project familiarity time and improving standardization
Simple example: strong tag, originally there was a b tag, but the effect is the same. But in SEO, the most obvious behavior is different in the reader. The content of the strong tag is meant to be re-read, which is good for emphasis. To put it bluntly, what you write in real time means nothing, CSS styles can help you display it how you want. But search engine crawlers crawl your HTML pages. If the semantics are good, just like your articles are neatly written, it will be easier for them to "read".
The
title attribute has no clear meaning and only represents a title. h1 represents a clearly hierarchical title, which also has a great impact on the capture of page information;
strong is to mark the key content and has the meaning of strengthening the tone. When using a reading device to read the Internet: strong will be stressed, while b is to display the emphasized content.
i content is displayed in italics, em indicates emphasized text;
Physical Style Elements -- Natural style tags b, i, u, s, pre Semantic Style Elements -- Semantic style tags strong, em, ins, del, code should use semantics accurately Style tags, but cannot be abused. If you are not sure, use natural style tags.
I think semantics improves the maintainability of the project. The w3c specification recommends that we separate structure, performance and behavior. Semantic tags play such a role. Most of the semantic tags have their own styles, which can be reduced to a certain extent. It reduces the amount of code and forms a unified style, such as first-level headings and second-level headings, etc. It also makes our WYSIWYG header content and steps clear at a glance, shortening the project familiarity time and improving standardization
Simple example:
strong
tag, originally there was ab
tag, but the effect is the same. But inSEO
, the most obvious behavior is different in the reader. The content of thestrong
tag is meant to be re-read, which is good for emphasis.To put it bluntly, what you write in real time means nothing, CSS styles can help you display it how you want.
But search engine crawlers crawl your HTML pages. If the semantics are good, just like your articles are neatly written, it will be easier for them to "read".