Internal Linking Strategy & Optimization Plan

1. The Hub and Spoke Architecture

Hydrilla.org is built on a strict silo architecture. The core principle is that authority flows from the top-level hubs down into the long-tail spokes, and spokes cross-link to reinforce the hub.

Top-Level Hubs: /biology/, /identification/, /control/, /impact/, /distribution/, /research/
Spokes: Long-tail articles residing within these folders (e.g., /control/pond-removal/).
Rule 1: Every spoke MUST link back to its parent hub using exact match or partial match anchor text (e.g., "Hydrilla Control Overview"). This is handled automatically by the breadcrumbs and the back button.
Rule 2: Spokes within the same hub must cross-link to each other. This is handled by the "Related Guides" sidebar component.

2. Contextual In-Content Linking (The "Bridge" Strategy)

While structural links (sidebars, footers) are great for indexation, contextual in-body links carry the most SEO weight. We use "Bridges" to connect silos where contextually relevant.

Approved Cross-Silo Bridges

Source Silo	Target Silo	Contextual Hook
/identification/	/control/	"Once you have properly identified hydrilla, the next step is implementing an effective control strategy..."
/biology/	/impact/	"Because of its rapid growth rate, hydrilla has a severe ecological impact on native ecosystems..."
/research/	/distribution/	"Statistical data aligns with the rapid expansion seen across our state-by-state distribution maps..."
/control/	/biology/	"Treatment timing must be aligned with the plant's life cycle, specifically targeting vulnerable turions..."

3. The Rotating Authority Footer Component

To prevent the site from looking like a Wikipedia directory and diluting PageRank with 100+ footer links, we utilize a React-driven rotating footer (footer-rotating-authority.tsx) that serves a subset of links dynamically.

The Pool: All 68 pages are categorized into Identification, Biology, Treatment, Impact/Research, and State Distribution.
The Logic: On page load, the component identifies the current silo. It ALWAYS forces the most relevant category to appear in column 1 (e.g., if you are reading about Herbicides, the "Treatment Methods" column is guaranteed to show).
The Shuffle: Columns 2 and 3 are randomly selected from the remaining categories. Within each column, exactly 4 links are randomly selected from that category's pool.
The Result: Every time Googlebot crawls the site, it discovers new pathways deep into the architecture, ensuring deep pages stay indexed without bloating the DOM size.

4. Orphan Page Prevention

The script/prerender.js file has been engineered to inject a static <noscript> version of the footer. Because React doesn't run in some simple crawler environments, this ensures a static HTML fallback exists containing links to the hub pages. Furthermore, the XML sitemap (`/sitemap.xml`) serves as the ultimate failsafe, guaranteeing Google is aware of all 68 trailing-slash URLs regardless of internal linking state.