Scanned sites / www.123dentist.com / 2026-10-03-1017

www.123dentist.com scan from 10/3/2026, 10:17:39 AM

Scan 2026-10-03-1017

Scanned 10/3/2026, 10:17:39 AM, finished 10/4/2026, 6:01:44 AM. Found on page 1 of brave web search results

Site: https://www.123dentist.com/

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

66/ 100Needs work

On October 3, 2026 the Site Spider crawled 3065 pages and 2931 assets of www.123dentist.com, starting from https://www.123dentist.com/. It scored 66 out of 100, a result that needs work. 10 of 16 checks found something to fix, led by title tags (1,011), heavy assets (23), sitemap coverage (1,653); 4 checks passed. Most of the points went to title tags (−6.1), heavy assets (−6), sitemap coverage (−5.9). 2 checks found something the score does not count, listed as noted. 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, 2 low and 1 info findings. See the security findings ↓

Pages crawled
3065
Assets fetched
2931
Status
Completed
Checks with issues
10 of 16
CoverageJob finished, partial coverage

5,996 of 6,000 discovered URLs were fetched, 4 blocked by robots.txt, 32,385 left out by the 5,000-page and 1,000-asset budget. The job finished, but the crawl did not reach everything it found. HTML only: nothing here ran JavaScript. 300 link destinations on other sites were checked, 1916 left unchecked.

  • Title tags1,011 issues
    1011 of 1653 pages have title issues. 18 noindex or canonicalized pages excluded.
    −6.1 points
  • Meta descriptions913 issues
    913 of 1653 pages have meta description issues. 18 noindex or canonicalized pages excluded.
    −4.4 points
  • Headings1,060 issues
    1060 of 1653 pages have heading issues. 18 noindex or canonicalized pages excluded.
    −3.8 points
  • Broken links8 issues
    863 internal links point at 8 broken URLs.
    −0.1 points
  • Links to other sites7,285 noted
    0 destinations answered with an error, 294 could not be determined (timeouts, rate limits or refusals), 1916 were left unchecked by the per-scan cap, of 300 destinations checked.
  • Redirects843 issues
    844 redirecting URLs, 0 of them chained.
    −2 points
  • Non-200 responses551 issues
    1395 URLs did not return a 2xx response. 1394 of them are pages, 551 with an error status; the rest are assets or redirects.
    −3.3 points
  • Rate limitedOK
    The site did not rate limit the crawler.
  • Indexability5 issues
    5 of 1669 indexable pages have indexability warnings. 2 pages noindex by design.
  • Image alt textOK
    0 of 25567 image references have no alt attribute. 10550 use an empty alt (decorative), which is fine.
  • Heavy assets23 issues
    23 assets larger than 500 KB among 2931 fetched assets.
    −6 points
  • Orphan pagesOK
    0 pages have no internal links pointing at them.
  • Sitemap coverage1,653 issues
    1 sitemap listing 0 URLs: 1653 crawled pages missing, 0 listed URLs broken or redirecting, 0 reachable only via the sitemap.
    −5.9 points
  • Internal link countsOK
    Internal link counts for 500 pages.
  • Thin contentOK
    0 of 1653 pages have fewer than 200 words. 18 noindex or canonicalized pages excluded.
  • Duplicate content551 issues
    1 group of pages with identical HTML.
    −2.6 points

Where this scan sits among all scanned sites

2051 sites, median 80%, average 78%

www.123dentist.com scores 66%, higher than 10% of the 2051 scanned sites. See the full ranking.

0521040%: 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%: 2 sites36%: 1 site37%: 2 sites38%: 2 sites39%: 1 site40%: 2 sites41%: 3 sites42%: 0 sites43%: 1 site44%: 1 site45%: 4 sites46%: 4 sites47%: 3 sites48%: 2 sites49%: 6 sites50%: 4 sites51%: 3 sites52%: 9 sites53%: 6 sites54%: 8 sites55%: 6 sites56%: 6 sites57%: 7 sites58%: 14 sites59%: 6 sites60%: 10 sites61%: 14 sites62%: 16 sites63%: 19 sites64%: 16 sites65%: 28 sites66%: 24 sites67%: 39 sites68%: 34 sites69%: 24 sites70%: 46 sites71%: 48 sites72%: 64 sites73%: 57 sites74%: 57 sites75%: 73 sites76%: 83 sites77%: 76 sites78%: 96 sites79%: 78 sites80%: 104 sites81%: 102 sites82%: 99 sites83%: 91 sites84%: 87 sites85%: 73 sites86%: 76 sites87%: 66 sites88%: 67 sites89%: 53 sites90%: 39 sites91%: 39 sites92%: 33 sites93%: 17 sites94%: 14 sites95%: 10 sites96%: 7 sites97%: 8 sites98%: 1 site99%: 2 sites100%: 56 sites66% 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 several critical SEO issues requiring attention, especially broken links and non-200 responses. Fixing these and enhancing title tags and meta descriptions can improve performance significantly.

  1. 1

    Fix Broken Links

    Why: Resolving broken links enhances user experience and SEO rankings.

    How: Identify and update/remove links to the 8 broken URLs listed in your crawl report.

    Checks: broken-links

  2. 2

    Resolve Non-200 Responses

    Why: Correcting URL issues boosts usability and search engine rankings.

    How: Address the 1395 URLs with non-200 responses, focusing on 551 errors.

    Checks: status-codes

  3. 3

    Improve Sitemap Coverage

    Why: A complete sitemap helps search engines index your pages accurately.

    How: Update your sitemap to include 1653 crawled pages that are missing.

    Checks: sitemap-coverage

  4. 4

    Fix Title Tag Issues

    Why: Unique and optimal title tags enhance search visibility.

    How: Revise titles for 1011 pages as per the guidelines of length and uniqueness.

    Checks: titles

  5. 5

    Enhance Meta Descriptions

    Why: Proper meta descriptions improve click-through rates from search results.

    How: Create or revise meta descriptions for 913 pages identified as having issues.

    Checks: meta-descriptions

  6. 6

    Address Headings Issues

    Why: Properly structured headings improve SEO and clarity for users.

    How: Consolidate headings to ensure only one H1 per page for 1060 pages with heading issues.

    Checks: headings

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

Your website has several security risks, including missing Content Security Policy headers, outdated JavaScript libraries with known vulnerabilities, and an exposed Google API key. Addressing these issues is crucial to improving your site's security posture.

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

    Missing Content Security PolicyMedium

    Why it matters: Without a Content Security Policy (CSP), your site is vulnerable to attacks such as Cross-Site Scripting (XSS).

    Fix: Implement a CSP header to control the sources of scripts, styles, and frames. For example: Content-Security-Policy: default-src 'self'; script-src 'self' https://trustedscripts.example.com.

    Evidence: Content Security Policy

  2. 2

    Vulnerable JavaScript LibrariesMedium

    Why it matters: Outdated jQuery versions in use have known vulnerabilities that may be exploited depending on site usage.

    Fix: Upgrade jQuery versions to at least 3.5.0 to fix these vulnerabilities.

    Evidence: Vulnerable JavaScript libraries

  3. 3

    Exposed Google API KeyMedium

    Why it matters: The Google API key found in the code can be abused if not restricted appropriately.

    Fix: Restrict the API key usage in the Google Cloud console by setting HTTP referrer restrictions.

    Evidence: Keys and secrets in page code

  4. 4

    Software Version DisclosureLow

    Why it matters: The server banners disclose the framework but not the version, which can provide hints for attackers.

    Fix: Consider removing the X-Powered-By header or customize it to hide framework details.

    Evidence: Software version disclosure

  5. 5

    Third-Party Scripts Without Subresource IntegrityLow

    Why it matters: Scripts from other domains can be altered, posing a risk if any are compromised.

    Fix: Implement Subresource Integrity (SRI) for third-party scripts where possible, or use a Content Security Policy.

    Evidence: Third-party scripts

  6. 6

    Sensitive Paths in robots.txtInfo

    Why it matters: The robots.txt file includes private paths which are publicly accessible, potentially exposing sensitive areas of your site.

    Fix: Review and secure the paths mentioned in robots.txt with appropriate access controls.

    Evidence: Sensitive paths in robots.txt

What the checks found

  • FoundContent Security PolicyMedium

    None of the 1671 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.123dentist.com/ → no content-security-policy
    • https://www.123dentist.com/find-your-dentist/ → no content-security-policy
    • https://www.123dentist.com/contact-us/ → no content-security-policy
    • https://www.123dentist.com/fr/ → no content-security-policy
    • https://www.123dentist.com/alberta/ → no content-security-policy
    • https://www.123dentist.com/alberta/calgary/ → no content-security-policy
    • https://www.123dentist.com/alberta/edmonton/ → no content-security-policy
    • https://www.123dentist.com/alberta/red-deer/ → no content-security-policy
    • https://www.123dentist.com/british-columbia/ → no content-security-policy
    • https://www.123dentist.com/british-columbia/vancouver/ → no content-security-policy
    • https://www.123dentist.com/british-columbia/surrey/ → no content-security-policy
    • https://www.123dentist.com/british-columbia/burnaby/ → no content-security-policy
  • FoundVulnerable JavaScript librariesMedium

    2 libraries with published vulnerabilities: jQuery 3.1.2, jQuery 3.1.3. Whether they are exploitable depends on how the site uses them, but each has a fixed release.

    • jQuery 3.1.2 in https://www.123dentist.com/wp-content/plugins/gravityforms/js/placeholders.jque…: CVE-2019-11358 (prototype pollution), CVE-2020-11022, CVE-2020-11023 (XSS via HTML passed to DOM methods); fixed in 3.5.0
    • jQuery 3.1.3 in https://www.123dentist.com/wp-content/plugins/gravityforms/js/placeholders.jque…: CVE-2019-11358 (prototype pollution), CVE-2020-11022, CVE-2020-11023 (XSS via HTML passed to DOM methods); fixed in 3.5.0
  • FoundKeys and secrets in page codeMedium

    1 credential-like value found in code served to every visitor: Google API key.

    • Google API key AIzaSy…yo (39 chars) in https://www.123dentist.com/: browser keys are expected in pages, but must be restricted by HTTP referrer and API in the Google Cloud console
  • NoteSoftware version disclosure

    Responses name the framework in an X-Powered-By header but hide the version.

    • server: cloudflare (5996 responses)
    • x-powered-by: WP Engine (17 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.)

    • next-api.patientprism.com (40 script tags)
    • maps.googleapis.com (40 script tags)
    • www.google.com (40 script tags)
  • NoteSensitive paths in robots.txt

    robots.txt lists 2 paths 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/
    • Disallow: /wp-login.php
10 checks passed
  • OKHTTPS

    All 1671 crawled pages were served over HTTPS.

  • OKHTTP Strict Transport Security

    strict-transport-security is set on all 1671 HTML pages.

  • OKClickjacking protection

    x-frame-options is set on all 1671 HTML pages.

  • OKMIME sniffing protection

    x-content-type-options is set on all 1671 HTML pages.

  • OKReferrer policy

    referrer-policy is set on all 1671 HTML pages.

  • OKPermissions policy

    permissions-policy is set on all 1671 HTML pages.

  • OKCookie flags

    All 1 cookie carry Secure, HttpOnly and SameSite flags.

  • OKMixed content

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

  • OKForms over HTTPS

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

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

Own www.123dentist.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.123dentist.com. Removal needs no account and no proof of purchase.
www.123dentist.com scan 2026-10-03-1017 | DIY SEO Hub