Content Accessibility
Summary of what content could and could not be evaluated during this automated analysis. The JS rendering barrier blocked access to virtually all page content.
Technical, SEO, content, and UX audit of the current gsm808.com website - September 2026
Four key dimensions scored based on automated crawl analysis conducted September 2026. The site's JavaScript-only rendering is the primary factor driving low scores across all categories.
Issues identified through automated HTTP crawl and header inspection of gsm808.com.
| Finding | Severity | Detail | Action Required |
|---|---|---|---|
JavaScript-Only Rendering |
Critical | Site is a single-page application where all content is rendered client-side via JavaScript. Crawlers without JS execution cannot read any body content beyond the HTML shell. | Migrate to server-side rendering (SSR) or static site generation (SSG) using Next.js, Astro, or a similar framework. |
No sitemap.xml |
High | No sitemap found at gsm808.com/sitemap.xml (HTTP 404). Search engines have no roadmap of the site's page inventory. | Generate and submit a sitemap.xml to Google Search Console and Bing Webmaster Tools. |
No robots.txt |
High | No robots.txt found (HTTP 404). Without explicit crawl directives, bots operate with no guidance on allowed or disallowed paths. | Create a robots.txt with explicit allow rules and a Sitemap reference line. |
All Subpages Return 404 to Crawlers |
Critical | Pages at /products, /about, and /contact all return HTTP 404 to non-JS crawlers. Client-side routing handles these routes internally but search engines cannot reach them. | Implement SSR or pre-rendering so each route returns a full HTML response with meaningful content and a 200 status code. |
No Open Graph Tags Detected |
Medium | Without og:title, og:description, and og:image, social shares of any page URL will produce poor-quality previews with no image or description. | Add Open Graph meta tags to every route. Each route should have a unique og:title and og:description. |
No Twitter Card Meta Detected |
Low | Twitter/X shares will not produce rich link previews without twitter:card and twitter:image tags. | Add twitter:card, twitter:title, twitter:description, and twitter:image meta tags to all routes. |
Assessment of standard SEO ranking factors. Many items are marked Unknown due to the JS-rendering barrier preventing content extraction.
| Factor | Status | Notes |
|---|---|---|
Title Tag |
Partial | "Green Star Marine | Marine Product Development" confirmed on root URL only. Subpages likely share the same title since routing is client-side. |
Meta Description |
Unknown | Could not be extracted due to JS rendering. Verify in browser that each route has a unique, descriptive meta description under 160 characters. |
H1 Tag |
Unknown | Not extractable via automated crawl. Open each major route in a browser and inspect the DOM to confirm one unique H1 per page. |
Keyword Strategy |
Not Assessed | Page copy is not crawlable. A manual keyword gap analysis using Ahrefs, SEMrush, or Google Keyword Planner is required. |
Page Speed |
Likely Poor | JS-first rendering typically adds 1-3 seconds to First Contentful Paint. Run PageSpeed Insights immediately to get a baseline score. |
Core Web Vitals |
Not Measured | Requires PageSpeed Insights or Lighthouse with a real browser. CWV directly affects Google's ranking signals. Prioritize this measurement. |
Backlink Profile |
Not Assessed | Requires Ahrefs or SEMrush audit. Domain authority and inbound link quality are significant ranking factors in competitive B2B spaces. |
Local SEO / Schema |
Unknown | No structured data detected in the HTML shell. Verify in-browser and add schema.org Organization and LocalBusiness markup if applicable. |
HTTPS |
Confirmed | Site loads correctly over HTTPS. Certificate appears valid. No mixed content issues detected in the HTML shell. |
Mobile Responsiveness |
Unknown | Cannot verify from automated crawl. Test manually on iOS Safari and Android Chrome. Mobile-friendliness is a confirmed Google ranking factor. |
Summary of what content could and could not be evaluated during this automated analysis. The JS rendering barrier blocked access to virtually all page content.
Ten actions that can be started now, before any development work begins, to improve the site's baseline posture.
The five highest-impact actions, ranked by urgency and potential SEO/business impact.
The single largest barrier to organic growth is the SPA architecture. Until pages are server-rendered or pre-built, Google cannot index any content except the homepage title. Migrate to Next.js (App Router with SSR), Astro, or a comparable SSG solution. This is the prerequisite for all other SEO work.
These two files cost almost nothing to create and immediately signal to search engines that the site is professionally managed. The sitemap.xml should list every route with its last-modified date. The robots.txt should include a Sitemap line pointing to the sitemap URL.
Without a baseline score, there is no way to measure improvement. Run both tools now against the current site, save the results, and use them to prioritize performance fixes during the new site build. Core Web Vitals scores directly influence Google's ranking signals.
Open every route of the current site in a browser and document what exists: headings, copy, images, CTAs, forms, and any embedded content. This inventory is the foundation for the content migration plan, copywriting brief, and new site information architecture.
Both tools are free and provide direct visibility into how search engines see the site, including crawl errors, index coverage, and keyword impressions. Setting them up now ensures data is accumulating from the current baseline, making before-and-after comparisons possible once the new site launches.