Error in using canonical addresses
Posted: Tue Jan 28, 2025 4:47 am
If the address of the website page itself is written as canonical, this is an error. Many developers may say that they do not make such mistakes, but such an error occurs quite often. It occurs due to the programmer's unwillingness to check this information in Yandex or Google help when writing canonical addresses.
Why is this bad: The resulting duplicate list building for mlm pages will not disappear from the website and will negatively affect promotion.
How to fix: Look at Yandex or Google tips and fix the error.
Internal links on the site work via redirect.
If internal links lead to pages that differ by one character (for example, the absence of a slash at the end) from those to which the redirect is configured, the visitor, clicking on them, first gets to a non-existent page without a slash and only then to the correct address.
Considering the speed of processing requests by the server, the user will not notice such a “long” transition, but search robots pay special attention to this.
Why it's bad: Such a redirect overloads the server with unnecessary work. At the same time, search engine robots may not have time to process all the pages of the website in the allotted time.
How to fix: Make sure that all internal links lead to the desired pages without using unnecessary redirects.
This error does not occur on the entire website, but only in one block or section. To identify it, you will have to "comb" the entire web resource. To make this work easier, you can use one of the many services for automatic site analysis.
The site is often unavailable.
Almost every web resource has periodic access problems. If we are talking about 10-30 minutes a month, this will not affect the optimization of the website, as well as its promotion. But if the crashes occur frequently, and each lasts quite a long time, it is necessary to conduct an analysis.
Why it's bad: Difficult or non-existent access to pages reduces the site's ranking, as a result of which they may lose their positions in search engines or even temporarily fall out of the index.
How to fix: Analyze the frequency and duration of the web resource's unavailability using the Yandex.Metrica Reports tool.
Reports -> Standard reports -> Monitoring -> Test results
Frequent crashes may be caused by problems with hosting. If technical support was unable to fix the situation, you may want to consider changing your hosting.
The site does not have a Favicon.
Most sites have this option, but due to errors (for example, deleting a file or a link to it from the code), the Favicon may disappear.
Website Optimization_Favicon
Why it's bad: A snippet without a Favicon loses its visual appeal, becoming less noticeable. As a result, the number of clicks to the site from search results decreases.
How to fix : Read the official Yandex help, which provides detailed information on setting up Favicon.
Scripts, styles, service information in the page code.
The lighter the code, the higher the loading speed of the website pages. Therefore, the page code should be freed from styles, scripts and service files as much as possible. However, as the web resource improves, its code grows with new constructions, turning some old code blocks into garbage.
When examining the code of a website, you may come across fragments of documented code that have lost their relevance because they are not used.
Why it's bad: Page loading speed increases. Indexing speed decreases.
How to fix: First, regularly check the relevance of loaded styles and scripts, as well as their necessity for the correct operation of the website. Second, remove CSS styles and scripts from the code. Third, rid the code of documented code blocks and service blocks.
Contact information in the header in the form of pictures.
As a rule, the main methods of communication are in the "header" of the web resource. If on a commercial Internet site the contact information is presented as a picture, this reduces its accessibility for the visitor.
The capabilities of search algorithms do not extend to texts in images, which they cannot recognize correctly. In this regard, all the information required by the visitor must be presented on the website in the form of text.
Why is this bad: The resulting duplicate list building for mlm pages will not disappear from the website and will negatively affect promotion.
How to fix: Look at Yandex or Google tips and fix the error.
Internal links on the site work via redirect.
If internal links lead to pages that differ by one character (for example, the absence of a slash at the end) from those to which the redirect is configured, the visitor, clicking on them, first gets to a non-existent page without a slash and only then to the correct address.
Considering the speed of processing requests by the server, the user will not notice such a “long” transition, but search robots pay special attention to this.
Why it's bad: Such a redirect overloads the server with unnecessary work. At the same time, search engine robots may not have time to process all the pages of the website in the allotted time.
How to fix: Make sure that all internal links lead to the desired pages without using unnecessary redirects.
This error does not occur on the entire website, but only in one block or section. To identify it, you will have to "comb" the entire web resource. To make this work easier, you can use one of the many services for automatic site analysis.
The site is often unavailable.
Almost every web resource has periodic access problems. If we are talking about 10-30 minutes a month, this will not affect the optimization of the website, as well as its promotion. But if the crashes occur frequently, and each lasts quite a long time, it is necessary to conduct an analysis.
Why it's bad: Difficult or non-existent access to pages reduces the site's ranking, as a result of which they may lose their positions in search engines or even temporarily fall out of the index.
How to fix: Analyze the frequency and duration of the web resource's unavailability using the Yandex.Metrica Reports tool.
Reports -> Standard reports -> Monitoring -> Test results
Frequent crashes may be caused by problems with hosting. If technical support was unable to fix the situation, you may want to consider changing your hosting.
The site does not have a Favicon.
Most sites have this option, but due to errors (for example, deleting a file or a link to it from the code), the Favicon may disappear.
Website Optimization_Favicon
Why it's bad: A snippet without a Favicon loses its visual appeal, becoming less noticeable. As a result, the number of clicks to the site from search results decreases.
How to fix : Read the official Yandex help, which provides detailed information on setting up Favicon.
Scripts, styles, service information in the page code.
The lighter the code, the higher the loading speed of the website pages. Therefore, the page code should be freed from styles, scripts and service files as much as possible. However, as the web resource improves, its code grows with new constructions, turning some old code blocks into garbage.
When examining the code of a website, you may come across fragments of documented code that have lost their relevance because they are not used.
Why it's bad: Page loading speed increases. Indexing speed decreases.
How to fix: First, regularly check the relevance of loaded styles and scripts, as well as their necessity for the correct operation of the website. Second, remove CSS styles and scripts from the code. Third, rid the code of documented code blocks and service blocks.
Contact information in the header in the form of pictures.
As a rule, the main methods of communication are in the "header" of the web resource. If on a commercial Internet site the contact information is presented as a picture, this reduces its accessibility for the visitor.
The capabilities of search algorithms do not extend to texts in images, which they cannot recognize correctly. In this regard, all the information required by the visitor must be presented on the website in the form of text.