Scanned sites / www.bellerivedental.ca / 2026-10-29-0017
www.bellerivedental.ca scan from 2026-10-29 00:17:47 UTC DR 5
A newer scan exists. See the latest report for www.bellerivedental.ca.
DR is Ahrefs Domain Rating (0-100, backlink strength), used under its Domain Rating License.
Scan 2026-10-29-0017
Scanned 2026-10-29 00:17:47 UTC, finished 2026-10-29 00:21:43 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.
On October 29, 2026 the Site Spider crawled 144 pages and 494 assets of www.bellerivedental.ca, starting from https://www.bellerivedental.ca/. It scored 91 out of 100, an excellent result. 7 of 33 checks found something to fix, led by heavy assets (5), title tags (38), meta descriptions (43); 14 checks passed. Most of the points went to heavy assets (−3), 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
- 494
- Status
- Completed
- Checks with issues
- 7 of 33
638 of 639 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 issues38 of 121 pages have title issues. 13 noindex or canonicalized pages excluded.−2.8 points
- Meta descriptions43 issues43 of 121 pages have meta description issues. 13 noindex or canonicalized pages excluded.−2.6 points
- HeadingsOK0 of 121 pages have heading issues. 13 noindex or canonicalized pages excluded.
- Broken linksOK0 internal links point at 0 broken URLs.
- Links to other sites1 issue1 destination answered with an error, 16 could not be determined (timeouts, rate limits or refusals), of 108 destinations checked.−0.3 points
- Redirects12 issues11 redirecting URLs, 5 of them chained.−0.4 points
- Non-200 responses16 noted16 URLs did not return a 2xx response. 10 of them are pages, 0 with an error status; the rest are assets or redirects.
- Rate limitedOKThe site did not rate limit the crawler.
- IndexabilityOK0 of 134 indexable pages have indexability warnings.
- Image alt textOK0 of 1029 image references have no alt attribute. 5 use an empty alt (decorative), which is fine.
- Heavy assets5 issues5 assets larger than 500 KB among 494 fetched assets.−3 points
- Orphan pages1 issue1 page have no internal links pointing at them.
- Sitemap coverage1 issue1 sitemap listing 120 URLs: 1 crawled page missing, 0 listed URLs broken or redirecting, 0 reachable only via the sitemap.
- Internal link counts1 notedInternal link counts for 134 pages; 1 worth a look.
- Thin contentOK0 of 121 pages have fewer than 200 words. 13 noindex or canonicalized pages excluded.
- Duplicate contentOK0 groups of pages with identical HTML.
- URL format17 noted17 of 144 page URLs are harder to read, share or cache than they need to be.
- Canonicals13 noted13 of 134 pages have a canonical worth checking.
- Robots directives134 noted134 pages carry a robots directive; 0 carry none.
- Anchor text85 noted85 destinations are linked without useful anchor text, or with nofollow.
- Title and heading structure17 noted17 of 121 pages could use the title, heading and snippet space better. 13 noindex or canonicalized pages excluded.
- Image weight and alt length21 noted21 images over 100 KB; 0 with alt text over 100 characters.
- Response anomalies1 noted1 URL answered in a way worth looking at.
- HTML and head validationOKAll 134 pages keep their head tags in <head>, once each, under Googlebot's 2 MB.
- hreflangOKNo page declares hreflang.
- Structured data21 noted116 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 duplicatesOKNo near duplicates among 120 pages with enough text to compare.
- Soft 404sOKNone of 134 pages answering 200 reads like an error page.
- AccessibilityNot checkedNot checked: the accessibility audit runs in the browser. Tick "Include JavaScript rendering checks" when you request a scan to run it.
- Link positions5 noted5 of 121 linked pages are linked only from the template, never from another page's content.
- PaginationOKNo page declares rel=next or rel=prev pagination.
- Headers and cookiesOK0 cookies set by the site; 11 response headers recorded across 638 URLs.
- Orphans in searchNot checkedNot checked: import a Search Console Pages export on the scan page to find pages Google shows that the site does not link to.
- Link ScoreOKLink Score (internal PageRank, 0-100) for 134 pages; 0 hold almost none (10 or less).
- JavaScript renderingNot checkedNot 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 checkedNot checked yet: PageSpeed Insights runs on the top pages once the crawl has finished.
- Spelling40 noted40 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
2341 sites, median 79%, average 78%
www.bellerivedental.ca scores 91%, higher than 90% of the 2341 scanned sites. See the full ranking.
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...
Fix plan
Written by gpt-4o-mini from the scan findingsThe health score is excellent, but there are several areas requiring attention to improve SEO performance. Focus on redirects, title tags, meta descriptions, heavy assets, orphan pages, and sitemap coverage for optimal results.
- 1
Fix Redirects
Why: Reduce redirect chains to improve site performance and user experience.
How: Update the affected URLs to direct them to the final destination without intermediate hops.
Checks: redirects
- 2
Optimize Title Tags
Why: 38 pages have long title tags that may not display fully in search results.
How: Shorten title tags to under 60 characters to enhance clarity and SEO performance.
Checks: titles
- 3
Improve Meta Descriptions
Why: 43 pages have lengthy meta descriptions which may be cut off in search results.
How: Revise meta descriptions to be concise, under 160 characters, while retaining key information.
Checks: meta-descriptions
- 4
Shrink Heavy Assets
Why: Reduce loading times by addressing large files impacting performance.
How: Compress or reformat the large files identified in the crawl report.
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
Link to Orphan Pages
Why: 1 orphan page is not linked internally, lowering its visibility and SEO potential.
How: Add links to the orphan page from relevant existing pages to improve its discoverability.
Checks: orphan-pages
- 6
Update Sitemap Coverage
Why: One crawled page is missing from the sitemap which may hinder indexing.
How: Add the missing page to the sitemap and resubmit it to search engines.
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 crawlThe site has several security vulnerabilities primarily related to missing HTTP headers that protect against various attacks, such as clickjacking and data leaks. Additionally, a sensitive API key is exposed in the page code. Immediate attention is needed to implement the suggested security headers and restrict API key usage.
- 0 high
- 4 medium
- 3 low
- 1 info
- 1
Missing HSTS HeaderMedium
Why it matters: Without HSTS, visitors can be intercepted during their first request, leading to potential man-in-the-middle attacks.
Fix: Add the header 'Strict-Transport-Security: max-age=31536000; includeSubDomains' to all responses.
Evidence: HTTP Strict Transport Security
- 2
Missing Content Security PolicyMedium
Why it matters: Without a CSP, malicious scripts can be executed because there are no restrictions on where resources can load from.
Fix: Add the header 'Content-Security-Policy: default-src 'self';' to all HTML pages.
Evidence: Content Security Policy
- 3
Missing X-Frame-Options HeaderMedium
Why it matters: Without this header, your site is vulnerable to clickjacking attacks, potentially allowing other sites to overlay controls.
Fix: Add the header 'X-Frame-Options: DENY' to all HTML pages.
Evidence: Clickjacking protection
- 4
Leaked API KeyMedium
Why it matters: An exposed Google API key can be abused if not restricted, leading to unauthorized access and potential charges.
Fix: Restrict the API key in the Google Cloud console to specific referrers and remove it from the page code.
Evidence: Keys and secrets in page code
- 5
Missing X-Content-Type-Options HeaderLow
Why it matters: Lack of this protects against MIME sniffing vulnerabilities, which can lead to execution of malicious content.
Fix: Add the header 'X-Content-Type-Options: nosniff' to all HTML pages.
Evidence: MIME sniffing protection
- 6
Missing Referrer PolicyLow
Why it matters: Not having a Referrer-Policy can expose sensitive URL parameters when users navigate away from your site.
Fix: Add the header 'Referrer-Policy: no-referrer' to all HTML pages.
Evidence: Referrer policy
- 7
Server Version ExposureLow
Why it matters: Revealing the server version can be exploited by attackers to target known vulnerabilities.
Fix: Remove the 'X-Powered-By' header or set it to 'X-Powered-By: [your-framework-name]' to obscure server details.
Evidence: Software version disclosure
- 8
Missing Permissions PolicyInfo
Why it matters: A Permissions-Policy helps to limit what features are available to potentially malicious scripts.
Fix: Add the header 'Permissions-Policy: geolocation=(self)' to all HTML pages.
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 (638 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.
- sacryelectric.comDR 092/100 · rank 152 · 85 pages
- sgvet.comDR 692/100 · rank 152 · 33 pages
- outlookoptometry.comDR 392/100 · rank 152 · 13 pages
- jmsante.plDR 3191/100 · rank 190 · 4,973 pages
- www.brunilaw.comDR 091/100 · rank 190 · 12 pages
- hotspringsfind.comDR 091/100 · rank 190 · 428 pages
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.