LadresseConceptStore.com

CONCEPT STORE - L'Adresse Concept Store

2,756,657 issues found
  Errors: 1,008,778 |   Warnings: 114,415 |   Info: 1,633,464 | Pages: 20,382 | Date: Apr 22, 2020
Site Audit: Summary
Indexing and crawlability
Resources with 4xx status code
5,829
Resources with 5xx status code
0
Resources restricted from indexing
1,389
404 page set up correctly
Yes
robots.txt file
Yes
.xml sitemap
Yes
Redirects
Fixed www and non-www versions
Yes
Issues with HTTP/HTTPS site versions
No
Pages with 302 redirect
0
Pages with 301 redirect
206
Pages with long redirect chains
0
Pages with meta refresh
0
Pages with rel="canonical"
20,154
Encoding and technical factors
Mobile friendly
Yes
HTTPS pages with mixed content issues
0
Pages with multiple canonical URLs
0
Pages with Frames
0
Pages with W3C HTML errors and warnings
-
Pages with W3C CSS errors and warnings
-
Too big pages
21
URLs
Dynamic URLs
17,252
Too long URLs
13,069
Links
Broken links
66,101
Pages with excessive number of links
20,154
Dofollow external links
106,935
Images
Broken images
0
Empty alt text
1,423,935
On-page
Empty title tags
0
Duplicate titles
110
Too long titles
657
Empty meta description
0
Duplicate meta descriptions
2,839
Too long meta description
0
Localization
Language Versions
1
Pages with hreflang elements
20,154
Incorrect language codes
0
Invalid URLs
0
Missing return links
1,000,000
Conflicting hreflang elements
0
Non-canonical pages with hreflang elements
17,315
Missing "x-default" values
20,154
Incomplete hreflang values
20,154
Site Audit: Details
Resources with 4xx status code (5,829 resources)

Some of your resources return 4xx status codes.

HTTP status code
404
Not found
Found on pages
20
HTTP status code
404
Not found
Found on pages
20
HTTP status code
404
Not found
Found on pages
20
HTTP status code
404
Not found
Found on pages
20
HTTP status code
404
Not found
Found on pages
39
HTTP status code
404
Not found
Found on pages
9
HTTP status code
404
Not found
Found on pages
20
HTTP status code
404
Not found
Found on pages
20
HTTP status code
404
Not found
Found on pages
1
HTTP status code
404
Not found
Found on pages
1
HTTP status code
404
Not found
Found on pages
1
HTTP status code
404
Not found
Found on pages
1
HTTP status code
404
Not found
Found on pages
13
HTTP status code
404
Not found
Found on pages
13
HTTP status code
404
Not found
Found on pages
1
HTTP status code
404
Not found
Found on pages
1
HTTP status code
404
Not found
Found on pages
1
HTTP status code
404
Not found
Found on pages
5
HTTP status code
404
Not found
Found on pages
5
HTTP status code
404
Not found
Found on pages
4
HTTP status code
404
Not found
Found on pages
4
HTTP status code
404
Not found
Found on pages
1
HTTP status code
404
Not found
Found on pages
1
HTTP status code
404
Not found
Found on pages
1
HTTP status code
404
Not found
Found on pages
1
HTTP status code
404
Not found
Found on pages
12
HTTP status code
404
Not found
Found on pages
12
HTTP status code
404
Not found
Found on pages
1
HTTP status code
404
Not found
Found on pages
1
HTTP status code
404
Not found
Found on pages
1
HTTP status code
404
Not found
Found on pages
11
HTTP status code
404
Not found
Found on pages
11
HTTP status code
404
Not found
Found on pages
1
HTTP status code
404
Not found
Found on pages
1
HTTP status code
404
Not found
Found on pages
5
HTTP status code
404
Not found
Found on pages
4
HTTP status code
404
Not found
Found on pages
4
HTTP status code
404
Not found
Found on pages
11
HTTP status code
404
Not found
Found on pages
11
HTTP status code
404
Not found
Found on pages
13
HTTP status code
404
Not found
Found on pages
13
HTTP status code
404
Not found
Found on pages
12
HTTP status code
404
Not found
Found on pages
12
HTTP status code
404
Not found
Found on pages
11
HTTP status code
404
Not found
Found on pages
11
HTTP status code
404
Not found
Found on pages
7
HTTP status code
404
Not found
Found on pages
7
HTTP status code
404
Not found
Found on pages
9
HTTP status code
404
Not found
Found on pages
4
HTTP status code
404
Not found
Found on pages
4
HTTP status code
404
Not found
Found on pages
10
HTTP status code
404
Not found
Found on pages
10
and 5,329 more resources
About this SEO Factor:

4xx errors often point to a problem on a website. For example, if you have a broken link on a page, and visitors click it, they may see a 4xx error. It's important to regularly monitor and fix these errors, because they may have negative impact and lower your site's authority in users' eyes.

Resources with 5xx status code (0 resources)

Well done! Your website is free from 5xx errors.

About this SEO Factor:

5xx error messages are sent when the server has a problem or error. It's important to regularly monitor these errors and investigate their causes, because they may have negative impact and lower the site's authority in search engines' eyes.

404 page set up correctly (Yes)

Good job! Your site's 404 error page is set up correctly.

About this SEO Factor:

A custom 404 error page can help you keep users on the website. In a perfect world, it should inform users that the page they are looking for doesn't exist, and feature such elements as your HTML sitemap, the navigation bar and a search field. But more importantly, a 404 error page should return the 404 response code. This may sound obvious, but unfortunately it's rarely so.

According to Google Search Console:

"Returning a code other than 404 or 410 for a non-existent page... can be problematic. Firstly, it tells search engines that there's a real page at that URL. As a result, that URL may be crawled and its content indexed. Because of the time Googlebot spends on non-existent pages, your unique URLs may not be discovered as quickly or visited as frequently and your site's crawl coverage may be impacted. We recommend that you always return a 404 (Not found) or a 410 (Gone) response code in response to a request for a non-existing page."

robots.txt file (Yes)

Well done! A robots.txt file is available on your website.

About this SEO Factor:

The robots.txt file is automatically crawled by robots when they arrive at your website. This file should contain commands for robots, such as which pages should or should not be indexed. If you want to disallow indexing of some content (for example, pages with private or duplicate content), just use an appropriate rule in the robots.txt file. For more information on such rules, check out http://www.robotstxt.org/robotstxt.html.

Please note that commands placed in the robots.txt file are more like suggestions rather than absolute rules for robots to follow. There's no guarantee that some robot will not check the content that you have disallowed.

.xml sitemap (Yes)

Well done! An .xml sitemap is present on your website. Remember to resubmit it to search engines each time you make changes to it.

About this SEO Factor:

An XML sitemap should contain all of the website pages that you want to be indexed, and should be located on the website one directory structure away from the homepage (ex. http://www.site.com/sitemap.xml). In general, it serves to aid indexing. You should update it each time you add new pages to your website. Besides, the sitemap should follow particular syntax.

The sitemap allows you to set the priority of each page, telling search engines which pages they are supposed to crawl more often (i.e. they are more frequently updated). Learn how to create an .xml sitemap at http://www.sitemaps.org/.

Resources restricted from indexing (1,389 resources)

Some of your site's resources are restricted from indexing. It is recommended to re-check the robots.txt file, and make sure that all your useful content gets indexed and is not blocked by mistake.

HTTP status code
200
Successful
Robots' instructions
Disallowed
Noindex meta tag
HTTP status code
200
Successful
Robots' instructions
Disallowed
Noindex meta tag
HTTP status code
200
Successful
Robots' instructions
Disallowed
Noindex meta tag
HTTP status code
200
Successful
Robots' instructions
Disallowed
Noindex meta tag
HTTP status code
200
Successful
Robots' instructions
Disallowed
Noindex meta tag
HTTP status code
200
Successful
Robots' instructions
Disallowed
Noindex meta tag
HTTP status code
200
Successful
Robots' instructions
Disallowed
Noindex meta tag
HTTP status code
200
Successful
Robots' instructions
Disallowed
Noindex meta tag
HTTP status code
200
Successful
Robots' instructions
Disallowed
X-Robots tag
HTTP status code
200
Successful
Robots' instructions
Disallowed
X-Robots tag
HTTP status code
200
Successful
Robots' instructions
Disallowed
X-Robots tag
HTTP status code
200
Successful
Robots' instructions
Disallowed
X-Robots tag
HTTP status code
200
Successful
Robots' instructions
Disallowed
X-Robots tag
HTTP status code
200
Successful
Robots' instructions
Disallowed
X-Robots tag
HTTP status code
200
Successful
Robots' instructions
Disallowed
X-Robots tag
HTTP status code
200
Successful
Robots' instructions
Disallowed
X-Robots tag
HTTP status code
200
Successful
Robots' instructions
Disallowed
X-Robots tag
HTTP status code
200
Successful
Robots' instructions
Disallowed
X-Robots tag
HTTP status code
200
Successful
Robots' instructions
Disallowed
X-Robots tag
HTTP status code
200
Successful
Robots' instructions
Disallowed
X-Robots tag
HTTP status code
200
Successful
Robots' instructions
Disallowed
X-Robots tag
HTTP status code
200
Successful
Robots' instructions
Disallowed
X-Robots tag
HTTP status code
200
Successful
Robots' instructions
Disallowed
X-Robots tag
HTTP status code
200
Successful
Robots' instructions
Disallowed
X-Robots tag
HTTP status code
200
Successful
Robots' instructions
Disallowed
X-Robots tag
HTTP status code
200
Successful
Robots' instructions
Disallowed
X-Robots tag
HTTP status code
200
Successful
Robots' instructions
Disallowed
X-Robots tag
HTTP status code
200
Successful
Robots' instructions
Disallowed
X-Robots tag
HTTP status code
200
Successful
Robots' instructions
Disallowed
X-Robots tag
HTTP status code
200
Successful
Robots' instructions
Disallowed
X-Robots tag
HTTP status code
200
Successful
Robots' instructions
Disallowed
X-Robots tag
Resource URL