Scanned sites / www.bellerivedental.ca / 2026-10-09-1338

www.bellerivedental.ca scan from 10/9/2026, 1:38:19 PM DR 5

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

Scan 2026-10-09-1338

Scanned 10/9/2026, 1:38:19 PM, finished 10/9/2026, 1:49:55 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 October 9, 2026 the Site Spider crawled 142 pages and 569 assets of www.bellerivedental.ca, starting from https://www.bellerivedental.ca/. It scored 89 out of 100, a good result. 7 of 23 checks found something to fix, led by heavy assets (8), title tags (37), meta descriptions (43); 7 checks passed. Most of the points went to heavy assets (−4.8), title tags (−2.8), meta descriptions (−2.6). 9 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: Medium4 medium, 3 low and 1 info findings. See the security findings ↓

Pages crawled
142
Assets fetched
569
Status
Completed
Checks with issues
7 of 23
CoverageComplete crawl

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

  • Title tags37 issues
    37 of 119 pages have title issues. 13 noindex or canonicalized pages excluded.
    −2.8 points
  • Meta descriptions43 issues
    43 of 119 pages have meta description issues. 13 noindex or canonicalized pages excluded.
    −2.6 points
  • HeadingsOK
    0 of 119 pages have heading issues. 13 noindex or canonicalized pages excluded.
  • Broken linksOK
    0 internal links point at 0 broken URLs.
  • Links to other sites1 issue
    1 destination answered with an error, 17 could not be determined (timeouts, rate limits or refusals), of 108 destinations checked.
    −0.3 points
  • Redirects12 issues
    11 redirecting URLs, 5 of them chained.
    −0.4 points
  • Non-200 responses16 noted
    16 URLs did not return a 2xx response. 10 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 132 indexable pages have indexability warnings.
  • Image alt textOK
    0 of 1138 image references have no alt attribute. 5 use an empty alt (decorative), which is fine.
  • Heavy assets8 issues
    8 assets larger than 500 KB among 569 fetched assets.
    −4.8 points
  • 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.
  • Internal link counts1 noted
    Internal link counts for 132 pages; 1 worth a look.
  • 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.
  • URL format17 noted
    17 of 142 page URLs are harder to read, share or cache than they need to be.
  • Canonicals13 noted
    13 of 132 pages have a canonical worth checking.
  • Robots directives132 noted
    132 pages carry a robots directive; 0 carry none.
  • Anchor text79 noted
    79 destinations are linked without useful anchor text, or with nofollow.
  • Title and heading structure17 noted
    17 of 119 pages could use the title, heading and snippet space better. 13 noindex or canonicalized pages excluded.
  • Image weight and alt length25 noted
    25 images over 100 KB; 0 with alt text over 100 characters.
  • Response anomalies1 noted
    1 URL answered in a way worth looking at.

Where this scan sits among all scanned sites

2184 sites, median 79%, average 78%

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

0551100%: 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%: 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%: 1 site28%: 0 sites29%: 0 sites30%: 0 sites31%: 0 sites32%: 0 sites33%: 1 site34%: 0 sites35%: 2 sites36%: 2 sites37%: 1 site38%: 3 sites39%: 2 sites40%: 2 sites41%: 2 sites42%: 0 sites43%: 2 sites44%: 1 site45%: 4 sites46%: 6 sites47%: 4 sites48%: 4 sites49%: 5 sites50%: 4 sites51%: 4 sites52%: 10 sites53%: 6 sites54%: 9 sites55%: 8 sites56%: 7 sites57%: 12 sites58%: 16 sites59%: 6 sites60%: 15 sites61%: 13 sites62%: 20 sites63%: 24 sites64%: 18 sites65%: 37 sites66%: 29 sites67%: 34 sites68%: 33 sites69%: 39 sites70%: 42 sites71%: 66 sites72%: 75 sites73%: 66 sites74%: 60 sites75%: 75 sites76%: 80 sites77%: 92 sites78%: 100 sites79%: 87 sites80%: 103 sites81%: 104 sites82%: 110 sites83%: 90 sites84%: 99 sites85%: 71 sites86%: 71 sites87%: 64 sites88%: 59 sites89%: 57 sites90%: 34 sites91%: 40 sites92%: 27 sites93%: 22 sites94%: 13 sites95%: 7 sites96%: 5 sites97%: 11 sites98%: 2 sites99%: 0 sites100%: 64 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

The site is performing well but has critical SEO issues to address. Focus on fixing redirects, status codes, title and meta description issues for better visibility.

  1. 1

    Fix Redirects

    Why: Chained redirects can dilute page authority and slow down loading times.

    How: Update the URLs to point directly without multiple redirects.

    Checks: redirects

  2. 2

    Resolve Non-200 Responses

    Why: Non-200 statuses can harm user experience and SEO rankings.

    How: Identify the pages and ensure they return a 200 status by correcting links or removing redirects.

    Checks: status-codes

  3. 3

    Improve Title Tags

    Why: Overly long titles can be truncated in search results, diluting their impact.

    How: Shorten titles to under 60 characters while retaining relevant keywords.

    Checks: titles

  4. 4

    Enhance Meta Descriptions

    Why: Long meta descriptions may be cut off in search results, reducing click-through rates.

    How: Revise meta descriptions to be concise, ideally under 160 characters.

    Checks: meta-descriptions

  5. 5

    Optimize Heavy Assets

    Why: Large assets can slow page load times, impacting user retention and SEO.

    How: Compress images and scripts to reduce sizes; consider lazy loading where appropriate.

    Evidence: 71.4 KB of script, loaded by 132 pages, so every visitor to any of them downloads it.

    132 pages affected

    Depends on: If it is a download rather than part of the page, weight matters less; move it out of the page instead.

    Checks: heavy-assets

  6. 6

    Add Sitemap Entry for Orphan Page

    Why: Not including this page in your sitemap may lead to lower visibility in search engines.

    How: Update the sitemap to include the orphan page for better indexing.

    Evidence: One URL: not in sitemap.

    1 page affected

    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 website lacks essential security protections like HTTP Strict Transport Security and Content Security Policy. These vulnerabilities could lead to interception of user data and exploitation through malicious scripts or clickjacking. Immediate action is required to implement suggested headers for improved security.

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

    Missing HTTP Strict Transport SecurityMedium

    Why it matters: Without HSTS, visitors can be intercepted when accessing the site over plain HTTP.

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

    Evidence: HTTP Strict Transport Security

  2. 2

    Missing Content Security PolicyMedium

    Why it matters: The absence of CSP allows potentially malicious scripts and resources to be loaded from any source.

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

    Evidence: Content Security Policy

  3. 3

    Missing X-Frame-OptionsMedium

    Why it matters: Lack of X-Frame-Options exposes the site to clickjacking attacks.

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

    Evidence: Clickjacking protection

  4. 4

    Leaked Google API KeyMedium

    Why it matters: An exposed API key could lead to unauthorized access if not properly restricted.

    Fix: Restrict this key in the Google Cloud console by setting appropriate HTTP referrer restrictions.

    Evidence: Keys and secrets in page code

  5. 5

    Missing X-Content-Type-OptionsLow

    Why it matters: Without this header, browsers could misinterpret files and execute them as scripts.

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

    Evidence: MIME sniffing protection

  6. 6

    Missing Referrer PolicyLow

    Why it matters: Absence of a referrer policy could leak sensitive information, like page URLs, to third parties.

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

    Evidence: Referrer policy

  7. 7

    Exposure of Server and Framework VersionsLow

    Why it matters: Revealing server software versions increases vulnerability to specific attacks.

    Fix: Remove or obscure headers: Server: and X-Powered-By: values.

    Evidence: Software version disclosure

  8. 8

    Missing Permissions PolicyInfo

    Why it matters: Not specifying a permissions policy could allow injected scripts to access features like the microphone.

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

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

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 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-10-09-1338 | DIY SEO Hub