S = SEARCH
E = ENGINE
O = OPTIMIZATION
SEO = search engine optimization
explanation: be found more easily in search engines.
our service: we can help you!
seo4all provides a comprehensive checklist, general infos, documents, tips and tricks for professional seo (search engine optimization).
SEARCH ENGINE OPTIMIZATION FOR ALL!!!
what do you get:
- ✔️ free checklist
- ✔️ free documents (how to's / templates)
- ✔️ free directories
- ✔️ free lexicon
- ✔️ free link building tips
- ✔️ free recommendations for action
- ✔️ free tips and tricks
- ✔️ free tools
- ✔️ free website audit tips
- ✔️ seo4all BOOK (planning)
- ✔️ ALL tips, tricks and recommendations are tried and tested in real production environments, live websites, online shops and in successful companies that have generated at least 15+ million euros in annual sales 💰!!!
AUDIT (CHECKLIST)
CRITERIA | DESCRIPTION/ Recommendations | ONPAGE/ OFFPAGE | GOOD | MEDIUM | BAD |
---|---|---|---|---|---|
GENERAL | |||||
Domain age | Age of the Domain in years | >5 | 2 - 5 | <2 | |
Alexa Ranking (Global) | Calculation of the generated backlink traffic | <10K | 10K - 100K | >100K | |
Alexa Ranking (National) | Calculation of the generated backlink traffic | <1K | 1K - 10K | >10K | |
Bing Index | Number of pages listed in the Bing Index | >1K | 100 - 1K | <100 | |
Google Index | Number of pages listed in the Google Index | >1K | 100 - 1K | <100 | |
Google PageRank | Importance of the domain (0-10) | >8 | 3 - 7 | <2 | |
SECURITY | |||||
HTTPS/SSL-Encryption | SSL certificate exists and is valid | exists and is valid | exists | not existing | |
SSL Certificate - Expiration | Expiration date of the SSL certificate. Recommendations: Update your SSL certificate regularly. |
onpage | |||
SSL Certificate - Version | Protocol Version of the SSL certificate. Recommendations: Update your SSL certificate to the latest version. |
onpage | |||
SSL Certificate - Name | The name of the domain or subdomain under which your SSL certificate is registered must match with the name displayed in the address bar. Recommendations: Install the right certificate. Subdomains require their own security certificates, so you can use a wildcard or multi-domain SSL certificate to protect multiple subdomains at once. |
onpage | |||
SSL Certificate - Encryption algorithm | Using newer encryption algorithms on your website can avoid data security risks. Recommendations: Update the encryption algorithm regularly. |
onpage | |||
HTTPS-URLs in XML-Sitemap | Specify HTTPS URLs in the XML sitemap file. Recommendations: Replace all HTTP URLs with HTTPS URLs in your XML sitemap. |
onpage | |||
HTTPS encryption | Recommendations: Migrate your site to the secure HTTPS protocol. | onpage | |||
rel="canonical" from HTTP to HTTPS | Recommendations: Set up a 301 redirect from the HTTP to the HTTPS version of your website. In this case, you can be sure that search engines will rank HTTPS pages. | onpage | |||
HTTPS to HTTP redirect | Recommendations: Do not redirect secure HTTPS pages to insecure HTTP pages. If you add a redirect to an HTTPS page, make sure the redirected page loads over a secure HTTPS connection. | onpage | |||
Mixed content | Recommendations: Make sure that all page resources are loaded over a secure HTTPS connection. | onpage | |||
SITEMAP (TXT or XML) | |||||
Use Sitemap (txt or xml) | Recommendations: Create a sitemap in XML file format, add it to your website and submit the link with the position to search engines. You can create separate sitemaps in XML format for URLs, images, videos, news and mobile content. OR: Create a sitemap in TXT file format and add a link URL per line. |
onpage | |||
sitemap.xml / sitemapindex.xml | Present and error-free | yes | no | ||
XML sitemap too large | Recommendations: Split your large XML sitemap file into smaller files. Then create a sitemap index file in XML file format, add links to each sitemap on your site, and submit the index file to Google. Make sure the location of your new XML sitemaps is included in the robots.txt file. | onpage | |||
Non-canonical pages in XML sitemap | Recommendations: Make sure your XML sitemap contains only canonical URLs. | onpage | |||
Noindex pages in XML sitemap | Recommendations: Depending on your goals, you should remove pages with the noindex meta tag from your XML sitemap or remove the noindex tag from those pages. | onpage | |||
XML sitemap not found in robots.txt file | Recommendations: Add a link to your XML sitemap file to the robots.txt file. To make sure search engines can index your XML sitemap file, check the sitemap report in Google Search Console. | onpage | |||
ROBOTS.TXT | |||||
Use robots.txt | Recommendations: Create a robots.txt file and add it to the root directory of your website. | onpage | present | faulty | not present |
Blocked by robots.txt | Recommendations: Make sure that pages with valuable content are not accidentally blocked by the robots.txt file. If your goal is to prevent pages from being indexed by search engines, do not block such pages by the robots.txt file, but use the noindex directive instead. | onpage | |||
META PAGE TITLE | |||||
Meta Page Title | Recommendations: Write a unique and concise title for each page of the website and add the most relevant keywords to it. | onpage | >10 and <70 | <10 or >70 | |
Use the HTML title tag | Recommendations: Analyze all pages with an empty or missing "< title >" tag and write a unique and concise title for each page and add the most relevant keywords to it. |
onpage | |||
URLs with duplicate page titles | Recommendations: Write a unique and concise title for each page of the website and add the most relevant keywords. | onpage | |||
Multiple title tags | Recommendations: Remove unnecessary title tags. Choose only one unique title for each page. | onpage | |||
Title too long | Recommendations: The title should be 60-70 characters long. Each word should be separated by a space. Describe succinctly what the page is about. | onpage | |||
Title too short | Recommendations: The title should be 60-70 characters long. Each word should be separated by a space. Describe succinctly what the page is about. | onpage | |||
META KEYWORDS | |||||
Meta Keywords | Meta Keywords are comma separated values. Recommendations: Every page should have a unique set of 13 keywords with the most relevant keywords. | onpage | 13 | ||
Keywords in content | Relation of keywords to content. Recommendations: All Meta Keywords should be present in the page content. Relation: 3-5% keywords should be present in the website content. | onpage | >5% | >3% and <5% | <3% |
META DESCRIPTION | |||||
Meta Description | Meta Description should have >40 and <160 characters. | onpage | >150 and <160 | <150 or >160 | |
Use the HTML meta description | Recommendations: Analyze all pages with an empty or missing "< meta name="description" content="Your unique page description." >" meta description and write a unique and concise description for each page and add the most relevant keywords to it. |
onpage | |||
URLs with duplicate meta description | Recommendations: Write a unique and concise meta description for each page of the website and add the most relevant keywords. | onpage | |||
Multiple meta descriptions | Recommendations: Remove unnecessary meta descriptions. Choose only one unique description for each page. | onpage | |||
Meta description too long | Recommendations: The meta description should be 40-160 characters long. Each word should be separated by a space. Describe succinctly what the page is about. | onpage | |||
Meta description too short | Recommendations: The meta description should be 40-160 characters long. Each word should be separated by a space. Describe succinctly what the page is about. | onpage | |||
CONTENT - Headings | |||||
H1 heading | H1 once per page or once per section tag Recommendations: Make sure all your web pages have a < h1 > header tag filled with concise, relevant and unique text. Depending on the type of website and page structure, there may be more than one < h1 > tag, but it is highly recommended to use only one < h1 > tag per page. IMPORTANT: Your pages must be logically structured. |
onpage | 1 per page (or section tag) | 0 | |
H1 heading too long | Recommendations: Make sure all your web pages have a < h1 > header tag filled with concise, relevant and unique text. | onpage | |||
Multiple H1 headings | Recommendations: If possible, use a single < h1 > tag on a page. This way, the structure of the page will be clear to all search engines. | onpage | |||
Duplicate H1 headings | Recommendations: Write a unique < h1 > for each page on your website and add a clear description of the page's content. | onpage | |||
Identical H1 / title tag | Recommendations: Use different texts in the < title > and < h1 > tags. | onpage | |||
H2 heading | H2 tag exists at least one time and is filled with concise text. Recommendations: For pages with < h2 > header tags, make sure that these tags are filled with concise text that briefly describes the main content of the following block. Depending on the website type and page structure, there may be more than one < h2 > tag, but IMPORTANT: Your pages must be logically structured. | onpage | >1 | 0 | |
H2 heading too long | Recommendations: For pages with < h2 > header tags, make sure that these tags are filled with concise text that briefly describes the main content of the following block. | onpage | >1 | 0 | |
CONTENT - FRAME | |||||
Frameset/iFrame | Page uses Frameset/iFrame. Recommendations: Avoid using < frame > tags on the pages of the website that you want to index. |
0 | 1 | >1 | |
CONTENT | |||||
URL too long | Recommendations: The length of your URLs should be a maximum of 75 characters. | onpage | <75 | ||
WWW redirect | Redirection from non-www to www or vice versa. Recommendations: If necessary, redirect all non-www URLs on your site to www. |
onpage | present | faulty | not present |
Multiple rel="canonical" | Recommendations: Remove all canonical URLs except the URL you want to use as the truly canonical version of the page. | onpage | |||
Duplicate content | Recommendations: Make the content unique on a double page. | onpage | |||
URLs with double slashes | Recommendations: Make sure you have configured a server-side redirect with a forward slash. Check which pages on your website have links to such pages and replace such links with correct ones to avoid unnecessary redirects. | onpage | |||
Trailing slashes in URLs | Recommendations: Set up server redirects so that your pages are always accessible either with or without a trailing slash. | onpage | |||
URLs with duplicate page titles | The title tag has 10-70 characters. | onpage | >10 and <70 | <10 or >70 | |
Number of words | Number of words in the HTML body. Recommendations: The content should be more than 300 words. Make sure the text on the page fully reveals the topic or describes the products featured on the page in detail. Write a unique text for each page and add the most relevant keywords to it. |
onpage | >500 | 300 - 500 | <300 |
LSO optimization level | Optimization level of the page topic. | onpage | >50% | 20% - 50% | <20% |
Relevance of metadata | Relevance of metadata to content. | onpage | >50% | <50% | 0 |
CONTENT - IMAGES | |||||
Image too large | Recommendations: Optimize your images and try to reduce the size of the images without losing their quality. Use e. g. WEBP or SVG. | onpage | |||
Image alt attribute | Images without alternative text. Recommendations: Write precise and relevant alt text for each image. | onpage | 0 | <20% | >20% |
3XX Images | Recommendations: Specify the direct path to the image files, replacing each URL from which the redirect is established with relevant ones. If you are using images from an external resource and cannot replace the URLs, make sure that the images uploaded via the new URL are relevant to your content. | onpage | |||
4XX Images (not found) | Recommendations: Check all URLs for broken images and replace the image URLs with relevant, currently working ones or remove the links to the broken images from your website. | onpage | |||
5XX Images (loading failed) | Recommendations: Check the URLs of all images that return a 5XX response code. If these are your URLs, check the web server error log. If you regularly experience problems with server operation, identify the cause and eliminate it. Note that the problem may be temporary and means that technical work was performed on your server during the call. If a 5XX response code is returned for URLs of images from an external resource, check that the resource is reliable. If the problem was triggered by technical work, you can continue using the image. If the site regularly experiences problems with web server accessibility, it is recommended to replace or delete the image. |
onpage | |||
External Image files with 3XX, 4XX or 5XX | Recommendations: Contact the website operator and ask them to fix the errors. | onpage | |||
CONTENT - LINKS | |||||
Nofollow Links | Website has less than 10% nofollow links in relation to all links | <10% | 10% - 30% | >30% | |
CONTENT - LINKS - INTERNAL | |||||
Internal Links | Website has less than 100 internal links | >50 and <100 | 10 - 50 | <10 | |
Anchor/Link text | Recommendations: Make sure that all links contain an anchor/link text. Use concise wording in anchor/link texts. | onpage | |||
Timeout | Recommendations: Make sure that all links to external sites work correctly. | onpage | |||
Incoming internal links | Recommendations: Make sure that the most important pages on your website have at least a few internal links pointing to them. All internal links must not be tagged with the rel="nofollow" attribute! | onpage | |||
Too many internal links | Recommendations: Make sure you need all of them and that they fit naturally into the UX/UI of your product. Remove all unnecessary links. Depending on the type of website (aggregator, online store, blog, forum), you can have pages with more than 300 links if they are of value to visitors. | onpage | |||
Nofollow | Recommendations: Do not use the rel="nofollow" attribute for your website's internal linking! Use the "Disallow" rule in the robots.txt file to prevent search engine robots from following your website's internal links. | onpage | |||
CONTENT - LINKS - EXTERNAL | |||||
External Links | Website has less than 10% external links in relation to all links | <10% | 10% - 30% | >30% | |
Anchor/Link text | Recommendations: Make sure that all links contain an anchor/link text. Use concise wording in anchor/link texts. | onpage | |||
Timeout | Recommendations: Make sure that all links to external sites work correctly. | onpage | |||
Nofollow | Recommendations: Make sure that all external links tagged with the rel="nofollow" attribute really need to be tagged with this attribute. Google recommends using the rel="sponsored" attribute for sponsored links and the rel="ugc" attribute for user-generated content in links (e.g. comments). The rel="nofollow" attribute makes it clear to search engines that you do not want your page to link to the website you are linking to. | onpage | |||
LINKS - INDEXING | |||||
Canonical Chain | Recommendations: Avoid using canonical chains, even though search engines claim they can crawl them without any problems. To avoid confusing search engine bots, you should point to a single canonical page whenever possible. This means you need to replace non-canonical links with direct links to canonical ones. For example, page A will link directly to page C as canonical, bypassing page B. | onpage offpage |
|||
Blocked by noindex | Recommendations: Only use this directive on pages that you do not want to appear in search results. Make sure that these pages are not blocked by the robots.txt file. Otherwise, search engine bots will not be able to see the noindex directive, and if other websites link to these pages, they may appear in search results. | onpage offpage |
|||
Blocked by nofollow | Recommendations: Only use the nofollow attribute if you don't want search engine bots to follow all links on a particular web page. Make sure that pages that use the nofollow attribute are not blocked by the robots.txt file. Otherwise, search engine bots will not be able to see the nofollow attribute. | onpage offpage |
|||
Blocked by X-Robots-Tag | Recommendations: Make sure that any directive specified in the X-Robots-Tag header is applied to pages that you really don't want to be shown and/or contain links that you don't want search engine robots to follow. Also note that pages that contain indexing directives in the X-Robots-Tag header should not be blocked by the robots.txt file. Otherwise, search engine bots won't be able to see the directives. | onpage offpage |
|||
HTML | |||||
HTML Errors | Number of HTML Errors | 0 | 0 - 10 | >10 | |
HTML Warnings | Number of HTML Warnings | 0 (1x HTML5) | 0 - 10 | >10 | |
Doctype Declaration | Page uses HTML5 Declaration | HTML5 | HTML Strict | HTML4 | |
Character set encoding | Page uses UTF-8 charset | UTF-8 | Iso-XXX | None | |
CSS | |||||
Inline Styles | Number of inline styles | 0 | 0 - 5 | >5 | |
Style Tags | Number of inline style tags | 0-1 | 1 - 3 | >3 | |
Link Tags (Stylesheet) | Number of stylesheet link tags | 0-1 | 1 - 3 | >3 | |
CSS Errors | Number of CSS Errors | 0 | 0 - 10 | >10 | |
CSS Warnings | Number of CSS Warnings | 0 | 0 - 10 | >10 | |
CSS too big | Recommendations: Optimize the code of every large CSS file. | onpage offpage |
|||
Compress CSS | Recommendations: Configure server-side CSS compression. Only load external resources if they are provided in compressed form. | onpage offpage |
|||
CSS caching | Recommendations: Configure caching of your CSS files. | onpage offpage |
|||
Too many CSS files | Recommendations: Only load CSS files that are necessary for the correct display of your website. | onpage offpage |
|||
CSS minification | Recommendations: Only load minified CSS files. | onpage offpage |
|||
3XX CSS file | Recommendations: Specify the direct path to the CSS files, replacing each URL from which the redirect is established with relevant current ones. If you are using CSS files from an external resource and cannot replace the URLs, make sure the URLs point to the correct files. |
onpage offpage |
|||
4XX or 5XX CSS file | Recommendations: Make sure that the path to the CSS files being called is correct and that the website's web server is working properly. | onpage offpage |
|||
External CSS files with 3XX, 4XX or 5XX | Recommendations: Contact the website operator and ask them to fix the errors. | onpage offpage |
|||
JAVASCRIPT | |||||
Inline Scripts | Number of inline scripts | 0 | 0 - 5 | >5 | |
Script Tags | Number of inline script tags | 0-1 | 1 - 3 | >3 | |
JAVASCRIPT too big | Recommendations: Optimize the code of every large JAVASCRIPT file. | onpage offpage |
|||
Compress JAVASCRIPT | Recommendations: Configure server-side JAVASCRIPT compression. Only load external resources if they are provided in compressed form. | onpage offpage |
|||
JAVASCRIPT caching | Recommendations: Configure caching of your JAVASCRIPT files. | onpage offpage |
|||
Too many JAVASCRIPT files | Recommendations: Only load JAVASCRIPT files that are necessary for the correct display of your website. | onpage offpage |
|||
JAVASCRIPT minification | Recommendations: Only load minified JAVASCRIPT files. | onpage offpage |
|||
3XX JavaScript file | Recommendations: Specify the direct path to the JavaScript files, replacing each URL from which the redirect is established with relevant current ones. If you are using JavaScript files from an external resource and cannot replace the URLs, make sure the URLs point to the correct files. |
onpage offpage |
|||
4XX or 5XX JavaScript file | Recommendations: Make sure that the path to the JavaScript files being called is correct and that the website's web server is working properly. | onpage offpage |
|||
External Javascript files with 3XX, 4XX or 5XX | Recommendations: Contact the website operator and ask them to fix the errors. | onpage offpage |
|||
LOCALIZATION | |||||
HTML language definition | Present and error-free | country-specific | faulty | not set | |
Invalid language code | Recommendations: Review all pages and specify the correct page language codes. Follow ISO 639-1 format for attributes specifying the language and ISO 3166-1 Alpha 2 format for attributes specifying the region. | onpage | |||
Hreflang page does not link to itself | Recommendations: Add the missing hreflang attribute and link to the code so that the page points to itself. For example, a German version of a page should have the rel="alternate" hreflang="de" attribute and link to that version of the page. | onpage | |||
Hreflang to non-canonical | Recommendations: Check all pages and change the hreflang attribute so that the URL points to the canonical version of the page. If the URL that the hreflang attribute points to is indeed canonical, change the rel="canonical" attribute. In any case, both the hreflang and rel="canonical" attributes must point to the same URL, which you consider to be the main URL. If the page does not have different versions, the rel="canonical" attribute can be removed. |
onpage | |||
Hreflang and HTML lang do not match | Recommendations: Check all pages and make sure that the hreflang and HTML lang attributes use the same language code. | onpage | |||
Confirmation links (return links) are missing on Hreflang pages | Recommendations: To fix this error, use the same set of < URL >, rel="alternate" and hreflang values on all language or regional versions of the page. This way, all hreflang pages will have backlinks to other versions of the page. | onpage | |||
Multiple language codes for one page | Recommendations: Check all pages and remove the unnecessary hreflang attribute or replace the language code with the correct one. You cannot specify more than one language code for a single URL, but you can specify multiple regions for the chosen language version, e.g. en-us, en-gb, etc. |
onpage | |||
Invalid HTML lang | Recommendations: Review all pages and specify the correct HTML lang attribute using the correct language or regional version codes. Adhere to ISO 639-1 format for attributes specifying the language and ISO 3166-1 Alpha 2 format for attributes specifying the region. |
onpage | |||
Double Languages in Hreflang | Recommendations: Check all pages and correct the hreflang attributes so that each URL has a single language code. | onpage | |||
HTML lang missing | Recommendations: Use the HTML lang attribute to specify which language the page's text is written in and/or which region the page is intended for. Follow ISO 639-1 format for attributes specifying the language and ISO 3166-1 Alpha 2 format for attributes specifying the region. |
onpage | |||
X-default hreflang attribute missing | Recommendations: Create a special backup page for languages that are not supported on your site and add it to the hreflang attribute using the x-default tag. | onpage | |||
PAGE SPEED / PERFORMANCE | |||||
Server response time | time until the server responds | <100 ms | 100 - 300 ms | >300 ms | |
Loading time | total time of the first page load | <1 Sek. | 1 - 3 Sek. | >3 Sek. | |
Timeout | Recommendations: Make sure that the pages that aren't accessible are loading correctly. If your website's pages take too long to load, it can negatively impact the user experience and also slow down the indexing of the page. | onpage | |||
Google PageSpeed (Desktop) | Estimating Desktop Speed | >90% | 75% - 90% | <75% | |
Google PageSpeed (Mobile) | Estimating Mobile Speed | >90% | 75% - 90% | <75% | |
Google PageSpeed (Mobile user experience) | Assessment of mobile usability | >90% | 75% - 90% | <75% | |
Yahoo YSlow | Estimation of speed | >90% | 75% - 90% | <75% | |
HTML too large | Recommendations: Optimize by improving its structure. Remove unnecessary code elements, empty lines, whitespace, scripts and styles etc. For example, remove inline styles and move them to separate CSS files. | onpage | |||
Slow page loading speed | Recommendations: Optimize the HTML code for all pages. This is important because if the HTML code of the page is not optimized, the page will take longer to load. Also consider checking your web server, as it could be the cause of the problem. If optimizing your code doesn't help, consider switching to a faster web server. | onpage | |||
Compress content and resources | Recommendations: Enable compression on your web pages by using the Content-Encoding entity to make the page load faster. Only load external resources if they are compressed. | onpage | |||
Largest Contentful Paint (LCP) under real conditions / in a development environment | Recommendations: Speed up server response time to ensure that the largest image or block of text is displayed in less than 2.5 seconds. To speed this up, use preloading on pages with static content and optimize top-of-page code. Also, optimize font and image file sizes and eliminate render-blocking JavaScript and CSS features. | onpage | |||
First Input Delay (FID) under real conditions | Recommendations: Optimize JavaScript files by minifying them and removing unnecessary or redundant data without affecting the code. Also remove unused or unnecessary JavaScript libraries. Split the JavaScript code into bundles and load only the parts that are needed at any given time. | onpage | |||
Cumulative Layout Shift (CLS) under real conditions / in a development environment | Recommendations: Use size attributes for media files (images and videos) to reserve space in the final layout rendering. Avoid inserting new content over already rendered content and use CSS transform animations. | onpage | |||
First Contentful Paint (FCP) under real conditions / in a development environment | Recommendations: Speed up server response time by preloading on pages with static content. Optimize font and image file sizes and top-of-page code. Eliminate render-blocking JavaScript and CSS. | onpage | |||
Page speed index | Recommendations: Increase the loading speed of your page by compressing images on the page, optimizing Javascript and CSS, and using page caching. When loading web fonts, use the font the user already has so that the text is visible without delay. | onpage | |||
Time to interaction (TTI) | Recommendations: Optimize JavaScript code! Optimize JavaScript files by minifying them and removing unnecessary or redundant data without affecting the code. Also remove unused or unnecessary JavaScript libraries. Split the JavaScript code into bundles and load only the parts that are needed at any given time. | onpage | |||
Total Blocking Time (TBT) | Recommendations: Optimize the execution of long tasks. For example, split a large script into several smaller ones that are loaded gradually. Minify the code by removing unnecessary elements and splitting it into separate packages. | onpage | |||
HTTP HEADER | |||||
HTML and HTTP headers contain noindex | Recommendations: Choose one of two ways to prevent the page from appearing in search results: either add the "noindex" tag to the HTML code (meta tag) of the page or use it in the HTTP request (X-Robots tag). | onpage | |||
HTML and HTTP headers contain nofollow | Recommendations: Choose one of two ways to prevent search engines from indexing the links on the page: either add the "nofollow" attribute to the HTML code (meta tag) of the page or use it in the HTTP request (X-Robots tag). | onpage | |||
SERVER | |||||
Directory-Browsing | Folder view on the server is prevented | yes | no | ||
Server Signature | Server signature is not displayed | yes | no | ||
Server-Time | The server time is set correctly | yes | no | ||
Server-Location | The server location is in the same country as the business headquarters. | yes | no | ||
IP neighborhood | number of domains of the same IP | <3 | 3 - 10 | >10 | |
REDIRECTS | |||||
Meta-Refresh-Redirect | Recommendations: If you don't absolutely need to use the meta refresh redirect tag, remove it and set up a 301 server-side redirect instead. | onpage | |||
Redirect chain | Recommendations: Remove unnecessary links from the chain by setting up a redirect from the first version of the page directly to the current address of the page. | onpage | |||
Redirect loop | Recommendations: Remove redirects so that the page returns a 200 OK response code. If you must use redirects, change the address of the redirect landing page to the correct address. This page should return the 200 OK response code and it should not have a redirect. | onpage | |||
Temporary redirects (302, 303, 307) | Recommendations: Make sure you don't accidentally use 302, 303 or 307 redirects (e.g. for split testing). Remove temporary redirects when they are no longer needed. If the page address has changed forever, set up 301 redirects instead. | onpage | |||
Redirect to 4xx or 5xx | Recommendations: If the page returns a 4XX response code, replace the address of the target redirect page with the appropriate address. A 5XX response code indicates that there is a problem with the page's web server. The error may be temporary and mean that technical work was performed on your server during a request. Check the web server's error log. If server problems occur regularly, determine the cause and fix it. | onpage | |||
HTTP STATUS CODE | |||||
4XX pages in XML sitemap | Recommendations: Remove URLs with 4xx response code from the XML sitemap. Make sure that the XML sitemap only contains URLs that return 200 OK response codes. | onpage | |||
3XX pages in XML sitemap | Recommendations: Replace redirecting URLs in the XML sitemap with destination URLs. If a destination URL is already in the XML sitemap, you should delete URLs with 3XX redirects from the XML sitemap. | onpage | |||
5XX pages in XML sitemap | Recommendations: Make sure your XML sitemap contains up-to-date data and no pages with server error codes. | onpage | |||
3XX Status-Code | Recommendations: Make sure that the number of 3XX pages on your website does not exceed 5% of the total number of pages. If their number exceeds 10%, then you have a critical problem and should immediately remove some of the redirects. | onpage | |||
4XX-HTTP-Status-Code | Recommendations: Check the list of 4XX URLs and analyze each internal page that links to a 4XX URL. Remove such broken links or replace them with appropriate links to live and accessible pages. Also, you can set up 301 redirects when moving or deleting the website pages to avoid 4XX errors. | onpage | |||
5XX-HTTP-Status-Code | Recommendations: Analyze the list of URLs that return 5XX Server Response Codes. Try to reproduce the server error for these URLs through the browser. Also, check the server's error log. If this is a constant problem for many pages on your website, contact your hosting provider or web developer. Your server may be overloaded or misconfigured. It is also important to remember that this error may be a temporary problem and means that the website's server was undergoing maintenance while you were visiting. | onpage | |||
Canonical URL results in a 3XX status code | Recommendations: Analyze the list of canonical URL pages that point to redirected pages. Replace canonical URLs that contain redirects with 200 OK pages that should be indexed and displayed in the SERPs. | onpage | |||
Canonical URL with a 4XX status code | Recommendations: Review the list of pages with canonical links pointing to 4XX URLs. Replace such canonical URLs with links to the valid 200 OK version of the page that you want to index in search results. | onpage | |||
Canonical URL with a 5XX status code | Recommendations: 5XX errors indicate that there is a problem with your web server. Contact your hosting provider or web developer as your server may be overloaded or misconfigured. You should also keep in mind that this may be a temporary problem. It is possible that the website's server was undergoing maintenance while you were trying to access it. If the wrong URL was specified as canonical, replace it with the link to the valid 200 OK page version that you want to have indexed in search results. | onpage | |||
Internal links to 3XX redirect pages | Recommendations: Replace all internal links with current page URL addresses. | onpage | |||
External links to 3XX | Recommendations: Manually review each external 3XX link and make sure the redirected pages contain the desired information. If so, replace the link with the new version of the URL. If the desired information is not present, replace or delete the link from your website. | onpage | |||
External links to 4XX | Recommendations: Check all pages and remove or replace any broken links. All external links from your site should lead to pages with a 200 OK response code. | onpage | |||
External links to 5XX | Recommendations: Review all pages and remove or replace any broken links. If the site you are linking to has regular server unavailability issues, remove or replace links pointing to that site. All external links from your site should lead to pages with a 200 OK response code. | onpage | |||
Hreflang to 3XX, 4XX or 5XX | Recommendations: Check URLs with 3XX, 4XX or 5XX response codes pointed to by hreflang attributes. Instead of these URLs, use pages that display the response code 200 OK. | onpage | |||
USABILITY | |||||
RSS-Feed | Integration as a meta tag and linked on the page. | present | faulty | not present | |
Open Graph | Open Graph elements present | present | faulty | not present | |
Rich-/Microdata | Rich-/Microdata elements present | present | faulty | not present | |
Root/Home page path | do this "/" and not "/cms/index.php" | yes | no | ||
Underscore URLs | Website does not use underscore URLs for internal URLs | yes | no | ||
Fully Parameterized URLs | Website does not use fully parameterized URLs for internal URLs | yes | no | ||
Contemporary layout | Layout is well-thought-out and has clear navigation etc. | onpage | |||
Favicon | Recommendations: Add a favicon to your website. | onpage | present | faulty | not present |
Apple Touch Icon | Present and error-free | onpage | present | faulty | not present |
Printability | Present and error-free | onpage | present | faulty | not present |
Flash | Page uses Flash Recommendations: Use HTML5 instead of Flash on your website. |
onpage | 0 | 1 | >1 |
Twitter Card Tag | Recommendations: Use the Twitter Card tag to make the links to your pages that you share in your Twitter feed look attractive. IMPORTANT: The URLs inside the Twitter Card tags must be absolute and use the http:// or https:// protocols. | onpage | present | faulty | not present |
MOBILE DEVICES / RESPONSIVE DESIGN | |||||
Responsive Design | Website developed for Desktop, Tablet and Mobile Devices (Smartphones) | onpage | yes | partial | no |
MobileOK Checker | Assessment of mobile compatibility | >50% | 10% - 50% | <10% | |
Viewport-Meta-Tag | Recommendations: Set the viewport meta tag < meta name="viewport" content="width=device-width, initial-scale=1" > for each individual web page and test your website on mobile devices to make sure everything works correctly. |
onpage | |||
Fixed width value in the viewport meta tag | Recommendations: Scale pages to fit screens of different sizes. To do this, the viewport meta tag must contain the device-width value. | onpage | |||
Use compatible plugins | Recommendations: Use modern, widely supported technologies (e.g. HTML5) on the site. | onpage | |||
Minimum Text to Code/HTML ratio | Recommendations: To reduce page size and speed up page loading time, shorten HTML code. For example, remove all unnecessary comments, spaces and blank lines. | onpage | >50% | 25% - 50% | <25% |
AMP (Accelerated Mobile Pages) | |||||
Use AMP pages | Recommendations: Plan to add AMP pages to your website. They can help your website load faster on mobile devices and improve the user experience. | onpage | |||
Blocked by robots.txt | Recommendations: Make sure AMP pages are not blocked in your robots.txt file. Check if you need to enter login credentials to access AMP pages. | onpage | |||
AMP-Page Domain-Mismatch | Recommendations: Use the same domains for the AMP page and its canonical version. Host the canonical page (mypage.com/images) and the AMP page (amp.mysite.com/tables or mypage.com/amp/images) on the same domain. | onpage | |||
Error in rejection | Recommendations: Replace deprecated elements that are no longer supported with modern elements that comply with the current AMP specification. | onpage | |||
AMP HTML tag error | Recommendations: Fix any AMP HTML tag errors to ensure pages conform to AMP guidelines and display correctly. | onpage | |||
AMP HTML attribute error | Recommendations: Fix any AMP HTML attribute errors to ensure pages conform to AMP guidelines and display correctly. | onpage | |||
Errors in Layout/Style | Recommendations: Fix any errors found in layout and styles to ensure pages comply with AMP guidelines and display correctly. | onpage | |||
Template Errors | Recommendations: Does an attribute contain mustache template syntax? Remove it. Does an attribute contain unhighlighted template syntax? Highlight the mustache template. |
onpage | |||
SOCIAL MEDIA | |||||
Number of Likes, Shares and Comments | >100 | 10 - 100 | <10 | ||
Google Plus One | Number of Pluses | >100 | 10 - 100 | <10 | |
Twitter Tweets | Number of Tweets | >100 | 10 - 100 | <10 | |
LinkedIn Shares | Number of Shares | >100 | 10 - 100 | <10 | |
Xing Shares | Number of Shares | >100 | 10 - 100 | <10 | |
Pinterest Pins | Number of Pins | >100 | 10 - 100 | <10 | |
Delicious Bookmarks | Number of Bookmarks | >100 | 10 - 100 | <10 | |
StumbleUpon Bookmarks | Numder of Bookmarks | >100 | 10 - 100 | <10 | |
SEM POTENTIAL | |||||
Google AdWords Quality-Score | Quality-Score for the existing keywords. | >7 | 3 - 7 | <3 | |
BACKLINKS / REFERENCES | |||||
Wikipedia Backlinks | Number of backlinks in Wikipedia | >3 | 1 - 2 | 0 | |
Dmoz Backlinks | Number of backlinks in DMoz | >3 | 1 - 2 | 0 | |
Yahoo Directory Links | Number of backlinks in the Yahoo Directory | >3 | 1 - 2 | 0 | |
Google Backlink-Index | Number of backlinks in the Google Index | >100 | 10 - 100 | <10 | |
Bing Backlink-Index | Number of backlinks in the Bing Index | >100 | 10 - 100 | <10 | |
Alexa Backlink-Index | Number of backlinks in the Alexa index | >1K | 10 - 1K | <10 | |
Root-/Homepage Backlinks | All backlinks that lead to the root/homepage | >100K | 100K - 1K | <1K | |
Deep-/Subpages Backlinks | All backlinks that lead to deep/subpages | >100K | 1K - 100K | <1K | |
IP Backlinks | All backlinks from other IP domains | >2.5K | 500 - 2.5K | <500 | |
C-Block Backlinks | All backlinks from other C-Block domains | >5K | 1K - 5K | <1K | |
All public backlinks | All publicly recorded backlinks | >2 Mio. | 10K - 2 Mio. | <10K | |
Natural-looking link profile | Even source distribution of link industries | Uneven | ~ | Evenly | |
Variations of anchor texts | Different uses of anchor texts | onpage | Uneven | ~ | Evenly |
Youtube videos | Use Youtube video with location information. | offpage | |||
Google Business View | Use Google Business View with location information. | offpage | |||
Reviews and Descriptions | Place keywords in reviews and descriptions. | offpage | |||
SERIOUSNESS | |||||
MyWot Trustworthiness | Rating of the trustworthiness of MyWot | good | medium | bad | |
MyWot youth protection | Rating of the youth protection of MyWot | good | medium | bad | |
Save Browsing | Website supports Save Browsing | yes | no | ||
Website is in Spam list? | Website is in Spam list | no | yes | ||
Contact form/page | contact option available | yes | no | ||
Whois information | Whois record is equal to the imprint data | yes | no | ||
Imprint | Page present and complete | yes | no | ||
Privacy policy | Page present and complete | yes | no | ||
Terms and conditions | Page present and complete | yes | no | ||
Terms of use | Page present and complete | yes | no | ||
FAQ (Frequently asked questions) | Page present and complete | yes | no | ||
Directions description | Description present and complete | yes | no | ||
Data protection-compliant social buttons | Use of data protection-compliant social buttons | yes | no | ||
SERIOUSNESS - AUTHOR | |||||
Author meta tag | Present and error-free | present | faulty | not present | |
Google+ | Website is connected to Google+ Page | present | faulty | not present | |
humans.txt | Present and error-free | present | faulty | not present | |
VISIBILITY | |||||
Google Rankings | ranking of the specified keywords | 100% in Top 10 | 50% - 100% Top 10 | <50% Top 10 | |
Bing Rankings | ranking of the specified keywords | 100% in Top 10 | 50% - 100% Top 10 | <50% Top 10 | |
General visibility | General visibility in search engines | >100K | 1K - 100K | <1K | |
PAGE VIEWS/VISITS | |||||
Alexa page views/visitors | Average Pageviews | >10 | 3 - 10 | <3 | |
Alexa length of stay | Average length of stay | >10 Min. | 10 Min. - 10 Min. | <3 Min. | |
Alexa bounce rate | Average bounce rate | <33% | 33% - 66% | >66% | |
Alexa visitors via a search | Number of visitors from a search | >30% | 10% - 30% | <10% |
DIRECTORIES / BUSINESS LISTINGS / CATALOGS / SOCIAL MEDIA
Here is a suggested list of trusted directories and catalogs where your business may be listed. This can increase your visibility in searches and boost your business performance. Make sure your business is found on the most reliable resources.
- A-Zbusinessfinder
- Acxiom
- Annuaire des Entreprises de France
- Apple Maps
- auskunft.de
- AussieWeb
- B2BYellowpages.com
- BBB
- BBB.org
- belocal.de
- bing.de
- bingplaces.com
- BizAdee
- BizCommunity.com
- BizVotes.com
- blaue-branchen.de (yellowmap)
- BOTW.org
- Brabys.com
- branchenbuchdeutschland.de
- branchenbuchsuche.de
- branchenmorgen.de (yellowmap)
- Brownbook
- business-branchenbuch.de
- Business Listings
- BusinessZoom.co.nz
- Callupcontact
- CanadaOne
- Central Index
- ChamberOfCommerce.com
- city-map.com
- CitySquares.com
- Cityvisitor.co.uk
- Cybo
- Cylex
- Daily Record
- dasoertliche.de
- dastelefonbuch.de
- Delicious Bookmarks
- DeTelefoongids
- Digg Bookmarks
- directory.ac
- dLook
- dmoz
- ExpressBusinessDirectory
- EZLocal.com
- facebook.com
- factual.com (foursquare)
- FDF.pl
- Finda.co.nz
- Find-Us-Here
- foursquare.com/city-guide
- freieauskunft.de (yellowmap)
- FreeIndex.co.uk
- Fypie
- Fyple
- gelbeseiten.de
- GetFave.com
- gimpsy.com
- gmx.net
- GoldenPages.ie
- golocal.de
- google.com/intl/de/business
- Google Business Profile
- Google My Business
- Google Places
- goyellow.de
- GuiaMais H
- HotFrog
- iBegin.com
- Independent
- infobel.com
- InSing
- InsiderPages.com
- IrelandYP
- joeant.com
- Kennstdueinen
- klicktel.de (11880)
- Kompass
- koomio.com
- Lacartes
- LAnnuaire.fr
- LinktoAdd.nl
- lokaleauskunft.de (yellowmap)
- Local Business Guide
- Local.com
- Local.fr
- LocalBD.co.nz
- LocalSearch.ie
- Manta.com
- mapquest.com
- marktplatz-mittelstand.de
- meinestadt.de (dasoertliche)
- meinesuche.net
- mein-verzeichniseintrag.de
- MerchantCircle.com
- MisterImprese
- MisterWhat
- MKB-Bedrijvengids
- MyHuckelberry.com
- MyLocalServices.co.uk
- Mysheriff
- NAVITIME
- NZSBDirectory.co.nz
- PagesJaunes
- PaginasAmarillas.es
- PKT.pl
- plus.google.com
- POIDB
- pointoo.de
- ProfileCanada
- qualigo.com
- Qype
- SaleSpider
- SaYellow.com
- SearchLocal.nz
- Scoot.co.uk
- Showmelocal.com
- SmartGuy
- Spoke
- stadtbranchenbuch.com
- StartLocal
- StreetDir
- StumbleUpon Bookmarks
- TeleListas
- TheBestOf.co.uk
- TheGreenBook
- TheTradeFinder.co.uk
- ThomsonLocal.com
- ThreeBestRated.com
- Todoenlaces.com
- tomtom.com
- TouchLocal.com
- Tripped.co.uk
- Tumblr
- Tupalo
- Tuugo.us
- twitter.com
- uberall.com
- UK Small Business Directory
- unternehmensauskunft.com
- unternehmensverzeichnis.org
- Wampit
- WAND
- web.de
- web2.cylex.de
- Websites.ca
- werkenntdenbesten.de
- Where2Go
- WhoDoYou
- wikipedia
- wogibtswas.de
- Word of Mouth
- World Business Directory (WBD)
- Yabsta.ie
- Yahoo
- Yahoo Local
- yalwa.de
- Yell.com
- Yellowbook.com
- yellowmap.de
- Yellow Pages
- YellowSA.co.za
- yelp.de
- Yelu.sg
- yext.com
- youtube.com
- Zenbu.co.nz
- ZipLeaf
- firmenpresse.de
- newsmax.com
- presseanzeiger.de
- 118000.fr
- 11880.com
- 11890.ie
- 118Information.co.uk
- 192.com
- 2FindLocal
- 411.ca
- aligo.at
- sicherheits-berater.de
- sicheriminternet.de
- simobit.de
- . . .
- do you know more directories, business listings, catalogs or social media? let us know. help us to grow and extend seo4all.
REVIEWS
- Ciao.de
- Dooyoo.de
- Erfahrungen.com
- Google Places
- KennstDuEinen.de
- Qype
- Yelp
- . . .
- do you know more review pages? let us know. help us to grow and extend seo4all.
SEO TOOLS
- ahrefs Keyword Explorer
- Alexa's Keyword Research
- AMZ Tracker
- ANSWER THE PUBLIC
- bananacontent
- Bing Webmaster Tools
- Can I Rank
- cognitiveseo.com
- Copyscape
- drlinkcheck.com
- FAQfox (WebpageFX)
- getIndexed.io
- G Maps Ranking Extractor
- Google Alerts
- Google Bulk Inspect URLs
- Google Erweiterte Suche
- Google Markup Helper
- Google Mobile Page Speed Test
- Google News Extractor
- Google Search Console
- Greenlane Google Indexation Tester
- GrepWords
- Grid My Business
- GSC Helper
- GTmetrix
- hreflang Generator
- H-supertools
- HTTP Status Code Checker
- HyperSuggest
- Infinite Suggest
- InstaKeywords
- iSpionage
- Jaaxy
- K-META
- keylime toolbox
- Keys4up
- KeySearch
- Keywords Everywhere
- Keyword Eye
- Keyword Keg
- Keyword Revealer
- Keyword Snatcher
- Keyword Surfer
- Keyword Tool Dominator
- Keyword Hero
- Keyword.io
- Keyword Discovery
- Keyword Finder
- Keyword Researcher
- Keyword Tool
- KEYWORD-TOOLS.ORG
- KeywordPro
- Keyword Shitter
- KeywordTool.io
- Keywords everywhere
- KNIME
- Kparser
- KWFinder.com
- Lighthouse
- Local SERP Checker
- Long Tail Pro
- LSI Graph
- majestic.com
- Market Samurai
- MerchantWords
- MerchNinja
- MetaCrawler
- MetaGer
- Metric Tools
- Microsoft SEO Toolkit
- Mobile First Index Checker
- Mobile Friendly Check
- Mobile PageSpeed Test
- Mobile SERP Test
- Moz Keyword Explorer
- Onpage Monitoring Tool
- OpenLinkProfiler
- OpenThesaurus
- PageSpeed Insights
- Power Suggest Pro
- QuestionDB
- RankTank Ranking Checker
- Rich Result Test
- Ryte
- saney.com
- Schema Markup Generator
- Scientific Seller
- ScrapeBox
- Screaming Frog
- searchanalyzer.io
- searchanalyticsforsheets.com
- Searchvolume.io
- SECockpit
- Seed Keywords
- semaGER
- SEMrush
- SEMrush Sensor
- SEMScoop
- SEOBOOK
- seochat
- SEOdiver
- SEOkicks
- SEO Scout
- SEO Explorer
- SEO REVIEW TOOLS
- SEOmonitor
- SEOlyze
- SEORCH
- seospark.io
- SEO Tools for Excel
- SERP Keyword Extractor
- SERP Scraper Google Docs
- SERP Snippet Extractor
- SeoStack
- SERPWoo
- Sheets for Marketers
- Similarweb
- Simple SERP Scraper
- Sistrix
- SISTRIX SERP Snippet Generator
- Sistrix Smart
- Site Analyzer Pro
- Siteliner
- Structured Data Testing Tool
- sonar
- Soovle
- SpyFu
- Squirrly
- Squoosh
- StoryBase
- TermExplorer
- TEXToptimizer
- Thesaurus.com
- Twinword Ideas
- Ubersuggest
- vidIQ
- Viral Launch
- Visual Thesaurus
- w3.org/developers/tools/
- W-FRAGEN-TOOL.COM
- WebCEO
- Web.dev
- Wortliga
- Wordstream
- Wordtracker
- Wortschatz Uni Leipzig
- XENU
- xml-sitemaps.com
- Yahoo Yslow
- Yandex Keyword statistics
- yslow.org
- . . .
- do you know more review pages? let us know. help us to grow and extend seo4all.
how can i support seo4all?
you are welcome. you can provide support in different ways:
- creating or extending checklists
- creating or extending directories
- creating or extending documents (templates)
- creating or extending recommendations for action
- creating or extending seo tools
- become a sponsor and donate, if you use seo4all or if you think, that seo4all is useful or if seo4all has given you a coffee cup's worth of benefits.
why supporting or sponsoring seo4all?
seo4all is a project of Walid Moussa (MW) under the MIT license.
MW provides a lot of software and utilities as freeware for the web without requiring the users to pay any fee.
however, maintaining the web site, updating the existing utilities and releasing new utilities require to invest a fair amount of time and also money (especially for hosting).
do you use seo4all or do you find seo4all useful? has seo4all given you a coffee cup's worth of benefits this year?
make your decision and give something back. with your donation you support the development of seo4all and other useful free software.
i greatly appreciate your support!
kind regards
Copyright © by Walid Moussa (MW)
Code released under the MIT license.