Scanned sites / www.glamorgandental.ca / 2026-10-25-0103

www.glamorgandental.ca scan from 2026-10-25 01:03:43 UTC DR 3

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

Scan 2026-10-25-0103

Scanned 2026-10-25 01:03:43 UTC, finished 2026-10-25 01:05:26 UTC. Found with openstreetmap overpass

Site: https://www.glamorgandental.ca/

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

86/ 100Good

On October 25, 2026 the Site Spider crawled 120 pages and 150 assets of www.glamorgandental.ca, starting from https://www.glamorgandental.ca/. It scored 86 out of 100, a good result. 9 of 33 checks found something to fix, led by heavy assets (17), meta descriptions (50), links to other sites (5); 11 checks passed. Most of the points went to heavy assets (−6), meta descriptions (−3.6), links to other sites (−1.8). 13 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: Medium5 medium and 3 low findings. See the security findings ↓

Pages crawled
120
Assets fetched
150
Status
Completed
Checks with issues
9 of 33
CoverageComplete crawl

270 of 286 discovered URLs were fetched, 16 blocked by robots.txt. The crawl reached everything it found. HTML only: nothing here ran JavaScript. 40 link destinations on other sites were checked.

  • Title tags19 issues
    19 of 98 pages have title issues. 13 noindex or canonicalized pages excluded.
    −1.7 points
  • Meta descriptions50 issues
    50 of 98 pages have meta description issues. 13 noindex or canonicalized pages excluded.
    −3.6 points
  • Headings9 issues
    9 of 98 pages have heading issues. 13 noindex or canonicalized pages excluded.
    −0.5 points
  • Broken linksOK
    0 internal links point at 0 broken URLs.
  • Links to other sites5 issues
    5 destinations answered with an error, 19 could not be determined (timeouts, rate limits or refusals), of 40 destinations checked.
    −1.8 points
  • Redirects9 issues
    9 redirecting URLs, 2 of them chained.
    −0.3 points
  • Non-200 responses9 noted
    9 URLs did not return a 2xx response. 9 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.
  • Indexability3 issues
    3 of 101 indexable pages have indexability warnings. 10 pages noindex by design.
    −0.3 points
  • Image alt textOK
    0 of 279 image references have no alt attribute. 68 use an empty alt (decorative), which is fine.
  • Heavy assets17 issues
    17 assets larger than 500 KB among 150 fetched assets.
    −6 points
  • Orphan pages4 issues
    4 pages have no internal links pointing at them.
    −0.1 points
  • Sitemap coverage4 issues
    1 sitemap listing 98 URLs: 0 crawled pages missing, 0 listed URLs broken or redirecting, 4 reachable only via the sitemap.
    −0.2 points
  • Internal link counts10 noted
    Internal link counts for 111 pages; 10 worth a look.
  • Thin contentOK
    0 of 98 pages have fewer than 200 words. 13 noindex or canonicalized pages excluded.
  • Duplicate contentOK
    0 groups of pages with identical HTML.
  • URL format3 noted
    3 of 120 page URLs are harder to read, share or cache than they need to be.
  • Canonicals13 noted
    13 of 111 pages have a canonical worth checking.
  • Robots directives111 noted
    111 pages carry a robots directive; 0 carry none.
  • Anchor text12 noted
    12 destinations are linked without useful anchor text, or with nofollow.
  • Title and heading structure5 noted
    5 of 98 pages could use the title, heading and snippet space better. 13 noindex or canonicalized pages excluded.
  • Image weight and alt length14 noted
    14 images over 100 KB; 0 with alt text over 100 characters.
  • Response anomalies3 noted
    3 URLs answered in a way worth looking at.
  • HTML and head validationOK
    All 111 pages keep their head tags in <head>, once each, under Googlebot's 2 MB.
  • hreflangOK
    No page declares hreflang.
  • Structured data11 noted
    78 of 98 indexable pages carry structured data: Organization (42), FAQPage (37), Question (37), Answer (37), Dentist (35). 11 pages with errors a rich result would fail on.
  • Near duplicatesOK
    No near duplicates among 93 pages with enough text to compare.
  • Soft 404sOK
    None of 111 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 positions4 noted
    4 of 94 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 cookies1 noted
    1 cookie set by the site, 1 missing a protective flag; 11 response headers recorded across 270 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 111 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.
  • Spelling30 noted
    30 words an English dictionary does not know, on 42 pages. Product names and jargon will appear here too.

Where this scan sits among all scanned sites

2315 sites, median 79%, average 78%

www.glamorgandental.ca scores 86%, higher than 77% of the 2315 scanned sites. See the full ranking.

0571140%: 0 sites1%: 0 sites2%: 0 sites3%: 0 sites4%: 0 sites5%: 0 sites6%: 0 sites7%: 0 sites8%: 0 sites9%: 1 site10%: 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%: 17 sites59%: 8 sites60%: 16 sites61%: 12 sites62%: 19 sites63%: 27 sites64%: 22 sites65%: 32 sites66%: 36 sites67%: 34 sites68%: 35 sites69%: 46 sites70%: 44 sites71%: 68 sites72%: 70 sites73%: 69 sites74%: 69 sites75%: 71 sites76%: 86 sites77%: 92 sites78%: 107 sites79%: 85 sites80%: 106 sites81%: 105 sites82%: 114 sites83%: 98 sites84%: 108 sites85%: 86 sites86%: 69 sites87%: 73 sites88%: 59 sites89%: 63 sites90%: 33 sites91%: 44 sites92%: 37 sites93%: 23 sites94%: 16 sites95%: 11 sites96%: 9 sites97%: 12 sites98%: 4 sites99%: 1 site100%: 70 sites86% 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

The website has several redirect issues, title and meta description errors, and orphan pages. Optimizing these will enhance SEO performance. Focus on resolving redirects and improving titles and descriptions for maximum impact.

  1. 1

    Fix Redirect Issues

    Why: Reduce redirect chains to improve loading speed and user experience.

    How: Update URLs to link directly. Ensure consistent URL format across mentions.

    Checks: redirects

  2. 2

    Address Title Tag Problems

    Why: Enhancing title tags can improve click-through rates and relevance.

    How: Revise titles for 19 pages to stay within 50-60 characters based on SEO best practices.

    Checks: titles

  3. 3

    Rectify Meta Description Issues

    Why: Clear and relevant meta descriptions can boost visibility in search results.

    How: Add or refine meta descriptions for 50 pages, ensuring they succinctly describe page content.

    Checks: meta-descriptions

  4. 4

    Resolve Headings Problems

    Why: Proper headings improve content structure and user readability.

    How: Add H1 tags to 9 pages where they are missing or correct multiple H1s.

    Checks: headings

  5. 5

    Improve Orphan Pages' Internal Linking

    Why: Linking to orphan pages enhances site navigation and authority.

    How: Add internal links to 4 orphan pages from relevant existing content.

    Checks: orphan-pages

  6. 6

    Optimize Heavy Assets

    Why: Reducing the size of assets improves website load speed.

    How: Reduce the size of large assets, especially scripts, used on multiple pages.

    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 has several security headers missing that could expose users to risks like man-in-the-middle attacks, clickjacking, and information leakage. Immediate action is required to enhance security practices and protect both the site and its visitors.

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

    Missing HTTP Strict Transport Security (HSTS)Medium

    Why it matters: HSTS prevents man-in-the-middle attacks that could occur if a user types the URL without 'https://'.

    Fix: Add the header 'Strict-Transport-Security' with a value of 'max-age=31536000; includeSubDomains'.

    Evidence: HTTP Strict Transport Security

  2. 2

    Missing Content Security Policy (CSP)Medium

    Why it matters: Without a CSP, the site is vulnerable to cross-site scripting (XSS) attacks as scripts can load from untrusted sources.

    Fix: Implement 'Content-Security-Policy' header, for example: 'default-src 'self'; script-src 'self' https://trusted.com;'.

    Evidence: Content Security Policy

  3. 3

    Missing Clickjacking ProtectionMedium

    Why it matters: Without X-Frame-Options, the site can be embedded in other sites, risking clickjacking attacks.

    Fix: Add 'X-Frame-Options' header with a value 'DENY'.

    Evidence: Clickjacking protection

  4. 4

    Cookie Flags MissingMedium

    Why it matters: Cookies without flags can be read by client-side scripts, increasing risk of attacks.

    Fix: Set the cookie 'tpg_post_views' with flags: 'HttpOnly', 'Secure', and 'SameSite=Strict'.

    Evidence: Cookie flags

  5. 5

    Exposed Google API KeyMedium

    Why it matters: An exposed API key can be abused by others, leading to potential data leaks and incursions.

    Fix: Restrict the API key in the Google Cloud console to specific referrers that are authorized.

    Evidence: Keys and secrets in page code

  6. 6

    Missing MIME Sniffing ProtectionLow

    Why it matters: Lack of this header may lead browsers to execute files as different types than intended.

    Fix: Add 'X-Content-Type-Options' header with a value of 'nosniff'.

    Evidence: MIME sniffing protection

  7. 7

    Missing Referrer PolicyLow

    Why it matters: Without this policy, sensitive URL information can be leaked to third-party sites.

    Fix: Add 'Referrer-Policy' header with a value of 'no-referrer-when-downgrade'.

    Evidence: Referrer policy

  8. 8

    Server Version DisclosureLow

    Why it matters: Detailed server banners leak information that could help attackers exploit known vulnerabilities.

    Fix: Remove or obscure server banners in the configuration to prevent revealing version information.

    Evidence: Software version disclosure

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.glamorgandental.ca/ → no strict-transport-security
    • https://www.glamorgandental.ca/canadian-dental-care-plan/ → no strict-transport-security
    • https://www.glamorgandental.ca/about/ → no strict-transport-security
    • https://www.glamorgandental.ca/blog/ → no strict-transport-security
    • https://www.glamorgandental.ca/privacy-policy/ → no strict-transport-security
    • https://www.glamorgandental.ca/service/cosmetic-dentistry/ → no strict-transport-security
    • https://www.glamorgandental.ca/service/dental-crowns/ → no strict-transport-security
    • https://www.glamorgandental.ca/service/dental-veneers/ → no strict-transport-security
    • https://www.glamorgandental.ca/service/dental-bonding/ → no strict-transport-security
    • https://www.glamorgandental.ca/service/restorative-dentistry/ → no strict-transport-security
    • https://www.glamorgandental.ca/service/dental-bridges/ → no strict-transport-security
    • https://www.glamorgandental.ca/service/dental-filling/ → no strict-transport-security
  • FoundContent Security PolicyMedium

    None of the 111 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.glamorgandental.ca/ → no content-security-policy
    • https://www.glamorgandental.ca/canadian-dental-care-plan/ → no content-security-policy
    • https://www.glamorgandental.ca/about/ → no content-security-policy
    • https://www.glamorgandental.ca/blog/ → no content-security-policy
    • https://www.glamorgandental.ca/privacy-policy/ → no content-security-policy
    • https://www.glamorgandental.ca/service/cosmetic-dentistry/ → no content-security-policy
    • https://www.glamorgandental.ca/service/dental-crowns/ → no content-security-policy
    • https://www.glamorgandental.ca/service/dental-veneers/ → no content-security-policy
    • https://www.glamorgandental.ca/service/dental-bonding/ → no content-security-policy
    • https://www.glamorgandental.ca/service/restorative-dentistry/ → no content-security-policy
    • https://www.glamorgandental.ca/service/dental-bridges/ → no content-security-policy
    • https://www.glamorgandental.ca/service/dental-filling/ → 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.glamorgandental.ca/ → no x-frame-options
    • https://www.glamorgandental.ca/canadian-dental-care-plan/ → no x-frame-options
    • https://www.glamorgandental.ca/about/ → no x-frame-options
    • https://www.glamorgandental.ca/blog/ → no x-frame-options
    • https://www.glamorgandental.ca/privacy-policy/ → no x-frame-options
    • https://www.glamorgandental.ca/service/cosmetic-dentistry/ → no x-frame-options
    • https://www.glamorgandental.ca/service/dental-crowns/ → no x-frame-options
    • https://www.glamorgandental.ca/service/dental-veneers/ → no x-frame-options
    • https://www.glamorgandental.ca/service/dental-bonding/ → no x-frame-options
    • https://www.glamorgandental.ca/service/restorative-dentistry/ → no x-frame-options
    • https://www.glamorgandental.ca/service/dental-bridges/ → no x-frame-options
    • https://www.glamorgandental.ca/service/dental-filling/ → 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.glamorgandental.ca/ → no x-content-type-options
    • https://www.glamorgandental.ca/canadian-dental-care-plan/ → no x-content-type-options
    • https://www.glamorgandental.ca/about/ → no x-content-type-options
    • https://www.glamorgandental.ca/blog/ → no x-content-type-options
    • https://www.glamorgandental.ca/privacy-policy/ → no x-content-type-options
    • https://www.glamorgandental.ca/service/cosmetic-dentistry/ → no x-content-type-options
    • https://www.glamorgandental.ca/service/dental-crowns/ → no x-content-type-options
    • https://www.glamorgandental.ca/service/dental-veneers/ → no x-content-type-options
    • https://www.glamorgandental.ca/service/dental-bonding/ → no x-content-type-options
    • https://www.glamorgandental.ca/service/restorative-dentistry/ → no x-content-type-options
    • https://www.glamorgandental.ca/service/dental-bridges/ → no x-content-type-options
    • https://www.glamorgandental.ca/service/dental-filling/ → 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.glamorgandental.ca/ → no referrer-policy
    • https://www.glamorgandental.ca/canadian-dental-care-plan/ → no referrer-policy
    • https://www.glamorgandental.ca/about/ → no referrer-policy
    • https://www.glamorgandental.ca/blog/ → no referrer-policy
    • https://www.glamorgandental.ca/privacy-policy/ → no referrer-policy
    • https://www.glamorgandental.ca/service/cosmetic-dentistry/ → no referrer-policy
    • https://www.glamorgandental.ca/service/dental-crowns/ → no referrer-policy
    • https://www.glamorgandental.ca/service/dental-veneers/ → no referrer-policy
    • https://www.glamorgandental.ca/service/dental-bonding/ → no referrer-policy
    • https://www.glamorgandental.ca/service/restorative-dentistry/ → no referrer-policy
    • https://www.glamorgandental.ca/service/dental-bridges/ → no referrer-policy
    • https://www.glamorgandental.ca/service/dental-filling/ → 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.glamorgandental.ca/ → no permissions-policy
    • https://www.glamorgandental.ca/canadian-dental-care-plan/ → no permissions-policy
    • https://www.glamorgandental.ca/about/ → no permissions-policy
    • https://www.glamorgandental.ca/blog/ → no permissions-policy
    • https://www.glamorgandental.ca/privacy-policy/ → no permissions-policy
    • https://www.glamorgandental.ca/service/cosmetic-dentistry/ → no permissions-policy
    • https://www.glamorgandental.ca/service/dental-crowns/ → no permissions-policy
    • https://www.glamorgandental.ca/service/dental-veneers/ → no permissions-policy
    • https://www.glamorgandental.ca/service/dental-bonding/ → no permissions-policy
    • https://www.glamorgandental.ca/service/restorative-dentistry/ → no permissions-policy
    • https://www.glamorgandental.ca/service/dental-bridges/ → no permissions-policy
    • https://www.glamorgandental.ca/service/dental-filling/ → 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 (270 responses)
    • x-powered-by: WP Rocket/3.23 (2 responses)
  • FoundCookie flagsMedium

    1 of 1 cookie are missing protective flags. Without HttpOnly a script can read the cookie; without Secure it travels over plain HTTP; without SameSite it is sent on cross-site requests.

    • tpg_post_views (set by https://www.glamorgandental.ca/blog/the-science-behind-dental-bonding-how-it-wo…) lacks HttpOnly, SameSite
  • 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.glamorgandental.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 5 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.)

    • fd.cleantalk.org (40 script tags)
    • maps.google.com (40 script tags)
    • app.medianv.com (40 script tags)
    • cdn.trustindex.io (3 script tags)
    • cdn.callrail.com (3 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
  • OKHTTPS

    All 111 crawled pages were served over HTTPS.

  • OKMixed content

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

  • OKForms over HTTPS

    39 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.

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.glamorgandental.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.glamorgandental.ca from its pages as published, the way a search engine does. It shows summary figures only.

Own www.glamorgandental.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.glamorgandental.ca. Removal needs no account and no proof of purchase.