Scanned sites / www.123dentist.com / 2026-09-13-1947
www.123dentist.com scan from 2026-09-13 19:47:32 UTC DR 67
A newer scan exists. See the latest report for www.123dentist.com.
DR is Ahrefs Domain Rating (0-100, backlink strength), used under its Domain Rating License.
Scan 2026-09-13-1947
Scanned 2026-09-13 19:47:32 UTC, finished 2026-09-13 23:25:41 UTC. 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.
On September 13, 2026 the Site Spider crawled 3365 pages and 2948 assets of www.123dentist.com, starting from https://www.123dentist.com/. It scored 63 out of 100, a result that needs work. 10 of 27 checks found something to fix, led by title tags (996), heavy assets (31), sitemap coverage (1,643); 6 checks passed. Most of the points went to title tags (−6), heavy assets (−6), sitemap coverage (−5.9). 11 checks found something the score does not count, listed as noted. 10 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 1 low findings. See the security findings ↓
- Pages crawled
- 3365
- Assets fetched
- 2948
- Status
- Completed
- Checks with issues
- 10 of 27
6,313 of 6,317 discovered URLs were fetched, 4 blocked by robots.txt, 27,479 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. 339 link destinations on other sites were checked, 1876 left unchecked.
- Title tags996 issues996 of 1643 pages have title issues. 22 noindex or canonicalized pages excluded.−6 points
- Meta descriptions896 issues896 of 1643 pages have meta description issues. 22 noindex or canonicalized pages excluded.−4.3 points
- Headings1,044 issues1044 of 1643 pages have heading issues. 22 noindex or canonicalized pages excluded.−3.8 points
- Broken links8 issues857 internal links point at 8 broken URLs.−0.1 points
- Links to other sites7,316 noted0 destinations answered with an error, 294 could not be determined (timeouts, rate limits or refusals), 1876 were left unchecked by the per-scan cap, of 300 destinations checked.
- Redirects855 issues856 redirecting URLs, 0 of them chained.−2.1 points
- Non-200 responses845 issues1701 URLs did not return a 2xx response. 1700 of them are pages, 845 with an error status; the rest are assets or redirects.−5.1 points
- Rate limitedOKThe site did not rate limit the crawler.
- Indexability5 issues5 of 1663 indexable pages have indexability warnings. 2 pages noindex by design.
- Image alt textOK0 of 25520 image references have no alt attribute. 10341 use an empty alt (decorative), which is fine.
- Heavy assets31 issues31 assets larger than 500 KB among 2948 fetched assets.−6 points
- Orphan pagesOK0 pages have no internal links pointing at them.
- Sitemap coverage1,643 issues1 sitemap listing 0 URLs: 1643 crawled pages missing, 0 listed URLs broken or redirecting, 0 reachable only via the sitemap.−5.9 points
- Internal link counts93 notedInternal link counts for 500 pages; 93 worth a look.
- Thin contentOK0 of 1643 pages have fewer than 200 words. 22 noindex or canonicalized pages excluded.
- Duplicate content845 issues1 group of pages with identical HTML.−4.1 points
- URL format1,712 noted1712 of 3365 page URLs are harder to read, share or cache than they need to be.
- Canonicals22 noted22 of 1665 pages have a canonical worth checking.
- Robots directives1,665 noted1665 pages carry a robots directive; 0 carry none.
- Anchor text950 noted950 destinations are linked without useful anchor text, or with nofollow.
- Title and heading structure993 noted993 of 1643 pages could use the title, heading and snippet space better. 22 noindex or canonicalized pages excluded.
- Image weight and alt length2,009 noted832 images over 100 KB; 1177 with alt text over 100 characters.
- Response anomalies838 noted838 URLs answered in a way worth looking at.
- HTML and head validationNot checkedNot checked: this scan was crawled before this check existed. Scan the site again to run it.
- hreflangNot checkedNot checked: this scan was crawled before this check existed. Scan the site again to run it.
- Structured dataNot checkedNot checked: this scan was crawled before this check existed. Scan the site again to run it.
- Near duplicatesNot checkedNot checked: this scan was crawled before this check existed. Scan the site again to run it.
- Soft 404s2 noted2 pages answer 200 but say they are not there.
- AccessibilityNot checkedNot checked: the accessibility audit runs in the browser. Tick "Include JavaScript rendering checks" when you request a scan to run it.
- Link positionsNot checkedNot checked: this scan was crawled before link positions were recorded. Scan the site again to run it.
- PaginationNot checkedNot checked: this scan was crawled before this check existed. Scan the site again to run it.
- Headers and cookiesOK0 cookies set by the site; 14 response headers recorded across 6313 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 1665 pages; 1457 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 Insights5 notedMobile performance 57 on average across 5 pages; 5 below Google's good thresholds.
- SpellingNot checkedNot checked: this scan was crawled before this check existed. Scan the site again to run it.
Where this scan sits among all scanned sites
2924 sites, median 80%, average 79%
www.123dentist.com scores 63%, higher than 7% of the 2924 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 findingsWritten from an earlier version of the analysis. The findings on this page have been recomputed since, so counts and labels here may differ from what the plan describes. The advice still points at the same checks.
Your website has several significant SEO issues, including broken links and status code errors. Addressing these will improve site health and search visibility.
- 1
Fix Broken Links
Why: 857 internal links are broken, affecting user experience and SEO.
How: Identify broken links from your crawl report and either update them to point to the correct URLs or remove them.
Checks: broken-links
- 2
Resolve Non-200 Responses
Why: 1701 pages return non-200 status codes, hindering access and indexing.
How: Check the URLs for errors, redirecting or correcting any that do not return a valid response (2xx).
Checks: status-codes
- 3
Update Title Tags
Why: 996 pages have title issues, potentially affecting click-through rates.
How: Adjust short titles to be at least 30 characters and ensure long titles do not exceed 60 characters.
Checks: titles
- 4
Improve Meta Descriptions
Why: 644 pages have meta description issues, affecting visibility in search results.
How: Create unique, concise descriptions under 160 characters for missing or long descriptions.
Checks: meta-descriptions
- 5
Fix Headings Structure
Why: 1044 pages have heading issues, which can confuse search engines and users.
How: Ensure each page has a single H1 tag describing the content, with appropriate H2s for subheadings.
Checks: headings
- 6
Correct Sitemap Coverage
Why: 1643 crawled pages are missing from the sitemap, limiting their discoverability.
How: Update your sitemap to include all relevant URLs and ensure it is submitted to search engines.
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 crawlThe website has several security vulnerabilities that need to be addressed, including missing strict transport security and content security policies. Additionally, there are vulnerable JavaScript libraries and an exposed API key, which should be restricted. Addressing these issues can help protect users and enhance overall security.
- 0 high
- 5 medium
- 1 low
- 0 info
- 1
Missing HTTP Strict Transport Security (HSTS)Medium
Why it matters: Lacking HSTS allows for man-in-the-middle attacks when users access the site without HTTPS.
Fix: Implement the Strict-Transport-Security header with a value of "max-age=31536000; includeSubDomains; preload".
Evidence: HTTP Strict Transport Security
- 2
Missing Content Security Policy (CSP)Medium
Why it matters: Absence of a CSP allows any script or style to load, increasing the risk of XSS attacks.
Fix: Add a Content-Security-Policy header with an appropriate policy, e.g., "default-src 'self';".
Evidence: Content Security Policy
- 3
No X-Frame-Options HeaderMedium
Why it matters: Without X-Frame-Options, the site is vulnerable to clickjacking.
Fix: Add the X-Frame-Options header with a value of "DENY" or "SAMEORIGIN".
Evidence: Clickjacking protection
- 4
Vulnerable JavaScript LibrariesMedium
Why it matters: The site uses jQuery 3.1.1, which has known vulnerabilities.
Fix: Upgrade jQuery to version 3.5.0 or later.
Evidence: Vulnerable JavaScript libraries
- 5
Exposed Google API KeyMedium
Why it matters: An API key visible in the source code could be misused if not properly restricted.
Fix: Restrict the API key usage by setting its referrer in the Google Cloud console.
Evidence: Keys and secrets in page code
- 6
Missing X-Content-Type-Options HeaderLow
Why it matters: Without this header, the browser can misinterpret content types, posing security risks.
Fix: Implement the X-Content-Type-Options header with a value of "nosniff".
Evidence: MIME sniffing protection
What the checks found
- FoundHTTP Strict Transport SecurityMedium
1629 of 1665 HTML pages send strict-transport-security. Without it a visitor who types the address without https:// can be intercepted on the first request.
- https://www.123dentist.com/ → no strict-transport-security
- https://www.123dentist.com/find-your-dentist/ → no strict-transport-security
- https://www.123dentist.com/contact-us/ → no strict-transport-security
- https://www.123dentist.com/alberta/edmonton/ → no strict-transport-security
- https://www.123dentist.com/nova-scotia/ → no strict-transport-security
- https://www.123dentist.com/ontario/brampton/ → no strict-transport-security
- https://www.123dentist.com/patient-financing/ → no strict-transport-security
- https://www.123dentist.com/blog/ → no strict-transport-security
- https://www.123dentist.com/about-123dentist/ → no strict-transport-security
- https://www.123dentist.com/canadian-dental-care-plan/how-to-apply-for-canadian-dental-care-plan-2026/ → no strict-transport-security
- https://www.123dentist.com/british-columbia/abbotsford-dentist/7-oaks-dental-centre/ → no strict-transport-security
- https://www.123dentist.com/blog/eat-this-not-that/ → no strict-transport-security
- FoundContent Security PolicyMedium
None of the 1665 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
- FoundClickjacking protectionMedium
1629 of 1665 HTML pages send 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.123dentist.com/ → no x-frame-options
- https://www.123dentist.com/find-your-dentist/ → no x-frame-options
- https://www.123dentist.com/contact-us/ → no x-frame-options
- https://www.123dentist.com/alberta/edmonton/ → no x-frame-options
- https://www.123dentist.com/nova-scotia/ → no x-frame-options
- https://www.123dentist.com/ontario/brampton/ → no x-frame-options
- https://www.123dentist.com/patient-financing/ → no x-frame-options
- https://www.123dentist.com/blog/ → no x-frame-options
- https://www.123dentist.com/about-123dentist/ → no x-frame-options
- https://www.123dentist.com/canadian-dental-care-plan/how-to-apply-for-canadian-dental-care-plan-2026/ → no x-frame-options
- https://www.123dentist.com/british-columbia/abbotsford-dentist/7-oaks-dental-centre/ → no x-frame-options
- https://www.123dentist.com/blog/eat-this-not-that/ → no x-frame-options
- FoundMIME sniffing protectionLow
1629 of 1665 HTML pages send 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.123dentist.com/ → no x-content-type-options
- https://www.123dentist.com/find-your-dentist/ → no x-content-type-options
- https://www.123dentist.com/contact-us/ → no x-content-type-options
- https://www.123dentist.com/alberta/edmonton/ → no x-content-type-options
- https://www.123dentist.com/nova-scotia/ → no x-content-type-options
- https://www.123dentist.com/ontario/brampton/ → no x-content-type-options
- https://www.123dentist.com/patient-financing/ → no x-content-type-options
- https://www.123dentist.com/blog/ → no x-content-type-options
- https://www.123dentist.com/about-123dentist/ → no x-content-type-options
- https://www.123dentist.com/canadian-dental-care-plan/how-to-apply-for-canadian-dental-care-plan-2026/ → no x-content-type-options
- https://www.123dentist.com/british-columbia/abbotsford-dentist/7-oaks-dental-centre/ → no x-content-type-options
- https://www.123dentist.com/blog/eat-this-not-that/ → no x-content-type-options
- FoundVulnerable JavaScript librariesMedium
1 library with published vulnerabilities: jQuery 3.1.1. Whether they are exploitable depends on how the site uses them, but each has a fixed release.
- jQuery 3.1.1 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
- 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
5 checks passed, 3 not applicable
- OKHTTPS
All 1665 crawled pages were served over HTTPS.
- OKSoftware version disclosure
The Server header names a product without a version, and there is no X-Powered-By header.
- 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.
- Not applicableReferrer policy
This scan predates the crawler recording the headers this check needs. Rescan the site to check it.
- Not applicablePermissions policy
This scan predates the crawler recording the headers this check needs. Rescan the site to check it.
- Not applicableCookie flags
This scan predates the crawler recording the headers this check needs. Rescan the site to check it.
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.
- peacevalleydrygoods.comDR 667/100 · rank 2545 · 12 pages
- coffeeculturecafe.comDR 3566/100 · rank 2589 · 139 pages
- hairrenterprise.comDR 066/100 · rank 2589 · 1,815 pages
- www.standardroofing.caDR 566/100 · rank 2589 · 69 pages
- riverparkautomotive.caDR 366/100 · rank 2589 · 12 pages
- www.canadaautoservice.comDR 366/100 · rank 2589 · 11 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.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.