Skip to content

Site overview

The domain, HTTPS, redirects, robots.txt and the sitemap.

The domain is missing from Webflow custom domains

Section titled “The domain is missing from Webflow custom domains”

site.domain.not_in_webflow_domains · Review signal (Needs review) · Severity: Info

Why it matters. Review project/site association. A different selected domain alone is not a mismatch; custom aliases may be intentional.

How to fix. Review the captured evidence and its measurement scope, then verify the intended behavior.

site.http_to_https_redirect_missing · Issue · Severity: Medium

Why it matters. Without a clean HTTPS redirect, visitors and search engines may reach an insecure or inconsistent version of the site.

How to fix. Configure a reliable redirect from HTTP to the HTTPS version of the selected domain.

site.http.unreachable · Issue · Severity: Low

Why it matters. A failed HTTP check can hide redirect problems and may leave visitors with an inconsistent or unavailable entry point.

How to fix. Confirm whether the HTTP host should redirect to the HTTPS production URL and test the expected behavior.

The selected domain is not reachable over HTTPS

Section titled “The selected domain is not reachable over HTTPS”

site.https.unreachable · Issue · Severity: Critical

Why it matters. If the primary HTTPS entry point is unavailable, visitors cannot reliably reach the site and dependent audit results become less trustworthy.

How to fix. Check DNS, SSL, publishing status and the domain configuration, then verify the HTTPS production URL.

The primary domain uses multiple redirects

Section titled “The primary domain uses multiple redirects”

site.redirect.chain · Issue · Severity: Low

Why it matters. Extra redirect hops slow the first visit, complicate troubleshooting and can dilute the clarity of the preferred URL.

How to fix. Remove unnecessary redirect hops and update internal links, canonical URLs and sitemap entries to the final destination.

site.redirect.loop · Issue · Severity: Critical

Why it matters. A redirect loop prevents visitors and crawlers from reaching the site and can block every dependent audit module.

How to fix. Fix the domain or page redirect configuration so the request reaches one final URL without cycling.

site.robots.blocks_all · Issue · Severity: Critical

Why it matters. A site-wide robots block can prevent search engines from crawling and indexing the published site.

How to fix. Remove the full-site disallow rule unless the target is intentionally non-indexable staging.

site.robots.missing · Issue · Severity: Low

Why it matters. Without a reliable robots.txt response, crawl instructions are unclear and a misconfiguration can go unnoticed.

How to fix. Confirm whether the production site should publish a robots.txt file and include the intended crawl guidance.

The sitemap response is not valid sitemap XML

Section titled “The sitemap response is not valid sitemap XML”

site.sitemap.invalid · Issue · Severity: Medium

Why it matters. An invalid sitemap can prevent search engines from discovering published URLs and can hide indexing coverage problems.

How to fix. Correct the sitemap output and the site’s SEO settings, then validate the published sitemap.

site.sitemap.lastmod_review · Review signal (Needs review) · Severity: Set per finding

Why it matters. A lastmod value can help crawlers prioritize updated URLs, but an absent or inaccurate value should not be treated as reliable freshness evidence.

How to fix. Review the sitemap entries and confirm that lastmod values are present where useful and reflect significant, verifiable page updates.

site.sitemap.missing · Issue · Severity: Medium

Why it matters. A missing sitemap can make URL discovery less reliable, especially for large or frequently changing sites.

How to fix. Enable or publish a valid sitemap and confirm that it represents the intended public URLs.

site.sitemap.url_scope_review · Review signal (Needs review) · Severity: Set per finding

Why it matters. A different host can be intentional for a sitemap index or alternate deployment, but it can also cause the sitemap to describe a different public URL scope than the audit target.

How to fix. Confirm whether the different sitemap hosts are intentional and align sitemap URLs with the preferred public domain where appropriate.

site.www_non_www.canonical_mismatch · Review signal (Needs review) · Severity: Info

Why it matters. Review the two captured canonical declarations. Unsampled host variants are unavailable, not known consistent.

How to fix. Review the captured evidence and its measurement scope, then verify the intended behavior.