A website that complies with the DIV+CSS layout of XHTML standard, let’s talk about its impact on SEO.
Simplified code
Using DIV+CSS layout, the page code is streamlined, I believe that anyone who knows about XHTML knows this. There are two direct benefits of code simplification: First, it improves the efficiency of spider crawling and can crawl the entire page in the shortest time, which will have certain benefits for the inclusion quality; second, it will be liked by spider because it can crawl efficiently, which will have certain benefits for the inclusion quantity.
Nesting problems of tables
Many SEOers say in their articles that search engines generally do not crawl table nestings of more than three layers, which has not been officially confirmed by search engines. The results of several of my experiments have not been fully released, but according to the current situation, spider crawls through the pages of Table layout and encounters multi-layer table nesting, it will skip the nested content or directly abandon the entire page.
Using Table layout, in order to achieve a certain visual effect, multiple tables have to be applied. If the nested table is the core content, if the spider skips this section and does not crawl to the core of the page, the page becomes a similar page. Too many similar pages on the website will affect rankings and domain name trust.
However, there is basically no such problem in DIV+CSS layout. From a technical perspective, XHTML does not need to be too nested when controlling styles.
Although this has not been confirmed, it is still recommended that friends who use Table layout should try not to use multi-layer table nesting as much as possible when designing. SEOers have explained this in the article, and I believe they are not without basis.
Speed issues
The DIV+CSS layout reduces the page code compared to the Table layout, and the loading speed is greatly improved, which is very beneficial when spider crawls. Too much page code may cause the crawling timeout, and spider will think that the page is inaccessible, affecting the inclusion and weight.
On the other hand, real SEOer is not just for pursuing inclusion and ranking. Fast response speed is the basis for improving user experience, which is very beneficial to the entire search engine optimization and marketing.
Impact on rankings
The DIV+CSS layout based on the XTHML standard will generally be improved as much as possible after the design is completed so that it can pass W3C verification. So far, no search engines say that ranking rules tend to favor websites or pages that comply with W3C standards, but it turns out that websites using XTHML architecture are generally ranked well. This may be controversial. Those who have objections can compare and observe more than three groups of websites of basically the same quality.
I think this situation may not be the ranking rule. The biggest possibility is that when spider crawls on the website, the above differences lead to different inclusion quality. It is recommended that friends who build websites or reprints should choose DIV+CSS layout under technical licenses.
Simplified code
Using DIV+CSS layout, the page code is streamlined, I believe that anyone who knows about XHTML knows this. There are two direct benefits of code simplification: First, it improves the efficiency of spider crawling and can crawl the entire page in the shortest time, which will have certain benefits for the inclusion quality; second, it will be liked by spider because it can crawl efficiently, which will have certain benefits for the inclusion quantity.
Nesting problems of tables
Many SEOers say in their articles that search engines generally do not crawl table nestings of more than three layers, which has not been officially confirmed by search engines. The results of several of my experiments have not been fully released, but according to the current situation, spider crawls through the pages of Table layout and encounters multi-layer table nesting, it will skip the nested content or directly abandon the entire page.
Using Table layout, in order to achieve a certain visual effect, multiple tables have to be applied. If the nested table is the core content, if the spider skips this section and does not crawl to the core of the page, the page becomes a similar page. Too many similar pages on the website will affect rankings and domain name trust.
However, there is basically no such problem in DIV+CSS layout. From a technical perspective, XHTML does not need to be too nested when controlling styles.
Although this has not been confirmed, it is still recommended that friends who use Table layout should try not to use multi-layer table nesting as much as possible when designing. SEOers have explained this in the article, and I believe they are not without basis.
Speed issues
The DIV+CSS layout reduces the page code compared to the Table layout, and the loading speed is greatly improved, which is very beneficial when spider crawls. Too much page code may cause the crawling timeout, and spider will think that the page is inaccessible, affecting the inclusion and weight.
On the other hand, real SEOer is not just for pursuing inclusion and ranking. Fast response speed is the basis for improving user experience, which is very beneficial to the entire search engine optimization and marketing.
Impact on rankings
The DIV+CSS layout based on the XTHML standard will generally be improved as much as possible after the design is completed so that it can pass W3C verification. So far, no search engines say that ranking rules tend to favor websites or pages that comply with W3C standards, but it turns out that websites using XTHML architecture are generally ranked well. This may be controversial. Those who have objections can compare and observe more than three groups of websites of basically the same quality.
I think this situation may not be the ranking rule. The biggest possibility is that when spider crawls on the website, the above differences lead to different inclusion quality. It is recommended that friends who build websites or reprints should choose DIV+CSS layout under technical licenses.