Page unreachable

What it is

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.

Why it matters

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.

How to fix it

1. Identify exactly why the page is unreachable: use Google Search Console's URL Inspection tool to check whether the URL is indexed, blocked, or returning an error. Note the specific reason (e.g., 404 Not Found, 500 Server Error, blocked by robots.txt, redirect loop, login wall).
2. Fix the root cause for that specific reason: restore deleted pages (or set up proper 301 redirects to relevant live pages), correct server errors with your hosting or development team, remove blocking rules from robots.txt if the page should be public, and eliminate redirect chains or loops.
3. Verify the page is publicly accessible without requiring a login or JavaScript execution that a bot cannot complete — crawlers cannot log in or interact with JS-gated content the same way a browser does.
4. Submit the corrected URL for re-indexing in Google Search Console (URL Inspection → Request Indexing) and, where available, Bing Webmaster Tools.
5. Once the page is confirmed reachable and indexed, add appropriate structured data (JSON-LD schema markup) to the page — Product schema for product pages, FAQPage schema for FAQ pages, BreadcrumbList for navigation context — so AI and search systems can understand and cite the content.
6. Re-test the page using Google's Rich Results Test to confirm the page loads correctly and any structured data is valid and error-free.

<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>

Fix it on your platform

Pick your platform for the exact steps.

Frequently asked questions

Authoritative references

• Intro to structured data — Google Search Central
• Product structured data — Google Search Central
• FAQ structured data — Google Search Central
• Breadcrumb structured data — Google Search Central
• Getting started with schema.org — Schema.org
• Rich Results Test — Google Search Central