SPIOUNby 6S

Crawl, redirects and server

What SPIOUN sees when it fetches your pages itself: titles, descriptions, speed, redirects, images.

What this tab shows

Site health
SPIOUN fetched every page itself and checked what a crawler sees.
robots.txt
The robots.txt file of each site: what crawlers may and may not visit.
Every URL
Every page SPIOUN fetched, with what it found on it.

The numbers at the top

URLs crawled
Pages SPIOUN fetched.
Broken
Pages answering with an error or not at all.
Redirected
Addresses that forward somewhere else.
Median response
Typical time for a page to answer. Under a second is good.
Pages with errors
Pages with at least one error to fix.

Issues on this page

Address redirects

What
This address forwards to another one.
Why
Every visit takes a detour, and if the address is in your sitemap Google wastes time on it. Google stores the final address, not this one.
How
Point links and the sitemap at the final address. Redirects themselves are fine; stale addresses in the sitemap are not. Steps for your platform →

Page not found (404)

What
The page does not exist at this address.
Why
Visitors and Google hit a dead end. If the address is linked or in your sitemap, that is a broken link.
How
If the page moved, add a redirect from the old address to the new one. If it is gone for good, remove it from the sitemap and from your menus. Steps for your platform →

Server refuses the page (4xx)

What
The server refuses this page (4xx).
Why
Google cannot read it, so it cannot rank.
How
Check whether the page needs a login or is blocked. Pages for the public must open without one. Steps for your platform →

Server error (5xx)

What
The server failed to answer (5xx).
Why
Google treats repeated server errors as a sign the site is down and may drop the page.
How
Open the page in a browser. If it fails, contact your hosting or fix the error on the server; then ask Google to re-check it. Steps for your platform →

Page could not be fetched

What
SPIOUN could not reach the page at all.
Why
Usually the site was down, too slow, or blocked the request. Google would see the same.
How
Open the page in a browser. If it loads, run the crawl again. If not, check hosting and DNS. Steps for your platform →

Slow response

What
The page took more than 2.5 seconds to answer.
Why
Slow pages lose visitors and Google crawls them less.
How
Ask your hosting about caching or a faster plan; large images and heavy plugins are the usual causes. Steps for your platform →

Response time notice

What
The page took more than 1.2 seconds to answer.
Why
Not critical, but faster is better for visitors and for crawling.
How
Same as for slow pages: caching, image sizes, fewer plugins. Steps for your platform →

Words used here

Redirect
An address that forwards to another address. Normal after a page moves. A problem when sitemaps or links still point to the old address, because every visit takes a detour. Glossary
404 (not found)
The server's answer when a page does not exist at that address. Expected for deleted pages; a problem when the address is still linked or listed in your sitemap. Glossary
robots.txt
A small text file at the root of your site that tells crawlers which parts they may visit. One wrong line (Disallow: /) can hide the whole site from Google. Glossary