Scanned sites / www.bellerivedental.ca / 2026-09-22-1745

www.bellerivedental.ca scan from 9/22/2026, 5:45:30 PM

A newer scan exists. See the latest report for www.bellerivedental.ca.

Scan 2026-09-22-1745

Scanned 9/22/2026, 5:45:30 PM, finished 9/22/2026, 6:43:38 PM. Found with openstreetmap overpass

Site: https://www.bellerivedental.ca/

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

89/ 100Good

On September 22, 2026 the Site Spider crawled 142 pages and 859 assets of www.bellerivedental.ca, starting from https://www.bellerivedental.ca/. It scored 89 out of 100, a good result. 6 of 14 checks found something to fix, led by title tags (37), meta descriptions (24), heavy assets (24); 8 checks passed. 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
142
Assets fetched
859
Status
Completed
Checks with issues
6 of 14
  • Title tags37 issues
    37 of 119 pages have title issues. 13 noindex or canonicalized pages excluded.
  • Meta descriptions24 issues
    24 of 119 pages have meta description issues. 13 noindex or canonicalized pages excluded.
  • HeadingsOK
    0 of 119 pages have heading issues. 13 noindex or canonicalized pages excluded.
  • Broken linksOK
    0 internal links point at 0 broken URLs.
  • Redirects12 issues
    11 redirecting URLs, 5 of them chained.
  • Non-200 responsesOK
    16 URLs did not return a 2xx response.
  • Rate limitedOK
    The site did not rate limit the crawler.
  • IndexabilityOK
    0 of 132 indexable pages have indexability warnings.
  • Image alt textOK
    0 of 1081 image references have no alt attribute. 6 use an empty alt (decorative), which is fine.
  • Heavy assets24 issues
    24 assets larger than 500 KB among the 100 heaviest.
  • Orphan pages1 issue
    1 page have no internal links pointing at them.
  • Sitemap coverage1 issue
    1 sitemap listing 118 URLs: 1 crawled page missing, 0 listed URLs broken or redirecting, 0 reachable only via the sitemap.
  • Thin contentOK
    0 of 119 pages have fewer than 200 words. 13 noindex or canonicalized pages excluded.
  • Duplicate contentOK
    0 groups of pages with identical HTML.

Where this scan sits among all scanned sites

1175 sites, median 82%, average 80%

www.bellerivedental.ca scores 89%, higher than 80% of the 1175 scanned sites. See the full ranking.

030590%: 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%: 1 site36%: 1 site37%: 0 sites38%: 0 sites39%: 0 sites40%: 0 sites41%: 0 sites42%: 0 sites43%: 0 sites44%: 0 sites45%: 2 sites46%: 1 site47%: 1 site48%: 1 site49%: 0 sites50%: 3 sites51%: 4 sites52%: 2 sites53%: 1 site54%: 3 sites55%: 1 site56%: 2 sites57%: 3 sites58%: 7 sites59%: 3 sites60%: 6 sites61%: 9 sites62%: 12 sites63%: 4 sites64%: 9 sites65%: 9 sites66%: 9 sites67%: 15 sites68%: 28 sites69%: 15 sites70%: 26 sites71%: 24 sites72%: 25 sites73%: 27 sites74%: 33 sites75%: 27 sites76%: 40 sites77%: 41 sites78%: 35 sites79%: 35 sites80%: 49 sites81%: 56 sites82%: 53 sites83%: 48 sites84%: 59 sites85%: 51 sites86%: 47 sites87%: 51 sites88%: 57 sites89%: 39 sites90%: 57 sites91%: 39 sites92%: 24 sites93%: 19 sites94%: 14 sites95%: 9 sites96%: 11 sites97%: 4 sites98%: 3 sites99%: 1 site100%: 17 sites89% 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 health score is solid, but there are several areas to improve, particularly with redirects and title/meta tag issues. Addressing these will enhance SEO and user experience.

  1. 1

    Fix Redirects

    Why: Chained redirects can slow down website speed and hurt user experience.

    How: Simplify redirects by pointing each old URL directly to its final destination URL.

    Checks: redirects

  2. 2

    Resolve Non-200 Responses

    Why: URLs returning errors can lead to a poor user experience and SEO penalties.

    How: Identify non-200 URLs and fix their configurations to return a 200 status.

    Checks: status-codes

  3. 3

    Optimize Title Tags

    Why: Long title tags can negatively impact SERP visibility.

    How: Revise 37 titles to be under 60 characters while still being descriptive.

    Checks: titles

  4. 4

    Edit Meta Descriptions

    Why: Meta descriptions over 160 characters can diminish click-through rates.

    How: Shorten 24 descriptions to 160 characters or less, ensuring they remain informative.

    Checks: meta-descriptions

  5. 5

    Reduce Heavy Assets

    Why: Large assets can slow down page load times, affecting SEO and user experience.

    How: Compress images above 500 KB using tools like TinyPNG or ImageOptim.

    Checks: heavy-assets

  6. 6

    Link to Orphan Page

    Why: Orphan pages are not accessible, which reduces their discoverability.

    How: Add internal links to the orphan page from other relevant pages.

    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

Your website has several crucial security issues that need urgent attention. High-risk areas include missing security headers such as HSTS, Content Security Policy, and X-Frame-Options, which leave your site exposed to various attacks. Additionally, a Google API key is publicly visible, which could allow unauthorized access if not properly restricted. It's important to implement these fixes promptly.

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

    Missing HSTS HeaderMedium

    Why it matters: Absence of HSTS allows man-in-the-middle attacks on initial requests.

    Fix: Add the header 'Strict-Transport-Security: max-age=63072000; includeSubDomains; preload'.

    Evidence: HTTP Strict Transport Security

  2. 2

    Missing Content Security PolicyMedium

    Why it matters: No CSP means the site is vulnerable to script injection attacks.

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

    Evidence: Content Security Policy

  3. 3

    Missing X-Frame-OptionsMedium

    Why it matters: Without X-Frame-Options, clickjacking attacks are possible.

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

    Evidence: Clickjacking protection

  4. 4

    Exposed Google API KeyMedium

    Why it matters: Publicly accessible keys can be abused to access services.

    Fix: Restrict the Google API key by HTTP referrer in the Google Cloud console.

    Evidence: Keys and secrets in page code

  5. 5

    Missing X-Content-Type-Options HeaderLow

    Why it matters: Not setting this header can allow browsers to interpret files as scripts.

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

    Evidence: MIME sniffing protection

  6. 6

    Missing Referrer PolicyLow

    Why it matters: Lack of this policy can lead to leaking sensitive information in HTTP referrer headers.

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

    Evidence: Referrer policy

  7. 7

    Server Version DisclosureLow

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

    Fix: Remove or modify the 'Server' and 'X-Powered-By' headers to hide version details.

    Evidence: Software version disclosure

  8. 8

    Missing Permissions PolicyInfo

    Why it matters: Without this header, potential browser features might be exploited.

    Fix: Add the header 'Permissions-Policy: interest-cohort=()'.

    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://www.bellerivedental.ca/ → no strict-transport-security
    • https://www.bellerivedental.ca/canadian-dental-care-plan/ → no strict-transport-security
    • https://www.bellerivedental.ca/about/ → no strict-transport-security
    • https://www.bellerivedental.ca/faqs/ → no strict-transport-security
    • https://www.bellerivedental.ca/privacy-policy/ → no strict-transport-security
    • https://www.bellerivedental.ca/weekend-dentist-edmonton/ → no strict-transport-security
    • https://www.bellerivedental.ca/service/our-services/ → no strict-transport-security
    • https://www.bellerivedental.ca/service/general-dentistry/ → no strict-transport-security
    • https://www.bellerivedental.ca/service/dental-cleanings/ → no strict-transport-security
    • https://www.bellerivedental.ca/service/dental-exams/ → no strict-transport-security
    • https://www.bellerivedental.ca/service/root-canal-therapy/ → no strict-transport-security
    • https://www.bellerivedental.ca/service/cosmetic-dentistry/ → no strict-transport-security
  • FoundContent Security PolicyMedium

    None of the 132 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.bellerivedental.ca/ → no content-security-policy
    • https://www.bellerivedental.ca/canadian-dental-care-plan/ → no content-security-policy
    • https://www.bellerivedental.ca/about/ → no content-security-policy
    • https://www.bellerivedental.ca/faqs/ → no content-security-policy
    • https://www.bellerivedental.ca/privacy-policy/ → no content-security-policy
    • https://www.bellerivedental.ca/weekend-dentist-edmonton/ → no content-security-policy
    • https://www.bellerivedental.ca/service/our-services/ → no content-security-policy
    • https://www.bellerivedental.ca/service/general-dentistry/ → no content-security-policy
    • https://www.bellerivedental.ca/service/dental-cleanings/ → no content-security-policy
    • https://www.bellerivedental.ca/service/dental-exams/ → no content-security-policy
    • https://www.bellerivedental.ca/service/root-canal-therapy/ → no content-security-policy
    • https://www.bellerivedental.ca/service/cosmetic-dentistry/ → 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.bellerivedental.ca/ → no x-frame-options
    • https://www.bellerivedental.ca/canadian-dental-care-plan/ → no x-frame-options
    • https://www.bellerivedental.ca/about/ → no x-frame-options
    • https://www.bellerivedental.ca/faqs/ → no x-frame-options
    • https://www.bellerivedental.ca/privacy-policy/ → no x-frame-options
    • https://www.bellerivedental.ca/weekend-dentist-edmonton/ → no x-frame-options
    • https://www.bellerivedental.ca/service/our-services/ → no x-frame-options
    • https://www.bellerivedental.ca/service/general-dentistry/ → no x-frame-options
    • https://www.bellerivedental.ca/service/dental-cleanings/ → no x-frame-options
    • https://www.bellerivedental.ca/service/dental-exams/ → no x-frame-options
    • https://www.bellerivedental.ca/service/root-canal-therapy/ → no x-frame-options
    • https://www.bellerivedental.ca/service/cosmetic-dentistry/ → 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.bellerivedental.ca/ → no x-content-type-options
    • https://www.bellerivedental.ca/canadian-dental-care-plan/ → no x-content-type-options
    • https://www.bellerivedental.ca/about/ → no x-content-type-options
    • https://www.bellerivedental.ca/faqs/ → no x-content-type-options
    • https://www.bellerivedental.ca/privacy-policy/ → no x-content-type-options
    • https://www.bellerivedental.ca/weekend-dentist-edmonton/ → no x-content-type-options
    • https://www.bellerivedental.ca/service/our-services/ → no x-content-type-options
    • https://www.bellerivedental.ca/service/general-dentistry/ → no x-content-type-options
    • https://www.bellerivedental.ca/service/dental-cleanings/ → no x-content-type-options
    • https://www.bellerivedental.ca/service/dental-exams/ → no x-content-type-options
    • https://www.bellerivedental.ca/service/root-canal-therapy/ → no x-content-type-options
    • https://www.bellerivedental.ca/service/cosmetic-dentistry/ → 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.bellerivedental.ca/ → no referrer-policy
    • https://www.bellerivedental.ca/canadian-dental-care-plan/ → no referrer-policy
    • https://www.bellerivedental.ca/about/ → no referrer-policy
    • https://www.bellerivedental.ca/faqs/ → no referrer-policy
    • https://www.bellerivedental.ca/privacy-policy/ → no referrer-policy
    • https://www.bellerivedental.ca/weekend-dentist-edmonton/ → no referrer-policy
    • https://www.bellerivedental.ca/service/our-services/ → no referrer-policy
    • https://www.bellerivedental.ca/service/general-dentistry/ → no referrer-policy
    • https://www.bellerivedental.ca/service/dental-cleanings/ → no referrer-policy
    • https://www.bellerivedental.ca/service/dental-exams/ → no referrer-policy
    • https://www.bellerivedental.ca/service/root-canal-therapy/ → no referrer-policy
    • https://www.bellerivedental.ca/service/cosmetic-dentistry/ → 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.bellerivedental.ca/ → no permissions-policy
    • https://www.bellerivedental.ca/canadian-dental-care-plan/ → no permissions-policy
    • https://www.bellerivedental.ca/about/ → no permissions-policy
    • https://www.bellerivedental.ca/faqs/ → no permissions-policy
    • https://www.bellerivedental.ca/privacy-policy/ → no permissions-policy
    • https://www.bellerivedental.ca/weekend-dentist-edmonton/ → no permissions-policy
    • https://www.bellerivedental.ca/service/our-services/ → no permissions-policy
    • https://www.bellerivedental.ca/service/general-dentistry/ → no permissions-policy
    • https://www.bellerivedental.ca/service/dental-cleanings/ → no permissions-policy
    • https://www.bellerivedental.ca/service/dental-exams/ → no permissions-policy
    • https://www.bellerivedental.ca/service/root-canal-therapy/ → no permissions-policy
    • https://www.bellerivedental.ca/service/cosmetic-dentistry/ → 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: cloudflare (1001 responses)
    • x-powered-by: WP Rocket/3.23.1.1 (2 responses)
  • FoundKeys and secrets in page codeMedium

    1 credential-like value found in code served to every visitor: Google API key.

    • Google API key AIzaSy…uE (39 chars) in https://www.bellerivedental.ca/: browser keys are expected in pages, but must be restricted by HTTP referrer and API in the Google Cloud console
  • NoteThird-party scripts

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

    • maps.google.com (40 script tags)
    • connect.podium.com (40 script tags)
    • firstin.ca (80 script tags)
    • www.google.com (39 script tags)
    • cdn.trustindex.io (1 script tag)
    • cdn.callrail.com (39 script tags)
    • app.medianv.com (39 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/
5 checks passed, 1 not applicable
  • OKHTTPS

    All 132 crawled pages were served over HTTPS.

  • OKMixed content

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

  • OKForms over HTTPS

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

  • OKVulnerable JavaScript libraries

    2 library versions recognised, none with known vulnerabilities.

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

Own www.bellerivedental.ca?

  • 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.bellerivedental.ca. Removal needs no account and no proof of purchase.
www.bellerivedental.ca scan 2026-09-22-1745 | DIY SEO Hub