Site Architecture

Site Architecture is where you plan and structure your website’s pages for local SEO and multi-location businesses. This feature helps you create a clean, strategic URL hierarchy that connects your services to your service areas, ensuring search engines and AI systems understand your site’s structure.

Before building your site architecture, you need to select your content workflow. This determines how Floyi guides you through the content creation process.

1. Local Site + Resources (Recommended for most local businesses)

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

2. Local Site Only

• Create service and location 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

1. Navigate to the Site Architecture page from the sidebar.
2. Review the three workflow cards displayed at the top.
3. Click Select on your preferred workflow.
4. If you have existing work and switch scopes, a confirmation dialog will appear.

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

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

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 real-time preview shows how each line 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

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

Replace Existing Option:

Before generating, you can toggle Replace existing pages:

• Off (default): New pages are added to your existing structure
• On: Clears your current architecture and rebuilds from scratch

Enable “Replace existing” only when you want a complete rebuild. This removes all previously generated pages.

Generate:

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

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.

1. Navigate to Settings from the main menu.
2. Click on Integrations.
3. Find the Google Business Profile section.
4. Click Connect Google Account and sign in with the Google account that manages your GBP.
5. Grant the required permissions for Floyi to access your business profile data.
6. 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.

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)

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.

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

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

1. Click the Fetch from URL button in the Locations section.
2. Enter the URL of your locations page (e.g., https://example.com/locations).
3. Select your preferred location format (State > City > Neighborhood or City > Neighborhood).
4. Click Fetch Locations.
5. The AI analyzes your page and extracts locations into the text area.

This feature uses credits. The cost is displayed before you confirm.

• 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

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

Table View:

• Displays all pages in a flat, sortable list
• Shows URL path, page type, and status
• Use search to find specific pages
• Click column headers to sort

Tree View:

• Shows hierarchical parent-child relationships
• Expand/collapse sections to focus on specific areas
• Visualizes your URL depth at a glance

Toggle between views using the view selector buttons above the preview.

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

1. Click Edit Mode to enable editing.
2. Click on any page row to modify:
   • Title: The display name of the page
   • Slug: The URL segment (auto-generated from title)
   • Page Type: The category of page (service, location, etc.)
3. Changes are tracked with a yellow indicator.
4. Click Save Changes to apply all modifications.

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

Affected Pages Indicator:

When editing, Floyi shows how many pages will be affected by your changes. If you change a parent page’s slug, all child pages will have their URLs updated. The indicator helps you understand the scope of your changes before saving.

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.

1. Select Single mode in the add pages section.
2. Select the Parent Page (or leave as root for top-level pages).
3. Choose the Page Type:
   • services_hub - Services directory page
   • service - Individual service page
   • subservice - Service variant (child of a service)
   • locations_hub - Locations directory page
   • state - State hub page
   • city - City hub page
   • neighborhood - Neighborhood/area page
   • market - Broader service area (e.g., “Bay Area”, “North Dallas”)
   • service_location - Service + location combo page
   • pricing - Pricing and packages page
   • process - How your service works page
   • faq - FAQ page
   • reviews - Reviews/testimonials page
   • case_studies - Case studies page
   • about - About page
   • contact - Contact page
4. Enter the Title.
5. The Slug auto-generates from the title (you can customize it).
6. Click Add Page.

1. Click the delete icon on any page row.
2. Review the confirmation dialog showing:
   • The page being deleted
   • Any child pages that will also be removed
3. Confirm to delete the page and all descendants.

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

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

1. Select Bulk mode in the “Add pages (manual)” section.
2. Click Download CSV template to get the required format.
3. Prepare your file with columns:
   • Title: Page name (required)
   • Slug: URL segment (optional, auto-generated from title if blank)
   • Type: Page type code (optional)
   • Parent: Parent page title or URL path (optional)
4. Click Import CSV and select your file.
5. Review the preview table:
   • Valid rows show normal styling
   • Invalid rows are highlighted with red borders
   • Error messages explain what needs fixing

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

1. Click the Export button in the header.
2. Choose your format:
   • CSV: Standard spreadsheet format
   • Excel (XLSX): Full Excel workbook
   • Google Sheets: Creates a new document in your Google Drive

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

Each page has additional settings you can configure for SEO and tracking.

• Title: The display name shown in navigation and headers.
• Slug: The URL segment for this page (lowercase, hyphens only).
• 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).
• Keywords: Optional keyword list for SEO planning.
• Published: Mark as published when the page is live on your site.
• Archived: Archive pages that are no longer needed but you want to keep the record.

• Tracking Enabled: Enable SERP and AI tracking for this page.
• Primary Query Override: Custom search query for tracking (instead of auto-generated).

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 both your local/service pages and your blog/resource content.

The connection works like this:

1. Build your architecture: Create service and location pages in Site Architecture.
2. Configure tracking: In Topical Authority Settings, define your Query Strategy (see below).
3. Enable page types: Select which page types (service, city, service_location, etc.) should be tracked.
4. Run SERP refresh: Floyi fetches rankings and AI data for your architecture pages using the query patterns you defined.
5. 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:

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

The query uses tokens from your page metadata (service name, city, state, neighborhood) to build realistic search queries that match how customers actually search.

Tracking by Page Type:

You can selectively enable tracking for specific page types:

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

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.

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)

All slugs are automatically normalized:

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

After completing your site architecture:

1. Review your complete site structure.
2. Click Continue to Topical Research.
3. Build your content calendar for blog and resource pages.
4. Generate briefs and drafts that link back to your service pages.

1. Finalize your site structure.
2. Click Continue to Topical Authority.
3. Track your rankings and visibility across your service areas.
4. Monitor how your pages perform in search and AI results.

The Site Architecture page is skipped entirely. Navigate directly to Topical Research to begin planning your content strategy.

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