All 128 checks

These pages answered with a 5xx status code (the code a server sends when it fails to build a page, such as 500 Internal Server Error).

These addresses answered with a 4xx status code (the code a server sends when a page is missing or gone, such as 404 Not Found).

These pages answered with a status code (the server's three-digit reply) of 401 (login needed), 403 (access forbidden) or 429 (too many requests).

Raptor followed the redirects (rules that forward one address to another) from these addresses and came back to an address it had already passed through.

Raptor requested these pages and got nothing back, not even a status code (the three-digit reply a server sends with every page).

Each of these addresses forwards to another address that forwards again: two or more redirects (rules that send one address to another) before the final answer.

Each of these addresses forwards once to another address with a redirect (a rule, such as a 301 or 302, that sends visitors and search engines on).

These pages give robots rules (instructions for search engines) in both a meta tag and an X-Robots-Tag header, and together the two say both follow and nofollow (do not follow this page's links).

These pages carry a nofollow rule (a robots meta tag or X-Robots-Tag header telling search engines not to follow any link on the page).

These pages carry a nosnippet rule (a robots meta tag or X-Robots-Tag header asking search engines not to show a text preview under the page's link).

These pages carry a noimageindex rule (a robots meta tag or X-Robots-Tag header asking search engines not to list the page's images).

The site's robots.txt (its file of rules for crawlers) names one or more well-known AI crawlers and blocks them from the site's root address (/).

These pages carry a noai or noimageai rule (a robots meta tag or X-Robots-Tag header asking AI systems not to use the page's text or images).

These short pages load as if they were fine, but their title or text says something like 'page not found' or 'no longer available', which makes them soft 404s (error pages that report success).

Each page's canonical tag (the line in <head> that names the preferred address) points to a page that returns an error (a 4xx or 5xx status code) or is marked noindex (told search engines not to list it).

The HTML of these pages holds more than one canonical tag (the line naming a page's preferred address).

The canonical tag (the line naming a page's preferred address) on these pages gives a relative address, such as /page, instead of a full one that starts with https:// and the domain.

These pages give a canonical (the preferred address of a page) both in their HTML and in the HTTP Link header (a line the server sends along with the page).

These pages give no canonical tag (a line in <head>, or a server header, that names a page's preferred address).

The canonical tag on these pages (a line in <head>, or a server header, naming the preferred address) points to a different address.

The canonical tag (the line naming a page's preferred address) on these pages sits outside <head>, the top section of the page's code, and no server header gives one instead.

Following the canonical tags (lines naming a page's preferred address) from these pages through other crawled pages leads back to the start, and no page in the loop names itself.

The canonical tag (the line naming a page's preferred address) on these pages points to a crawled page whose own canonical tag points somewhere else again.

These pages give robots rules (instructions for search engines) in both a meta tag and an X-Robots-Tag header, and together the two say both index (list this page) and noindex (do not list it).

These pages carry a noindex rule (a robots meta tag or X-Robots-Tag header that tells search engines not to list the page).

These pages carry the none rule (a robots meta tag or X-Robots-Tag header that means noindex and nofollow together: do not list this page or follow its links).

These pages have hreflang tags (lines in <head> listing the page's versions in other languages), and at least one listed version that Raptor crawled does not list the page in return.

The hreflang tags (lines in <head> listing the page's versions in other languages) on these pages use a code that is not a valid language, or language and region, such as en-UK instead of en-GB.

The hreflang tags (lines in <head> listing the page's versions in other languages) on these pages point to a crawled page whose status code (the server's three-digit reply) is not 200 OK, such as a 404 error.

The hreflang tags (lines in <head> listing the page's versions in other languages) on these pages point to a crawled page that names a different address as its preferred one.

The hreflang tags (lines in <head> listing the page's versions in other languages) on these pages point to a crawled page marked noindex (told search engines not to list it).

The hreflang tags (lines in <head> listing the page's versions in other languages) on these pages use the same language code more than once.

In their hreflang tags (lines in <head> listing a page's versions in other languages), these pages label a crawled version with one language code while that version labels itself with another.

These pages have hreflang tags (lines in <head> listing the page's versions in other languages), but none of the tags names the page's own address.

These pages have hreflang tags (lines in <head> listing the page's versions in other languages), but no x-default entry (the version to show when no listed language matches).

These sitemaps (files listing a site's pages for search engines) are named in robots.txt (the site's crawling rules) or in another sitemap, but did not answer 200 OK, failed to load or held no sitemap.

These sitemap files (files that list a site's pages for search engines) could not be read as valid XML, the format sitemaps are written in.

These entries in a sitemap (the file that lists your pages for search engines) are not complete addresses starting with http:// or https:// and a domain, as the sitemap format requires.

Raptor found no sitemap (an XML file listing the pages you want search engines to find), either in robots.txt (the site's file of crawling rules) or at the usual addresses such as /sitemap.xml.

These sitemap files (files that list a site's pages for search engines) list no addresses at all.

These addresses are in a sitemap (the file that lists your pages for search engines), but the crawled page answered with an error (a 4xx or 5xx status code) or is marked noindex (told search engines not to list it).

These sitemap files (files that list a site's pages for search engines) each list more than 50,000 URLs, the most the sitemap format allows in one file.

These sitemap files (files that list a site's pages for search engines) each hold more than 50 MB of text, the most the sitemap format allows in one file.

These crawled pages are not in any sitemap (the file that lists your pages for search engines) Raptor read.

These addresses are listed in more than one sitemap file (a file that lists a site's pages for search engines).

The HTML the server sends for these pages has no canonical tag (the line in <head> naming the preferred address); one appears only after the page's JavaScript runs in a browser.

These pages use the same title (the headline shown in search results and browser tabs) as another crawled page.

These pages use the same meta description (the summary search engines may show under the title) as another crawled page.

The first H1 heading (the main heading at the top of a page) on these pages matches the first H1 of another crawled page.

These pages have an H2 heading (a section heading under the main one) with the same text as an H2 on another crawled page.

The text of these pages matches another crawled page word for word.

The path of these addresses (the part after the domain) holds a space, written as %20 or as a plain space.

These page addresses run past 115 characters, counting the whole address from https:// to the end.

The path of these addresses (the part after the domain) holds capital letters.

The path of these addresses (the part after the domain) holds underscores (_).

These addresses contain a query string (the part after a ?, such as ?page=2 or ?sort=price).

The path of these addresses (the part after the domain) holds two slashes in a row (//).

The path of these addresses (the part after the domain) holds characters beyond plain unaccented letters, digits and common symbols, such as é, ü or Japanese script.

The path of these addresses (the part after the domain) has the same part between slashes twice, such as /blog/blog/ or /shop/sale/shop/.

Raptor crawled these addresses with UTM tags in them (settings after the ? that start with utm_ and label where a visit came from in analytics).

These pages link to pages on this site that answer with an error status code (a 4xx or 5xx reply, such as 404 Not Found), counting where a link ends up after redirects.

These pages link to localhost, 127.0.0.1 or a similar loopback address, which points at the visitor's own computer rather than at your site.

No other crawled page links to these pages, counting links to old addresses that forward here and ignoring links a page makes to itself.

These pages have no links to other pages on the same site, so a visitor or a search engine that lands on one has nowhere further on the site to go.

These pages link to other pages on the site with no visible anchor text (the clickable words of a link), for example a link wrapped around an icon.

These pages have links to other pages on the site whose whole text is a generic phrase, such as 'read more', 'learn more', 'here' or 'more'.

These pages link to other pages on the same site with rel="nofollow" (a note asking search engines not to follow or give credit to that link).

These pages have a crawl depth (the number of links Raptor followed from the start page to reach them) of more than 4 clicks.

These pages hold more than 100 links to other websites, counting repeats.

These pages have no title (the headline shown in search results and browser tabs), or an empty one.

The code of these pages holds more than one <title> tag, which sets the headline shown in search results and browser tabs.

The first <title> tag on these pages, which sets the headline shown in search results, sits outside <head>, the top section of the page's code.

These page titles (the headline shown in search results and browser tabs) run past 60 characters.

These page titles (the headline shown in search results and browser tabs) are shorter than 30 characters.

These page titles (the headline shown in search results and browser tabs) are wider than 561 pixels in Raptor's estimate of how Google draws them.

These page titles (the headline shown in search results and browser tabs) are narrower than 200 pixels in Raptor's estimate of how Google draws them.

These pages have no meta description (the summary search engines may show under the title), or an empty one.

The code of these pages holds more than one meta description tag (the summary search engines may show under the title).

The meta description (the summary search engines may show under the title) on these pages sits outside <head>, the top section of the page's code.

These meta descriptions (the summary search engines may show under the title) run past 155 characters.

These meta descriptions (the summary search engines may show under the title) are shorter than 70 characters.

These meta descriptions (the summary search engines may show under the title) are wider than 985 pixels in Raptor's estimate of how Google draws them.

These pages have no H1 heading (the main heading at the top of a page) with any text in it.

These pages have more than one H1 heading (the main heading at the top of a page).

The first H1 heading (the main heading at the top of a page) on these pages is exactly the same as the page title.

These pages have an H1 heading (the main heading at the top of a page) longer than 70 characters.

These pages have no H2 heading (a section heading one level under the main heading).

These pages have an H2 heading (a section heading one level under the main heading) longer than 70 characters.

The headings on these pages skip a level, for example an H2 followed straight by an H4, or the first heading on the page is not an H1 (the main heading).

These pages have fewer than 100 words of visible text, counting menus and footers.

These pages score below 10 on the Flesch reading-ease scale (0 to 100, worked out from sentence and word length, where higher is easier).

These pages score below 30 on the Flesch reading-ease scale (0 to 100, worked out from sentence and word length, where higher is easier), but not low enough to count as very hard.

Some images on these pages have no alt attribute at all, so they carry no alt text (a short written description of the image).

Some images on these pages have alt text (a short written description of an image) longer than 100 characters.

Some images on these pages lack a width or height attribute in their HTML.

These pages hold a block of structured data (code that describes the page's content to search engines) written as JSON-LD that has a syntax error, so it cannot be read.

The structured data (code that describes the page's content to search engines) on these pages lacks a field Google requires for its type, such as a name for a Product or a start date for an Event.

Raptor found no structured data (code that describes the page's content to search engines) on these pages, in JSON-LD or microdata form.

The HTML the server sends for these pages has no title (the headline shown in search results and browser tabs); one appears only after the page's JavaScript runs in a browser.

The HTML the server sends for these pages has no meta description (the summary search engines may show under the title); one appears only after the page's JavaScript runs in a browser.

The HTML the server sends for these pages has no H1 heading (the main heading at the top of a page); one appears only after the page's JavaScript runs in a browser.

The HTML the server sends for these pages has no structured data (code that describes the page's content to search engines); it appears only after the page's JavaScript runs in a browser.

These pages were served from an http:// address, without HTTPS (the encrypted connection that shows a padlock in the browser).

These https:// pages load images, scripts, styles, frames or media from http:// addresses, which is called mixed content.

These pages hold a form whose action (the address it sends what visitors type to) starts with http://, so the data travels unencrypted.

These pages are served from an http:// address and hold a form whose action (the address it sends what visitors type to) also starts with http://.

These pages have links with target="_blank" (open in a new tab) and no rel="noopener" or rel="noreferrer", the setting that stops the new page reaching back to this one.

These https:// pages are served without a Strict-Transport-Security header (HSTS, a rule telling browsers to use only HTTPS for this site from then on).

These pages are served without a Content-Security-Policy header (a list of rules telling the browser which scripts and files the page may load).

These pages are served without the X-Content-Type-Options: nosniff header, which tells browsers to trust the file type the server declares instead of guessing.

These pages are served without an X-Frame-Options header (a rule telling browsers whether other sites may show the page inside a frame).

These pages send no Referrer-Policy header (a rule for how much of the page's address is passed to other sites), or set it to unsafe-url or no-referrer-when-downgrade.

In Google's PageSpeed Insights test (one lab load of each page), these pages took more than 4 seconds to show their largest image or text block, a measure called LCP (Largest Contentful Paint).

In Google's PageSpeed Insights test (one lab load of each page), these pages took more than 2.5 seconds to show their largest image or text block (LCP, Largest Contentful Paint), but not long enough to rate Poor.

Google's data from real Chrome visits shows these pages, or the whole site where a page has too few visits, taking more than 500 milliseconds to react to a tap, click or key press (INP, Interaction to Next Paint).

Google's data from real Chrome visits shows these pages, or the whole site where a page has too few visits, taking more than 200 milliseconds to react to a tap, click or key press (INP, Interaction to Next Paint).

In Google's PageSpeed Insights test (one lab load of each page), these pages scored more than 0.25 for CLS (Cumulative Layout Shift), a measure of how much the content moves while the page loads.

In Google's PageSpeed Insights test (one lab load of each page), these pages scored more than 0.1 for CLS (Cumulative Layout Shift, how much the content moves while loading), but not enough to rate Poor.

In Google's PageSpeed Insights test (one lab load of each page), these pages took more than 3 seconds to show their first text or image, a measure called FCP (First Contentful Paint).

In Google's PageSpeed Insights test, the server took more than 0.8 seconds to start sending each of these pages, a measure called TTFB (Time to First Byte).

These pages scored below 50 out of 100 in Google's PageSpeed Insights test, a lab load of each page that rates its loading speed.

These pages scored below 90 out of 100 in Google's PageSpeed Insights test, a lab load of each page that rates its loading speed, but not low enough to rate Poor.

When Raptor crawled these pages, the server took 1.5 seconds or more to start answering, counting any redirects on the way.

These pages load a script file in <head> without async, defer or type="module", so the browser stops drawing the page until the script has downloaded and run.

These pages load more than 20 scripts or 100 KB of inline script, counting both script files and code written straight into the page.

These pages load more than 10 scripts from servers other than the page's own, such as analytics, ads, chat and tag managers.

While Raptor rendered these pages in a browser, their JavaScript failed with an error the page did not handle, up to 5 errors per page.

While Raptor rendered these pages in a browser, their JavaScript failed with more than 5 errors that the page did not handle.