Scanned sites / www.bellerivedental.ca / 2026-09-17-2308

www.bellerivedental.ca scan from 9/17/2026, 11:08:08 PM

Scan 2026-09-17-2308

Scanned 9/17/2026, 11:08:08 PM, finished 9/17/2026, 11:27:13 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 17, 2026 the Site Spider crawled 142 pages and 849 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
849
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 1021 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

1075 sites, median 82%, average 80%

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

027540%: 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%: 2 sites46%: 1 site47%: 0 sites48%: 0 sites49%: 0 sites50%: 3 sites51%: 4 sites52%: 1 site53%: 1 site54%: 2 sites55%: 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%: 22 sites71%: 21 sites72%: 23 sites73%: 24 sites74%: 30 sites75%: 27 sites76%: 37 sites77%: 36 sites78%: 33 sites79%: 30 sites80%: 41 sites81%: 52 sites82%: 50 sites83%: 45 sites84%: 52 sites85%: 47 sites86%: 45 sites87%: 47 sites88%: 54 sites89%: 38 sites90%: 51 sites91%: 36 sites92%: 25 sites93%: 17 sites94%: 16 sites95%: 8 sites96%: 9 sites97%: 4 sites98%: 2 sites99%: 1 site100%: 12 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

To enhance SEO, prioritize fixing redirect chains, addressing non-200 responses, optimizing title tags and meta descriptions, and resolving orphan pages. Improving these areas can positively impact visibility and user experience.

  1. 1

    Fix Redirect Chains

    Why: Chains can dilute link equity and confuse search engines.

    How: Redirect each chained URL directly to its final destination to simplify the redirect path.

    Checks: redirects

  2. 2

    Resolve Non-200 Responses

    Why: These URLs can hinder site accessibility and SEO rankings.

    How: Identify pages with non-200 responses and ensure they return a 200 status by either fixing or removing them.

    Checks: status-codes

  3. 3

    Optimize Title Tags

    Why: Long titles can reduce search engine visibility and click-through rates.

    How: Revise titles to be under 60 characters while retaining essential keywords.

    Checks: titles

  4. 4

    Improve Meta Descriptions

    Why: Overly long descriptions can hurt search ranking and appear truncated in search results.

    How: Edit descriptions to be concise and under 160 characters, incorporating key information.

    Checks: meta-descriptions

  5. 5

    Address Orphan Pages

    Why: Orphan pages are less discoverable and can waste crawl budget.

    How: Create internal links to the orphan page from relevant content to enhance navigation.

    Checks: orphan-pages

  6. 6

    Reduce Heavy Assets

    Why: Large assets can slow site loading times, impacting user experience.

    How: Optimize images by compressing them or using lower resolution where possible.

    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

The website lacks essential security headers, increasing vulnerability to various attacks. Implementing headers like HSTS and CSP will significantly improve security. Additionally, review API key exposure and server banner disclosure to mitigate risks further.

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

    Missing HSTS HeaderMedium

    Why it matters: Without HSTS, visitors can be intercepted if they don't use HTTPS.

    Fix: Add 'Strict-Transport-Security: max-age=31536000; includeSubDomains' to HTTP responses.

    Evidence: HTTP Strict Transport Security

  2. 2

    Missing Content Security PolicyMedium

    Why it matters: Absence of CSP allows scripts from untrusted sources, heightening risk of XSS.

    Fix: Include 'Content-Security-Policy: default-src 'self';' in HTTP responses.

    Evidence: Content Security Policy

  3. 3

    No Clickjacking ProtectionMedium

    Why it matters: Lack of X-Frame-Options allows the site to be embedded in frames, risking user data.

    Fix: Set 'X-Frame-Options: DENY' or use CSP 'frame-ancestors' directive.

    Evidence: Clickjacking protection

  4. 4

    Leaked API KeyMedium

    Why it matters: The exposed Google API key can be exploited if not properly restricted.

    Fix: Restrict API key usage in the Google Cloud console and remove it from HTML code.

    Evidence: Keys and secrets in page code

  5. 5

    Missing MIME Sniffing ProtectionLow

    Why it matters: Without proper MIME type settings, browsers may execute files incorrectly.

    Fix: Add 'X-Content-Type-Options: nosniff' to HTTP headers.

    Evidence: MIME sniffing protection

  6. 6

    No Referrer Policy SetLow

    Why it matters: Lack of a referrer policy exposes full URL information to third parties.

    Fix: Implement 'Referrer-Policy: no-referrer' or similar policy.

    Evidence: Referrer policy

  7. 7

    Server Banner DisclosureLow

    Why it matters: Revealing server version can aid attackers in finding vulnerabilities.

    Fix: Hide version info by configuring the server to suppress 'Server' and 'X-Powered-By' headers.

    Evidence: Software version disclosure

  8. 8

    Missing Permissions PolicyInfo

    Why it matters: Absence of permissions policy may leave features open to exploitation.

    Fix: Include 'Permissions-Policy: geolocation=(self)'; if these features aren't needed.

    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 (991 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-17-2308 | DIY SEO Hub