Every vacation rental site competes for the same booking dollar. But before you can optimize for AI citations or conversion, the site has to actually exist on the internet in a way that search engines, AI crawlers, and — critically — potential guests can reach it. Cabin-Rentals.us fails at this most fundamental threshold. Across every diagnostic tool available, the site is unreachable, unindexed, and invisible.
This 5-layer AEO/GEO audit applies the same scoring framework used across Stay Citable client programs: Technical Foundation, Content Structure, Entity Optimization, AI Visibility, and Competitive Position. The difference here is that nearly every score lands at zero — not because of subtle content gaps or schema omissions, but because the site itself cannot be accessed by any automated tool, search crawler, or AI engine.
Audit Methodology
The audit was conducted on June 28, 2026 using the following diagnostic chain:
- DNS resolution and origin tracing (dig, nslookup)
- HTTPS and HTTP connectivity tests across multiple User-Agent profiles (curl, Python requests with full browser headers, custom TLS adapters)
- Cloudflare Pages origin direct access attempt
- Google, Bing, and DuckDuckGo indexed-page enumeration (site: operator)
- Wayback Machine archive check
- Google cache retrieval attempt
- Subdomain enumeration (www, blog, app)
- Netlify and Vercel deployment footprint check
Every test returned the same result: the site is behind Cloudflare with a broken origin connection, and zero pages exist in any public index.
Technical Diagnostics: What We Found
DNS: The domain cabin-rentals.us resolves to Cloudflare IPs (172.66.44.195, 172.66.47.61) with a CNAME record pointing to cabin-rentals-us.pages.dev. DNS itself is functional — the problem is upstream.
HTTPS (port 443): All HTTPS connections fail with SSL handshake failure (sslv3 alert handshake failure). This is not a certificate expiry issue — it is Cloudflare’s edge refusing the TLS handshake, likely due to Bot Fight Mode or an “I’m Under Attack” security level that blocks all non-browser TLS fingerprints.
HTTP (port 80): HTTP connections return Cloudflare error code 1001: “DNS resolution error.” In Cloudflare’s taxonomy, error 1001 means the edge proxy cannot resolve the origin server’s hostname. The pages.dev origin exists but is not responding to proxied requests.
Direct origin access: Connecting directly to cabin-rentals-us.pages.dev returns HTTP 403 Forbidden from Cloudflare. The Pages deployment either has access controls enabled or is not configured to serve content.
Search engine indexes: Zero pages from cabin-rentals.us appear in Google, Bing, or DuckDuckGo indexes as of June 28, 2026. The site:cabin-rentals.us operator returns empty on all three engines.
Internet Archive: The Wayback Machine has no snapshots of cabin-rentals.us. The domain has historical records from 2003-2009 under previous ownership, but the current vacation rental incarnation has zero captures.
Google cache: No cached version available.
Deployment footprint: No Netlify or Vercel deployments detected. The only infrastructure signal is the Cloudflare Pages origin, which returns 403.
Layer 1: Technical Foundation — Score: 0/100
A site that cannot be reached scores zero on technical foundation by definition. The specific failures:
| Check | Result | Impact |
|---|---|---|
| HTTPS accessibility | SSL handshake failure | 100% of secure traffic blocked |
| HTTP accessibility | Error 1001 (origin unreachable) | 100% of HTTP traffic blocked |
| Origin server | 403 Forbidden | Pages deployment inaccessible |
| Search engine indexability | Zero indexed pages | Invisible to all crawlers |
| Wayback Machine presence | Zero captures | No archival record |
| Robots.txt | Unreachable | Cannot verify directives |
| Sitemap.xml | Unreachable | Cannot verify structure |
| Mobile responsiveness | Unverifiable | Cannot test |
| Page speed / Core Web Vitals | Unverifiable | Cannot measure |
| Security headers | Unverifiable | Cannot audit |
Root cause: Cloudflare is configured to proxy traffic to an origin (cabin-rentals-us.pages.dev) that is either not deployed, has restrictive access controls, or is misconfigured. Error 1001 specifically means Cloudflare’s edge cannot resolve the origin hostname — this is a DNS or origin-configuration failure inside the Cloudflare dashboard, not an external attack or temporary outage.
Layer 2: Content Structure — Score: 0/100
Without access to the site, content structure cannot be evaluated. Everything that would be scored — information architecture, heading hierarchy, answer-lead format, FAQ sections, internal linking topology, content freshness signals — is trapped behind an unreachable origin.
The vacancy here is total. Even if the site has excellent content behind Cloudflare’s wall, that content has zero discoverable footprint. No page titles appear in search snippets. No heading structure is parseable. No URL hierarchy is crawlable.
Layer 3: Entity Optimization — Score: 0/100
Entity optimization — the Schema.org structured data layer that tells AI engines what the organization is, what it offers, where it operates, and how it connects to the broader knowledge graph — requires the site to serve HTML with JSON-LD blocks. Cabin-Rentals.us serves nothing.
We cannot verify whether the site has:
- Organization or LocalBusiness schema with proper @id, name, url, sameAs, and knowsAbout
- WebSite schema with SearchAction or SitelinksSearchBox
- LodgingBusiness or similar property-type schema on listing pages
- FAQPage markup on any informational pages
- BreadcrumbList for crawl-path signals
- AggregateRating or Review markup for trust signals
- GeoCoordinates or address markup for local entity signals
In the vacation rental vertical, entity optimization is the single highest-leverage AEO tactic. OTAs like Airbnb and Vrbo dominate AI citations through domain authority alone. Independent property managers compete by building structured entity signals that distinguish professionally-managed inventory from peer-to-peer listings. None of that work can begin if search engines and AI crawlers cannot reach the site.
Layer 4: AI Visibility — Score: 0/100
AI visibility is measured by whether the site’s content can be retrieved and cited by ChatGPT, Perplexity, Gemini, Claude, Grok, Copilot, and other AI engines. The prerequisites are:
- The site must be crawlable by search engine bots (Googlebot, Bingbot, etc.)
- The site must be indexed in search engine databases that AI engines query
- The site must serve content with clear entity signals, answer-lead structure, and citable claims
- The site should provide an llms.txt file for direct AI crawler consumption
Cabin-Rentals.us fails at prerequisite 1. Without crawlability, there is no indexation. Without indexation, there is no AI retrieval. Without AI retrieval, there is no citation.
The site’s AI visibility is not low — it is nonexistent. Not a single AI engine can discover, read, or cite any page on cabin-rentals.us.
Layer 5: Competitive Position — Score: N/A
Competitive position analysis requires at minimum a functioning competitor site and a functioning target site. With cabin-rentals.us unreachable, no competitive benchmarking is possible on the target side.
For context, the vacation rental AEO landscape (documented in our PNW competitor analysis) shows that Vacasa, Evolve, AvantStay, Natural Retreats, and Airbnb all have live, crawlable sites with varying schema coverage. The gap between a functioning competitor and an unreachable site is not a competitive gap — it is a categorical difference between “in the game” and “not on the field.”
Revenue Impact: The Conversion Funnel That Doesn’t Exist
Every dollar of vacation rental revenue flows through a funnel:
Search/discovery -> Site visit -> Property browse -> Listing view -> Booking
Cabin-Rentals.us breaks at step 1. The funnel has no intake. The revenue impact of every subsequent optimization — better property photos, smoother booking UX, trust badges, social proof — is zero because no potential guest ever reaches the site.
The specific revenue blockers, in priority order:
- Origin unreachable (Cloudflare error 1001): The site does not load. Zero traffic. Zero bookings. This is not a conversion optimization problem — it is an existence problem.
- SSL failure: Even if the origin were fixed, the HTTPS handshake failure would block all secure traffic. Modern browsers default to HTTPS; an SSL failure is functionally identical to the site being down.
- Zero search presence: Even if the site loaded, it has no indexed pages. No one searching for “cabin rentals,” “vacation cabins,” or any location-specific variant will find it.
- Zero AI citation potential: Even if indexed, the site serves no structured data, no answer-lead content, and no entity signals — meaning even after crawlability is fixed, AI citation readiness requires a full content and schema build-out.
The One Fix That Unlocks Everything
Before any SEO optimization, before any content strategy, before any schema markup — fix the Cloudflare origin configuration.
Step-by-step:
- Log into the Cloudflare dashboard for cabin-rentals.us
- Navigate to DNS settings and verify the CNAME record for cabin-rentals-us.pages.dev is correct
- In Cloudflare Pages, verify the project is deployed and the custom domain is properly configured
- Check Pages access controls — if Cloudflare Access or Zero Trust is enabled, either disable it or add rules for search engine crawlers
- Verify the Pages deployment build succeeded — a failed build or missing deployment returns 403
- Temporarily lower Cloudflare security level from “I’m Under Attack” to “High” or “Medium” to allow search crawler access
- Test: curl -sL https://cabin-rentals.us/ should return HTTP 200 with HTML content
- Submit the site to Google Search Console and Bing Webmaster Tools
- Generate and submit a sitemap
- Verify indexation within 48-72 hours
Until step 7 returns HTTP 200 with real HTML, every other action in this report is blocked.
Post-Restoration Priority Roadmap
Assuming the origin issue is resolved and the site becomes accessible, the following 90-day roadmap addresses the full AEO/GEO stack:
Days 1-7: Crawlability & Indexation
- Submit sitemap.xml to Google Search Console and Bing Webmaster Tools
- Verify robots.txt allows crawling
- Fix any 301/308 redirect chains
- Set up Google Search Console monitoring
- Submit to Bing IndexNow API
Days 8-14: Schema Foundation
- Implement Organization or LocalBusiness JSON-LD with @id, name, url, description, sameAs
- Add WebSite schema with SearchAction
- Add BreadcrumbList to all pages
- If the site lists properties, add LodgingBusiness or Product schema per listing with price, location, amenities, and availability signals
Days 15-30: Content Structure
- Audit existing page content for answer-lead format (first paragraph directly answers a search question)
- Add FAQPage schema with 5-8 questions per high-value page (homepage, top destination pages, booking/FAQ page)
- Create an llms.txt and llms-full.txt file describing the site’s structure and content for AI crawlers
- Implement location-specific landing pages with GeoCoordinates schema
Days 31-60: AI Citation Readiness
- Publish 4-6 blog posts targeting high-intent vacation rental queries with answer-lead openings, named statistics, inline citations, and FAQ sections
- Add HowTo schema for any booking-process or travel-planning content
- Implement Review and AggregateRating schema with real guest review data
- Cross-link property listings to destination guides and vice versa for topical authority
Days 61-90: Measurement & Iteration
- Run a Day 0 baseline across 50-100 target prompts on ChatGPT, Perplexity, Gemini, Claude, Grok, and Copilot
- Track citation rate, citation position, and share of voice vs. OTAs
- Re-test at Day 90 and measure citation lift
- Iterate content and schema based on which pages are getting cited and which are not
Scoring Summary
| Layer | Score | Weight | Weighted Score |
|---|---|---|---|
| Technical Foundation | 0/100 | 20% | 0.0 |
| Content Structure | 0/100 | 20% | 0.0 |
| Entity Optimization | 0/100 | 25% | 0.0 |
| AI Visibility | 0/100 | 25% | 0.0 |
| Competitive Position | N/A | 10% | N/A |
| Overall | 0/100 | 0.0 |
This is the lowest possible score — and it is accurate. The site is not “doing poorly” at AEO/GEO. It is not participating. Every point in the scoring framework assumes the site can be reached. Until step 7 in the fix list above returns HTTP 200, the score cannot rise above zero.
FAQ
Is the site permanently down? No evidence suggests the domain is abandoned. DNS resolves correctly, Cloudflare Pages is configured, and the domain is registered. The failure is in the Cloudflare-to-origin connection — a configuration issue, not a domain expiration or hosting cancellation. This is fixable in under an hour by someone with Cloudflare dashboard access.
Could the site be blocking bots intentionally? Possibly, but error 1001 is not a bot-blocking response. Cloudflare’s deliberate bot-blocking returns 403 with a challenge page, not 1001. Error 1001 specifically means the origin server cannot be resolved — this is an infrastructure failure, not a policy decision.
What is the revenue cost of this outage? If the site was previously generating bookings, every day offline is lost revenue. For a vacation rental site with even modest traffic (1,000 visitors/month) and a 2% booking conversion rate at $200 average booking value, a month offline costs approximately $4,000 in direct booking revenue plus the compounding loss of search rankings, backlinks, and brand trust. The actual cost depends on prior traffic and booking volume, which we cannot verify.
How does this compare to the average vacation rental site? Vacation rental sites that are live and indexed typically score 35-55 on this framework (our PNW competitor analysis showed schema gaps, FAQPage absence, and entity authority underinvestment across all five competitors). A live site with basic crawlability starts at roughly 20-25 points just from having accessible pages. Cabin-Rentals.us at 0/100 is an outlier — not representative of the vertical, but a cautionary case study in infrastructure neglect.
What should the owner do first? Log into Cloudflare. Check the Pages deployment. Fix the origin connection. Everything else waits.
Sources
- Cloudflare error code documentation: Error 1001 — DNS resolution error
- Direct diagnostic testing: curl, Python requests, dig, nslookup on June 28, 2026
- Search engine index verification: Google, Bing, DuckDuckGo site: operator queries
- Internet Archive: Wayback Machine CDX API query for cabin-rentals.us
- Stay Citable 5-layer AEO/GEO audit methodology (applied to staycitable.com, June 2026)
- Stay Citable PNW vacation rental AEO competitor analysis (June 2026): Vacasa, Evolve, AvantStay, Natural Retreats, Airbnb schema and content audit
Get your free citation audit. Every site has an AEO/GEO baseline — even sites that are currently invisible. We audit 50-100 prompts across ChatGPT, Perplexity, Gemini, Claude, Grok, and Copilot, measure exactly where you stand, and deliver a prioritized 60-90 day roadmap in 5 business days. See what a free citation audit delivers and get your free audit.