Scanned sites / www.bellerivedental.ca / 2026-10-26-0329
www.bellerivedental.ca scan from 2026-10-26 03:29:16 UTC DR 5
DR is Ahrefs Domain Rating (0-100, backlink strength), used under its Domain Rating License.
Scan 2026-10-26-0329
Scanned 2026-10-26 03:29:16 UTC, finished 2026-10-26 03:32:19 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 26, 2026 the Site Spider crawled 144 pages and 479 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
- 479
- Status
- Completed
- Checks with issues
- 7 of 33
623 of 624 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 1032 image references have no alt attribute. 5 use an empty alt (decorative), which is fine.
- Heavy assets5 issues5 assets larger than 500 KB among 479 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 text81 noted81 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 length22 noted22 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 623 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
2316 sites, median 79%, average 78%
www.bellerivedental.ca scores 91%, higher than 90% of the 2316 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 findingsYour website is performing well with a health score of 91/100. However, there are some issues to address to further enhance SEO performance, especially with redirects and meta descriptions.
- 1
Fix Redirect Chains
Why: Chained redirects can slow down page loading and affect user experience.
How: Replace chained redirects with a direct URL that points to the final destination. Update necessary links.
Checks: redirects
- 2
Resolve Non-200 Responses
Why: Non-200 responses can negatively impact SEO performance and user experience.
How: Identify the 10 pages returning non-200 responses. Either fix the URLs or remove them if they are obsolete.
Checks: status-codes
- 3
Optimize Title Tags
Why: 39 pages have title issues that can hinder search engine optimization.
How: Shorten title tags to be under 60 characters while maintaining clarity about page content.
Checks: titles
- 4
Improve Meta Descriptions
Why: 43 pages have meta description issues, reducing the quality of search results.
How: Shorten meta descriptions to be under 160 characters and ensure they accurately summarize page content.
Checks: meta-descriptions
- 5
Shrink Heavy Assets
Why: Reducing heavy assets will improve page load speed, affecting user experience and SEO.
How: Compress image files and scripts identified. Use tools like TinyPNG for images and Gzip for scripts.
Evidence: 85.5 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
- 6
Link to Orphan Page
Why: Orphan pages do not receive any internal links, making them hard to find for users and search engines.
How: Add links to the orphan page from relevant sections of the site to improve accessibility.
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 crawlThe website has several security shortcomings that could expose it to attacks, including the absence of important HTTP response headers like HSTS and Content Security Policy. Implementing these headers will improve protection against various types of attacks, such as man-in-the-middle and clickjacking.
- 0 high
- 4 medium
- 3 low
- 1 info
- 1
Missing HTTP Strict Transport Security (HSTS)Medium
Why it matters: Without HSTS, visitors can be intercepted on their first request if they do not use HTTPS.
Fix: Add the header 'Strict-Transport-Security: max-age=31536000; includeSubDomains; preload'.
Evidence: HTTP Strict Transport Security
- 2
Missing Content Security Policy (CSP)Medium
Why it matters: Lack of CSP allows scripts and iframes to load from unauthorized sources, risking XSS attacks.
Fix: Add a header like 'Content-Security-Policy: default-src 'self'; script-src 'self' https://trusted-source.com;'.
Evidence: Content Security Policy
- 3
Missing X-Frame-Options HeaderMedium
Why it matters: Without X-Frame-Options, the site is vulnerable to clickjacking attacks by being framed on malicious sites.
Fix: Add the header 'X-Frame-Options: DENY' or use a CSP frame-ancestors directive.
Evidence: Clickjacking protection
- 4
Exposed Google API KeyMedium
Why it matters: An exposed API key can be abused if not properly restricted, potentially leading to unexpected charges or data access.
Fix: Restrict the API key by HTTP referrer in the Google Cloud Console and regenerate it if exposed.
Evidence: Keys and secrets in page code
- 5
Missing X-Content-Type-Options HeaderLow
Why it matters: Without this, browsers might execute scripts based on content rather than declared type, risking code execution.
Fix: Add the header 'X-Content-Type-Options: nosniff'.
Evidence: MIME sniffing protection
- 6
Missing Referrer Policy HeaderLow
Why it matters: Without a Referrer Policy, sensitive page URLs can be leaked to third-party websites through referrer information.
Fix: Add the header 'Referrer-Policy: no-referrer-when-downgrade'.
Evidence: Referrer policy
- 7
Server Banner Reveals Version InformationLow
Why it matters: Disclosure of server or framework versions can aid attackers in finding vulnerabilities.
Fix: Configure your server to hide version information or use 'Server: nginx' to obscure details.
Evidence: Software version disclosure
- 8
Missing Permissions-Policy HeaderInfo
Why it matters: Lacking this header could allow injected scripts to access sensitive features like the camera or geolocation.
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 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 (623 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 146 · 85 pages
- sgvet.comDR 692/100 · rank 146 · 33 pages
- outlookoptometry.comDR 392/100 · rank 146 · 13 pages
- www.brunilaw.comDR 091/100 · rank 184 · 12 pages
- indietool.ioDR 4491/100 · rank 184 · 2,051 pages
- yoast.comDR 9191/100 · rank 184 · 929 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.