Site Audit Issues WE Resolve
Duplicate Page Titles | ||
What is the issue? | Why is it bad? | How to fix |
| This means that the same title is used on more than one page of your website. The page title is displayed in the browser tab and search engines use it to generate the snippet shown in the search results. | For accessibility purposes, the W3C consortium (https://en.ryte.com/wiki/W3C) recommends having a unique and descriptive title on every page of your website. Regarding SEO, duplicate page titles waste ranking potential and confuse users and search engines. | To fix this issue, ensure that each page has a descriptive and unique page title. |
Duplicate Content | ||
What is the issue? | Why is it bad? | How to fix |
| This means that more than one page on your website has a high percentage of the same written content. | Duplicate content (https://en.ryte.com/wiki/Duplicate_Content) impacts rankings as search engines have difficulty deciding which page is more relevant for a particular search intent. | There are a few ways to fix duplicate content. You can make content more unique, add a canonical tag (https://en.ryte.com/wiki/Canonical_Tag) to the page that should rank, add noindex (https://en.ryte.com/wiki/Noindex) to duplicate content, or simply avoid it in the first place by providing a link to recurring information instead of describing everything on the page. |
Internal “nofollow” Links | ||
What is the issue? | Why is it bad? | How to fix |
| Here you will find internal links marked with nofollow (https://en.ryte.com/wiki/Nofollow). Nofollow allows you to specify links on your page that search engine bots should not follow when they are crawling your website. It is typically implemented on paid links or used when link quality cannot be guaranteed. | It’s best practice to avoid using nofollow links internally, as it signals to search engines that your page might be untrustworthy. Additionally, implementing nofollow to conserve link juice (https://en.ryte.com/wiki/Link_Juice) for more important pages will result in losing the link juice entirely. | Remove the nofollow attribute on all internal links. |
Pages over 1MB | ||
What is the issue? | Why is it bad? | How to fix |
| This means that the total size of the page, including images, JavaScript, CSS, is larger than 1 megabyte. | The smaller the page size, the faster it will load, which is better for user experience. | Identify the files that make each page so large and try to reduce their size. Often pictures have the biggest potential to make your site faster. |
Pages with Long Click Paths | ||
What is the issue? | Why is it bad? | How to fix |
| The click path measures the number of clicks required to navigate from the homepage to a particular page. | If a page is more than 6 clicks from the homepage, search engines might perceive this page as less important and may reflect this in its rankings. | Where it makes sense, add links from one page to another to improve the internal navigation. Keep your site structure as flat as possible. |
Images missing ALT tags | ||
What is the issue? | Why is it bad? | How to fix |
| An ALT tag is an alternative text that describes an image. It is displayed when an image does not load, is used on screen readers for the visually impaired, and is a factor in image SEO (https://en.ryte.com/wiki/Image_SEO). | For the accessibility of a website, every picture must have an ALT tag. This way if the image cannot be seen or does not load, visitors can still understand what should be displayed. It also improves your image’s potential to rank in image searches. | Try to describe the picture so well with ALT tags that the visually impaired can understand the context of the content and search engines can interpret it correctly. |
Indexable Pages Missing in the Sitemap.xml | ||
What is the issue? | How to fix | |
| This issue shows you pages that are indexable but could not be found in the sitemap.xml (https://zabiniazi.com/sitemap_index.xml). | Add all indexable pages (https://en.ryte.com/magazine/index-control-using-xml-sitemaps) to the sitemap.xml. | |
Broken Outbound Content | ||
What is the issue? | Why is it bad? | How to fix |
| Broken outbound content occurs when you link to an external page whose path has changed or has been deleted. It can be recognized by a 4xx or 5xx status code (https://en.ryte.com/wiki/Http_Status_Code). | Linking to broken content outside of your website annoys your visitors and indicates your website is not properly maintained. | You can fix broken outbound content by adjusting the links or removing them from your page. |
Pages missing a Twitter Preview | ||
What is the issue? | Why is it bad? | How to fix |
| This means that the preview image for the page has not been specified for Twitter. | If one of these pages is shared, Twitter will randomly choose an image from that page for a preview image, meaning that you will have no say in what is displayed to users. | Go to the source code and take control of your Twitter (https://en.ryte.com/wiki/Twitter_Cards) presence. |
Broken Pages | ||
What is the issue? | Why is it bad? | How to fix |
| Broken pages arise when you delete pages that are still linked or mentioned somewhere. They can be recognized by the 4xx and 5xx status codes (https://en.ryte.com/wiki/Http_Status_Code). | Broken pages annoy your visitors and search engine crawlers. | You fix these mistakes by restoring pages or removing all links and mentions to them. |
Broken CSS Files | ||
What is the issue? | Why is it bad? | How to fix |
| The CSS file (https://en.ryte.com/wiki/CSS) is missing, broken, or not loading correctly. CSS defines how your pages should be styled and rendered. | If there is an error in these files, the content will be misrepresented and users will see an incomplete or incorrect design displayed on the page. | You can fix these mistakes by restoring the CSS files, updating their URL path, or removing all references to them. |
Duplicate Descriptions | ||
What is the issue? | Why is it bad? | How to fix |
| This means that the same meta description is used on more than one page of your website. | Duplicate meta descriptions waste ranking potential and can confuse searchers and search engines. | To fix this issue, ensure that each page has a detailed and unique meta description. If that is not possible, it’s better to leave the meta description blank than to have a duplicate one. |
Internal Temporary Redirects | ||
What is the issue? | Why is it bad? | How to fix |
| An internal temporary redirect indicates that the page the user or search engine is trying to access has been temporarily moved to a different location. | Since search engines assume that temporary redirects will soon be removed, no ranking potential will be transferred to these pages. | Change the redirect (https://en.ryte.com/wiki/Redirect) from temporary to permanent to send the appropriate signals to search engines. Ideally, you’ll even change all internal links that point to the redirects directly. |
Broken Canonicals | ||
What is the issue? | Why is it bad? | How to fix |
| A broken canonical tag is a canonical (https://en.ryte.com/wiki/Canonical_Tag) that points to a 4xx or 5xx status code (https://en.ryte.com/wiki/Http_Status_Code). | If broken canonicals are on your page, the wrong page might rank in the search engines. If there are many broken canonicals on your page, Google might ignore the canonicals on your website entirely. | Either change the canonical tag to an existing page with identical content or restore the broken page. |
Broken Redirects | ||
What is the issue? | Why is it bad? | How to fix |
| A broken redirect means that a redirect is forwarding visitors to a broken page or a page with a 4xx or 5xx status code (https://en.ryte.com/wiki/Http_Status_Code). | Broken redirects annoy your visitors and search engine crawlers. | To avoid frustrated visitors from leaving your website, restore the broken pages by removing all redirects or changing the redirect destination to another page. |
Non-indexable Pages with High Relevance | ||
What is the issue? | Why is it bad? | How to fix |
| Non-indexable pages with high relevance are pages that you’ve specified not to be indexed by the search engines but have many incoming links and mentions. | Pages with high relevance signal that the page has value for users, but since it’s non-indexable, users will not be able to find it in the search engines. | Make sure pages with high relevance are indexable. The following article (https://en.ryte.com/product-insights/10-steps-for-checking-indexability-with-ryte) will provide instructions on how to allow indexing. |
Blocked JavaScript Files in Robots.txt | ||
What is the issue? | Why is it bad? | How to fix |
| If you have blocked search engines from crawling your JavaScript files, they may not be able to access your whole website. | Google has made it clear (https://webmasters.googleblog.com/2014/10/updating-our-technical-webmaster.html) that blocking Javascript files may now result in suboptimal rankings. | Add “Allow: .js” to your robots.txt or allow the blocked JavaScript files to be analyzed. |
Blocked CSS Files in Robots.txt | ||
What is the issue? | Why is it bad? | How to fix |
| If you have blocked search engines from crawling your CSS files, they may not be able to access your whole website. | Google has made it clear (https://webmasters.googleblog.com/2014/10/updating-our-technical-webmaster.html) that blocking the CSS files may now result in suboptimal rankings because then they won’t be able to render your URLs correctly. | Add “Allow: .css” to your robots.txt or allow the blocked CSS files to be analyzed. |
Broken Javascript Files | ||
What is the issue? | Why is it bad? | How to fix |
| The JavaScript file (https://en.ryte.com/wiki/JavaScript) is missing, broken, or not loading correctly. JavaScript is a programming language used to make websites dynamic. | Broken JavaScript files are likely to misrepresent content or prevent certain features from being shown. | You can fix these mistakes by restoring JavaScript files, updating their URL path, or removing all references to them. |
Broken Images | ||
What is the issue? | Why is it bad? | How to fix |
| Broken images arise when an image has been deleted from the server but is still embedded on the website, or if the image does not load fast enough. | This is an issue as it means that a picture on your page is missing or displayed incorrectly. | Use the Inspector to find the page with the broken image. Then, either restore the image under the same URL, update the URL path, or delete the image. |
Broken XML Files | ||
What is the issue? | Why is it bad? | How to fix |
| This means an XML (https://en.ryte.com/wiki/XML) file on your page is broken with a status code (https://en.ryte.com/wiki/Http_Status_Code) of 4xx of 5xx. The sitemap.xml is a typical example of an XML file on your page. | If your page has a broken XML file, the page will not be displayed correctly. If your Sitemap.xml is one of these broken files, search engine bots will not analyze your page as you’ve specified. | To fix this issue, check all mentions to the broken XML file and either alter their path, delete the mentions, or restore the XML file. |
Slow Pages | ||
What is the issue? | Why is it bad? | How to fix |
| These are the pages that take more than 1 second to load. | The faster a page loads, the faster it can satisfy the user’s search. Page performance, including page speed, is now a ranking factor in Google (https://webmasters.googleblog.com/2018/01/using-page-speed-in-mobile-search.html). | There could be several reasons why pages are loading slowly. See this article (https://en.ryte.com/magazine/pagespeed-optimization-how-can-i-improve-my-websites-loading-time) for a full list of potential reasons and tips on how to fix them. |
Duplicate H1 Tags | ||
What is the issue? | Why is it bad? | How to fix |
| This means that multiple pages on your website use the same main headline. | While it’s no longer important to Google, unique H1 tags are important for usability and accessibility. Screen readers may read out the H1 to orient the visually impaired. | You should give all pages of your website a logical and unique H1 so that no two pages have the same main headline. |
“hreflang” Tags with Errors | ||
What is the issue? | Why is it bad? | How to fix |
| This means that the hreflang tag has been implemented incorrectly. The hreflang tag (https://en.ryte.com/wiki/Hreflang) connects sites with the same content in different languages for search engines. | If there are errors in the hreflang, users might not see the correct page for their country or language. | Ensure that all alternate language versions of the page are referenced with the hreflang tag. Here (https://en.ryte.com/product-insights/international-seo-on-our-new-hreflang-report) are some instructions on how to work with this report. |
Pages with Invalid Canonicals | ||
What is the issue? | Why is it bad? | How to fix |
| This means that there are indexable pages that do not have a canonical tag or have invalid syntax. (https://en.ryte.com/wiki/Canonical_Tag) | If the canonicals are missing or invalid, you relinquish control of your website’s indexing. Therefore the incorrect version of the page might be shown in search engine results, risking search engine traffic. | Check what’s wrong with the specific canonical tag and correct its syntax. |
Unsecure Technology (Flash) | ||
What is the issue? | Why is it bad? | How to fix |
| This issue checks your website for Flash (https://en.ryte.com/wiki/Flash), a programming language primarily used for website animation. | Flash is plagued with security issues and is, therefore, a popular way for criminals to smuggle malware onto computers. | It’s best practice to eliminate Flash, replacing it with new technology like HTML5. |
Broken Pagination | ||
What is the issue? | Why is it bad? | How to fix |
| Broken pagination (https://en.ryte.com/wiki/Pagination) occurs when the pages mentioned by rel=next or rel=prev point to a 4xx or 5xx status code (https://en.ryte.com/wiki/Http_Status_Code). | If the pagination is broken, a paginated version of a page might rank instead of the first page. | Correct the rel=next and rel=prev tags on the corresponding page in the source code. |
Broken “hreflang” Attribute | ||
What is the issue? | Why is it bad? | How to fix |
| This means that the hreflang tag links to a broken page. The hreflang tag (https://en.ryte.com/wiki/Hreflang) connects sites with the same content in different languages for search engines. | If there are errors in the hreflang, users might not see the correct page for their country or language. | Ensure that all alternate language versions of the page are referenced with the hreflang tag. Here (https://en.ryte.com/product-insights/international-seo-on-our-new-hreflang-report) are some instructions on how to work with this report. |
Links to Suspicious Sites | ||
What is the issue? | Why is it bad? | How to fix |
| This indicates that there is a link on your website to a potentially dubious or hacked site. | Links like these are bad for your credibility and can even result in search engine penalties. | To fix this issue, open the link in the Inspector to find out where it is on your website. Then, replace or delete the link. |
Pages with a Low Word Count | ||
What is the issue? | Why is it bad? | How to fix |
| The following pages have fewer than 300 words. | Google might consider pages like these inadequate at answering user’s search queries, often resulting in decreased rankings. | To fix this issue add more text to these pages or remove them entirely. |
Orphaned Pages (without Internal Follow Links) | ||
What is the issue? | Why is it bad? | How to fix |
| This means that the following pages have fewer than 3 incoming internal links. | The fewer internal incoming links a page has, the less likely a user may find it. | Ensure that users can find these pages by increasing the amount of relevant internal links. |
Non-indexable Pages in the Sitemap.xml | ||
What is the issue? | Why is it bad? | How to fix |
| The Sitemap.xml shows a search engine on which pages on your website are available and should be indexed. | Including non-indexable pages in the Sitemap.xml wastes search engine resources that could have been used for important pages. | Remove all non-indexable pages (https://en.ryte.com/magazine/index-control-using-xml-sitemaps) from the sitemap.xml. |
URLs with Special Characters | ||
What is the issue? | Why is it bad? | How to fix |
| This means that the following special characters $-_.*!%u2019(), are present in a URL address. | If a URL contains these special characters, browsers might not be able to locate the page correctly. | Special characters need to be translated or encoded by replacing the special character with the corresponding ASCII code. You can do this manually or with a script editor. |
No-index/No-follow Pages | ||
What is the issue? | Why is it bad? | How to fix |
| This means that these pages have been specified with noindex (https://en.ryte.com/wiki/Noindex) and therefore cannot be found by the search engines. | These pages will not show up in the search engines. If they contain important information, searchers will not be able to find them. | Change the robot’s directive on the following pages. |
Conflicting Robots Meta Directive | ||
What is the issue? | Why is it bad? | How to fix |
| This conflict occurs when information in the robot’s meta directive differs from the robots.txt file. | Conflicting information means that search engines don’t understand how to interpret these pages, potentially preventing your page from being indexed. | Check why the information in the robots meta directive and robots.txt file are different and make sure that they are identical. |
Cross-domain Canonicals | ||
What is the issue? | Why is it bad? | How to fix |
| A cross-domain canonical is a canonical tag (https://en.ryte.com/wiki/Canonical_Tag) on your website that points to another website. | If the canonical points to a different website, the tag recommends including the contents of the other website in the search engine index, not your page. | Unless this was implemented on purpose (which is very rare), ensure that the canonicals (https://en.ryte.com/magazine/canonical-tag-practice-guide) on your website always point to a page that is on your website. |
Pages with Few Internal Incoming Links | ||
What is the issue? | Why is it bad? | How to fix |
| This means that the following pages have fewer than 3 incoming internal links. | The fewer internal incoming links a page has, the less likely a user may find it. | Ensure that users can find these pages by increasing the amount of relevant internal links. |
Missing File Type | ||
What is the issue? | Why is it bad? | How to fix |
| This means that the MIME (https://en.ryte.com/wiki/MIME) type is missing in your HTML or HTTP header or that they are conflicting. | The browser may not display the file correctly. | To fix this issue, add a MIME type to either the HTML or HTTP header or resolve the conflict. |
Pages missing a Facebook Preview | ||
What is the issue? | Why is it bad? | How to fix |
| This means that the preview image for the page has not been specified for Facebook. | If the preview image has not been set, when the link is shared, Facebook will randomly choose an image from that page. | Check out the following guide to learn more about customizing your Facebook Open Graph tags (https://en.ryte.com/magazine/open-graph-optimization-tips-that-website-operators-should-consider). |
Pages without Compression | ||
What is the issue? | Why is it bad? | How to fix |
| The files on these pages have not been compressed (https://en.ryte.com/wiki/File_Size) by gzip or deflate. | Without page compression, page speed will decrease, encouraging visitors to leave your page prematurely. | Activate compression (https://en.ryte.com/magazine/compress-code-for-a-faster-website) on your server. |
Dublicate Page Titles
Dublicate Page Titles
Dublicate Page Titles
Tab #2
Tab #3
Dublicate Page Titles
What is the issue?
This means that the same title is used on more than one page of your website. The page title is displayed in the browser tab and search engines use it to generate the snippet shown in the search results.
Why is it bad?
For accessibility purposes, the W3C consortium (https://en.ryte.com/wiki/W3C) recommends having a unique and descriptive title on every page of your website. Regarding SEO, duplicate page titles waste ranking potential and confuse users and search engines.
How to Fix?
To fix this issue, ensure that each page has a descriptive and unique page title.
Dublicate Page Titles
What is the issue?
This means that the same title is used on more than one page of your website. The page title is displayed in the browser tab and search engines use it to generate the snippet shown in the search results.
Why is it bad?
For accessibility purposes, the W3C consortium (https://en.ryte.com/wiki/W3C) recommends having a unique and descriptive title on every page of your website. Regarding SEO, duplicate page titles waste ranking potential and confuse users and search engines.
How to Fix?
To fix this issue, ensure that each page has a descriptive and unique page title.
Dublicate Page Titles
What is the issue?
This means that the same title is used on more than one page of your website. The page title is displayed in the browser tab and search engines use it to generate the snippet shown in the search results.
Why is it bad?
For accessibility purposes, the W3C consortium (https://en.ryte.com/wiki/W3C) recommends having a unique and descriptive title on every page of your website. Regarding SEO, duplicate page titles waste ranking potential and confuse users and search engines.
How to Fix?
To fix this issue, ensure that each page has a descriptive and unique page title.
Tab #2
Tab #3
Why is it bad?
How to fix
This means that the same title is used on more than one page of your website. The page title is displayed in the browser tab and search engines use it to generate the snippet shown in the search results.For accessibility purposes, the W3C consortium (https://en.ryte.com/wiki/W3C) recommends having a unique and descriptive title on every page of your website. Regarding SEO, duplicate page titles waste ranking potential and confuse users and search engines.To fix this issue, ensure that each page has a descriptive and unique page title.
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Ut elit tellus, luctus nec ullamcorper mattis, pulvinar dapibus leo.