Scanned sites / www.callranger.com / 2026-10-02-0231

www.callranger.com scan from 10/2/2026, 2:31:40 AM

Scan 2026-10-02-0231

Scanned 10/2/2026, 2:31:40 AM, finished 10/2/2026, 2:48:42 AM. Found on page 5 of brave web search results

Site: https://www.callranger.com/

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

85/ 100Good

On October 2, 2026 the Site Spider crawled 74 pages and 229 assets of www.callranger.com, starting from https://www.callranger.com/. It scored 85 out of 100, a good result. 11 of 16 checks found something to fix, led by meta descriptions (63), title tags (23), heavy assets (4); 4 checks passed. Most of the points went to meta descriptions (−7), title tags (−3.2), heavy assets (−2.4). 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: Medium4 medium, 3 low and 1 info findings. See the security findings ↓

Pages crawled
74
Assets fetched
229
Status
Completed
Checks with issues
11 of 16
CoverageComplete crawl

303 of 303 discovered URLs were fetched. The crawl reached everything it found. HTML only: nothing here ran JavaScript. 13 link destinations on other sites were checked.

  • Title tags23 issues
    23 of 65 pages have title issues. 7 noindex or canonicalized pages excluded.
    −3.2 points
  • Meta descriptions63 issues
    63 of 65 pages have meta description issues. 7 noindex or canonicalized pages excluded.
    −7 points
  • Headings3 issues
    3 of 65 pages have heading issues. 7 noindex or canonicalized pages excluded.
    −0.3 points
  • Broken links1 issue
    1 internal link point at 1 broken URL.
    −0.3 points
  • Links to other sites1 issue
    1 destination answered with an error, 8 could not be determined (timeouts, rate limits or refusals), of 13 destinations checked.
    −0.4 points
  • Redirects1 issue
    2 redirecting URLs, 0 of them chained.
    −0.1 points
  • Non-200 responses1 issue
    4 URLs did not return a 2xx response. 2 of them are pages, 1 with an error status; the rest are assets or redirects.
    −0.1 points
  • Rate limitedOK
    The site did not rate limit the crawler.
  • IndexabilityOK
    0 of 66 indexable pages have indexability warnings. 6 pages noindex by design.
  • Image alt textOK
    0 of 322 image references have no alt attribute. 161 use an empty alt (decorative), which is fine.
  • Heavy assets4 issues
    4 assets larger than 500 KB among 229 fetched assets.
    −2.4 points
  • Orphan pages3 issues
    3 pages have no internal links pointing at them.
    −0.2 points
  • Sitemap coverage19 issues
    7 sitemaps listing 49 URLs: 16 crawled pages missing, 0 listed URLs broken or redirecting, 3 reachable only via the sitemap.
    −1.6 points
  • Internal link countsOK
    Internal link counts for 72 pages.
  • Thin content1 issue
    1 of 65 pages have fewer than 200 words. 7 noindex or canonicalized pages excluded.
    −0.1 points
  • Duplicate contentOK
    0 groups of pages with identical HTML.

Where this scan sits among all scanned sites

1694 sites, median 80%, average 79%

www.callranger.com scores 85%, higher than 72% of the 1694 scanned sites. See the full ranking.

0511020%: 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%: 1 site42%: 0 sites43%: 1 site44%: 0 sites45%: 3 sites46%: 2 sites47%: 3 sites48%: 2 sites49%: 5 sites50%: 3 sites51%: 5 sites52%: 7 sites53%: 6 sites54%: 7 sites55%: 4 sites56%: 5 sites57%: 6 sites58%: 11 sites59%: 6 sites60%: 9 sites61%: 11 sites62%: 15 sites63%: 15 sites64%: 10 sites65%: 19 sites66%: 19 sites67%: 32 sites68%: 26 sites69%: 24 sites70%: 38 sites71%: 36 sites72%: 48 sites73%: 46 sites74%: 47 sites75%: 53 sites76%: 67 sites77%: 60 sites78%: 78 sites79%: 61 sites80%: 83 sites81%: 102 sites82%: 80 sites83%: 78 sites84%: 73 sites85%: 59 sites86%: 61 sites87%: 54 sites88%: 59 sites89%: 50 sites90%: 32 sites91%: 36 sites92%: 21 sites93%: 12 sites94%: 12 sites95%: 7 sites96%: 7 sites97%: 8 sites98%: 2 sites99%: 2 sites100%: 54 sites85% 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

Your website has good health but requires fixes for broken links, redirects, and several metadata issues. A focus on optimizing titles and descriptions will enhance search visibility.

  1. 1

    Fix Broken Links

    Why: Fixing broken links improves user experience and SEO.

    How: Remove or update the link to 'https://www.callranger.com/heating-services/' on the page at 'https://www.callranger.com/services/'.

    Checks: broken-links

  2. 2

    Resolve Redirects

    Why: Minimizing unnecessary redirects enhances speed and SEO performance.

    How: Consider updating the URL for 'https://www.callranger.com/services/heating-services/' directly or use a permanent 301 redirect to the final URL.

    Checks: redirects

  3. 3

    Update Meta Descriptions

    Why: Revising meta descriptions helps improve click-through rates and can enhance search rankings.

    How: Add concise, relevant descriptions for the 62 pages missing metadata based on the target keywords.

    Checks: meta-descriptions

  4. 4

    Fix Title Tag Issues

    Why: Correcting title tags will improve SERP appearance and relevance.

    How: Revise the 23 pages with long or duplicate title tags to be concise and unique, ideally under 60 characters.

    Checks: titles

  5. 5

    Address Headings Issues

    Why: Proper heading structure helps SEO and enhances content readability.

    How: Ensure each page has only one H1 and appropriately structure subsequent headings (H2, H3 etc.) for the 3 problematic pages.

    Checks: headings

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

Your website has several security vulnerabilities that need immediate attention, particularly regarding response headers that protect against various attacks. Implementing these fixes will enhance your site's security and protect user data.

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

    Missing HTTP Strict Transport Security (HSTS)Medium

    Why it matters: Without HSTS, attackers can intercept initial requests made without HTTPS.

    Fix: Add the header: Strict-Transport-Security: max-age=31536000; includeSubDomains

    Evidence: HTTP Strict Transport Security

  2. 2

    Missing Content Security Policy (CSP)Medium

    Why it matters: Without CSP, there are no restrictions on where scripts and resources can load from, increasing XSS risk.

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

    Evidence: Content Security Policy

  3. 3

    No Clickjacking Protection (X-Frame-Options)Medium

    Why it matters: Pages can be embedded in frames elsewhere, leading to clickjacking attacks.

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

    Evidence: Clickjacking protection

  4. 4

    Cookies Missing Secure FlagsMedium

    Why it matters: Lack of these flags allows potential interception and abuse of session cookies.

    Fix: Set flags: HttpOnly, Secure, and SameSite=Strict on the cookie.

    Evidence: Cookie flags

  5. 5

    Missing MIME Sniffing Protection (X-Content-Type-Options)Low

    Why it matters: Without this header, browsers may incorrectly execute files as scripts based on their content.

    Fix: Add the header: X-Content-Type-Options: nosniff

    Evidence: MIME sniffing protection

  6. 6

    Absence of Referrer PolicyLow

    Why it matters: Not specifying this allows full URL disclosures on link clicks, potentially leaking sensitive information.

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

    Evidence: Referrer policy

  7. 7

    Server Version DisclosureLow

    Why it matters: Exposing server version information helps attackers identify vulnerabilities.

    Fix: Remove the headers: Server: [your value], X-Powered-By: [your value]

    Evidence: Software version disclosure

  8. 8

    Missing Permissions PolicyInfo

    Why it matters: This header controls access to sensitive browser features, limiting potential attack vectors.

    Fix: Add the header: Permissions-Policy: fullscreen=(self)

    Evidence: Permissions policy

What the checks found

  • FoundHTTP Strict Transport SecurityMedium

    70 of 72 HTML pages send strict-transport-security. Without it a visitor who types the address without https:// can be intercepted on the first request.

    • https://www.callranger.com/wp-login.php → no strict-transport-security
    • https://www.callranger.com/wp-login.php?action=lostpassword → no strict-transport-security
  • FoundContent Security PolicyMedium

    None of the 72 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.callranger.com/ → no content-security-policy
    • https://www.callranger.com/ranger-careers/ → no content-security-policy
    • https://www.callranger.com/faq/ → no content-security-policy
    • https://www.callranger.com/why-ranger/bozeman-mt-licensed-plumbers/ → no content-security-policy
    • https://www.callranger.com/about-ranger-plumbing/ → no content-security-policy
    • https://www.callranger.com/recent-projects/ → no content-security-policy
    • https://www.callranger.com/why-ranger/ → no content-security-policy
    • https://www.callranger.com/why-ranger/unbeatable-plumbing-knowledge/ → no content-security-policy
    • https://www.callranger.com/why-ranger/we-always-answer-our-phones/ → no content-security-policy
    • https://www.callranger.com/services/ → no content-security-policy
    • https://www.callranger.com/services/bozeman-plumbing-repair/ → no content-security-policy
    • https://www.callranger.com/services/water-heater-repair/ → no content-security-policy
  • FoundClickjacking protectionMedium

    2 of 72 HTML pages send 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.callranger.com/ → no x-frame-options
    • https://www.callranger.com/ranger-careers/ → no x-frame-options
    • https://www.callranger.com/faq/ → no x-frame-options
    • https://www.callranger.com/why-ranger/bozeman-mt-licensed-plumbers/ → no x-frame-options
    • https://www.callranger.com/about-ranger-plumbing/ → no x-frame-options
    • https://www.callranger.com/recent-projects/ → no x-frame-options
    • https://www.callranger.com/why-ranger/ → no x-frame-options
    • https://www.callranger.com/why-ranger/unbeatable-plumbing-knowledge/ → no x-frame-options
    • https://www.callranger.com/why-ranger/we-always-answer-our-phones/ → no x-frame-options
    • https://www.callranger.com/services/ → no x-frame-options
    • https://www.callranger.com/services/bozeman-plumbing-repair/ → no x-frame-options
    • https://www.callranger.com/services/water-heater-repair/ → 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.callranger.com/ → no x-content-type-options
    • https://www.callranger.com/ranger-careers/ → no x-content-type-options
    • https://www.callranger.com/faq/ → no x-content-type-options
    • https://www.callranger.com/why-ranger/bozeman-mt-licensed-plumbers/ → no x-content-type-options
    • https://www.callranger.com/about-ranger-plumbing/ → no x-content-type-options
    • https://www.callranger.com/recent-projects/ → no x-content-type-options
    • https://www.callranger.com/why-ranger/ → no x-content-type-options
    • https://www.callranger.com/why-ranger/unbeatable-plumbing-knowledge/ → no x-content-type-options
    • https://www.callranger.com/why-ranger/we-always-answer-our-phones/ → no x-content-type-options
    • https://www.callranger.com/services/ → no x-content-type-options
    • https://www.callranger.com/services/bozeman-plumbing-repair/ → no x-content-type-options
    • https://www.callranger.com/services/water-heater-repair/ → 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.callranger.com/ → no referrer-policy
    • https://www.callranger.com/ranger-careers/ → no referrer-policy
    • https://www.callranger.com/faq/ → no referrer-policy
    • https://www.callranger.com/why-ranger/bozeman-mt-licensed-plumbers/ → no referrer-policy
    • https://www.callranger.com/about-ranger-plumbing/ → no referrer-policy
    • https://www.callranger.com/recent-projects/ → no referrer-policy
    • https://www.callranger.com/why-ranger/ → no referrer-policy
    • https://www.callranger.com/why-ranger/unbeatable-plumbing-knowledge/ → no referrer-policy
    • https://www.callranger.com/why-ranger/we-always-answer-our-phones/ → no referrer-policy
    • https://www.callranger.com/services/ → no referrer-policy
    • https://www.callranger.com/services/bozeman-plumbing-repair/ → no referrer-policy
    • https://www.callranger.com/services/water-heater-repair/ → 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.callranger.com/ → no permissions-policy
    • https://www.callranger.com/ranger-careers/ → no permissions-policy
    • https://www.callranger.com/faq/ → no permissions-policy
    • https://www.callranger.com/why-ranger/bozeman-mt-licensed-plumbers/ → no permissions-policy
    • https://www.callranger.com/about-ranger-plumbing/ → no permissions-policy
    • https://www.callranger.com/recent-projects/ → no permissions-policy
    • https://www.callranger.com/why-ranger/ → no permissions-policy
    • https://www.callranger.com/why-ranger/unbeatable-plumbing-knowledge/ → no permissions-policy
    • https://www.callranger.com/why-ranger/we-always-answer-our-phones/ → no permissions-policy
    • https://www.callranger.com/services/ → no permissions-policy
    • https://www.callranger.com/services/bozeman-plumbing-repair/ → no permissions-policy
    • https://www.callranger.com/services/water-heater-repair/ → no permissions-policy
  • FoundSoftware version disclosureLow

    Responses reveal the exact server or framework version, which lets an attacker look up known vulnerabilities for it without guessing.

    • server: Apache (303 responses)
    • x-powered-by: PHP/7.2.34 (86 responses)
  • FoundCookie flagsMedium

    1 of 1 cookie 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.

    • wordpress_test_cookie (set by https://www.callranger.com/wp-login.php) lacks HttpOnly, SameSite
  • NoteSensitive paths in robots.txt

    robots.txt lists 1 path that look private. robots.txt is public and does not restrict access, so it doubles as a map for anyone probing the site; those paths need real access control.

    • Disallow: /wp-admin/
7 checks passed
  • OKHTTPS

    All 72 crawled pages were served over HTTPS.

  • OKMixed content

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

  • OKForms over HTTPS

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

  • OKVulnerable JavaScript libraries

    2 library versions recognised, none with known vulnerabilities.

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

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

Own www.callranger.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.callranger.com. Removal needs no account and no proof of purchase.
www.callranger.com scan 2026-10-02-0231 | DIY SEO Hub