Site Architecture

Site Architecture is where you plan and structure your website’s pages. Choose from four site types (Local Business for multi-location service businesses, Service Agency for agencies, consultancies, and professional firms, SaaS for software products, or E-commerce for one-brand DTC stores and multi-brand retailers), and Floyi generates a complete URL blueprint with proper hierarchy. If your site is only a blog, you can skip this stage. The result is a clean, strategic site structure that helps search engines and AI systems understand exactly what you offer and where you offer it. Site Architecture is one of Floyi’s strategy flow tools: once your pages are mapped, plan supporting content with resource topic research and track everything in the Authority Planner.

Part 1: Choosing Your Site Type and Content Scope

Before building your site architecture, you need to select your site type and your content workflow. The site type determines which generator and page kinds are available, and the content workflow determines how Floyi guides you through the rest of the content creation process.

Site Types

Local Business — For service businesses that operate in specific geographic areas (plumbers, tree services, HVAC, dental practices, etc.). Uses the Local Site Generator to create service and location pages.

Service Agency — For agencies, consultancies, and professional firms (marketing agencies, IT companies, law firms, accounting practices, staffing firms, etc.). Uses the Service Agency Generator to create service, industry, and solution pages.

SaaS — For software products and platforms (project management tools, analytics platforms, CRMs, marketing automation, etc.). Uses the SaaS Generator to create feature, use case, integration, and solution pages.

E-commerce — For online stores selling products directly (DTC brands, multi-brand retailers, specialty retailers, etc.). Uses the E-commerce Generator to create category, brand and collection pages.

Content / Resources — For blogs and educational sites with no service or product pages. Choosing it skips Site Architecture and takes you to Topical Research.

Available Workflow Modes

1. Site + Resources (Recommended for most businesses)

Build your service pages (and location or industry pages) first
Then create educational blog and resource content
Full workflow: Site Architecture → Topical Research → Content Creation

2. Site Only

Create service and location/industry pages only
Skip blog or resource content entirely
Ideal for businesses focused purely on service pages
Leads directly to Topical Authority for tracking

3. Resources Only

Skip site architecture entirely
Jump directly to Topical Research for blog content
Best for brands focusing only on educational or thought leadership content

How to Select Your Scope

Navigate to the Site Architecture page from the sidebar.
Under What type of site are you building?, choose SaaS, E-commerce, Service Agency or Local Business. To skip this stage, choose Content / Resources under or skip architecture.
Under What are you building?, click a workflow card, such as Local Site + Resources, Local Site Only or Resources Only. Your choice saves as soon as you click it.

If pages already exist, changing the site type asks you to confirm, since pages that don’t apply to the new type may be removed. Switching to Resources Only with existing pages opens a Change workflow? dialog.

Part 2: The Local Site Generator

The Local Site Generator automatically creates your entire site structure from simple lists of services and locations.

Step 1: Enter Your Services

In the Services text area, enter your services one per line.

Basic Format:

Tree Trimming
Tree Removal
Stump Grinding

Hierarchical Format (Service > Subservice):

Tree Trimming > Crown Reduction
Tree Trimming > Deadwood Removal
Tree Removal > Emergency Removal
Tree Removal > Large Tree Removal

Maximum service depth is 2 levels (Service > Subservice).

Step 2: Enter Your Locations

In the Locations text area, enter your service areas one per line.

Choose Your Location Format:

State > City > Neighborhood: Use when operating across multiple states

Texas > Dallas > Uptown
Texas > Dallas > Oak Lawn
Texas > Houston > Montrose

City > Neighborhood: Use for single-state businesses
```
Dallas > Uptown
Dallas > Oak Lawn
Houston > Montrose
```

Click the format toggle buttons above the locations field to switch between formats.

Location Preview Panel:

As you type locations, a Preview shows how your first lines will be parsed:

Displays the detected State, City, and Neighborhood for each entry
Warns if a location has too many levels for your selected format
Helps you catch formatting issues before generating

Step 3: Configure URL Structure

Fine-tune how your URLs are structured:

Hub Folders:

Services Hub: Toggle on to group all services under /services/ (e.g., /services/tree-trimming/)
Locations Hub: Toggle on to group all locations under /locations/ (e.g., /locations/texas/)
You can customize the hub slugs (e.g., change “services” to “what-we-do”)

Service + Location Pages:

Toggle on to create combined pages like /locations/texas/dallas/tree-trimming/
These pages target searches like “tree trimming in Dallas, TX”

URL Style:

Path Style: Nested structure → /locations/texas/dallas/tree-trimming/
Combined Style: Flattened structure → /locations/texas-dallas-tree-trimming/

If your hierarchy exceeds 4 levels deep, the system automatically switches to Combined style.

Service + Location Page Estimate:

When you enable Service + Location pages, Floyi shows a calculation preview:

Example: 5 services × 10 locations = 50 service+location pages
This helps you understand the scale of pages before generating

Step 4: Generate Your Architecture

Replace Existing Option:

Before generating, you can toggle Replace existing pages:

Off (default): Use this for your first generation. If your architecture already has pages, generating with this off shows an error.
On: Clears your current architecture and rebuilds from scratch

Turn on Replace existing pages only when you want a complete rebuild. This removes all previously generated pages.

Generate:

Review your services and locations in the preview.
Toggle Replace existing pages if you want to start fresh.
Click Generate Structure.
The system creates all pages with proper parent-child relationships.
Review your complete site structure in the Preview panel.

Part 2B: The Service Agency Generator

The Service Agency Generator creates your site structure from lists of services, industries, and optional solutions. It is designed for agencies and professional firms that serve multiple industries.

Step 1: Enter Your Services

In the Services text area, enter your services one per line. The format is the same as the Local Site Generator.

Basic Format:

SEO
PPC Management
Web Design
Content Marketing

Hierarchical Format (Service > Subservice):

SEO > Technical SEO
SEO > Local SEO
PPC Management > Google Ads
PPC Management > Social Ads

Maximum service depth is 2 levels (Service > Subservice).

Step 2: Enter Your Industries

In the Industries text area, enter the industries your agency serves, one per line.

Healthcare
Financial Services
Real Estate
SaaS
E-commerce

Industries represent the verticals your agency targets. Each industry becomes its own page grouped under an Industries Hub.

Step 3: Enter Your Solutions (Optional)

In the Solutions / Use Cases (optional, one per line) text area, enter packaged solutions or use cases, one per line.

Lead Generation System
Brand Launch Package
Website Redesign Program
Marketing Audit

Solutions represent bundled offerings or outcomes. They are grouped under a Solutions Hub. This field is optional — skip it if your agency does not productize solutions.

Step 4: Cross-Product Pages (Service + Industry)

When you have both services and industries, Floyi can generate Service + Industry pages that target searches like “SEO for Healthcare” or “PPC Management for SaaS.”

These pages combine every service with every industry
Example: 4 services x 5 industries = 20 service+industry pages
Floyi shows a page estimate before generating so you can gauge the scale

Step 5: Configure URL Structure

Fine-tune how your agency URLs are structured:

Hub Folders:

Services Hub: Toggle on to group all services under /services/ (e.g., /services/seo/)
Industries Hub: Toggle on to group all industries under /industries/ (e.g., /industries/healthcare/)
Solutions Hub: Toggle on to group all solutions under /solutions/ (e.g., /solutions/lead-generation-system/)
You can customize the hub slugs (e.g., change “industries” to “who-we-serve”)

Service × Industry Pages:

Toggle on to create combined pages like /industries/healthcare/seo/
These pages target searches like “SEO for Healthcare”

Step 6: Generate Your Architecture

Review your services, industries, and solutions in the preview panel.
Toggle Replace existing pages if you want to start fresh.
Click Generate Structure.
The system creates all pages with proper parent-child relationships.
Switch to the Preview panel to see your complete site structure.

Example Agency Site Structure

For a digital marketing agency:

/                                          Home
/about/                                    About
/contact/                                  Contact
/services/                                 Services Hub
  /services/seo/                           Service
    /services/seo/technical-seo/           Subservice
  /services/ppc-management/                Service
  /services/content-marketing/             Service
/industries/                               Industries Hub
  /industries/healthcare/                  Industry
    /industries/healthcare/seo/            Service + Industry
    /industries/healthcare/ppc-management/ Service + Industry
  /industries/saas/                        Industry
    /industries/saas/seo/                  Service + Industry
/solutions/                                Solutions Hub
  /solutions/lead-generation-system/       Solution
  /solutions/brand-launch-package/         Solution

Part 2C: The SaaS Generator

The SaaS Generator creates your site structure from lists of features, use cases, integrations, and optional solutions. It is designed for software products and platforms that need to communicate capabilities, buyer-specific value, and ecosystem connectivity.

Step 1: Describe Your Product

In the Product field, describe what your software is, for example “project management software”. This descriptor is used throughout your architecture and in query strategy tokens for tracking.

Step 2: Enter Your Features

In the Features text area, enter your product features one per line.

Workflow Automation
Real-Time Analytics
Team Collaboration
Custom Dashboards
API Access

Each feature becomes its own page grouped under a Features Hub. Features represent the core capabilities of your product. You can enter up to 20 features.

Step 3: Enter Your Use Cases

In the Use Cases text area, enter the use cases or buyer personas your product serves, one per line.

Marketing Teams
Sales Teams
Product Managers
Customer Success
Engineering Teams

Use cases represent the audiences or scenarios your product addresses. Each use case becomes its own page grouped under a Use Cases Hub. You can enter up to 15 use cases.

Step 4: Enter Your Integrations (Optional)

In the Integrations text area, enter the tools and platforms your product integrates with, one per line.

Salesforce
HubSpot
Slack
Zapier
Google Analytics

Integrations represent your product’s ecosystem connectivity. They are grouped under an Integrations Hub. This field is optional — skip it if your product does not have integrations to highlight.

Step 5: Cross-Product Pages (Feature + Use Case)

When you have both features and use cases, Floyi can generate Feature + Use Case pages that target searches like “Workflow Automation for Marketing Teams” or “Real-Time Analytics for Sales Teams.”

These pages combine every feature with every use case, up to 100 pages
Example: 5 features x 5 use cases = 25 feature+use case pages
Floyi shows a page estimate before generating so you can gauge the scale

Step 6: Configure URL Structure

Fine-tune how your SaaS URLs are structured:

Hub Folders:

Features Hub: Toggle on to group all features under /features/ (e.g., /features/workflow-automation/)
Use Cases Hub: Toggle on to group all use cases under /use-cases/ (e.g., /use-cases/marketing-teams/)
Integrations Hub: Toggle on to group all integrations under /integrations/ (e.g., /integrations/salesforce/)
You can customize the hub slugs (e.g., change “features” to “capabilities” or “use-cases” to “who-its-for”)

Feature + Use Case Pages:

Toggle on to create combined pages like /use-cases/marketing-teams/workflow-automation/
These pages target searches like “Workflow Automation for Marketing Teams”

Step 7: Generate Your Architecture

Review your features, use cases, and integrations in the preview panel.
Toggle Replace existing pages if you want to start fresh.
Click Generate Structure.
The system creates all pages with proper parent-child relationships.
Switch to the Preview panel to see your complete site structure.

Example SaaS Site Structure

For a SaaS analytics platform:

/                                          Home
/about/                                    About
/contact/                                  Contact
/features/                                 Features Hub
  /features/workflow-automation/           Feature
  /features/real-time-analytics/           Feature
/use-cases/                                Use Cases Hub
  /use-cases/marketing-teams/              Use Case
  /use-cases/sales-teams/                  Use Case
    /use-cases/marketing-teams/workflow-automation/  Feature + Use Case
/integrations/                             Integrations Hub
  /integrations/salesforce/                Integration
  /integrations/hubspot/                   Integration
/solutions/                                Solutions Hub
  /solutions/enterprise-analytics/         Solution

Part 2D: The E-commerce Generator

The E-commerce Generator creates your site structure from lists of categories, brands and collections. It is designed for online stores, both one-brand DTC shops and multi-brand retailers.

Store Model

Choose your Store model before entering data, then enter your Store / Brand Name:

Own brand (DTC): A single brand selling its own products. Categories and collections organize the catalog. Brand pages are not generated.
Multi-brand (Retailer): Multiple brands sold through one store. Categories, brands, and collections all generate pages, plus Category × Brand cross-product pages.

Step 1: Enter Your Categories

In the Categories text area, enter your product categories one per line.

Running Shoes
Trail Shoes
Walking Shoes
Basketball Shoes

Categories represent the primary way customers browse your catalog. Each category becomes its own page grouped under a Categories Hub.

Step 2: Enter Your Brands (Multi-Brand Only)

In the Brands text area, enter the brands your store carries, one per line.

Nike
Adidas
New Balance
Brooks

Brands are only available in multi-brand mode. Each brand becomes its own brand page grouped under a Brands Hub.

Step 3: Enter Your Collections (Optional)

In the Collections text area, enter curated product collections, one per line.

Best Sellers
New Arrivals
Under $100
Editor's Picks

Collections represent curated groupings that cut across categories. They are grouped under a Collections Hub.

Step 4: Cross-Product Pages (Category × Brand)

In multi-brand mode, when you have both categories and brands, Floyi generates Category × Brand pages that target searches like “Nike Running Shoes” or “Adidas Trail Shoes.”

These pages combine every category with every brand
Example: 4 categories × 4 brands = 16 cross-product pages
Floyi shows a page estimate before generating so you can gauge the scale
Cross-product pages are capped at 200
Choose Category-first or Brand-first to set which comes first in the URL

Step 5: Configure URL Structure

Fine-tune how your e-commerce URLs are structured:

Hub Folders:

Categories Hub: Toggle on to group all categories under a hub folder, /shop/ by default (e.g., /shop/running-shoes/)
Brands Hub: Toggle on to group all brands under /brands/ (e.g., /brands/nike/)
Collections Hub: Toggle on to group all collections under /collections/ (e.g., /collections/best-sellers/)
You can customize the hub slugs (e.g., change “categories” to “shop” or “collections” to “curated”)

Category × Brand Pages:

Toggle on to create combined pages like /shop/running-shoes/nike/
These pages target searches like “Nike Running Shoes”

Step 6: Generate Your Architecture

Review your categories, brands, and collections in the preview panel.
Toggle Replace existing pages if you want to start fresh.
Click Generate Structure.
The system creates all pages with proper parent-child relationships.
Switch to the Preview panel to see your complete site structure.

Example E-commerce Site Structure

For a multi-brand shoe retailer:

/                                              Home
/about/                                        About
/contact/                                      Contact
/shop/                                         Categories Hub
  /shop/running-shoes/                         Category
    /shop/running-shoes/nike/                  Category + Brand
    /shop/running-shoes/adidas/                Category + Brand
  /shop/trail-shoes/                           Category
/brands/                                       Brands Hub
  /brands/nike/                                Brand Page
  /brands/adidas/                              Brand Page
/collections/                                  Collections Hub
  /collections/best-sellers/                   Collection
  /collections/new-arrivals/                   Collection

Part 3: Google Business Profile Integration

If your business has a verified Google Business Profile (GBP), you can connect it to Floyi to sync your business data and streamline your local SEO workflow.

Connecting Your Google Business Profile

Navigate to Settings from the main menu.
Click on Integrations.
Find the Google Business Profile section.
Click Connect Google Account and sign in with the Google account that manages your GBP.
Grant the required permissions for Floyi to access your business profile data.
Select which business profile to connect if you manage multiple locations.

The connection is managed per workspace. Once connected, any team member with access can use the synced data.

What Data Syncs from GBP

When connected, Floyi can pull the following data from your Google Business Profile:

Business Name: Your official business name as listed on Google
Address: Full street address, city, state, and postal code
Phone Number: Primary contact number
Website URL: Your business website
Business Category: Your primary Google business category
Opening Hours: Regular operating hours for each day
Service Areas: Regions you serve (for service-area businesses)

How GBP Data Works with Site Architecture

The GBP connection enhances your Site Architecture workflow in two key ways:

1. Business Info Sync (Brand Foundation)

In Brand Foundation, you can click Sync from GBP in the Business Info card to populate your structured business data automatically. This data is then used to generate LocalBusiness Schema (JSON-LD) that you can deploy across your location pages.

2. Location Data for Architecture

If your GBP includes multiple locations or service areas, this information can inform your Site Architecture planning. Use your GBP service areas as a starting point for your locations list in the generator.

Managing Your GBP Connection

Disconnect: Return to Settings > Integrations to disconnect your Google account at any time
Refresh Data: Click “Sync from GBP” in Brand Foundation to pull the latest data from your profile
Multiple Profiles: If you manage multiple GBP listings, you can switch between them in Settings

Your GBP data is never modified by Floyi—the connection is read-only for syncing purposes.

Part 4: Fetching Locations from a URL

If your business already has a locations page on your website, Floyi can extract the location list automatically using AI.

How to Use Location Fetching

Choose your Location format first (State > City > Neighborhood or City > Neighborhood (no state)).
Under Optional: Agents can fetch your live locations list from a URL (user-provided only), enter the URL of your locations page (e.g., https://example.com/locations).
Click Fetch Locations from URL.
If your Locations list already has entries, confirm that you want to replace them.
Floyi analyzes your page and fills the Locations list.

The cost is shown next to the button. You’re charged only when Floyi finds locations; a failed or empty fetch is free. If you enter a URL and leave the Locations list empty, Floyi fetches the locations when you click Generate Structure and charges the same cost, which shows above the button before you click.

Best Practices for URL Fetching

Use a page that lists all your locations clearly
Pages with addresses, city names, or location directories work best
The system handles up to 200 locations per fetch
Review extracted locations before generating; you can edit the list manually

Part 5: Managing Your Pages

Once your architecture is generated, you can view, edit, and manage individual pages.

Viewing Your Structure

Table (the default):

Displays all pages in a flat list sorted by URL
Shows each page’s title, type and URL

Tree:

Shows hierarchical parent-child relationships
Visualizes your URL depth at a glance

Switch between Tree and Table with the buttons above the preview. Publish status is managed in Topical Authority, not here.

Collapsing Panels

On larger screens, you can collapse either the Builder or Preview panel to focus on one at a time:

Click the left chevron to collapse the Builder panel
Click the right chevron to collapse the Preview panel
A “Show builder” or “Show preview” button appears to restore the collapsed panel

Editing Pages

Click Edit above the preview.
Change any page’s:
- Title: The display name of the page
- Slug: The URL segment (auto-generated from title)
- Page Type: The category of page (service, location, etc.)
Click Save changes to apply all modifications, or Discard to drop them. Click Done editing to leave edit mode.

Edit mode changes titles, slugs and page types. Pages can’t be moved to a different parent here.

When you change a page’s slug, all descendant pages automatically update their URL paths.

Affected Pages Indicator:

When editing, a Changing N pages note shows how many pages your changes affect. If you change a parent page’s slug, all child pages will have their URLs updated. The note helps you understand the scope of your changes before saving.

Adding Pages (Single vs Bulk Mode)

The “Add pages (manual)” section has two modes:

Single: Add one page at a time with full control over each field
Bulk: Import multiple pages from a CSV/Excel file or add rows manually

Toggle between modes using the Single / Bulk buttons.

Adding Individual Pages (Single Mode)

Select Single mode in the Add pages (manual) section.
Enter the Title. The Slug auto-generates from the title, and you can customize it.
Choose the Page type (available types depend on your selected site type):

Shared page types (all site types):
- Services Hub — directory page grouping all services
- Service — an individual service offering
- Subservice — a variant or specialization under a service
- Pricing — pricing and packages page
- Process — how your service works
- FAQ — frequently asked questions
- Reviews — testimonials and social proof
- Case Studies — success stories and outcomes
- About — brand story and team
- Contact — contact information
Local Business only:
- Locations Hub — directory page grouping all locations
- State — state-level location page
- City — city-level location page
- Neighborhood — neighborhood or district page
- Market — broader service area (e.g., “Bay Area”, “North Dallas”)
- Service + Location — combined service and location page
Service Agency only:
- Industries Hub — directory page grouping all industries
- Industry — an industry vertical the agency serves
- Service + Industry — combined service and industry page
- Solutions Hub — directory page grouping all solutions
- Solution — a packaged solution or use case
SaaS only:
- Features Hub — directory page grouping all features
- Feature — an individual product feature page
- Use Cases Hub — directory page grouping all use cases
- Use Case — a use case or buyer persona page
- Integrations Hub — directory page grouping all integrations
- Integration — an individual integration page
- Solutions Hub — directory page grouping all solutions
- Solution — a packaged solution or outcome page
- Feature + Use Case — combined feature and use case page
Optionally, choose a Parent (optional). Leave it empty for a top-level page.
Click Add page.

Deleting Pages

Click Edit above the preview.
Click Delete on the page’s row.
Review the Delete page dialog, which lists the page and the Child pages to be deleted.
Confirm to delete the page and all descendants.

Deleting a parent page removes all its children. This cannot be undone.

Part 6: Bulk Import & Export

For large site structures, use bulk operations to save time.

Importing Pages (CSV/Excel)

Select Bulk mode in the “Add pages (manual)” section.
Click Download CSV template to get the required format.
Prepare your file with columns:
- Title: Page name (required)
- Slug: URL segment (optional, auto-generated from title if blank)
- Type: Page type name or code (optional). It must be one of your site type’s page types.
- Parent: Parent page title or URL path (optional)
Click Import CSV and select your file. CSV and XLSX files both work.
Review the preview table:
- Valid rows show normal styling
- Invalid rows are highlighted with red borders
- Error messages explain what needs fixing. A type that isn’t one of your site type’s page types is named with its row number; pick a valid type before saving.

Flexible Column Headers:

Floyi recognizes multiple header variations:

Title: Title, PageTitle
Slug: Slug, UrlSlug
Type: Type, PageType, Kind
Parent: Parent, ParentPage, ParentPath, ParentUrl

Apply to All Options:

Two toggles help when all rows share the same type or parent:

Apply type to all: Set a single page type for all imported rows
Apply parent to all: Set a single parent page for all imported rows

When enabled, individual row values are locked and the global setting applies.

Duplicate Detection:

Floyi automatically detects pages that would create duplicate URL paths:

Duplicates are flagged and skipped during import
You’ll see a summary of how many pages were added vs. skipped

Manual Row Editing:

You can also add rows manually in bulk mode:

Click Add row to create new empty rows
Edit title, slug, type, and parent directly in the table
Click Clear rows to start over

When your rows look right, click Add pages.

Exporting Your Architecture

Click Export in the Preview panel.
Choose Export to XLSX, Export to CSV or Export to Google Sheets. Google Sheets creates a new document in your Google Drive.

Exports include all page data: titles, slugs, types, URL paths, and metadata.

Part 7: Page Configuration Options

Each page carries the fields below. In Site Architecture you edit the title, slug and page type. Publish status, keywords and tracking are managed in Topical Authority, where each page has a details drawer.

Page Fields

Title: The display name shown in navigation and headers.
Slug: The URL segment for this page (letters, numbers, hyphens, underscores, and dots; case is preserved for hreflang codes like zh-TW).
URL Path: The complete URL path from root (auto-calculated).
Page Type: The semantic category of the page.
Geo Data: Geographic metadata for location pages (state, city, neighborhood).

Managed in Topical Authority

Published: Mark a page as published when it is live on your site.
Keywords: Keywords and anchors for the page.
Primary Query: The search query used for tracking, with a manual override when the generated one doesn’t match how people search.

[!NOTE] Page names in non-Latin scripts get transliterated or renamed slugs, and Floyi flags those pages for review.

How Site Architecture Connects to Topical Authority

Pages you create in Site Architecture can be tracked alongside your Topical Research topics in the Topical Authority module. This gives you a unified view of rankings and AI visibility across your local/service pages, agency pages, SaaS product pages, e-commerce pages, and your blog/resource content.

The connection works like this:

Build your architecture: Create your pages in Site Architecture (services, locations, features, use cases, etc.).
Configure tracking: In Topical Authority Settings, define your Query Strategy (see below).
Enable page types: Select which page types (Service, City, Service + Location, Feature, Use Case, etc.) should be tracked.
Run SERP refresh: Floyi fetches rankings and AI data for your architecture pages using the query patterns you defined.
View unified metrics: See all your pages in the Topical Authority Planner and Scorecard.

Query Strategy for Architecture Pages:

In Topical Authority Settings, you configure a primary query pattern that Floyi uses to generate search queries for your architecture pages. For example:

Local Business:

Pattern: {service} in {city}, {state}
Page: “Tree Trimming” service in “Dallas, Texas”
Generated query: “Tree trimming in Dallas, TX”

Service Agency:

Pattern: {service} for {industry}
Page: “SEO” service for “Healthcare” industry
Generated query: “SEO for Healthcare”

SaaS:

Pattern: {product} {feature} for {use_case}
Page: “Workflow Automation” feature for “Marketing Teams” use case
Generated query: “Acme Workflow Automation for Marketing Teams”

Available SaaS tokens: {feature}, {use_case}, {integration}, {solution}, {product}, {brand}

E-commerce:

Pattern: {category} {brand} {store_name}
Page: “Running Shoes” category for “Nike” brand
Generated query: “Nike Running Shoes ShoeStore”

Available E-commerce tokens: {category}, {brand}, {collection}, {product_name}, {store_name}

The query uses tokens from your page metadata to build realistic search queries that match how customers actually search.

Tracking by Page Type:

You can selectively enable tracking for specific page types:

Local Business page types:

Page Type	What It Tracks
Service	Individual service offerings
Service + Location	Combined service + location pages (e.g., “Tree trimming Dallas”)
City	City-level location pages
State	State-level location pages
Neighborhood	Neighborhood/district pages
Services Hub	Services directory page
Locations Hub	Locations directory page

Service Agency page types:

Page Type	What It Tracks
Service	Individual service offerings
Industry	Industry vertical pages (e.g., “Healthcare”)
Service + Industry	Combined service + industry pages (e.g., “SEO for Healthcare”)
Solution	Packaged solution or use case pages
Services Hub	Services directory page
Industries Hub	Industries directory page
Solutions Hub	Solutions directory page

SaaS page types:

Page Type	What It Tracks
Feature	Feature-level pages
Use Case	Use case pages
Integration	Integration pages
Solution	Solution/outcome pages
Feature + Use Case	Cross-product pages (e.g., “Workflow Automation for Marketing Teams”)
Features Hub	Features directory page
Use Cases Hub	Use cases directory page
Integrations Hub	Integrations directory page
Solutions Hub	Solutions directory page

E-commerce page types:

Page Type	What It Tracks
Category	Product category pages
Brand Page	Brand storefront pages (multi-brand only)
Collection	Curated collection pages
Category + Brand	Cross-product pages (e.g., “Nike Running Shoes”)
Categories Hub	Categories directory page
Brands Hub	Brands directory page
Collections Hub	Collections directory page

Pages not in the enabled list will still appear in your architecture but won’t consume credits for SERP tracking.

Primary Query Override:

For individual pages that need a custom search query (different from the pattern-generated one), use the Primary Query Override field. This is useful when:

The auto-generated query doesn’t match real search behavior
You want to track a specific long-tail variation
The page targets a unique keyword

Part 8: URL Structure Best Practices

Maximum Depth

Floyi enforces a maximum URL depth of 4 levels:

/level-1/level-2/level-3/level-4/

This ensures URLs remain clean and search-engine friendly.

Example Site Structure

For a tree service company in Texas:

/                                       Home
/about/                                 About
/contact/                               Contact
/services/                              Services Hub
  /services/tree-trimming/              Service
  /services/tree-removal/               Service
    /services/tree-removal/emergency/   Subservice
/locations/                             Locations Hub
  /locations/texas/                     State
    /locations/texas/dallas/            City
      /locations/texas/dallas/uptown/   Neighborhood
      /locations/texas/dallas/tree-trimming/  Service + Location
    /locations/texas/houston/           City

Slug Normalization

All slugs are automatically normalized:

Converted to lowercase
Spaces replaced with hyphens
Special characters removed
Maximum 200 characters

Part 9: Continuing Your Workflow

After completing your site architecture:

For “Site + Resources” Scope

Review your complete site structure.
Click Next: Topical Research.
Plan your blog and resource content.
Track your site pages and your resource content side by side in Topical Authority.

For “Site Only” Scope

Finalize your site structure.
Click Continue to Topical Authority. It opens Topical Authority on your site pages.
Track your rankings and visibility across your service areas, industry verticals, or product features.
Monitor how your pages perform in search and AI results.

For “Resources Only” Scope

Click Continue to Topical Research in the Resources Only Mode panel to begin planning your content strategy. You can reopen Site Architecture from the sidebar later if you change your mind.

The Next and Continue buttons stay disabled until your architecture has at least one page.

Tips for Success

Start with your services: Define your core offerings before adding locations or industries.
Use consistent naming: Keep service, location, industry, and feature names consistent across your site.
Plan your hierarchy: Sketch your structure before generating to avoid rework.
Review before generating: The preview panel shows exactly what will be created.
Edit after generation: You can always add, remove, or modify pages after the initial generation.
Use the tree view: Visualize your hierarchy to catch structural issues early.
Export for review: Share exports with your team before implementation.
Check the page estimate: Before generating, note how many cross-product pages (service+location, service+industry, or feature+use case) will be created.

Quick Reference: Page Types

Shared (all site types):

Page Type	Description
Services Hub	Parent page grouping all services
Service	A primary service offering
Subservice	A specific variant under a service
Pricing	Pricing and packages
Process	How your service works
FAQ	Frequently asked questions
Reviews	Testimonials and social proof
Case Studies	Success stories and outcomes
About	Brand story and team
Contact	Contact information

Local Business:

Page Type	Description
Locations Hub	Parent page grouping all locations
State	State-level location page
City	City-level location page
Neighborhood	Neighborhood or district page
Market	Broader service area (e.g., “Bay Area”)
Service + Location	Combined service + location page

Service Agency:

Page Type	Description
Industries Hub	Parent page grouping all industries
Industry	An industry vertical the agency serves
Service + Industry	Combined service + industry page
Solutions Hub	Parent page grouping all solutions
Solution	A packaged solution or use case

SaaS:

Page Type	Description
Features Hub	Parent page grouping all features
Feature	An individual product feature
Use Cases Hub	Parent page grouping all use cases
Use Case	A use case or buyer persona page
Integrations Hub	Parent page grouping all integrations
Integration	An individual integration page
Solutions Hub	Parent page grouping all solutions
Solution	A packaged solution or outcome
Feature + Use Case	Combined feature + use case page

E-commerce:

Page Type	Description
Categories Hub	Parent page grouping all categories
Category	A product category page
Brands Hub	Parent page grouping all brands
Brand Page	A brand storefront page
Collections Hub	Parent page grouping all collections
Collection	A curated product collection page
Product	Individual product detail page
Category + Brand	Combined category + brand cross-product page