How to fix page unreachable on Webflow
Ensure every page that should appear in AI-powered answers and rich results is actually reachable by crawlers, then add structured data so search engines and AI systems can read and surface its content.
Steps for Webflow
- In the Webflow Designer, confirm the page is published: go to Pages panel → right-click the page → Page Settings → ensure it is not set to 'Exclude from search index' (noindex) and is published in the current project.
- Check Project Settings → SEO → confirm 'Disable Webflow subdomain indexing' or any global noindex setting is not accidentally applied to production.
- For broken CMS collection item URLs, check the CMS Collections panel — confirm the item is set to 'Published' (not 'Draft' or 'Archived') and the slug matches the expected URL.
- For redirects, go to Project Settings → Hosting → Redirects and add a 301 redirect from the broken path to the correct live URL.
- To add structured data, open the page in the Designer → Add an Embed element (from the Add panel → Components → Embed) → paste your JSON-LD <script> block directly. For CMS-driven pages, use dynamic binding inside the Embed element to pull in product name, price, etc. from Collection fields.
- Publish the site, then submit in Google Search Console and verify with the Rich Results Test.
<script type="application/ld+json">
{
"@context": "https://schema.org/",
"@type": "Product",
"name": "Your Product Name",
"description": "A clear description of the product.",
"offers": {
"@type": "Offer",
"priceCurrency": "USD",
"price": "29.99",
"availability": "https://schema.org/InStock",
"url": "https://www.yourstore.com/products/your-product"
}
}
</script>What is page unreachable?
When a page is "unreachable," it means search engine crawlers and AI answer engines cannot access it — the page either returns an error (like a 404 or 500), is blocked by robots.txt, requires a login, or has a technical redirect problem. In the context of Answer Engine Optimization (AEO), an unreachable page cannot be read, indexed, or cited by AI-powered search features (like Google's AI Overviews, Bing Copilot, or ChatGPT search). Even if a page exists on your site and looks fine to a visitor, a crawler hitting a wall means that page is invisible to the entire AI and search ecosystem.
AI answer engines and search crawlers can only surface content they can actually access and parse. If your product pages, FAQ pages, or category pages are unreachable, they will never appear in AI-generated answers, rich results, or organic search listings — meaning you lose traffic that your competitors will capture instead. A blocked or broken page also cannot benefit from any structured data (schema markup) you've added to it, since the data is never read. Over time, a pattern of unreachable pages can damage your site's overall crawl health and authority, dragging down rankings for every page — costing you real revenue. There may also be accessibility and legal implications if critical pages (such as returns policies or accessibility statements) are inaccessible.
See the complete Page unreachable guide for every platform and the full background.
Not sure if your Webflow store has this?
Run a free SEOLZ audit — we’ll find page unreachable and every other issue across your whole site.
Scan my site free