Scanned sites / www.bellerivedental.ca / 2026-09-16-2148

www.bellerivedental.ca scan from 9/16/2026, 9:48:16 PM

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

Scan 2026-09-16-2148

Scanned 9/16/2026, 9:48:16 PM, finished 9/16/2026, 10:09:45 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 16, 2026 the Site Spider crawled 142 pages and 861 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
861
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 1002 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

1053 sites, median 82%, average 80%

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

028550%: 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%: 1 site46%: 1 site47%: 0 sites48%: 1 site49%: 0 sites50%: 3 sites51%: 3 sites52%: 1 site53%: 1 site54%: 1 site55%: 1 site56%: 2 sites57%: 3 sites58%: 6 sites59%: 3 sites60%: 5 sites61%: 8 sites62%: 12 sites63%: 4 sites64%: 8 sites65%: 9 sites66%: 7 sites67%: 15 sites68%: 27 sites69%: 12 sites70%: 20 sites71%: 20 sites72%: 23 sites73%: 24 sites74%: 30 sites75%: 27 sites76%: 37 sites77%: 37 sites78%: 31 sites79%: 29 sites80%: 41 sites81%: 52 sites82%: 45 sites83%: 44 sites84%: 49 sites85%: 46 sites86%: 44 sites87%: 47 sites88%: 55 sites89%: 37 sites90%: 50 sites91%: 36 sites92%: 24 sites93%: 17 sites94%: 15 sites95%: 8 sites96%: 9 sites97%: 5 sites98%: 2 sites99%: 1 site100%: 10 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 has a good health score but needs some improvements. Focus on fixing the redirects and non-200 responses as they can significantly impact user experience. Adjust title tags and meta descriptions for better SEO. Lastly, address orphan pages and heavy assets to enhance overall performance.

  1. 1

    Fix Redirects

    Why: Redirects can confuse search engines and users. Chained redirects slow down page loading.

    How: Update URLs to avoid multiple hops and ensure direct linking.

    Checks: redirects

  2. 2

    Resolve Non-200 Responses

    Why: Error responses can lead to poor user experiences and affect rankings.

    How: Identify problematic URLs and update them or ensure they return 2xx responses.

    Checks: status-codes

  3. 3

    Update Title Tags

    Why: Long or duplicate titles may harm SEO visibility.

    How: Shorten titles to under 60 characters and ensure uniqueness.

    Checks: titles

  4. 4

    Revise Meta Descriptions

    Why: Descriptive meta can improve click-through rates in search results.

    How: Ensure all descriptions are under 160 characters and compelling.

    Checks: meta-descriptions

  5. 5

    Link to Orphan Pages

    Why: Orphan pages are not indexed well, losing traffic and visibility.

    How: Create internal links to connect the orphan page with relevant content.

    Checks: orphan-pages

  6. 6

    Optimize Heavy Assets

    Why: Large assets can slow down page loading and affect SEO.

    How: Compress images and reduce file sizes while maintaining quality.

    Checks: heavy-assets

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 important security improvements to make. These include missing security headers that protect against various attacks and the exposure of your Google API key, which could allow misuse. Implementing these fixes is essential to enhance the security of your site.

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

    Missing HTTP Strict Transport Security (HSTS)Medium

    Why it matters: Without HSTS, visitors may be susceptible to interception on their first connection.

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

    Evidence: HTTP Strict Transport Security

  2. 2

    Missing Content Security Policy (CSP)Medium

    Why it matters: No CSP reduces protection against cross-site scripting (XSS) and data injection attacks.

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

    Evidence: Content Security Policy

  3. 3

    Missing X-Frame-Options HeaderMedium

    Why it matters: Absence of this header allows potential clickjacking attacks on your site.

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

    Evidence: Clickjacking protection

  4. 4

    Leaked Google API KeyMedium

    Why it matters: Exposure of the API key can result in unauthorized access and usage.

    Fix: Restrict the API key usage by specifying allowed referrers in Google Cloud console.

    Evidence: Keys and secrets in page code

  5. 5

    Missing X-Content-Type-Options HeaderLow

    Why it matters: This could lead to a browser executing files as scripts, posing a threat.

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

    Evidence: MIME sniffing protection

  6. 6

    Missing Referrer Policy HeaderLow

    Why it matters: Without this, sensitive page addresses can be exposed to external sites.

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

    Evidence: Referrer policy

  7. 7

    Exposed Server and Framework VersionsLow

    Why it matters: Disclosing software version numbers can assist attackers in identifying vulnerabilities.

    Fix: Remove the X-Powered-By header and update server configuration to hide version info.

    Evidence: Software version disclosure

  8. 8

    Missing Permissions Policy HeaderInfo

    Why it matters: Lacking this header allows scripts to potentially utilize browser features unnecessarily.

    Fix: Add the header: Permissions-Policy: geolocation=(self), microphone=(), camera=()

    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 (1003 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.

This report was produced by the DIY SEO Hub Site Spider crawling www.bellerivedental.ca from its public pages. Anyone can run a scan of any site they own or are authorised to check. Is this your site? Claim it to manage the listing, or ask for removal through the support form.

www.bellerivedental.ca scan 2026-09-16-2148 | DIY SEO Hub