Scanned sites / www.seacanfl.com / 2026-09-18-0200
www.seacanfl.com scan from 9/18/2026, 2:00:02 AM
Scan 2026-09-18-0200
Scanned 9/18/2026, 2:00:02 AM, finished 9/18/2026, 2:01:53 AM. Found on page 1 of chatgpt for browser (api usage) results
Site: https://www.seacanfl.com/
Download SQLite databaseEvery page and asset from this scan, with the crawl events, in one file.
On September 18, 2026 the Site Spider crawled 15 pages and 172 assets of www.seacanfl.com, starting from https://www.seacanfl.com/. It scored 78 out of 100, a good result. 8 of 14 checks found something to fix, led by title tags (13), meta descriptions (7), thin content (6); 6 checks passed. The list below shows each check's result, the fix plan, when present, explains what to do first, and the security review at the end of the page covers headers, transport, libraries and exposed files.
Security review: Medium4 medium, 2 low and 1 info findings. See the security findings ↓
- Pages crawled
- 15
- Assets fetched
- 172
- Status
- Completed
- Checks with issues
- 8 of 14
- Title tags13 issues13 of 13 pages have title issues. 2 noindex or canonicalized pages excluded.
- Meta descriptions7 issues7 of 13 pages have meta description issues. 2 noindex or canonicalized pages excluded.
- Headings2 issues2 of 13 pages have heading issues. 2 noindex or canonicalized pages excluded.
- Broken linksOK0 internal links point at 0 broken URLs.
- RedirectsOK0 redirecting URLs, 0 of them chained.
- Non-200 responsesOK1 URL did not return a 2xx response.
- Rate limitedOKThe site did not rate limit the crawler.
- IndexabilityOK0 of 13 indexable pages have indexability warnings. 2 pages noindex by design.
- Image alt text2 issues2 of 64 image references have no alt attribute.
- Heavy assets4 issues4 assets larger than 500 KB among the 100 heaviest.
- Orphan pages5 issues5 pages have no internal links pointing at them.
- Sitemap coverage5 issues1 sitemap listing 15 URLs: 0 crawled pages missing, 0 listed URLs broken or redirecting, 3 reachable only via the sitemap.
- Thin content6 issues6 of 13 pages have fewer than 200 words. 2 noindex or canonicalized pages excluded.
- Duplicate contentOK0 groups of pages with identical HTML.
Where this scan sits among all scanned sites
1078 sites, median 82%, average 80%
www.seacanfl.com scores 78%, higher than 33% of the 1078 scanned sites. See the full ranking.
Green 90% and up (Excellent), lime 75 to 89 (Good), amber 50 to 74 (Needs work), red below 50 (Poor).
Internal link map
Loading the link map...
Fix plan
Written by gpt-4o-mini from the scan findingsYour site has critical SEO issues primarily with titles, meta descriptions, and a non-200 response. Addressing these will enhance visibility and accessibility. I recommend focusing on fixing titles first, followed by meta descriptions and heading issues.
- 1
Fix Non-200 Responses
Why: Eliminating 404 errors helps improve user experience and site credibility.
How: Update or remove the link to the missing asset: https://www.seacanfl.com/wp-content/plugins/gravityforms/assets/css/dist/fonts/gform-icons-common.eot?8i2g28.
Checks: status-codes
- 2
Update Title Tags
Why: Optimizing title tags enhances click-through rates from search results.
How: Revise titles to be 30-60 characters: e.g., change 'Home - SEA CAN' to 'SEA CAN: Your Source for Containers'.
Checks: titles
- 3
Optimize Meta Descriptions
Why: Meta descriptions influence search engine results and user clicks.
How: Add concise, appealing meta descriptions for missing entries: e.g., 'Explore affordable container sales for your needs.'
Checks: meta-descriptions
- 4
Address Missing Headings
Why: Headings help structure content and improve SEO.
How: Add an H1 heading to the pages https://www.seacanfl.com/orlando/ and https://www.seacanfl.com/tampa/.
Checks: headings
- 5
Add Alt Text for Images
Why: Image alt text improves SEO and accessibility.
How: Add descriptive alt attributes to images that are missing them on respective pages.
Checks: images-alt
- 6
Improve Thin Content Pages
Why: Increasing content quality helps fulfill user intent and improves rankings.
How: Enhance pages with fewer than 200 words by adding relevant information.
Checks: thin-content
Generated automatically; verify each change against your own site before relying on it.
Security review
Written by gpt-4o-mini from 16 checks over the crawlThe website lacks important security headers that protect against various attacks and has exposed sensitive API keys. Implementing these recommendations will enhance security and reduce risks for your users.
- 0 high
- 4 medium
- 2 low
- 1 info
- 1
Missing HTTP Strict Transport Security (HSTS)Medium
Why it matters: Without HSTS, users may be vulnerable to man-in-the-middle attacks when accessing the site without HTTPS.
Fix: Add 'Strict-Transport-Security: max-age=31536000; includeSubDomains' to web server configuration.
Evidence: HTTP Strict Transport Security
- 2
Missing Content Security Policy (CSP)Medium
Why it matters: The absence of CSP allows unrestricted loading of resources, increasing the risk of cross-site scripting attacks.
Fix: Add 'Content-Security-Policy: default-src 'self';' to web server configuration.
Evidence: Content Security Policy
- 3
Missing X-Frame-Options HeaderMedium
Why it matters: Lack of X-Frame-Options allows potential clickjacking attacks by embedding your site in malicious frames.
Fix: Add 'X-Frame-Options: DENY' to web server configuration.
Evidence: Clickjacking protection
- 4
Exposed Google API KeyMedium
Why it matters: Exposed credentials can be misused if not properly restricted.
Fix: Restrict the API key usage in Google Cloud console by setting HTTP referrer restrictions.
Evidence: Keys and secrets in page code
- 5
Missing X-Content-Type-Options HeaderLow
Why it matters: Without this header, browsers may interpret files incorrectly, posing security risks.
Fix: Add 'X-Content-Type-Options: nosniff' to web server configuration.
Evidence: MIME sniffing protection
- 6
Missing Referrer-Policy HeaderLow
Why it matters: Not setting a Referrer-Policy can lead to leaking sensitive URL information to third-party sites.
Fix: Add 'Referrer-Policy: no-referrer' to web server configuration.
Evidence: Referrer policy
- 7
Missing Permissions Policy HeaderInfo
Why it matters: Not using Permissions Policy allows unauthorized use of browser features.
Fix: Add 'Permissions-Policy: geolocation=(self), microphone=()' to web server configuration.
Evidence: Permissions policy
What the checks found
- FoundHTTP Strict Transport SecurityMedium
No HTML page sends strict-transport-security. Without it a visitor who types the address without https:// can be intercepted on the first request.
- https://www.seacanfl.com/ → no strict-transport-security
- https://www.seacanfl.com/on-site-storage/ → no strict-transport-security
- https://www.seacanfl.com/office-containers/ → no strict-transport-security
- https://www.seacanfl.com/custom-containers/ → no strict-transport-security
- https://www.seacanfl.com/container-sales/ → no strict-transport-security
- https://www.seacanfl.com/faq/ → no strict-transport-security
- https://www.seacanfl.com/orlando/ → no strict-transport-security
- https://www.seacanfl.com/tampa/ → no strict-transport-security
- https://www.seacanfl.com/privacy-policy/ → no strict-transport-security
- https://www.seacanfl.com/sitemap/ → no strict-transport-security
- https://www.seacanfl.com/thank-you-schematics/ → no strict-transport-security
- https://www.seacanfl.com/order-form/ → no strict-transport-security
- FoundContent Security PolicyMedium
None of the 15 HTML pages send a Content-Security-Policy header or meta tag, so the browser has no restriction on where scripts, styles and frames may load from.
- https://www.seacanfl.com/ → no content-security-policy
- https://www.seacanfl.com/on-site-storage/ → no content-security-policy
- https://www.seacanfl.com/office-containers/ → no content-security-policy
- https://www.seacanfl.com/custom-containers/ → no content-security-policy
- https://www.seacanfl.com/container-sales/ → no content-security-policy
- https://www.seacanfl.com/faq/ → no content-security-policy
- https://www.seacanfl.com/orlando/ → no content-security-policy
- https://www.seacanfl.com/tampa/ → no content-security-policy
- https://www.seacanfl.com/privacy-policy/ → no content-security-policy
- https://www.seacanfl.com/sitemap/ → no content-security-policy
- https://www.seacanfl.com/thank-you-schematics/ → no content-security-policy
- https://www.seacanfl.com/order-form/ → no content-security-policy
- FoundClickjacking protectionMedium
No HTML page sends x-frame-options. Without X-Frame-Options (or a CSP frame-ancestors directive) the pages can be embedded in a frame on another site and overlaid with invisible controls.
- https://www.seacanfl.com/ → no x-frame-options
- https://www.seacanfl.com/on-site-storage/ → no x-frame-options
- https://www.seacanfl.com/office-containers/ → no x-frame-options
- https://www.seacanfl.com/custom-containers/ → no x-frame-options
- https://www.seacanfl.com/container-sales/ → no x-frame-options
- https://www.seacanfl.com/faq/ → no x-frame-options
- https://www.seacanfl.com/orlando/ → no x-frame-options
- https://www.seacanfl.com/tampa/ → no x-frame-options
- https://www.seacanfl.com/privacy-policy/ → no x-frame-options
- https://www.seacanfl.com/sitemap/ → no x-frame-options
- https://www.seacanfl.com/thank-you-schematics/ → no x-frame-options
- https://www.seacanfl.com/order-form/ → no x-frame-options
- FoundMIME sniffing protectionLow
No HTML page sends x-content-type-options. Without X-Content-Type-Options: nosniff a browser may run a file as a script because of its contents rather than its declared type.
- https://www.seacanfl.com/ → no x-content-type-options
- https://www.seacanfl.com/on-site-storage/ → no x-content-type-options
- https://www.seacanfl.com/office-containers/ → no x-content-type-options
- https://www.seacanfl.com/custom-containers/ → no x-content-type-options
- https://www.seacanfl.com/container-sales/ → no x-content-type-options
- https://www.seacanfl.com/faq/ → no x-content-type-options
- https://www.seacanfl.com/orlando/ → no x-content-type-options
- https://www.seacanfl.com/tampa/ → no x-content-type-options
- https://www.seacanfl.com/privacy-policy/ → no x-content-type-options
- https://www.seacanfl.com/sitemap/ → no x-content-type-options
- https://www.seacanfl.com/thank-you-schematics/ → no x-content-type-options
- https://www.seacanfl.com/order-form/ → no x-content-type-options
- FoundReferrer policyLow
No HTML page sends referrer-policy. Without a Referrer-Policy the full page address, including any query string, is sent to every site a visitor clicks through to.
- https://www.seacanfl.com/ → no referrer-policy
- https://www.seacanfl.com/on-site-storage/ → no referrer-policy
- https://www.seacanfl.com/office-containers/ → no referrer-policy
- https://www.seacanfl.com/custom-containers/ → no referrer-policy
- https://www.seacanfl.com/container-sales/ → no referrer-policy
- https://www.seacanfl.com/faq/ → no referrer-policy
- https://www.seacanfl.com/orlando/ → no referrer-policy
- https://www.seacanfl.com/tampa/ → no referrer-policy
- https://www.seacanfl.com/privacy-policy/ → no referrer-policy
- https://www.seacanfl.com/sitemap/ → no referrer-policy
- https://www.seacanfl.com/thank-you-schematics/ → no referrer-policy
- https://www.seacanfl.com/order-form/ → no referrer-policy
- FoundPermissions policyInfo
No HTML page sends permissions-policy. A Permissions-Policy header turns off browser features the site does not use (camera, microphone, geolocation), limiting what an injected script could do.
- https://www.seacanfl.com/ → no permissions-policy
- https://www.seacanfl.com/on-site-storage/ → no permissions-policy
- https://www.seacanfl.com/office-containers/ → no permissions-policy
- https://www.seacanfl.com/custom-containers/ → no permissions-policy
- https://www.seacanfl.com/container-sales/ → no permissions-policy
- https://www.seacanfl.com/faq/ → no permissions-policy
- https://www.seacanfl.com/orlando/ → no permissions-policy
- https://www.seacanfl.com/tampa/ → no permissions-policy
- https://www.seacanfl.com/privacy-policy/ → no permissions-policy
- https://www.seacanfl.com/sitemap/ → no permissions-policy
- https://www.seacanfl.com/thank-you-schematics/ → no permissions-policy
- https://www.seacanfl.com/order-form/ → no permissions-policy
- FoundKeys and secrets in page codeMedium
1 credential-like value found in code served to every visitor: Google API key.
- Google API key AIzaSy…JQ (39 chars) in https://www.seacanfl.com/orlando/: browser keys are expected in pages, but must be restricted by HTTP referrer and API in the Google Cloud console
- NoteSoftware version disclosure
Responses name the framework in an X-Powered-By header but hide the version.
- server: nginx (187 responses)
- x-powered-by: WP Engine (15 responses)
- NoteThird-party scripts
Scripts run from 3 other domains without Subresource Integrity, so a compromise of any of them changes what runs on this site. (Tag managers and analytics rarely support SRI; a Content-Security-Policy that names these hosts is the usual control.)
- s.ksrndkehqnwntyxlhgto.com (15 script tags)
- www.google.com (10 script tags)
- maps.googleapis.com (2 script tags)
6 checks passed, 1 not applicable
- OKHTTPS
All 15 crawled pages were served over HTTPS.
- OKMixed content
No HTTPS page loads a script, stylesheet, font or image over plain HTTP.
- OKForms over HTTPS
12 forms found, all on HTTPS pages posting to HTTPS addresses.
- OKVulnerable JavaScript libraries
1 library version recognised, none with known vulnerabilities.
- OKExposed files and listings
None of the crawled URLs is a configuration file, backup, dump, repository folder or directory listing.
- OKSensitive paths in robots.txt
robots.txt does not point at admin, backup or private paths.
- Not applicableCookie flags
The crawl set no cookies, so there are no cookie flags to check.
A passive review of what the crawl recorded: response headers, page and script contents and the URLs it found. It does not probe the site, test TLS settings or look for files that were not linked. Generated automatically; verify each finding against your own site before acting on it.
This report was produced by the DIY SEO Hub Site Spider crawling www.seacanfl.com from its public pages. Anyone can run a scan of any site they own or are authorised to check. Is this your site? Claim it to manage the listing, or ask for removal through the support form.