Strategy & Planning
Sitemap: Old vs Proposed
Current site architecture analysis and recommended restructure for Green Star Marine's next web presence.
01Current Site Structure
What We Could Map
Automated extraction of gsm808.com's architecture was limited by its JavaScript-rendered SPA implementation.
Extraction Limitation
The current gsm808.com site uses client-side rendering. All subpages return 404 to crawlers, meaning only the root URL was accessible for automated analysis. The structure below represents the inferred architecture based on page title, SPA behavior patterns, and common marine industry site structures. A manual walkthrough with browser devtools is required to confirm the full route inventory.
Confirmed via crawler
Inferred from SPA behavior
gsm808.com (root)
Client-side routes (unknown structure)
Likely: Products / Services
Likely: About
Likely: Contact
Other routes unknown
02Proposed New Structure
Recommended Architecture
A server-rendered site structure built for B2B marine buyers: organized by buyer intent, with clear paths from discovery to conversion.
Home
Products & Solutions
[Product Category A]
[Product Category B]
Custom Development
Portfolio / Case Studies
Marine Vessels
Equipment
Technology
Services
Product Development
Engineering Consulting
Prototyping & Testing
Manufacturing Support
About
Company Story
Team
Certifications & Standards
Resources
Blog / Insights
Technical Downloads
FAQ
Contact
Request a Quote
Find a Distributor
Support
03Key Changes
Current vs Proposed Comparison
Eight structural changes that will have the most impact on discoverability, lead quality, and buyer experience.
| Area | Current | Proposed | Rationale |
|---|---|---|---|
| SEO Structure | Client-side routing only; bots see one URL | Server-rendered pages with unique, indexable URLs | Enables Google to crawl and index all pages independently, unlocking organic search traffic |
| Navigation Depth | Unknown (SPA, no confirmed structure) | 3-level hierarchy: top nav, section, sub-page | Organizes product and service complexity without overwhelming first-time visitors |
| Portfolio Section | Not confirmed to exist | Dedicated portfolio with case studies by category | Marine B2B buyers require proof of prior work; a portfolio section directly addresses the "show me examples" objection |
| Resources / Content | Not confirmed to exist | Blog, technical downloads, and FAQ hub | Content marketing in niche B2B sectors is a low-competition SEO lever; resources also support longer sales cycles |
| Services Page | Not confirmed or separated from products | Distinct services section with 4 service categories | Clarifies the consulting and development offering vs. the product catalog; serves different buyer types |
| Contact Paths | Single contact point (assumed) | Three separate paths: Quote, Distributor, Support | Reduces friction by routing buyers to the right conversation immediately; improves lead quality and response speed |
| sitemap.xml | Missing (404) | Auto-generated and submitted to Search Console | Required for search engines to discover all pages; without it, indexation relies entirely on link discovery |
| robots.txt | Missing (404) | Added with explicit allow rules and sitemap reference | Provides crawlers with clear directives; absence is a technical SEO flag and signals an unconfigured site |
04URL Structure
Recommended URL Patterns
Clean, hierarchical URLs that support SEO, are memorable for buyers, and scale cleanly as the product and portfolio grows.
gsm808.com/ -- homepage
gsm808.com/products/ -- products index
gsm808.com/products/[category]/ -- category page
gsm808.com/portfolio/ -- portfolio index
gsm808.com/portfolio/[project-slug]/ -- case study
gsm808.com/services/ -- services overview
gsm808.com/services/[service-slug]/ -- individual service
gsm808.com/about/ -- about
gsm808.com/resources/ -- resources hub
gsm808.com/resources/[post-slug]/ -- blog post / download
gsm808.com/contact/ -- contact index
gsm808.com/contact/quote/ -- request a quote form
gsm808.com/contact/distributor/ -- distributor finder
gsm808.com/contact/support/ -- support request
Implementation note: These patterns assume a server-rendered or statically-generated framework (Next.js, Astro, Nuxt, or similar). If the current SPA is retained, all routes must be pre-rendered at build time and included in sitemap.xml for search engines to index them. Client-side-only routing is not indexable without additional configuration (dynamic rendering or pre-rendering middleware).