Scanned sites / rbpa.ca / 2026-10-01-1622

rbpa.ca scan from 2026-10-01 16:22:45 UTC DR 1

A newer scan exists. See the latest report for rbpa.ca.

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

Scan 2026-10-01-1622

Scanned 2026-10-01 16:22:45 UTC, finished 2026-10-01 18:31:25 UTC. Found on page 5 of brave web search results

Site: https://rbpa.ca/

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

79/ 100Good

On October 1, 2026 the Site Spider crawled 129 pages and 379 assets of rbpa.ca, starting from https://rbpa.ca/. It scored 79 out of 100, a good result. 8 of 27 checks found something to fix, led by heavy assets (15), meta descriptions (54), title tags (34); 8 checks passed. Most of the points went to heavy assets (−6), meta descriptions (−4.3), title tags (−3.4). 11 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: Medium3 medium, 4 low and 2 info findings. See the security findings ↓

Pages crawled
129
Assets fetched
379
Status
Completed
Checks with issues
8 of 27
CoverageComplete crawl

508 of 509 discovered URLs were fetched, 1 blocked by robots.txt. The crawl reached everything it found. HTML only: nothing here ran JavaScript. 28 link destinations on other sites were checked.

  • Title tags34 issues
    34 of 79 pages have title issues. 21 noindex or canonicalized pages excluded.
    −3.4 points
  • Meta descriptions54 issues
    54 of 79 pages have meta description issues. 21 noindex or canonicalized pages excluded.
    −4.3 points
  • Headings24 issues
    24 of 79 pages have heading issues. 21 noindex or canonicalized pages excluded.
    −1.4 points
  • Broken linksOK
    0 internal links point at 0 broken URLs.
  • Links to other sites228 noted
    0 destinations answered with an error, 20 could not be determined (timeouts, rate limits or refusals), of 28 destinations checked.
  • Redirects25 issues
    30 redirecting URLs, 0 of them chained.
    −1 points
  • Non-200 responses33 noted
    33 URLs did not return a 2xx response. 29 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.
  • Indexability21 issues
    21 of 84 indexable pages have indexability warnings. 16 pages noindex by design. 16 noindex pages are listed in the sitemap, which asks search engines both to visit and to ignore them.
    −2.1 points
  • Image alt textOK
    0 of 2005 image references have no alt attribute. 273 use an empty alt (decorative), which is fine.
  • Heavy assets15 issues
    15 assets larger than 500 KB among 379 fetched assets.
    −6 points
  • Orphan pages25 issues
    25 pages have no internal links pointing at them.
    −1 points
  • Sitemap coverage28 issues
    7 sitemaps listing 99 URLs: 0 crawled pages missing, 4 listed URLs broken or redirecting, 8 reachable only via the sitemap.
    −1.7 points
  • Internal link counts2 noted
    Internal link counts for 100 pages; 2 worth a look.
  • Thin contentOK
    0 of 79 pages have fewer than 200 words. 21 noindex or canonicalized pages excluded.
  • Duplicate contentOK
    0 groups of pages with identical HTML.
  • URL format7 noted
    7 of 129 page URLs are harder to read, share or cache than they need to be.
  • Canonicals21 noted
    21 of 100 pages have a canonical worth checking.
  • Robots directives100 noted
    100 pages carry a robots directive; 0 carry none.
  • Anchor text19 noted
    19 destinations are linked without useful anchor text, or with nofollow.
  • Title and heading structure36 noted
    36 of 79 pages could use the title, heading and snippet space better. 21 noindex or canonicalized pages excluded.
  • Image weight and alt length42 noted
    42 images over 100 KB; 0 with alt text over 100 characters.
  • Response anomalies6 noted
    6 URLs answered in a way worth looking at.
  • 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 100 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; 12 response headers recorded across 508 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 100 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 68 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 scan sits among all scanned sites

2909 sites, median 80%, average 79%

rbpa.ca scores 79%, higher than 44% of the 2909 scanned sites. See the full ranking.

0761520%: 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%: 2 sites37%: 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%: 16 sites61%: 13 sites62%: 20 sites63%: 29 sites64%: 22 sites65%: 33 sites66%: 43 sites67%: 43 sites68%: 42 sites69%: 55 sites70%: 48 sites71%: 79 sites72%: 77 sites73%: 82 sites74%: 82 sites75%: 87 sites76%: 95 sites77%: 109 sites78%: 134 sites79%: 112 sites80%: 129 sites81%: 123 sites82%: 136 sites83%: 121 sites84%: 131 sites85%: 106 sites86%: 97 sites87%: 95 sites88%: 82 sites89%: 77 sites90%: 57 sites91%: 61 sites92%: 44 sites93%: 32 sites94%: 25 sites95%: 17 sites96%: 18 sites97%: 16 sites98%: 8 sites99%: 3 sites100%: 152 sites79% 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 (rules v4). 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 achieved a good health score of 79/100, but there are several areas for improvement. Prioritizing fixes will enhance user experience and SEO performance.

  1. 1

    Fix Redirects

    Why: Redirects can lead to a poor user experience and hinder SEO.

    How: Update the 30 URLs for direct access instead of redirection where possible.

    Checks: redirects

  2. 2

    Address Non-200 Responses

    Why: Non-200 responses can negatively impact user navigation and SEO.

    How: Resolve the 33 URLs not returning a 2xx response, ensuring they are live and accessible.

    Checks: status-codes

  3. 3

    Optimize Title Tags

    Why: Improving title tags enhances search visibility and click-through rates.

    How: Revise 34 pages with title issues to ensure each is unique and within optimal length.

    Checks: titles

  4. 4

    Update Meta Descriptions

    Why: Accurate meta descriptions can improve click-through rates from search results.

    How: Create and implement unique meta descriptions for the 54 pages in question.

    Checks: meta-descriptions

  5. 5

    Fix Heading Issues

    Why: Proper heading structure aids in content clarity and SEO.

    How: Adjust heading tags on 24 pages to ensure only one H1 tag per page and appropriate hierarchy.

    Checks: headings

  6. 6

    Resolve Sitemap Coverage Issues

    Why: Improper sitemap entries affect indexing and visibility.

    How: Update or remove the 4 sitemap URLs that are broken or redirecting.

    Checks: sitemap-coverage

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 has several security gaps that need attention, especially regarding HTTP headers. Key protections against interception, embedding, and potentially malicious scripts are missing. Implementing the recommended changes will enhance security for your users.

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

    Missing HTTP Strict Transport Security (HSTS)Medium

    Why it matters: Without HSTS, an initial request may be intercepted if a user types the URL 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: A lack of CSP allows scripts and styles to load from potentially harmful sources.

    Fix: Implement a CSP header like: Content-Security-Policy: default-src 'self';

    Evidence: Content Security Policy

  3. 3

    Missing X-Frame-Options (Clickjacking protection)Medium

    Why it matters: Pages can be embedded in another site, exposing them to clickjacking attacks.

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

    Evidence: Clickjacking protection

  4. 4

    Missing X-Content-Type-Options (MIME sniffing protection)Low

    Why it matters: Without this header, browsers may incorrectly interpret file types, risking security.

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

    Evidence: MIME sniffing protection

  5. 5

    Missing Referrer PolicyLow

    Why it matters: Without this policy, sensitive information may be leaked to third-party sites.

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

    Evidence: Referrer policy

  6. 6

    X-Powered-By DisclosureLow

    Why it matters: Disclosing the framework used can give attackers insights for targeting vulnerabilities.

    Fix: Remove or modify the X-Powered-By header.

    Evidence: Software version disclosure

  7. 7

    Third-party Scripts without Subresource IntegrityLow

    Why it matters: Compromise of third-party scripts could change site behavior maliciously.

    Fix: Consider implementing CSP or check if SRI is available for third-party scripts.

    Evidence: Third-party scripts

  8. 8

    Missing Permissions PolicyInfo

    Why it matters: This could allow injected scripts more access than necessary.

    Fix: Add the header: Permissions-Policy: not allowed.

    Evidence: Permissions policy

  9. 9

    Potentially Sensitive Paths in robots.txtInfo

    Why it matters: Sensitive paths may be exposed to individuals probing the site.

    Fix: Restrict access to /wp-admin/ through proper authentication measures.

    Evidence: Sensitive paths in robots.txt

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://rbpa.ca/ → no strict-transport-security
    • https://rbpa.ca/industries/ → no strict-transport-security
    • https://rbpa.ca/professionals/ → no strict-transport-security
    • https://rbpa.ca/dentists/ → no strict-transport-security
    • https://rbpa.ca/doctors/ → no strict-transport-security
    • https://rbpa.ca/lawyers/ → no strict-transport-security
    • https://rbpa.ca/architects/ → no strict-transport-security
    • https://rbpa.ca/engineers/ → no strict-transport-security
    • https://rbpa.ca/optometrists/ → no strict-transport-security
    • https://rbpa.ca/private-corporations/ → no strict-transport-security
    • https://rbpa.ca/real-estate/ → no strict-transport-security
    • https://rbpa.ca/technology/ → no strict-transport-security
  • FoundContent Security PolicyMedium

    None of the 100 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://rbpa.ca/ → no content-security-policy
    • https://rbpa.ca/industries/ → no content-security-policy
    • https://rbpa.ca/professionals/ → no content-security-policy
    • https://rbpa.ca/dentists/ → no content-security-policy
    • https://rbpa.ca/doctors/ → no content-security-policy
    • https://rbpa.ca/lawyers/ → no content-security-policy
    • https://rbpa.ca/architects/ → no content-security-policy
    • https://rbpa.ca/engineers/ → no content-security-policy
    • https://rbpa.ca/optometrists/ → no content-security-policy
    • https://rbpa.ca/private-corporations/ → no content-security-policy
    • https://rbpa.ca/real-estate/ → no content-security-policy
    • https://rbpa.ca/technology/ → 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://rbpa.ca/ → no x-frame-options
    • https://rbpa.ca/industries/ → no x-frame-options
    • https://rbpa.ca/professionals/ → no x-frame-options
    • https://rbpa.ca/dentists/ → no x-frame-options
    • https://rbpa.ca/doctors/ → no x-frame-options
    • https://rbpa.ca/lawyers/ → no x-frame-options
    • https://rbpa.ca/architects/ → no x-frame-options
    • https://rbpa.ca/engineers/ → no x-frame-options
    • https://rbpa.ca/optometrists/ → no x-frame-options
    • https://rbpa.ca/private-corporations/ → no x-frame-options
    • https://rbpa.ca/real-estate/ → no x-frame-options
    • https://rbpa.ca/technology/ → 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://rbpa.ca/ → no x-content-type-options
    • https://rbpa.ca/industries/ → no x-content-type-options
    • https://rbpa.ca/professionals/ → no x-content-type-options
    • https://rbpa.ca/dentists/ → no x-content-type-options
    • https://rbpa.ca/doctors/ → no x-content-type-options
    • https://rbpa.ca/lawyers/ → no x-content-type-options
    • https://rbpa.ca/architects/ → no x-content-type-options
    • https://rbpa.ca/engineers/ → no x-content-type-options
    • https://rbpa.ca/optometrists/ → no x-content-type-options
    • https://rbpa.ca/private-corporations/ → no x-content-type-options
    • https://rbpa.ca/real-estate/ → no x-content-type-options
    • https://rbpa.ca/technology/ → 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://rbpa.ca/ → no referrer-policy
    • https://rbpa.ca/industries/ → no referrer-policy
    • https://rbpa.ca/professionals/ → no referrer-policy
    • https://rbpa.ca/dentists/ → no referrer-policy
    • https://rbpa.ca/doctors/ → no referrer-policy
    • https://rbpa.ca/lawyers/ → no referrer-policy
    • https://rbpa.ca/architects/ → no referrer-policy
    • https://rbpa.ca/engineers/ → no referrer-policy
    • https://rbpa.ca/optometrists/ → no referrer-policy
    • https://rbpa.ca/private-corporations/ → no referrer-policy
    • https://rbpa.ca/real-estate/ → no referrer-policy
    • https://rbpa.ca/technology/ → 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://rbpa.ca/ → no permissions-policy
    • https://rbpa.ca/industries/ → no permissions-policy
    • https://rbpa.ca/professionals/ → no permissions-policy
    • https://rbpa.ca/dentists/ → no permissions-policy
    • https://rbpa.ca/doctors/ → no permissions-policy
    • https://rbpa.ca/lawyers/ → no permissions-policy
    • https://rbpa.ca/architects/ → no permissions-policy
    • https://rbpa.ca/engineers/ → no permissions-policy
    • https://rbpa.ca/optometrists/ → no permissions-policy
    • https://rbpa.ca/private-corporations/ → no permissions-policy
    • https://rbpa.ca/real-estate/ → no permissions-policy
    • https://rbpa.ca/technology/ → no permissions-policy
  • NoteSoftware version disclosure

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

    • server: nginx (508 responses)
    • x-powered-by: WP Engine (137 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.)

    • cdn.trustindex.io (24 script tags)
  • 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/
6 checks passed, 1 not applicable
  • OKHTTPS

    All 100 crawled pages were served over HTTPS.

  • OKMixed content

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

  • OKForms over HTTPS

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

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

Sites scoring near rbpa.ca

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

Own rbpa.ca?