Scanned sites / ridgerock.ca

SEO report for ridgerock.ca

The latest Site Spider scan of ridgerock.ca, with 1 scan on record. Each scan is at its own address, for example /domain/ridgerock-ca/2026-10-02-2302.

Latest scan

Scanned 10/2/2026, 11:02:28 PM, finished 10/2/2026, 11:40:50 PM. Found on page 5 of brave web search results

Site: https://ridgerock.ca/

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

73/ 100Needs work

On October 2, 2026 the Site Spider crawled 17 pages and 440 assets of ridgerock.ca, starting from https://ridgerock.ca/. It scored 73 out of 100, a result that needs work. 8 of 16 checks found something to fix, led by heavy assets (68), thin content (8), sitemap coverage (8); 5 checks passed. Most of the points went to heavy assets (−6), thin content (−5.3), sitemap coverage (−4). 3 checks 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, 3 low and 1 info findings. See the security findings ↓

Pages crawled
17
Assets fetched
440
Status
Completed
Checks with issues
8 of 16
CoverageComplete crawl

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

  • Title tags4 issues
    4 of 12 pages have title issues.
    −3.3 points
  • Meta descriptions5 issues
    5 of 12 pages have meta description issues.
    −3.3 points
  • Headings2 issues
    2 of 12 pages have heading issues.
    −1 points
  • Broken linksOK
    0 internal links point at 0 broken URLs.
  • Links to other sites24 noted
    0 destinations answered with an error, 2 could not be determined (timeouts, rate limits or refusals), of 3 destinations checked.
  • Redirects5 issues
    6 redirecting URLs, 0 of them chained.
    −1.7 points
  • Non-200 responses6 noted
    6 URLs did not return a 2xx response. 5 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.
  • IndexabilityOK
    0 of 12 indexable pages have indexability warnings.
  • Image alt textOK
    0 of 164 image references have no alt attribute. 44 use an empty alt (decorative), which is fine.
  • Heavy assets68 issues
    68 assets larger than 500 KB among 440 fetched assets.
    −6 points
  • Orphan pages8 issues
    8 pages have no internal links pointing at them.
    −2.7 points
  • Sitemap coverage8 issues
    2 sitemaps listing 12 URLs: 0 crawled pages missing, 0 listed URLs broken or redirecting, 8 reachable only via the sitemap.
    −4 points
  • Internal link countsOK
    Internal link counts for 12 pages.
  • Thin content8 issues
    8 of 12 pages have fewer than 200 words.
    −5.3 points
  • Duplicate contentOK
    0 groups of pages with identical HTML.

Where this site sits among all scanned sites

1899 sites, median 80%, average 79%

ridgerock.ca scores 73%, higher than 23% of the 1899 scanned sites. See the full ranking.

0551090%: 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%: 1 site40%: 2 sites41%: 2 sites42%: 0 sites43%: 1 site44%: 0 sites45%: 4 sites46%: 2 sites47%: 3 sites48%: 2 sites49%: 7 sites50%: 4 sites51%: 5 sites52%: 8 sites53%: 6 sites54%: 7 sites55%: 4 sites56%: 7 sites57%: 6 sites58%: 15 sites59%: 7 sites60%: 10 sites61%: 12 sites62%: 17 sites63%: 16 sites64%: 11 sites65%: 21 sites66%: 22 sites67%: 37 sites68%: 30 sites69%: 26 sites70%: 39 sites71%: 40 sites72%: 56 sites73%: 52 sites74%: 49 sites75%: 61 sites76%: 76 sites77%: 72 sites78%: 88 sites79%: 69 sites80%: 91 sites81%: 109 sites82%: 84 sites83%: 86 sites84%: 87 sites85%: 65 sites86%: 74 sites87%: 63 sites88%: 64 sites89%: 54 sites90%: 36 sites91%: 36 sites92%: 29 sites93%: 15 sites94%: 13 sites95%: 13 sites96%: 7 sites97%: 8 sites98%: 2 sites99%: 2 sites100%: 55 sites73% 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 several critical areas needing attention, including redirects, title tags, meta descriptions, headings, and thin content. Addressing these will enhance your site's SEO performance.

  1. 1

    Fix Redirects

    Why: Redirects can affect user experience and page authority.

    How: Update the URLs to point directly to their final destinations.

    Checks: redirects

  2. 2

    Optimize Title Tags

    Why: Long title tags can impact search engine visibility.

    How: Shorten the title tags for overlong entries to under 60 characters.

    Checks: titles

  3. 3

    Add Missing Meta Descriptions

    Why: Meta descriptions improve click-through rates from search results.

    How: Create concise and engaging descriptions for pages missing them.

    Checks: meta-descriptions

  4. 4

    Add Missing Headings

    Why: Headings are important for both SEO and accessibility.

    How: Insert an H1 heading on the pages identified without one.

    Checks: headings

  5. 5

    Reduce Heavy Assets

    Why: Large assets can slow down your website's load time.

    How: Optimize and shrink the specified heavy assets.

    Checks: heavy-assets

  6. 6

    Address Thin Content

    Why: Thin content affects user engagement and SEO ranking.

    How: Expand content on pages with fewer than 200 words to improve value.

    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 several important security headers, exposing it to risks such as MITM attacks, script injection, and clickjacking. Implementing these headers will significantly enhance the site's security posture.

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

    Missing HTTP Strict Transport Security (HSTS)Medium

    Why it matters: Without HSTS, non-HTTPS requests can be intercepted.

    Fix: Add 'Strict-Transport-Security: max-age=31536000; includeSubDomains' to all responses.

    Evidence: HTTP Strict Transport Security

  2. 2

    No Content Security Policy (CSP)Medium

    Why it matters: Lack of CSP allows unrestricted script and style sources.

    Fix: Add 'Content-Security-Policy: default-src 'self';' to all pages.

    Evidence: Content Security Policy

  3. 3

    Missing X-Frame-Options HeaderMedium

    Why it matters: Absence of X-Frame-Options allows clickjacking attacks.

    Fix: Add 'X-Frame-Options: DENY' to all pages.

    Evidence: Clickjacking protection

  4. 4

    Missing X-Content-Type-Options HeaderLow

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

    Fix: Add 'X-Content-Type-Options: nosniff' to all responses.

    Evidence: MIME sniffing protection

  5. 5

    No Referrer PolicyLow

    Why it matters: Lack of Referrer-Policy reveals full URLs to external sites.

    Fix: Add 'Referrer-Policy: no-referrer' to all pages.

    Evidence: Referrer policy

  6. 6

    Server Banner DisclosureLow

    Why it matters: Exposing server versions can aid attackers in finding vulnerabilities.

    Fix: Remove or obscure 'Server:' and 'X-Powered-By:' headers from responses.

    Evidence: Software version disclosure

  7. 7

    Missing Permissions Policy HeaderInfo

    Why it matters: Without this, browser features could be misused by injected scripts.

    Fix: Add 'Permissions-Policy: autoplay=(self), geolocation=(self)' to all pages.

    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://ridgerock.ca/ → no strict-transport-security
    • https://ridgerock.ca/portfolio/food-beverage-photography/ → no strict-transport-security
    • https://ridgerock.ca/portfolio/product-and-commercial-photography/ → no strict-transport-security
    • https://ridgerock.ca/portfolio/people-and-their-work-photography/ → no strict-transport-security
    • https://ridgerock.ca/portfolio/on-location-photography/ → no strict-transport-security
    • https://ridgerock.ca/portfolio/cookbook-and-packaging-photography/ → no strict-transport-security
    • https://ridgerock.ca/portfolio/ → no strict-transport-security
    • https://ridgerock.ca/about/ → no strict-transport-security
    • https://ridgerock.ca/thanks-for-reaching-out/ → no strict-transport-security
    • https://ridgerock.ca/book-time-thanks/ → no strict-transport-security
    • https://ridgerock.ca/food-beverage-product-photography/ → no strict-transport-security
    • https://ridgerock.ca/contact/ → no strict-transport-security
  • FoundContent Security PolicyMedium

    None of the 12 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://ridgerock.ca/ → no content-security-policy
    • https://ridgerock.ca/portfolio/food-beverage-photography/ → no content-security-policy
    • https://ridgerock.ca/portfolio/product-and-commercial-photography/ → no content-security-policy
    • https://ridgerock.ca/portfolio/people-and-their-work-photography/ → no content-security-policy
    • https://ridgerock.ca/portfolio/on-location-photography/ → no content-security-policy
    • https://ridgerock.ca/portfolio/cookbook-and-packaging-photography/ → no content-security-policy
    • https://ridgerock.ca/portfolio/ → no content-security-policy
    • https://ridgerock.ca/about/ → no content-security-policy
    • https://ridgerock.ca/thanks-for-reaching-out/ → no content-security-policy
    • https://ridgerock.ca/book-time-thanks/ → no content-security-policy
    • https://ridgerock.ca/food-beverage-product-photography/ → no content-security-policy
    • https://ridgerock.ca/contact/ → 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://ridgerock.ca/ → no x-frame-options
    • https://ridgerock.ca/portfolio/food-beverage-photography/ → no x-frame-options
    • https://ridgerock.ca/portfolio/product-and-commercial-photography/ → no x-frame-options
    • https://ridgerock.ca/portfolio/people-and-their-work-photography/ → no x-frame-options
    • https://ridgerock.ca/portfolio/on-location-photography/ → no x-frame-options
    • https://ridgerock.ca/portfolio/cookbook-and-packaging-photography/ → no x-frame-options
    • https://ridgerock.ca/portfolio/ → no x-frame-options
    • https://ridgerock.ca/about/ → no x-frame-options
    • https://ridgerock.ca/thanks-for-reaching-out/ → no x-frame-options
    • https://ridgerock.ca/book-time-thanks/ → no x-frame-options
    • https://ridgerock.ca/food-beverage-product-photography/ → no x-frame-options
    • https://ridgerock.ca/contact/ → 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://ridgerock.ca/ → no x-content-type-options
    • https://ridgerock.ca/portfolio/food-beverage-photography/ → no x-content-type-options
    • https://ridgerock.ca/portfolio/product-and-commercial-photography/ → no x-content-type-options
    • https://ridgerock.ca/portfolio/people-and-their-work-photography/ → no x-content-type-options
    • https://ridgerock.ca/portfolio/on-location-photography/ → no x-content-type-options
    • https://ridgerock.ca/portfolio/cookbook-and-packaging-photography/ → no x-content-type-options
    • https://ridgerock.ca/portfolio/ → no x-content-type-options
    • https://ridgerock.ca/about/ → no x-content-type-options
    • https://ridgerock.ca/thanks-for-reaching-out/ → no x-content-type-options
    • https://ridgerock.ca/book-time-thanks/ → no x-content-type-options
    • https://ridgerock.ca/food-beverage-product-photography/ → no x-content-type-options
    • https://ridgerock.ca/contact/ → 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://ridgerock.ca/ → no referrer-policy
    • https://ridgerock.ca/portfolio/food-beverage-photography/ → no referrer-policy
    • https://ridgerock.ca/portfolio/product-and-commercial-photography/ → no referrer-policy
    • https://ridgerock.ca/portfolio/people-and-their-work-photography/ → no referrer-policy
    • https://ridgerock.ca/portfolio/on-location-photography/ → no referrer-policy
    • https://ridgerock.ca/portfolio/cookbook-and-packaging-photography/ → no referrer-policy
    • https://ridgerock.ca/portfolio/ → no referrer-policy
    • https://ridgerock.ca/about/ → no referrer-policy
    • https://ridgerock.ca/thanks-for-reaching-out/ → no referrer-policy
    • https://ridgerock.ca/book-time-thanks/ → no referrer-policy
    • https://ridgerock.ca/food-beverage-product-photography/ → no referrer-policy
    • https://ridgerock.ca/contact/ → 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://ridgerock.ca/ → no permissions-policy
    • https://ridgerock.ca/portfolio/food-beverage-photography/ → no permissions-policy
    • https://ridgerock.ca/portfolio/product-and-commercial-photography/ → no permissions-policy
    • https://ridgerock.ca/portfolio/people-and-their-work-photography/ → no permissions-policy
    • https://ridgerock.ca/portfolio/on-location-photography/ → no permissions-policy
    • https://ridgerock.ca/portfolio/cookbook-and-packaging-photography/ → no permissions-policy
    • https://ridgerock.ca/portfolio/ → no permissions-policy
    • https://ridgerock.ca/about/ → no permissions-policy
    • https://ridgerock.ca/thanks-for-reaching-out/ → no permissions-policy
    • https://ridgerock.ca/book-time-thanks/ → no permissions-policy
    • https://ridgerock.ca/food-beverage-product-photography/ → no permissions-policy
    • https://ridgerock.ca/contact/ → 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: nginx (457 responses)
    • x-powered-by: PHP/7.3.33 (21 responses)
  • NoteThird-party scripts

    Scripts run from 1 other domain 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.)

    • www.googletagmanager.com (36 script tags)
7 checks passed, 1 not applicable
  • OKHTTPS

    All 12 crawled pages were served over HTTPS.

  • OKMixed content

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

  • OKForms over HTTPS

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

  • OKVulnerable JavaScript libraries

    1 library version 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.

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

No other scans of this site yet.

Sites scoring near ridgerock.ca

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

Own ridgerock.ca?

ridgerock.ca SEO report | DIY SEO Hub