Scanned sites / primeseas.com / 2026-11-09-2005

primeseas.com scan from 2026-11-09 20:05:23 UTC DR 0

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

Scan 2026-11-09-2005

Scanned 2026-11-09 20:05:23 UTC, finished 2026-11-09 20:06:23 UTC

Site: https://primeseas.com/

Download SQLite databaseEvery page and asset from this scan, with the crawl events, in one file.

90/ 100Excellent

On November 9, 2026 the Site Spider crawled 2 pages and 28 assets of primeseas.com, starting from https://primeseas.com/. It scored 90 out of 100, an excellent result. 2 of 31 checks found something to fix, led by sitemap coverage (1), orphan pages (1); 24 checks passed. Most of the points went to sitemap coverage (−6), orphan pages (−4). 5 checks found something the score does not count, listed as noted. 6 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: Medium3 medium, 2 low and 1 info findings. See the security findings ↓

Pages crawled
2
Assets fetched
28
Status
Completed
Checks with issues
2 of 31
CoverageComplete crawl

30 of 30 discovered URLs were fetched. The crawl reached everything it found. HTML only: nothing here ran JavaScript.

  • Title tagsOK
    0 of 0 pages have title issues. 1 noindex or canonicalized page excluded.
  • Meta descriptionsOK
    0 of 0 pages have meta description issues. 1 noindex or canonicalized page excluded.
  • HeadingsOK
    0 of 0 pages have heading issues. 1 noindex or canonicalized page excluded.
  • Broken linksOK
    0 internal links point at 0 broken URLs.
  • Links to other sitesNot checked
    Not checked: the crawl fetched nothing this check can look at.
  • Redirects2 noted
    2 redirecting URLs, 0 of them chained.
  • Non-200 responses3 noted
    3 URLs did not return a 2xx response. 1 of them is a page, 0 with an error status; the rest are assets or redirects.
  • Rate limitedOK
    The site did not rate limit the crawler.
  • IndexabilityOK
    0 of 1 indexable page have indexability warnings.
  • Image alt textOK
    0 of 0 image references have no alt attribute.
  • Heavy assetsOK
    0 assets larger than 500 KB among 28 fetched assets.
  • Orphan pages1 issue
    1 page have no internal links pointing at them.
    −4 points
  • Sitemap coverage1 issue
    No sitemap found. Tried: https://primeseas.com/sitemap.xml (301), https://www.primeseas.com/sitemap.xml (404). Add one at /sitemap.xml or list it in robots.txt.
    −6 points
  • Internal link counts1 noted
    Internal link counts for 1 page; 1 worth a look.
  • Thin contentOK
    0 of 0 pages have fewer than 200 words. 1 noindex or canonicalized page excluded.
  • Duplicate contentOK
    0 groups of pages with identical HTML.
  • URL formatOK
    All 2 page URLs are plain lowercase addresses without parameters.
  • Canonicals1 noted
    1 of 1 page have a canonical worth checking.
  • Robots directivesOK
    No page carries a robots directive; all 1 page are open to search engines.
  • Anchor textOK
    Every internal link has descriptive, followed anchor text.
  • Title and heading structureOK
    0 of 0 pages could use the title, heading and snippet space better. 1 noindex or canonicalized page excluded.
  • Image weight and alt lengthOK
    No image is over 100 KB or carries alt text over 100 characters.
  • Response anomaliesOK
    No redirect loops, header redirects or pages served as something other than HTML.
  • HTML and head validationOK
    All 1 page keep their head tags in <head>, once each, under Googlebot's 2 MB.
  • hreflangOK
    No page declares hreflang.
  • Structured dataOK
    1 of 0 indexable pages carry structured data: WebSite (1). 0 pages with errors a rich result would fail on.
  • Near duplicatesOK
    No near duplicates among 0 pages with enough text to compare.
  • Soft 404sOK
    None of 1 page 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.
  • PaginationOK
    No page declares rel=next or rel=prev pagination.
  • Headers and cookies2 noted
    3 cookies set by the site, 2 missing a protective flag; 11 response headers recorded across 30 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 1 page; 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 InsightsNot checked
    Not checked yet: PageSpeed Insights runs on the top pages once the crawl has finished.
  • SpellingOK
    No unfamiliar lower-case words on 0 pages (English pages only).

Where this scan sits among all scanned sites

2884 sites, median 80%, average 79%

primeseas.com scores 90%, higher than 85% of the 2884 scanned sites. See the full ranking.

0761510%: 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%: 7 sites52%: 8 sites53%: 9 sites54%: 10 sites55%: 10 sites56%: 8 sites57%: 17 sites58%: 18 sites59%: 10 sites60%: 15 sites61%: 13 sites62%: 20 sites63%: 29 sites64%: 22 sites65%: 33 sites66%: 43 sites67%: 43 sites68%: 42 sites69%: 53 sites70%: 47 sites71%: 80 sites72%: 76 sites73%: 82 sites74%: 82 sites75%: 87 sites76%: 95 sites77%: 109 sites78%: 131 sites79%: 113 sites80%: 128 sites81%: 125 sites82%: 133 sites83%: 119 sites84%: 130 sites85%: 106 sites86%: 94 sites87%: 95 sites88%: 82 sites89%: 74 sites90%: 56 sites91%: 59 sites92%: 43 sites93%: 30 sites94%: 25 sites95%: 16 sites96%: 19 sites97%: 16 sites98%: 8 sites99%: 3 sites100%: 151 sites90% 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

The site is in excellent health, but there are key areas for improvement including fixing redirects, addressing non-200 responses, handling an orphan page, and creating a sitemap. Focus on these changes to enhance SEO performance.

  1. 1

    Fix Redirects

    Why: Redirects can confuse search engines and harm rankings.

    How: Update the primary domain to point directly to its intended URL without unnecessary redirects.

    Checks: redirects

  2. 2

    Resolve Non-200 Responses

    Why: Non-200 responses impact user experience and indexing by search engines.

    How: Ensure the sitemap URL returns a valid 200 status and correct the URL if it's used elsewhere.

    Checks: status-codes

  3. 3

    Create a Sitemap

    Why: Sitemaps help search engines understand site structure and index pages better.

    How: Generate a sitemap and place it at /sitemap.xml. Update robots.txt to list the sitemap.

    Evidence: One URL: no sitemap found.

    1 page affected

    Checks: sitemap-coverage

  4. 4

    Link to Orphan Page

    Why: Increased internal linking helps search engines discover pages and improves their rankings.

    How: Add internal links to the orphan page from relevant sections of the site.

    Checks: orphan-pages

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 site primeseas.com has several security vulnerabilities that need to be addressed. Key issues include the absence of critical HTTP security headers, which could expose users to attacks such as clickjacking, data leakage, and cookie theft. Implementing recommended headers will improve overall security significantly.

  • 0 high
  • 3 medium
  • 2 low
  • 1 info
  1. 1

    Missing Content Security PolicyMedium

    Why it matters: Without a CSP, the site is vulnerable to attacks like cross-site scripting by allowing scripts from untrusted sources.

    Fix: Add the header: 'Content-Security-Policy: default-src 'self';'.

    Evidence: Content Security Policy

  2. 2

    Missing Clickjacking ProtectionMedium

    Why it matters: Absence of X-Frame-Options allows the site to be embedded in a malicious frame, risking user interaction with hidden controls.

    Fix: Add the header: 'X-Frame-Options: DENY'.

    Evidence: Clickjacking protection

  3. 3

    Missing Cookie Security FlagsMedium

    Why it matters: Cookies lacking HttpOnly, Secure, and SameSite flags are susceptible to theft and misuse, enhancing the risk of session hijacking.

    Fix: Set HttpOnly, Secure, and SameSite flags for 'wixSession' and 'ssr-caching' cookies.

    Evidence: Cookie flags

  4. 4

    Missing Referrer PolicyLow

    Why it matters: No Referrer-Policy exposes user's full URL to third parties when navigating away from the site.

    Fix: Add the header: 'Referrer-Policy: no-referrer'.

    Evidence: Referrer policy

  5. 5

    Software Version DisclosureLow

    Why it matters: Revealing the framework in the X-Powered-By header could provide attackers information useful for exploitation.

    Fix: Remove or modify the 'X-Powered-By' header to not disclose information.

    Evidence: Software version disclosure

  6. 6

    Missing Permissions PolicyInfo

    Why it matters: A Permissions-Policy header can restrict unnecessary browser features, protecting against injected scripts.

    Fix: Add the header: 'Permissions-Policy: geolocation=(), microphone=(), camera=()'.

    Evidence: Permissions policy

What the checks found

  • FoundContent Security PolicyMedium

    None of the 1 HTML page 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.primeseas.com/ → 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.primeseas.com/ → no x-frame-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.primeseas.com/ → 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.primeseas.com/ → no permissions-policy
  • FoundCookie flagsMedium

    2 of 3 cookies are missing protective flags. Without HttpOnly a script can read the cookie; without Secure it travels over plain HTTP; without SameSite it is sent on cross-site requests.

    • wixSession (set by https://www.primeseas.com/) lacks HttpOnly, SameSite
    • ssr-caching (set by https://www.primeseas.com/sitemap.xml) lacks Secure, HttpOnly, SameSite
  • NoteSoftware version disclosure

    Responses name the framework in an X-Powered-By header but hide the version.

    • server: cloudflare (27 responses)
    • server: Pepyaka (3 responses)
    • x-powered-by: Express (1 response)
8 checks passed, 2 not applicable
  • OKHTTPS

    All 1 crawled page were served over HTTPS.

  • OKHTTP Strict Transport Security

    strict-transport-security is set on all 1 HTML page.

  • OKMIME sniffing protection

    x-content-type-options is set on all 1 HTML page.

  • OKMixed content

    No HTTPS page loads a script, stylesheet, font or image over plain HTTP.

  • OKKeys and secrets in page code

    No API keys, tokens or private keys were found in the sampled HTML and scripts.

  • OKExposed files and listings

    None of the crawled URLs is a configuration file, backup, dump, repository folder or directory listing.

  • OKThird-party scripts

    The sampled pages load no scripts from other domains.

  • OKSensitive paths in robots.txt

    robots.txt does not point at admin, backup or private paths.

  • Not applicableForms over HTTPS

    No forms were found on the sampled pages.

  • Not applicableVulnerable JavaScript libraries

    No recognisable library versions were found in the sampled scripts.

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.

Sites scoring near primeseas.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 primeseas.com from its pages as published, the way a search engine does. It shows summary figures only.

Own primeseas.com?