Scanned sites / surferseo.com / 2026-10-01-0934

surferseo.com scan from 10/1/2026, 9:34:03 AM

Scan 2026-10-01-0934

Scanned 10/1/2026, 9:34:03 AM, finished 10/1/2026, 9:30:30 PM. Found with 42backlinks.com tool directory

Site: https://surferseo.com/

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

88/ 100Good

On October 1, 2026 the Site Spider crawled 829 pages and 3 assets of surferseo.com, starting from https://surferseo.com/. It scored 88 out of 100, a good result. 12 of 16 checks found something to fix, led by meta descriptions (230), title tags (166), redirects (247); 3 checks passed. Most of the points went to meta descriptions (−3), title tags (−2.7), redirects (−1.6). 1 check found something the score does not count, listed as noted. 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
829
Assets fetched
3
Status
Completed
Checks with issues
12 of 16
CoverageComplete crawl

832 of 832 discovered URLs were fetched. The crawl reached everything it found. HTML only: nothing here ran JavaScript. 300 link destinations on other sites were checked, 1585 left unchecked.

  • Title tags166 issues
    166 of 452 pages have title issues. 157 noindex or canonicalized pages excluded.
    −2.7 points
  • Meta descriptions230 issues
    230 of 452 pages have meta description issues. 157 noindex or canonicalized pages excluded.
    −3 points
  • Headings119 issues
    119 of 452 pages have heading issues. 157 noindex or canonicalized pages excluded.
    −1.2 points
  • Broken links20 issues
    71 internal links point at 20 broken URLs.
    −0.7 points
  • Links to other sites6 issues
    6 destinations answered with an error, 65 could not be determined (timeouts, rate limits or refusals), 1585 were left unchecked by the per-scan cap, of 300 destinations checked.
    −0.4 points
  • Redirects247 issues
    199 redirecting URLs, 118 of them chained.
    −1.6 points
  • Non-200 responses22 issues
    221 URLs did not return a 2xx response. 220 of them are pages, 22 with an error status; the rest are assets or redirects.
    −0.4 points
  • Rate limitedOK
    The site did not rate limit the crawler.
  • Indexability91 issues
    91 of 597 indexable pages have indexability warnings. 12 pages noindex by design. 1 noindex page is listed in the sitemap, which asks search engines both to visit and to ignore it.
    −1.5 points
  • Image alt text284 issues
    284 of 16857 image references have no alt attribute. 12141 use an empty alt (decorative), which is fine.
    −0.1 points
  • Heavy assetsOK
    0 assets larger than 500 KB among 3 fetched assets.
  • Orphan pages25 issues
    25 pages have no internal links pointing at them.
    −0.2 points
  • Sitemap coverage31 issues
    1 sitemap listing 541 URLs: 2 crawled pages missing, 4 listed URLs broken or redirecting, 24 reachable only via the sitemap.
    −0.3 points
  • Internal link countsOK
    Internal link counts for 500 pages.
  • Thin contentOK
    0 of 452 pages have fewer than 200 words. 157 noindex or canonicalized pages excluded.
  • Duplicate content4 issues
    1 group of pages with identical HTML.
    −0.1 points

Where this scan sits among all scanned sites

1629 sites, median 80%, average 79%

surferseo.com scores 88%, higher than 82% of the 1629 scanned sites. See the full ranking.

0511010%: 0 sites1%: 0 sites2%: 0 sites3%: 0 sites4%: 0 sites5%: 0 sites6%: 0 sites7%: 0 sites8%: 0 sites9%: 0 sites10%: 0 sites11%: 0 sites12%: 0 sites13%: 0 sites14%: 0 sites15%: 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%: 2 sites38%: 2 sites39%: 0 sites40%: 2 sites41%: 0 sites42%: 0 sites43%: 1 site44%: 0 sites45%: 3 sites46%: 2 sites47%: 3 sites48%: 2 sites49%: 5 sites50%: 3 sites51%: 5 sites52%: 7 sites53%: 6 sites54%: 6 sites55%: 3 sites56%: 5 sites57%: 5 sites58%: 10 sites59%: 5 sites60%: 9 sites61%: 11 sites62%: 15 sites63%: 15 sites64%: 10 sites65%: 18 sites66%: 18 sites67%: 31 sites68%: 25 sites69%: 22 sites70%: 35 sites71%: 37 sites72%: 47 sites73%: 39 sites74%: 46 sites75%: 53 sites76%: 60 sites77%: 59 sites78%: 75 sites79%: 57 sites80%: 80 sites81%: 101 sites82%: 80 sites83%: 78 sites84%: 71 sites85%: 55 sites86%: 57 sites87%: 52 sites88%: 56 sites89%: 47 sites90%: 31 sites91%: 34 sites92%: 22 sites93%: 11 sites94%: 13 sites95%: 7 sites96%: 6 sites97%: 7 sites98%: 2 sites99%: 2 sites100%: 53 sites88% 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 website has several SEO issues, primarily concerning broken links, redirect chains, non-200 responses, and meta data. Prioritizing their resolution will enhance user experience and improve search engine visibility. Recommended improvements focus on high-impact, quick-to-implement fixes.

  1. 1

    Fix Broken Internal Links

    Why: 71 internal links lead to broken URLs, harming both SEO and user experience.

    How: Identify and fix or remove the 71 broken links. Address the most critical link errors first.

    Checks: broken-links

  2. 2

    Reduce Redirect Chains

    Why: 199 URLs redirect, 118 of which are chained, which may impact crawl efficiency.

    How: Streamline redirects by updating URLs to direct to the final destination immediately.

    Checks: redirects

  3. 3

    Resolve Non-200 Responses

    Why: 221 URLs do not return 2xx responses, hindering access and indexing.

    How: Audit the affected pages for errors and correct them or remove them if necessary.

    Checks: status-codes

  4. 4

    Update Meta Descriptions

    Why: 230 pages have meta description issues; improving these can enhance SERP visibility.

    How: Craft unique, relevant meta descriptions for the affected pages, ensuring they stay within 160 characters.

    Checks: meta-descriptions

  5. 5

    Address Title Tag Issues

    Why: 166 pages have title tag issues; optimizing these can positively influence click-through rates.

    How: Revise shorter and overly long title tags, keeping them under 60 characters where feasible.

    Checks: titles

  6. 6

    Fix Indexed Noindex Page

    Why: One noindex page is listed in the sitemap, causing confusion for search engines.

    How: Remove the noindex page from the sitemap or change its indexing status as appropriate.

    Checks: indexability

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 crucial security headers, exposing it to various attacks such as tampering and code injection. Additionally, cookies do not have protective flags, risking user data security. Implementing recommended security controls will significantly enhance defenses against common threats.

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

    Missing Content Security PolicyMedium

    Why it matters: Without a CSP, the site has no restrictions on where scripts and resources can load from, increasing vulnerability to XSS attacks.

    Fix: Add a Content-Security-Policy header. Example: `Content-Security-Policy: default-src 'self';`

    Evidence: Content Security Policy

  2. 2

    Missing Clickjacking ProtectionMedium

    Why it matters: Without X-Frame-Options or CSP frame-ancestors, the site can be embedded in malicious frames, facilitating clickjacking attacks.

    Fix: Add X-Frame-Options header. Example: `X-Frame-Options: DENY` or use a CSP directive for frame ancestors.

    Evidence: Clickjacking protection

  3. 3

    Missing Cookie Security FlagsMedium

    Why it matters: Cookies without Secure, HttpOnly, and SameSite flags are susceptible to theft and CSRF attacks, compromising user sessions.

    Fix: Set flags for cookies: `Secure; HttpOnly; SameSite=Strict`

    Evidence: Cookie flags

  4. 4

    Missing MIME Sniffing ProtectionLow

    Why it matters: Absence of X-Content-Type-Options may allow browsers to misinterpret file types, leading to security risks.

    Fix: Add X-Content-Type-Options header. Example: `X-Content-Type-Options: nosniff`

    Evidence: MIME sniffing protection

  5. 5

    Missing Referrer PolicyLow

    Why it matters: Without a Referrer-Policy, sensitive URL information might be leaked to external sites when users navigate away.

    Fix: Add Referrer-Policy header. Example: `Referrer-Policy: no-referrer`

    Evidence: Referrer policy

  6. 6

    Missing Permissions PolicyInfo

    Why it matters: Absence of a Permissions-Policy allows unintended use of sensitive browser features, potentially exploited by malicious scripts.

    Fix: Add Permissions-Policy header. Example: `Permissions-Policy: geolocation=(self)`

    Evidence: Permissions policy

What the checks found

  • FoundContent Security PolicyMedium

    None of the 609 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://surferseo.com/ → no content-security-policy
    • https://surferseo.com/events/from-prompt-to-post/ → no content-security-policy
    • https://surferseo.com/pricing/ → no content-security-policy
    • https://surferseo.com/enterprise/ → no content-security-policy
    • https://surferseo.com/blog/why-use-surfer/ → no content-security-policy
    • https://surferseo.com/updates/ → no content-security-policy
    • https://surferseo.com/mcp/ → no content-security-policy
    • https://surferseo.com/ai-tracker/ → no content-security-policy
    • https://surferseo.com/content-audit/ → no content-security-policy
    • https://surferseo.com/content-editor/ → no content-security-policy
    • https://surferseo.com/topical-map/ → no content-security-policy
    • https://surferseo.com/blog/sites/ → 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://surferseo.com/ → no x-frame-options
    • https://surferseo.com/events/from-prompt-to-post/ → no x-frame-options
    • https://surferseo.com/pricing/ → no x-frame-options
    • https://surferseo.com/enterprise/ → no x-frame-options
    • https://surferseo.com/blog/why-use-surfer/ → no x-frame-options
    • https://surferseo.com/updates/ → no x-frame-options
    • https://surferseo.com/mcp/ → no x-frame-options
    • https://surferseo.com/ai-tracker/ → no x-frame-options
    • https://surferseo.com/content-audit/ → no x-frame-options
    • https://surferseo.com/content-editor/ → no x-frame-options
    • https://surferseo.com/topical-map/ → no x-frame-options
    • https://surferseo.com/blog/sites/ → 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://surferseo.com/ → no x-content-type-options
    • https://surferseo.com/events/from-prompt-to-post/ → no x-content-type-options
    • https://surferseo.com/pricing/ → no x-content-type-options
    • https://surferseo.com/enterprise/ → no x-content-type-options
    • https://surferseo.com/blog/why-use-surfer/ → no x-content-type-options
    • https://surferseo.com/updates/ → no x-content-type-options
    • https://surferseo.com/mcp/ → no x-content-type-options
    • https://surferseo.com/ai-tracker/ → no x-content-type-options
    • https://surferseo.com/content-audit/ → no x-content-type-options
    • https://surferseo.com/content-editor/ → no x-content-type-options
    • https://surferseo.com/topical-map/ → no x-content-type-options
    • https://surferseo.com/blog/sites/ → 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://surferseo.com/ → no referrer-policy
    • https://surferseo.com/events/from-prompt-to-post/ → no referrer-policy
    • https://surferseo.com/pricing/ → no referrer-policy
    • https://surferseo.com/enterprise/ → no referrer-policy
    • https://surferseo.com/blog/why-use-surfer/ → no referrer-policy
    • https://surferseo.com/updates/ → no referrer-policy
    • https://surferseo.com/mcp/ → no referrer-policy
    • https://surferseo.com/ai-tracker/ → no referrer-policy
    • https://surferseo.com/content-audit/ → no referrer-policy
    • https://surferseo.com/content-editor/ → no referrer-policy
    • https://surferseo.com/topical-map/ → no referrer-policy
    • https://surferseo.com/blog/sites/ → 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://surferseo.com/ → no permissions-policy
    • https://surferseo.com/events/from-prompt-to-post/ → no permissions-policy
    • https://surferseo.com/pricing/ → no permissions-policy
    • https://surferseo.com/enterprise/ → no permissions-policy
    • https://surferseo.com/blog/why-use-surfer/ → no permissions-policy
    • https://surferseo.com/updates/ → no permissions-policy
    • https://surferseo.com/mcp/ → no permissions-policy
    • https://surferseo.com/ai-tracker/ → no permissions-policy
    • https://surferseo.com/content-audit/ → no permissions-policy
    • https://surferseo.com/content-editor/ → no permissions-policy
    • https://surferseo.com/topical-map/ → no permissions-policy
    • https://surferseo.com/blog/sites/ → no permissions-policy
  • FoundCookie flagsMedium

    3 of 4 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.

    • utm_source (set by https://surferseo.com/blog/ai-citation-report/?utm_source=chatgpt.com) lacks Secure, HttpOnly, SameSite
    • utm_medium (set by https://surferseo.com/blog/seo-competitive-analysis/?utm_term=&utm_campaign=215…) lacks Secure, HttpOnly, SameSite
    • utm_campaign (set by https://surferseo.com/blog/seo-competitive-analysis/?utm_term=&utm_campaign=215…) lacks Secure, HttpOnly, SameSite
  • NoteThird-party scripts

    Scripts run from 13 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.)

    • ajax.googleapis.com (40 script tags)
    • assets.surferseo.art (259 script tags)
    • d3e54v103j8qbb.cloudfront.net (33 script tags)
    • marketing-assets.surferseo.art (231 script tags)
    • cdn.jsdelivr.net (6 script tags)
    • cdn.finsweet.com (1 script tag)
    • hubspotv2.use1-marketplace-1p-apps-prod-red.if.webflow.services (2 script tags)
    • unpkg.com (3 script tags)
    • js-eu1.hsforms.net (1 script tag)
    • apis.google.com (1 script tag)
    • app.surferseo.com (3 script tags)
    • cdnjs.cloudflare.com (2 script tags)
8 checks passed, 1 not applicable
  • OKHTTPS

    All 609 crawled pages were served over HTTPS.

  • OKHTTP Strict Transport Security

    strict-transport-security is set on all 609 HTML pages.

  • OKSoftware version disclosure

    The Server header names a product without a version, and there is no X-Powered-By header.

  • OKMixed content

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

  • OKForms over HTTPS

    60 forms found, all on HTTPS pages posting to HTTPS addresses.

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

  • OKSensitive paths in robots.txt

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

  • 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 surferseo.com

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

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

Own surferseo.com?

surferseo.com scan 2026-10-01-0934 | DIY SEO Hub