Scanned sites / www.seacanfl.com

SEO report for www.seacanfl.com DR 0

The latest Site Spider scan of www.seacanfl.com, with 1 scan on record. Each scan is at its own address, for example /domain/www-seacanfl-com/2026-09-18-0200.

DR is Ahrefs Domain Rating (0-100, backlink strength), used under its Domain Rating License.

Latest scan

Scanned 2026-09-18 02:00:02 UTC, finished 2026-09-18 02:01:53 UTC. 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.

76/ 100Good

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 76 out of 100, a good result. 9 of 27 checks found something to fix, led by title tags (13), meta descriptions (8), thin content (6); 10 checks passed. Most of the points went to title tags (−8.7), meta descriptions (−4.3), thin content (−3.2). 8 checks found something the score does not count, listed as noted. 10 checks were not run because the crawl fetched nothing for them. 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
9 of 27
CoverageComplete crawl

187 of 190 discovered URLs were fetched, 3 blocked by robots.txt. The crawl reached everything it found. HTML only: nothing here ran JavaScript. 4 link destinations on other sites were checked.

  • Title tags13 issues
    13 of 13 pages have title issues. 2 noindex or canonicalized pages excluded.
    −8.7 points
  • Meta descriptions8 issues
    8 of 13 pages have meta description issues. 2 noindex or canonicalized pages excluded.
    −4.3 points
  • Headings2 issues
    2 of 13 pages have heading issues. 2 noindex or canonicalized pages excluded.
    −0.8 points
  • Broken linksOK
    0 internal links point at 0 broken URLs.
  • Links to other sites1 noted
    0 destinations answered with an error, 1 could not be determined (timeouts, rate limits or refusals), of 4 destinations checked.
  • RedirectsOK
    0 redirecting URLs, 0 of them chained.
  • Non-200 responses1 noted
    1 URL did not return a 2xx response. 0 of them are pages, 0 with an error status; the rest are assets or redirects.
  • Rate limitedOK
    The site did not rate limit the crawler.
  • Indexability2 issues
    2 of 13 indexable pages have indexability warnings. 2 pages noindex by design. 2 noindex pages are listed in the sitemap, which asks search engines both to visit and to ignore them.
    −1.3 points
  • Image alt text2 issues
    2 of 64 image references have no alt attribute.
    −0.2 points
  • Heavy assets4 issues
    4 assets larger than 500 KB among 172 fetched assets.
    −2.4 points
  • Orphan pages5 issues
    5 pages have no internal links pointing at them.
    −1.3 points
  • Sitemap coverage5 issues
    1 sitemap listing 15 URLs: 0 crawled pages missing, 0 listed URLs broken or redirecting, 3 reachable only via the sitemap.
    −2 points
  • Internal link countsOK
    Internal link counts for 15 pages; none is a dead end or buried.
  • Thin content6 issues
    6 of 13 pages have fewer than 200 words. 2 noindex or canonicalized pages excluded.
    −3.2 points
  • Duplicate contentOK
    0 groups of pages with identical HTML.
  • URL formatOK
    All 15 page URLs are plain lowercase addresses without parameters.
  • Canonicals2 noted
    2 of 15 pages have a canonical worth checking.
  • Robots directives15 noted
    15 pages carry a robots directive; 0 carry none.
  • Anchor text1 noted
    1 destination are linked without useful anchor text, or with nofollow.
  • Title and heading structure8 noted
    8 of 13 pages could use the title, heading and snippet space better. 2 noindex or canonicalized pages excluded.
  • Image weight and alt length18 noted
    18 images over 100 KB; 0 with alt text over 100 characters.
  • Response anomaliesOK
    No redirect loops, header redirects or pages served as something other than HTML.
  • HTML and head validationNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.
  • hreflangNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.
  • Structured dataNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.
  • Near duplicatesNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.
  • Soft 404sOK
    None of 15 pages answering 200 reads like an error page.
  • AccessibilityNot checked
    Not checked: the accessibility audit runs in the browser. Tick "Include JavaScript rendering checks" when you request a scan to run it.
  • Link positionsNot checked
    Not checked: this scan was crawled before link positions were recorded. Scan the site again to run it.
  • PaginationNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.
  • Headers and cookiesOK
    0 cookies set by the site; 10 response headers recorded across 187 URLs.
  • Orphans in searchNot checked
    Not checked: import a Search Console Pages export on the scan page to find pages Google shows that the site does not link to.
  • Link ScoreOK
    Link Score (internal PageRank, 0-100) for 15 pages; 0 hold almost none (10 or less).
  • JavaScript renderingNot checked
    Not checked: this scan did not render pages. Tick "Include JavaScript rendering checks" when you request a scan to compare the served HTML with what a browser builds.
  • PageSpeed Insights5 noted
    Mobile performance 47 on average across 5 pages; 5 below Google's good thresholds.
  • SpellingNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.

Where this site sits among all scanned sites

2858 sites, median 80%, average 79%

www.seacanfl.com scores 76%, higher than 32% of the 2858 scanned sites. See the full ranking.

0751490%: 0 sites1%: 0 sites2%: 0 sites3%: 0 sites4%: 0 sites5%: 0 sites6%: 0 sites7%: 0 sites8%: 0 sites9%: 1 site10%: 0 sites11%: 0 sites12%: 0 sites13%: 0 sites14%: 1 site15%: 0 sites16%: 0 sites17%: 0 sites18%: 0 sites19%: 0 sites20%: 0 sites21%: 1 site22%: 0 sites23%: 0 sites24%: 0 sites25%: 0 sites26%: 0 sites27%: 0 sites28%: 1 site29%: 0 sites30%: 0 sites31%: 0 sites32%: 0 sites33%: 0 sites34%: 0 sites35%: 2 sites36%: 1 site37%: 1 site38%: 3 sites39%: 2 sites40%: 3 sites41%: 1 site42%: 2 sites43%: 3 sites44%: 2 sites45%: 6 sites46%: 5 sites47%: 5 sites48%: 6 sites49%: 8 sites50%: 6 sites51%: 6 sites52%: 8 sites53%: 9 sites54%: 10 sites55%: 9 sites56%: 8 sites57%: 17 sites58%: 18 sites59%: 10 sites60%: 15 sites61%: 13 sites62%: 20 sites63%: 29 sites64%: 21 sites65%: 33 sites66%: 43 sites67%: 42 sites68%: 42 sites69%: 52 sites70%: 46 sites71%: 79 sites72%: 76 sites73%: 81 sites74%: 82 sites75%: 87 sites76%: 95 sites77%: 108 sites78%: 131 sites79%: 112 sites80%: 126 sites81%: 125 sites82%: 132 sites83%: 120 sites84%: 129 sites85%: 107 sites86%: 95 sites87%: 94 sites88%: 79 sites89%: 75 sites90%: 54 sites91%: 58 sites92%: 43 sites93%: 28 sites94%: 25 sites95%: 14 sites96%: 17 sites97%: 16 sites98%: 7 sites99%: 3 sites100%: 149 sites76% here100%90%80%70%60%50%40%30%20%10%0%

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...

Start page (centre)OKRedirectErrorOrphanLinked from most pagesOne inbound link or noneRings = clicks from the start page. Size = inbound links. Drag to pan, scroll to zoom, click a page to see only its links.

Fix plan

Written by gpt-4o-mini from the scan findings

Written from an earlier version of the analysis. The findings on this page have been recomputed since, so counts and labels here may differ from what the plan describes. The advice still points at the same checks.

Your 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. 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. 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. 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. 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. 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. 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 crawl

The 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. 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. 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. 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. 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. 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. 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. 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.

Earlier scans of www.seacanfl.com

No other scans of this site yet.

Sites scoring near www.seacanfl.com

Their neighbours in the SEO rank table, which orders every scanned site by health score.

DR is Ahrefs Domain Rating (0-100, backlink strength), used under its Domain Rating License.

This report was produced by the DIY SEO Hub Site Spider crawling www.seacanfl.com from its pages as published, the way a search engine does. It shows summary figures only.

Own www.seacanfl.com?

  • Claim this site to manage the listing, hide it from the public lists, or keep it.
  • Want it gone instead? Ask through the support form or e-mail support@diyseohub.com, naming www.seacanfl.com. Removal needs no account and no proof of purchase.