Scanned sites / www.beddingtondentalclinic.com / 2026-10-05-0505

www.beddingtondentalclinic.com scan from 10/5/2026, 5:05:16 AM

Scan 2026-10-05-0505

Scanned 10/5/2026, 5:05:16 AM, finished 10/5/2026, 5:17:11 AM. Found with openstreetmap overpass

Site: https://www.beddingtondentalclinic.com/

Download SQLite databaseEvery page and asset from this scan, with the crawl events, in one file.

83/ 100Good

On October 5, 2026 the Site Spider crawled 158 pages and 579 assets of www.beddingtondentalclinic.com, starting from https://www.beddingtondentalclinic.com/. It scored 83 out of 100, a good result. 9 of 22 checks found something to fix, led by sitemap coverage (109), heavy assets (7), meta descriptions (55); 4 checks passed. Most of the points went to sitemap coverage (−4.4), heavy assets (−4.2), meta descriptions (−2.9). 9 checks found something the score does not count, listed as noted. 1 check was not run because the crawl fetched nothing for it. 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: Medium3 medium, 4 low and 2 info findings. See the security findings ↓

Pages crawled
158
Assets fetched
579
Status
Completed
Checks with issues
9 of 22
CoverageComplete crawl

737 of 738 discovered URLs were fetched. The crawl reached everything it found. HTML only: nothing here ran JavaScript. 9 link destinations on other sites have not been checked.

  • Title tags39 issues
    39 of 149 pages have title issues. 1 noindex or canonicalized page excluded.
    −2.6 points
  • Meta descriptions55 issues
    55 of 149 pages have meta description issues. 1 noindex or canonicalized page excluded.
    −2.9 points
  • Headings1 issue
    1 of 149 pages have heading issues. 1 noindex or canonicalized page excluded.
  • Broken linksOK
    0 internal links point at 0 broken URLs.
  • Links to other sitesNot checked
    Not checked: the crawl fetched nothing this check can look at.
  • Redirects8 issues
    8 redirecting URLs, 0 of them chained.
    −0.2 points
  • Non-200 responses8 noted
    8 URLs did not return a 2xx response. 8 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.
  • Indexability1 issue
    1 of 149 indexable pages have indexability warnings. 1 page noindex by design. 1 noindex page is listed in the sitemap, which asks search engines both to visit and to ignore it.
    −0.1 points
  • Image alt text3 issues
    3 of 939 image references have no alt attribute. 112 use an empty alt (decorative), which is fine.
  • Heavy assets7 issues
    7 assets larger than 500 KB among 579 fetched assets.
    −4.2 points
  • Orphan pages82 issues
    82 pages have no internal links pointing at them.
    −2.2 points
  • Sitemap coverage109 issues
    1 sitemap listing 124 URLs: 26 crawled pages missing, 0 listed URLs broken or redirecting, 82 reachable only via the sitemap.
    −4.4 points
  • Internal link counts1 noted
    Internal link counts for 150 pages; 1 worth a look.
  • Thin contentOK
    0 of 149 pages have fewer than 200 words. 1 noindex or canonicalized page excluded.
  • Duplicate contentOK
    0 groups of pages with identical HTML.
  • URL format4 noted
    4 of 158 page URLs are harder to read, share or cache than they need to be.
  • Canonicals1 noted
    1 of 150 pages have a canonical worth checking.
  • Robots directives150 noted
    150 pages carry a robots directive; 0 carry none.
  • Anchor text13 noted
    13 destinations are linked without useful anchor text, or with nofollow.
  • Title and heading structure50 noted
    50 of 149 pages could use the title, heading and snippet space better. 1 noindex or canonicalized page excluded.
  • Image weight and alt length73 noted
    73 images over 100 KB; 0 with alt text over 100 characters.
  • Response anomalies7 noted
    7 URLs answered in a way worth looking at.

Where this scan sits among all scanned sites

2072 sites, median 79%, average 78%

www.beddingtondentalclinic.com scores 83%, higher than 66% of the 2072 scanned sites. See the full ranking.

0531050%: 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%: 1 site28%: 0 sites29%: 0 sites30%: 0 sites31%: 0 sites32%: 0 sites33%: 1 site34%: 0 sites35%: 1 site36%: 2 sites37%: 2 sites38%: 3 sites39%: 2 sites40%: 2 sites41%: 1 site42%: 0 sites43%: 0 sites44%: 1 site45%: 4 sites46%: 5 sites47%: 4 sites48%: 4 sites49%: 3 sites50%: 5 sites51%: 5 sites52%: 9 sites53%: 7 sites54%: 7 sites55%: 7 sites56%: 5 sites57%: 11 sites58%: 15 sites59%: 7 sites60%: 12 sites61%: 9 sites62%: 19 sites63%: 21 sites64%: 16 sites65%: 37 sites66%: 27 sites67%: 35 sites68%: 34 sites69%: 33 sites70%: 35 sites71%: 63 sites72%: 67 sites73%: 55 sites74%: 60 sites75%: 78 sites76%: 78 sites77%: 88 sites78%: 91 sites79%: 86 sites80%: 98 sites81%: 103 sites82%: 105 sites83%: 87 sites84%: 90 sites85%: 67 sites86%: 67 sites87%: 66 sites88%: 64 sites89%: 51 sites90%: 34 sites91%: 42 sites92%: 24 sites93%: 19 sites94%: 15 sites95%: 7 sites96%: 4 sites97%: 10 sites98%: 2 sites99%: 1 site100%: 57 sites83% 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

Your site has a good health score, but there are several critical areas for improvement. Prioritizing these can enhance SEO performance significantly.

  1. 1

    Fix Redirects

    Why: Multiple redirects can slow page loading and dilute link equity.

    How: Simplify URLs by removing unnecessary redirects and ensuring all pages are accessible directly.

    Checks: redirects

  2. 2

    Resolve Non-200 Responses

    Why: Pages returning non-200 responses can harm user experience and SEO ranking.

    How: Identify and correct all pages that do not return a 2xx status, ensuring they are active.

    Checks: status-codes

  3. 3

    Update Title Tags

    Why: 39 pages have title issues, affecting click-through rates and SERP visibility.

    How: Revise title tags to be descriptive, ensuring they are between 30-60 characters.

    Checks: titles

  4. 4

    Improve Meta Descriptions

    Why: 55 meta descriptions need improvement to guide user clicks effectively.

    How: Create compelling meta descriptions for each page, keeping them under 160 characters.

    Checks: meta-descriptions

  5. 5

    Optimize Headings Structure

    Why: Improper heading usage can confuse both users and search engines.

    How: Ensure only one H1 tag per page and follow a clear hierarchy (H2, H3).

    Checks: headings

  6. 6

    Enhance Sitemap Coverage

    Why: 82 pages are only reachable via the sitemap, limiting discoverability.

    How: Include all important pages in your sitemap and remove noindex pages from it.

    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 several important security headers, which could expose it to various attacks, including man-in-the-middle threats and clickjacking. Implementing appropriate security headers will help protect both the site and its visitors.

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

    Missing HTTP Strict Transport Security (HSTS)Medium

    Why it matters: Lack of HSTS allows interception when visitors access the site without HTTPS.

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

    Evidence: HTTP Strict Transport Security

  2. 2

    Missing Content Security Policy (CSP)Medium

    Why it matters: Without a CSP, scripts and frames may load from untrusted sources, increasing XSS risks.

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

    Evidence: Content Security Policy

  3. 3

    Missing X-Frame-Options HeaderMedium

    Why it matters: Absence of this header allows the site to be embedded in frames, making it vulnerable to clickjacking.

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

    Evidence: Clickjacking protection

  4. 4

    Missing X-Content-Type-Options HeaderLow

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

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

    Evidence: MIME sniffing protection

  5. 5

    Missing Referrer-Policy HeaderLow

    Why it matters: Without a referrer policy, users' full URLs may be sent to external sites, compromising privacy.

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

    Evidence: Referrer policy

  6. 6

    Server and Framework Version DisclosureLow

    Why it matters: Revealing software versions can help attackers exploit known vulnerabilities.

    Fix: Remove the headers: server, x-powered-by or obscure their contents.

    Evidence: Software version disclosure

  7. 7

    Third-Party Scripts without Subresource IntegrityLow

    Why it matters: Running unverified scripts increases the risk of malicious changes through third-party domains.

    Fix: Implement Subresource Integrity (SRI) for third-party scripts or use a CSP to restrict sources.

    Evidence: Third-party scripts

  8. 8

    Missing Permissions-Policy HeaderInfo

    Why it matters: Not specifying this policy allows browsers to access features that might be leveraged through injected scripts.

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

    Evidence: Permissions policy

  9. 9

    Sensitive Paths Listed in robots.txtInfo

    Why it matters: Publicly listing sensitive paths may inadvertently inform potential attackers where to probe.

    Fix: Consider restricting access to sensitive areas with proper authentication instead of using robots.txt.

    Evidence: Sensitive paths in robots.txt

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.beddingtondentalclinic.com/ → no strict-transport-security
    • https://www.beddingtondentalclinic.com/canadian-dental-care-plan/ → no strict-transport-security
    • https://www.beddingtondentalclinic.com/our-team/ → no strict-transport-security
    • https://www.beddingtondentalclinic.com/tour-the-office/ → no strict-transport-security
    • https://www.beddingtondentalclinic.com/blog/ → no strict-transport-security
    • https://www.beddingtondentalclinic.com/saturday-dentist/ → no strict-transport-security
    • https://www.beddingtondentalclinic.com/privacy-policy/ → no strict-transport-security
    • https://www.beddingtondentalclinic.com/patient-forms/ → no strict-transport-security
    • https://www.beddingtondentalclinic.com/financials/ → no strict-transport-security
    • https://www.beddingtondentalclinic.com/service/all-on-4-teeth-in-a-day/ → no strict-transport-security
    • https://www.beddingtondentalclinic.com/service/amalgam-free/ → no strict-transport-security
    • https://www.beddingtondentalclinic.com/service/bone-graft/ → no strict-transport-security
  • FoundContent Security PolicyMedium

    None of the 150 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.beddingtondentalclinic.com/ → no content-security-policy
    • https://www.beddingtondentalclinic.com/canadian-dental-care-plan/ → no content-security-policy
    • https://www.beddingtondentalclinic.com/our-team/ → no content-security-policy
    • https://www.beddingtondentalclinic.com/tour-the-office/ → no content-security-policy
    • https://www.beddingtondentalclinic.com/blog/ → no content-security-policy
    • https://www.beddingtondentalclinic.com/saturday-dentist/ → no content-security-policy
    • https://www.beddingtondentalclinic.com/privacy-policy/ → no content-security-policy
    • https://www.beddingtondentalclinic.com/patient-forms/ → no content-security-policy
    • https://www.beddingtondentalclinic.com/financials/ → no content-security-policy
    • https://www.beddingtondentalclinic.com/service/all-on-4-teeth-in-a-day/ → no content-security-policy
    • https://www.beddingtondentalclinic.com/service/amalgam-free/ → no content-security-policy
    • https://www.beddingtondentalclinic.com/service/bone-graft/ → 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.beddingtondentalclinic.com/ → no x-frame-options
    • https://www.beddingtondentalclinic.com/canadian-dental-care-plan/ → no x-frame-options
    • https://www.beddingtondentalclinic.com/our-team/ → no x-frame-options
    • https://www.beddingtondentalclinic.com/tour-the-office/ → no x-frame-options
    • https://www.beddingtondentalclinic.com/blog/ → no x-frame-options
    • https://www.beddingtondentalclinic.com/saturday-dentist/ → no x-frame-options
    • https://www.beddingtondentalclinic.com/privacy-policy/ → no x-frame-options
    • https://www.beddingtondentalclinic.com/patient-forms/ → no x-frame-options
    • https://www.beddingtondentalclinic.com/financials/ → no x-frame-options
    • https://www.beddingtondentalclinic.com/service/all-on-4-teeth-in-a-day/ → no x-frame-options
    • https://www.beddingtondentalclinic.com/service/amalgam-free/ → no x-frame-options
    • https://www.beddingtondentalclinic.com/service/bone-graft/ → 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.beddingtondentalclinic.com/ → no x-content-type-options
    • https://www.beddingtondentalclinic.com/canadian-dental-care-plan/ → no x-content-type-options
    • https://www.beddingtondentalclinic.com/our-team/ → no x-content-type-options
    • https://www.beddingtondentalclinic.com/tour-the-office/ → no x-content-type-options
    • https://www.beddingtondentalclinic.com/blog/ → no x-content-type-options
    • https://www.beddingtondentalclinic.com/saturday-dentist/ → no x-content-type-options
    • https://www.beddingtondentalclinic.com/privacy-policy/ → no x-content-type-options
    • https://www.beddingtondentalclinic.com/patient-forms/ → no x-content-type-options
    • https://www.beddingtondentalclinic.com/financials/ → no x-content-type-options
    • https://www.beddingtondentalclinic.com/service/all-on-4-teeth-in-a-day/ → no x-content-type-options
    • https://www.beddingtondentalclinic.com/service/amalgam-free/ → no x-content-type-options
    • https://www.beddingtondentalclinic.com/service/bone-graft/ → 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.beddingtondentalclinic.com/ → no referrer-policy
    • https://www.beddingtondentalclinic.com/canadian-dental-care-plan/ → no referrer-policy
    • https://www.beddingtondentalclinic.com/our-team/ → no referrer-policy
    • https://www.beddingtondentalclinic.com/tour-the-office/ → no referrer-policy
    • https://www.beddingtondentalclinic.com/blog/ → no referrer-policy
    • https://www.beddingtondentalclinic.com/saturday-dentist/ → no referrer-policy
    • https://www.beddingtondentalclinic.com/privacy-policy/ → no referrer-policy
    • https://www.beddingtondentalclinic.com/patient-forms/ → no referrer-policy
    • https://www.beddingtondentalclinic.com/financials/ → no referrer-policy
    • https://www.beddingtondentalclinic.com/service/all-on-4-teeth-in-a-day/ → no referrer-policy
    • https://www.beddingtondentalclinic.com/service/amalgam-free/ → no referrer-policy
    • https://www.beddingtondentalclinic.com/service/bone-graft/ → 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.beddingtondentalclinic.com/ → no permissions-policy
    • https://www.beddingtondentalclinic.com/canadian-dental-care-plan/ → no permissions-policy
    • https://www.beddingtondentalclinic.com/our-team/ → no permissions-policy
    • https://www.beddingtondentalclinic.com/tour-the-office/ → no permissions-policy
    • https://www.beddingtondentalclinic.com/blog/ → no permissions-policy
    • https://www.beddingtondentalclinic.com/saturday-dentist/ → no permissions-policy
    • https://www.beddingtondentalclinic.com/privacy-policy/ → no permissions-policy
    • https://www.beddingtondentalclinic.com/patient-forms/ → no permissions-policy
    • https://www.beddingtondentalclinic.com/financials/ → no permissions-policy
    • https://www.beddingtondentalclinic.com/service/all-on-4-teeth-in-a-day/ → no permissions-policy
    • https://www.beddingtondentalclinic.com/service/amalgam-free/ → no permissions-policy
    • https://www.beddingtondentalclinic.com/service/bone-graft/ → 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 (737 responses)
    • x-powered-by: WP Rocket/3.21.0.1 (2 responses)
  • NoteThird-party scripts

    Scripts run from 3 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.)

    • cdnjs.cloudflare.com (120 script tags)
    • www.google.com (40 script tags)
    • cdn.callrail.com (40 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/
6 checks passed, 1 not applicable
  • OKHTTPS

    All 150 crawled pages were served over HTTPS.

  • OKMixed content

    No HTTPS page loads a script, stylesheet, font or image over plain HTTP.

  • OKForms over HTTPS

    3 forms found, all on HTTPS pages posting to HTTPS addresses.

  • OKVulnerable JavaScript libraries

    2 library versions recognised, none with known vulnerabilities.

  • OKKeys and secrets in page code

    No API keys, tokens or private keys were found in the sampled HTML and scripts.

  • 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.beddingtondentalclinic.com

Their neighbours in the SEO rank table, which orders every scanned site by health score.

This report was produced by the DIY SEO Hub Site Spider crawling www.beddingtondentalclinic.com from its pages as published, the way a search engine does. It shows summary figures only.

Own www.beddingtondentalclinic.com?

  • 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.beddingtondentalclinic.com. Removal needs no account and no proof of purchase.
www.beddingtondentalclinic.com scan 2026-10-05-0505 | DIY SEO Hub