Houston Geo-SEO Architecture

Subdirectory hub-and-spoke structure for neighborhood dominance, AI visibility, and consolidated domain authority.

Canopy (What It Does)
Understory (How It Flows)
Root Level (How It Is Built)

I. The Architecture

One domain, subdirectory hub-and-spoke. Every neighborhood rolls up authority to the city pillar.

thepropertyjoesgroup.com | +-----------+ | | /houston/ (future city nodes) [CITY PILLAR] | +-----+-----+-----+ | | | /houston/ /houston/ /houston/ river-oaks/ garden-oaks- [future [LUXURY] oak-forest/ nodes] | [FAMILY/VALUE] | /houston/ river-oaks/ avalon-place/ [ENCLAVE]

II. Why This Works

Authority consolidation + AI entity recognition + scalable expansion.

The Three Wins

  • Domain Authority Consolidation -- All link equity flows to one root domain. Every backlink to any neighborhood page strengthens the entire site.
  • AI Entity Recognition -- Search engines and AI answer engines see one clean entity tree: Brand > City > Neighborhood. Structured data reinforces the hierarchy.
  • Scalable Expansion -- Add new neighborhoods by adding subdirectories. No DNS changes, no new properties to manage, no authority dilution.

III. The Outcome

When someone asks an AI "best realtor in River Oaks" -- we own the answer.

Comprehensive Content-> Internal Link Equity-> Schema Markup-> AI Citations-> Clients

I. URL / Node Tree

Clean, semantic, crawlable hierarchy.

thepropertyjoesgroup.com /houston/ -- City Pillar (market overview, stats, why Houston) /houston/river-oaks/ -- Luxury Neighborhood Hub /houston/river-oaks/avalon-place/ -- Enclave (micro-community) /houston/river-oaks/market-stats/ -- Cluster: live data /houston/river-oaks/lifestyle/ -- Cluster: dining, culture, daily life /houston/river-oaks/schools/ -- Cluster: school guides /houston/river-oaks/homes-for-sale/ -- Cluster: active listings /houston/river-oaks/buying-guide/ -- Cluster: buyer/seller guides /houston/garden-oaks-oak-forest/ -- Family/Value Neighborhood Hub /houston/garden-oaks-oak-forest/market-stats/ /houston/garden-oaks-oak-forest/lifestyle/ /houston/garden-oaks-oak-forest/schools/ /houston/garden-oaks-oak-forest/homes-for-sale/ /houston/garden-oaks-oak-forest/buying-guide/

II. Content Cluster Project area (Per Node)

Every neighborhood hub gets these 5 content layers -- interlinked, schema-marked, AI-readable.

1. Market Stats DATA
  1. Median price + YoY change
  2. Days on market
  3. Inventory levels
  4. Price per sqft trends
  5. Quarterly refresh cadence

Schema: Dataset + StatisticalPopulation

2. Lifestyle EXPERIENCE
  1. Dining + entertainment
  2. Parks + outdoor spaces
  3. Cultural landmarks
  4. Commute + transit
  5. Neighborhood personality

Schema: Place + LocalBusiness (nearby POI)

3. Schools FAMILIES
  1. Public school ratings
  2. Private school options
  3. District boundaries
  4. Extracurricular programs
  5. Parent community insight

Schema: School + EducationalOrganization

4. Active Listings IDX
  1. Live MLS feed (filtered)
  2. Featured properties
  3. Price tier breakdown
  4. New listings alerts
  5. Sold history (social proof)

Schema: RealEstateListing + Offer

5. Buyer/Seller Guide CONVERSION
  1. Area-specific buying tips
  2. Pricing strategy by neighborhood
  3. Common pitfalls + HOA notes
  4. Investment outlook
  5. CTA: personalized consultation

Schema: FAQPage + HowTo

III. Internal Linking Strategy

Every page links up, across, and down -- forming a web that search engines and AI crawlers follow.

City Pillar-> Neighborhood Hub-> Cluster Pages-> Back to Hub-> Cross-link Siblings

Link Equity Flow

  • Vertical: City pillar links down to each neighborhood hub. Each hub links down to its 5 cluster pages. Every cluster page links back up to its hub AND the city pillar.
  • Horizontal: Neighborhood hubs cross-link to each other (e.g., River Oaks lifestyle links to Garden Oaks lifestyle for "family-friendly alternative").
  • Enclave: Avalon Place links up to River Oaks hub. River Oaks hub links down to Avalon Place. Mutual reinforcement.

IV. Rollout Sequence

Build the pillar first, prove the model, then expand.

Houston City Pillar

/houston/ -- Market overview, "Why Houston," top neighborhoods preview, LocalBusiness schema for TPJG. Establishes the root node.

River Oaks Hub (Luxury)

/houston/river-oaks/ + all 5 cluster pages + Avalon Place enclave. Full luxury treatment. Validates the template.

Garden Oaks / Oak Forest Hub (Family/Value)

/houston/garden-oaks-oak-forest/ + all 5 cluster pages. Proves the model works for non-luxury. Different audience, same structure.

Measure + Optimize

Track: organic impressions per neighborhood, AI citation frequency (ChatGPT/Perplexity/Google AI Overviews), crawl coverage, internal link clicks. Refine before expanding.

Expand

Add nodes: Memorial, Bellaire, The Heights, Piney Point, West University. Each follows the proven template. Priority = where TPJG already has transaction history (social proof).

I. Why Subdirectory (Research-Backed)

The decision: one domain, subdirectories only. Here is the evidence.

Subdirectory vs. Subdomain vs. Separate Domain

Backlinko (2025): "Subdirectories consolidate authority under one domain. When a page earns a backlink, the link equity flows directly into the main domain -- all pages share the same website authority and build a stronger foundation."
HubSpot Case Study: Migrated blog from blog.hubspot.com to hubspot.com/blog -- reported significant organic traffic gains. Moz community content migration to main domain saw improved rankings.
Buffer (2024): Consolidated blog from subdomain to subdirectory -- reported 2x increase in organic traffic over 6 months.
NameSilo / E-E-A-T Analysis (2025): "In 2025, where Google explicitly leans on E-E-A-T, subdirectories are powerful tools for entity reinforcement. Subdirectories strengthen entity association by consolidating signals under one domain identity."
Ignite Visibility: "Despite Google's official stance that subdomains receive equal treatment, many SEO professionals report substantial traffic gains after migrating from subdomains to subdirectories."

Why NOT Subdomains or Separate Domains

  • Subdomains (e.g., riveroaks.thepropertyjoesgroup.com): Google may treat as separate sites. Link equity does NOT automatically flow to root. Splits crawl budget. More DNS management.
  • Separate domains (e.g., riveroakshomes.com): Zero authority transfer. Must build DA from scratch per domain. Expensive. Fragments brand entity.
  • Subdirectories (e.g., /houston/river-oaks/): All authority compounds. Single crawl budget. One entity in AI knowledge graphs. Clean, scalable, no additional infrastructure.

II. AI Visibility Architecture (AEO)

How this structure feeds AI answer engines specifically.

Entity Tree for AI Crawlers

TPJG AEO Strategy (Internal, 2026-03): AI answer engines (ChatGPT, Perplexity, Google AI Overviews) favor sites with: comprehensive topical coverage, clear entity hierarchy, structured data (JSON-LD), and internal linking that demonstrates expertise depth.
Principle: A single domain with 50+ interlinked neighborhood pages signals "Houston real estate authority" more strongly to AI models than 50 scattered microsites. The entity tree (Brand > City > Neighborhood > Topic) maps directly to how LLMs organize knowledge.

Schema Markup Plan (Per Page Type)

  • City Pillar: LocalBusiness (TPJG) + Place (Houston) + BreadcrumbList
  • Neighborhood Hub: Place (neighborhood, geo-coordinates) + LocalBusiness (TPJG office) + BreadcrumbList + SameAs (Wikipedia, Wikidata)
  • Market Stats: Dataset + StatisticalPopulation + BreadcrumbList
  • Lifestyle: Place + ItemList (POI) + BreadcrumbList
  • Schools: EducationalOrganization + ItemList + BreadcrumbList
  • Listings: RealEstateListing + Offer + BreadcrumbList
  • Guides: FAQPage + HowTo + BreadcrumbList
Example JSON-LD (Neighborhood Hub)
{ "@context": "https://schema.org", "@type": "Place", "name": "River Oaks, Houston", "geo": { "@type": "GeoCoordinates", "latitude": "29.7504", "longitude": "-95.4286" }, "containedInPlace": { "@type": "City", "name": "Houston", "containedInPlace": { "@type": "State", "name": "Texas" } }, "description": "Luxury neighborhood guide for River Oaks...", "mainEntity": { "@type": "LocalBusiness", "name": "The Property Joes Group", "areaServed": { "@type": "Place", "name": "River Oaks" } } }

III. Technical Implementation Notes

For the build team -- how to execute.

Page Generation

  • Template-driven: one Next.js/static template per page type (hub, cluster, enclave)
  • Data layer: JSON config per neighborhood (name, slug, geo coords, school district, price range, personality tags)
  • Content layer: Markdown files per cluster page, processed at build time
  • IDX integration: filtered MLS feed per neighborhood boundary (polygon coordinates)
  • Canonical URLs: always trailing slash (/houston/river-oaks/ not /houston/river-oaks)

Crawl + Indexing

  • XML sitemap with lastmod dates per page (separate neighborhood sitemap)
  • robots.txt: Allow all /houston/ paths
  • Internal links: minimum 3 contextual links per page (up + across + down)
  • Breadcrumb nav on every page: Home > Houston > [Neighborhood] > [Topic]
  • hreflang: not needed (single market, English only)

Measurement Framework

  • Organic impressions per /houston/* URL (GSC)
  • AI citation checks: bi-weekly ChatGPT/Perplexity/Gemini queries for target keywords
  • Crawl stats: pages indexed in /houston/ (GSC Coverage)
  • Internal link click-through (GA4 events)
  • Lead attribution: form submissions tagged by source neighborhood page

IV. Research Sources

📚Library