INW Basecamp had been operating in the Pacific Northwest for years with a proven business model: premium outdoor recreation and corporate retreat facilities built around a basecamp concept. When the decision was made to expand into Arizona, the challenge was clear — they needed a complete digital presence for a new market, with no existing brand recognition, no local search history, and no organic footprint. The goal was day-one visibility. Here's how we built it.
The Challenge: A New Market With No Digital Footprint
What Starting From Zero Looks Like
Entering a new geographic market as a local business means starting from zero on every signal Google uses to evaluate local relevance. No indexed pages for the new location. No Google Business Profile for the Arizona address. No local citations in Arizona directories. No customer reviews mentioning the new location. No backlinks from Arizona-specific sources. From Google's perspective and from AI systems' perspective, the Arizona location of INW Basecamp simply didn't exist.
The Pacific Northwest presence was an asset — it provided domain authority, an existing entity in Google's knowledge graph, and established brand signals that would transfer to the new location over time. But it wasn't a substitute for location-specific establishment. A business that is well-known in Spokane is not automatically findable in Scottsdale. Each market requires its own entity signals, its own local content, and its own structured data.
Why Same-Day Execution Was Business-Critical
The Arizona launch had a hard date driven by an event booking. An anchor corporate retreat client had committed to the new location for an event six weeks out. The marketing window was six weeks — not three months of gradual SEO buildup. We needed the Arizona landing page indexed, the Facebook pixel collecting data, and the first ad campaigns active within 24 hours of receiving the brief. Anything slower than that left money on the table during the critical early booking period.
Building the Landing Page for Machine Readability
Structure First, Content Second
Our first decision was structural: what is the minimum viable page architecture that allows Google to understand the Arizona location as a distinct, real-world entity? The answer was a single dedicated landing page with a clear URL structure (/locations/arizona), a unique title and heading hierarchy explicitly naming the location, content specifically addressing the Arizona market's use case, and all four schema types implemented before the first line of body copy was written.
This sequence — structure and schema before content — is the inverse of how most landing pages are built. Most teams write the marketing copy first and add schema as an afterthought. We treat schema as the architecture that content populates. The schema defines what the page is and who it's for. The content provides the human-readable evidence. Both are necessary. Schema without compelling content fails to convert humans. Content without schema fails to be found by machines.
Schema Decisions Before the First Line of Code
Before writing any HTML, we mapped the complete schema architecture for the Arizona page. LocalBusiness schema with the Arizona physical address, phone number, and a new GBP link once it was verified. Service schema for the two primary offerings in the Arizona market: corporate retreat facilitation and guided outdoor excursion packages. FAQPage schema with six questions drawn directly from the sales calls INW Basecamp had already received from interested Arizona clients. BreadcrumbList schema positioning the page correctly within the existing site hierarchy.
The Schema Implementation
LocalBusiness Schema for a New Location Entity
The LocalBusiness schema for the Arizona location was implemented as a distinct entity from the Pacific Northwest locations — a separate JSON-LD object with the Arizona address, the Arizona phone number, and the Arizona service area explicitly defined. We used the TouristAttraction and SportsActivityLocation subtypes as supplemental types alongside LocalBusiness to signal the recreational nature of the facility to AI systems that use entity type for query matching.
The sameas property pointed to the new Arizona Google Business Profile URL — added within the same day as the landing page launch. This cross-reference, even on day one, signals to Google that the website entity and the GBP entity are the same real-world location. It accelerates entity recognition significantly compared to leaving the two data points unlinked.
FAQPage and Service Schema for Day-One Discoverability
The six FAQPage questions were drawn from actual client inquiries: “Does INW Basecamp offer corporate team-building retreats in Arizona?” “What outdoor activities are available at the Arizona location?” “How many people can the Arizona facility accommodate?” Each answer was written as a complete, standalone response — specific enough to be useful to AI systems, factual enough to be citable. These questions were placed in both the page content as visible Q&A blocks and in the FAQPage schema, ensuring consistency between what users see and what machines read.
Facebook Campaign Architecture
Cold Audience Strategy for an Unknown Brand in a New Market
The Facebook campaign launched the same day as the landing page, targeting a cold audience in the Phoenix and Scottsdale metro area. Audience parameters: business decision-makers aged 30 to 55, interests in corporate events, team building, and outdoor recreation, household income in the top quartile for the market. Creative: a 45-second video showcasing the Pacific Northwest facility with Arizona market-specific copy overlaid — the visual proof of concept that the brand's established quality would extend to the new location.
The goal of this initial campaign was not direct booking. It was pixel data accumulation and first-impression establishment. Every person who watched 50%+ of the video became a retargeting audience member. Every website visitor from the ad was pixeled. The conversion efficiency in weeks 5 and 6 of the campaign — when the anchor event's booking deadline created urgency — was dramatically higher because we had six weeks of warm audience data to retarget.
Lead Gen vs Direct Booking Decision
For a corporate retreat product at INW Basecamp's price point, direct booking CTAs — “Book Now” buttons — are the wrong call for cold audiences. The decision cycle for corporate retreat bookings involves multiple stakeholders, budget approval, and logistical review. Asking a cold prospect to book immediately produces almost no conversions and tells Facebook's algorithm the ads aren't working. We used lead generation forms instead — “Request Information” with a low-friction three-field form — which produced qualified leads at a cost the sales team could efficiently convert through the consultative process the product requires.
Same-Day Validation and Launch
Zero Schema Errors on the First Submission
The complete schema implementation — LocalBusiness, Service (two types), FAQPage, and BreadcrumbList — was validated in Google's Rich Results Test before the page went live. Zero errors. Zero warnings. This is the standard we hold every launch to, and it's achievable when schema is treated as architecture rather than an SEO afterthought. The page launched with every structured data signal in place, which meant Google could begin entity recognition from the first crawl rather than needing to revisit after schema errors were corrected.
What the First 72 Hours Showed
Within 24 hours, Google Search Console confirmed the Arizona landing page indexed. Within 48 hours, the FAQ rich results were appearing in Search Console's Enhancements report. Within 72 hours, branded searches for “INW Basecamp Arizona” were returning the landing page as the top result. The Facebook campaign had accumulated 847 video views and 23 landing page visits by hour 72 — a modest start, but the pixel data was building. By day 14, retargeting audiences were large enough to run conversion-focused campaigns. The new market had a digital presence, entity recognition, and an active ad pipeline — all from a single day of coordinated execution.