2 of 20

Expedia.com Sitemap

Expedia is one of the longest-standing digital travel planning and booking platforms, used by millions of travelers worldwide every day. Over the years, the Expedia Group has acquired multiple travel brands, consolidating services under a single, unified product interface. Their One Key rewards program, which integrates loyalty systems across all Expedia-owned ventures, plays a key role in driving customer retention and expanding audience reach.

Link to FigJam: https://www.figma.com/board/NGXrvlvEQrPpQhpeymjNFD/Expedia-Sitemap?node-id=0-1&t=N12XEMhrLuPdpGVN-1

3 of 20

Expedia.com Sitemap Part 1

4 of 20

Expedia.com Sitemap Part 2

5 of 20

Expedia.com Sitemap Part 3

6 of 20

Expedia.com Sitemap Footer

7 of 20

Expedia.com Sitemap Reflections

The hierarchy of Expedia’s page flow—starting with Stays and ending with Cruises—offers insight into both customer behavior and Expedia’s brand positioning. Stays (hotels, rentals, etc.), Expedia’s original offering since 1999, appears first, showing that users most strongly associate the platform with lodging options.
Following Stays, the site flows through Flights and Cars, then introduces Packages, bundling these services to craft a more convenient, cost-saving experience for users. This encourages customers to book multiple services together rather than separately or directly through providers.
Further down the hierarchy, Things to Do and Cruises appear last, likely because these categories sit within a more saturated travel advising market (e.g., Tripadvisor, social media) and users often prefer to book cruises directly with providers.
When exploring individual travel offering pages, the hierarchy remains consistent: deals and low-cost options appear first, followed by trending and featured destinations, then filtered travel types (by region, family-friendly, international, etc.), and finally, offerings unique to that category.
Across the site, the UI and page structure stay uniform, with only minor differences in search filters or promotional elements, supporting a predictable and efficient user experience.

8 of 20

Inn Route Information Architecture

Introducing Inn Route, a travel platform where “Inn-dependent” motels, boutique hotels, and campsites/RV parks come together to maintain their unique brand and identity while offering standardized perks for rewards-collecting guests. Travelers can choose individual stays or opt for a Route—tailored, themed road trip itineraries with pre-set lodgings, much like a resort package or time-share, but with the charm of independent properties. Instead of staying at big box chain hotels, guests can explore our historic, locally owned locations and earn points along the way, making each trip both rewarding and memorable.

Link to FigJam: https://www.figma.com/board/KgkSWv0plQwNHZhTYGfBjF/Inn-Route-IA?node-id=0-1&t=7uyfAdQ2gkMwP9DV-1

9 of 20

Inn Route Information Architecture Part 1

10 of 20

Inn Route Information Architecture Part 2

11 of 20

Inn Route Information Architecture Part 3

12 of 20

Inn Route Information Architecture Part 4

13 of 20

Inn Route Information Architecture Footer

14 of 20

Inn Route Information Architecture Reflections

With the growing popularity of remodeled motels, boutique hotels, and upscale campsites/RV parks—especially among Millennial and Gen Z travelers—independent properties often rely on third-party platforms like Expedia, sacrificing a portion of their sales.
Inn Route responds to this trend by creating an ecosystem where independent properties can market their offerings, follow booking standards, and participate in a unified rewards program, giving travelers an alternative to chain hotels.
A unique element of Inn Route’s information architecture is its “Routes” feature—curated, themed road trip itineraries where users can book multiple stays under one experience-driven flow.
While properties maintain their individual branding and imagery, Inn Route implements platform-wide UI standards and booking guidelines to ensure consistency across navigation, booking flows, and global elements like the site footer, while still highlighting each property’s unique identity.

15 of 20

“Inn Route” User Flow: Searching and Booking a Boutique Hotel

Link to FigJam: https://www.figma.com/board/cns8GFhRaeS6X4gimIb6nk/Inn-Route-User-Flow?node-id=0-1&t=lZXYvdKcQag0ND4b-1

16 of 20

Inn Route User Flow Part 1

17 of 20

Inn Route User Flow Part 2

18 of 20

Inn Route User Flow Part 3

19 of 20

Inn Route User Flow Reflections

Mobile apps often break up the purchase process into smaller, sequential screens, while websites typically offer a more seamless, consolidated checkout flow. This helps reduce friction and gives users more confidence when making a purchase on desktop, where they can view more information at once.
Since users tend to stay logged in longer on mobile apps, the sign-in step can be condensed or bypassed entirely. Users can open the app and immediately select their desired travel category, streamlining the entry point and reducing barriers to engagement.
The “Get INN with Us” section, which focuses on property registration and informational content, is more suited for desktop users (likely property managers). On mobile, this section can either be hidden, moved to a menu or settings area, or made accessible via a secondary navigation option, rather than occupying primary screen space.
When browsing hotels on mobile, instead of loading a full new page for each selection (as seen on the website), the app will use a slide-up card or bubble overlay that displays key property details and photos. This allows users to quickly preview options, swipe back to the main list, or tap for more in-depth information, keeping the flow lightweight and mobile-friendly.

20 of 20

Overall Reflection

While Expedia’s sitemap heavily influenced the information architecture (IA) of my travel platform, Inn Route, I wanted the rewards system to function more like loyalty programs from Marriott Bonvoy or IHG Hotels, offering guests points-based incentives tied to their stays. If I were to expand this project, I would analyze the sitemaps and IA of these hotel loyalty platforms to better understand how they structure user flows, reward tracking, and account management.

Additionally, I would dive deeper into the property registration and management side of the platform, since the needs of property owners and backend users would likely require a separate and distinct IA, focused on property onboarding, marketing tools, and inventory management.