Scanned sites / www.bellerivedental.ca / 2026-10-18-2048

www.bellerivedental.ca scan from 2026-10-18 20:48:06 UTC DR 5

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

Scan 2026-10-18-2048

Scanned 2026-10-18 20:48:06 UTC, finished 2026-10-18 20:52:12 UTC. 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 18, 2026 the Site Spider crawled 144 pages and 493 assets of www.bellerivedental.ca, starting from https://www.bellerivedental.ca/. It scored 89 out of 100, a good result. 7 of 33 checks found something to fix, led by heavy assets (9), title tags (38), meta descriptions (43); 14 checks passed. Most of the points went to heavy assets (−5.4), title tags (−2.8), meta descriptions (−2.6). 12 checks found something the score does not count, listed as noted. 4 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: Medium4 medium, 3 low and 1 info findings. See the security findings ↓

Pages crawled
144
Assets fetched
493
Status
Completed
Checks with issues
7 of 33
CoverageComplete crawl

637 of 638 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 tags38 issues
    38 of 121 pages have title issues. 13 noindex or canonicalized pages excluded.
    −2.8 points
  • Meta descriptions43 issues
    43 of 121 pages have meta description issues. 13 noindex or canonicalized pages excluded.
    −2.6 points
  • HeadingsOK
    0 of 121 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, 16 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 134 indexable pages have indexability warnings.
  • Image alt textOK
    0 of 937 image references have no alt attribute. 5 use an empty alt (decorative), which is fine.
  • Heavy assets9 issues
    9 assets larger than 500 KB among 493 fetched assets.
    −5.4 points
  • Orphan pages1 issue
    1 page have no internal links pointing at them.
  • Sitemap coverage1 issue
    1 sitemap listing 120 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 134 pages; 1 worth a look.
  • Thin contentOK
    0 of 121 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 144 page URLs are harder to read, share or cache than they need to be.
  • Canonicals13 noted
    13 of 134 pages have a canonical worth checking.
  • Robots directives134 noted
    134 pages carry a robots directive; 0 carry none.
  • Anchor text81 noted
    81 destinations are linked without useful anchor text, or with nofollow.
  • Title and heading structure17 noted
    17 of 121 pages could use the title, heading and snippet space better. 13 noindex or canonicalized pages excluded.
  • Image weight and alt length24 noted
    24 images over 100 KB; 0 with alt text over 100 characters.
  • Response anomalies1 noted
    1 URL answered in a way worth looking at.
  • HTML and head validationOK
    All 134 pages keep their head tags in <head>, once each, under Googlebot's 2 MB.
  • hreflangOK
    No page declares hreflang.
  • Structured data21 noted
    116 of 121 indexable pages carry structured data: ListItem (79), BreadcrumbList (77), Organization (48), FAQPage (42), Question (42). 21 pages with errors a rich result would fail on.
  • Near duplicatesOK
    No near duplicates among 120 pages with enough text to compare.
  • Soft 404sOK
    None of 134 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 positions5 noted
    5 of 121 linked pages are linked only from the template, never from another page's content.
  • PaginationOK
    No page declares rel=next or rel=prev pagination.
  • Headers and cookiesOK
    0 cookies set by the site; 11 response headers recorded across 637 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 134 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 InsightsNot checked
    Not checked yet: PageSpeed Insights runs on the top pages once the crawl has finished.
  • Spelling40 noted
    40 words an English dictionary does not know, on 34 pages. Product names and jargon will appear here too.

Where this scan sits among all scanned sites

2284 sites, median 79%, average 78%

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

0581150%: 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%: 0 sites28%: 1 site29%: 0 sites30%: 0 sites31%: 0 sites32%: 0 sites33%: 1 site34%: 0 sites35%: 2 sites36%: 2 sites37%: 1 site38%: 3 sites39%: 1 site40%: 3 sites41%: 1 site42%: 1 site43%: 3 sites44%: 1 site45%: 4 sites46%: 5 sites47%: 5 sites48%: 3 sites49%: 6 sites50%: 5 sites51%: 5 sites52%: 10 sites53%: 6 sites54%: 8 sites55%: 9 sites56%: 8 sites57%: 12 sites58%: 16 sites59%: 7 sites60%: 16 sites61%: 12 sites62%: 19 sites63%: 27 sites64%: 21 sites65%: 32 sites66%: 36 sites67%: 34 sites68%: 35 sites69%: 45 sites70%: 41 sites71%: 68 sites72%: 70 sites73%: 65 sites74%: 70 sites75%: 71 sites76%: 87 sites77%: 92 sites78%: 105 sites79%: 86 sites80%: 106 sites81%: 106 sites82%: 115 sites83%: 95 sites84%: 106 sites85%: 85 sites86%: 67 sites87%: 71 sites88%: 62 sites89%: 61 sites90%: 33 sites91%: 44 sites92%: 33 sites93%: 21 sites94%: 14 sites95%: 10 sites96%: 9 sites97%: 9 sites98%: 4 sites99%: 0 sites100%: 70 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

Several optimization opportunities exist, including fixing redirects, title and meta description issues, heavy assets, an orphan page, and sitemap coverage. Addressing these will enhance both user experience and SEO.

  1. 1

    Fix Redirects

    Why: Reducing redirects improves load time and user experience.

    How: Directly link to final destinations instead of causing additional hops.

    Checks: redirects

  2. 2

    Correct Title Tags

    Why: Optimizing titles enhances click-through rates and search rankings.

    How: Shorten titles to under 60 characters for better visibility in search results.

    Checks: titles

  3. 3

    Fix Meta Descriptions

    Why: Improving meta descriptions can increase site traffic by attracting more clicks.

    How: Rewrite descriptions to be succinct, ideally under 160 characters.

    Checks: meta-descriptions

  4. 4

    Optimize Heavy Assets

    Why: Reducing asset size decreases load times and improves site performance.

    How: Compress or optimize large images and scripts to reduce load times.

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

    134 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

  5. 5

    Link Orphan Page

    Why: Linking orphan pages can help improve their visibility and indexability.

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

    Checks: orphan-pages

  6. 6

    Update Sitemap Coverage

    Why: Ensuring all pages are in the sitemap helps with indexing.

    How: Include the missing page in the sitemap to ensure search engines can find it.

    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

Your website has multiple security vulnerabilities that could allow attackers to intercept traffic, execute malicious scripts, and retrieve sensitive data. Addressing these issues will strengthen the site's overall security and protect your visitors' information.

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

    Missing HTTP Strict Transport SecurityMedium

    Why it matters: Without HSTS, attackers can intercept the first request if a user types the address without HTTPS.

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

    Evidence: HTTP Strict Transport Security

  2. 2

    No Content Security PolicyMedium

    Why it matters: The absence of a CSP allows any scripts or styles to be loaded from anywhere, increasing the risk of XSS attacks.

    Fix: Add the header: Content-Security-Policy: default-src 'self'; script-src 'self' https://trustedsources.com;

    Evidence: Content Security Policy

  3. 3

    No Clickjacking ProtectionMedium

    Why it matters: Without X-Frame-Options, your pages can be embedded in frames by other sites, which can lead to clickjacking attacks.

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

    Evidence: Clickjacking protection

  4. 4

    Exposed Google API KeyMedium

    Why it matters: The public Google API key can be abused if not properly restricted by referrer and quota limits.

    Fix: Restrict it in the Google Cloud console to accepted HTTP referrers only.

    Evidence: Keys and secrets in page code

  5. 5

    Missing MIME Sniffing ProtectionLow

    Why it matters: Without X-Content-Type-Options: nosniff, browsers may interpret files incorrectly based on their contents.

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

    Evidence: MIME sniffing protection

  6. 6

    No Referrer PolicyLow

    Why it matters: Without a referrer policy, the full URL of your pages, including query strings, can be exposed to external sites.

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

    Evidence: Referrer policy

  7. 7

    Server Version DisclosureLow

    Why it matters: Revealing server version information can aid attackers in exploiting known vulnerabilities.

    Fix: Remove the X-Powered-By header or set it to a generic value.

    Evidence: Software version disclosure

  8. 8

    No Permissions PolicyInfo

    Why it matters: Without a Permissions-Policy header, unnecessary browser features may be accessible, increasing vulnerability to attacks.

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

    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 134 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 (637 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 134 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.