Scanned sites / www.smilesourcespokane.com / 2026-09-17-0142
www.smilesourcespokane.com scan from 9/17/2026, 1:42:49 AM
Scan 2026-09-17-0142
Scanned 9/17/2026, 1:42:49 AM, finished 9/17/2026, 2:07:35 AM. Found with openstreetmap overpass
Site: https://www.smilesourcespokane.com/
Download SQLite databaseEvery page and asset from this scan, with the crawl events, in one file.
On September 17, 2026 the Site Spider crawled 261 pages and 701 assets of www.smilesourcespokane.com, starting from https://www.smilesourcespokane.com/. It scored 78 out of 100, a good result. 9 of 14 checks found something to fix, led by redirects (232), meta descriptions (119), image alt text (83); 5 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: Medium5 medium, 1 low and 1 info findings. See the security findings ↓
- Pages crawled
- 261
- Assets fetched
- 701
- Status
- Completed
- Checks with issues
- 9 of 14
- Title tags25 issues25 of 126 pages have title issues. 3 noindex or canonicalized pages excluded.
- Meta descriptions119 issues119 of 126 pages have meta description issues. 3 noindex or canonicalized pages excluded.
- Headings6 issues6 of 126 pages have heading issues. 3 noindex or canonicalized pages excluded.
- Broken linksOK0 internal links point at 0 broken URLs.
- Redirects232 issues137 redirecting URLs, 103 of them chained.
- Non-200 responsesOK137 URLs did not return a 2xx response.
- Rate limitedOKThe site did not rate limit the crawler.
- IndexabilityOK0 of 126 indexable pages have indexability warnings. 3 pages noindex by design.
- Image alt text83 issues83 of 1202 image references have no alt attribute. 989 use an empty alt (decorative), which is fine.
- Heavy assets24 issues24 assets larger than 500 KB among the 100 heaviest.
- Orphan pages25 issues25 pages have no internal links pointing at them.
- Sitemap coverage25 issues15 sitemaps listing 126 URLs: 0 crawled pages missing, 0 listed URLs broken or redirecting, 25 reachable only via the sitemap.
- Thin content5 issues5 of 126 pages have fewer than 200 words. 3 noindex or canonicalized pages excluded.
- Duplicate contentOK0 groups of pages with identical HTML.
Where this scan sits among all scanned sites
1055 sites, median 82%, average 80%
www.smilesourcespokane.com scores 78%, higher than 34% of the 1055 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 findingsYour site has several issues that can improve its SEO performance. Prioritize fixing redirects, title/meta issues, and adding H1 tags to boost visibility.
- 1
Fix Redirects
Why: Chained redirects can slow down crawl efficiency and harm user experience.
How: Update URLs to point directly to their final destinations. Remove unnecessary redirects.
Checks: redirects
- 2
Resolve Non-200 Responses
Why: Non-200 status codes can prevent users and search engines from accessing content.
How: Identify and fix or remove URLs returning non-200 statuses, redirecting where necessary.
Checks: status-codes
- 3
Improve Title Tags
Why: Optimized titles improve click-through rates and search rankings.
How: Ensure all pages have titles between 30-60 characters and unique descriptions.
Checks: titles
- 4
Enhance Meta Descriptions
Why: Meta descriptions encourage clicks from search results.
How: Write unique meta descriptions for all pages, ideally between 50-160 characters.
Checks: meta-descriptions
- 5
Add Missing H1 Tags
Why: H1 tags help search engines understand page content and improve SEO.
How: Add a clear, descriptive H1 tag to each page, ideally including target keywords.
Checks: headings
- 6
Link to Orphan Pages
Why: Connecting orphan pages enhances site structure and user navigation.
How: Create internal links to these pages from relevant content to improve accessibility.
Checks: orphan-pages
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 critical security headers missing that leave it exposed to various attacks, including man-in-the-middle and clickjacking. A Google API key is also leaked, which may lead to unauthorized usage. Additionally, there are vulnerabilities in a JavaScript library in use. Immediate action is recommended to mitigate these vulnerabilities.
- 0 high
- 5 medium
- 1 low
- 1 info
- 1
Missing HTTP Strict Transport Security (HSTS)Medium
Why it matters: Without HSTS, visitors typing the address without HTTPS may be intercepted.
Fix: Add `Strict-Transport-Security: max-age=31536000; includeSubDomains` to all responses.
Evidence: HTTP Strict Transport Security
- 2
Missing Content Security Policy (CSP)Medium
Why it matters: Absence of CSP means there's no restriction on where scripts can load from, increasing XSS risk.
Fix: Add `Content-Security-Policy: default-src 'self';` to all responses.
Evidence: Content Security Policy
- 3
Missing X-Frame-Options HeaderMedium
Why it matters: Without this protection, your pages can be embedded in other sites, making users vulnerable to clickjacking.
Fix: Add `X-Frame-Options: DENY` to all responses.
Evidence: Clickjacking protection
- 4
Exposed Google API KeyMedium
Why it matters: A public API key can be abused without proper restrictions in place.
Fix: Restrict the key in Google Cloud console by referrer and usage, and consider regenerating the key.
Evidence: Keys and secrets in page code
- 5
Vulnerable JavaScript Library FoundMedium
Why it matters: Using jQuery 3.3.1 contains known vulnerabilities that may be exploitable depending on use.
Fix: Upgrade jQuery to version 3.5.0 or higher to mitigate these vulnerabilities.
Evidence: Vulnerable JavaScript libraries
- 6
Server Version DisclosureLow
Why it matters: Revealing the server version aids attackers in identifying potential exploits.
Fix: Configure the server to hide version information; remove or modify the Server response header.
Evidence: Software version disclosure
- 7
Missing Permissions Policy HeaderInfo
Why it matters: Absence of this header allows scripts to access features like the camera or geolocation, which can be exploited.
Fix: Add `Permissions-Policy: interest-cohort=()` to all responses to limit feature access.
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.smilesourcespokane.com/ → no strict-transport-security
- https://www.smilesourcespokane.com/dental-implants/ → no strict-transport-security
- https://www.smilesourcespokane.com/spokane-valley-wa/ → no strict-transport-security
- https://www.smilesourcespokane.com/north-side-wa/ → no strict-transport-security
- https://www.smilesourcespokane.com/south-hill-wa/ → no strict-transport-security
- https://www.smilesourcespokane.com/spokane-valley-wa/about-us/meet-our-doctors/ → no strict-transport-security
- https://www.smilesourcespokane.com/terms-conditions/ → no strict-transport-security
- https://www.smilesourcespokane.com/privacy-policy/ → no strict-transport-security
- https://www.smilesourcespokane.com/accessibility-commitment/ → no strict-transport-security
- https://www.smilesourcespokane.com/spokane-valley-wa/about-us/ → no strict-transport-security
- https://www.smilesourcespokane.com/spokane-valley-wa/about-us/our-technologies/ → no strict-transport-security
- https://www.smilesourcespokane.com/spokane-valley-wa/about-us/office-gallery/ → no strict-transport-security
- FoundContent Security PolicyMedium
None of the 129 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.smilesourcespokane.com/ → no content-security-policy
- https://www.smilesourcespokane.com/dental-implants/ → no content-security-policy
- https://www.smilesourcespokane.com/spokane-valley-wa/ → no content-security-policy
- https://www.smilesourcespokane.com/north-side-wa/ → no content-security-policy
- https://www.smilesourcespokane.com/south-hill-wa/ → no content-security-policy
- https://www.smilesourcespokane.com/spokane-valley-wa/about-us/meet-our-doctors/ → no content-security-policy
- https://www.smilesourcespokane.com/terms-conditions/ → no content-security-policy
- https://www.smilesourcespokane.com/privacy-policy/ → no content-security-policy
- https://www.smilesourcespokane.com/accessibility-commitment/ → no content-security-policy
- https://www.smilesourcespokane.com/spokane-valley-wa/about-us/ → no content-security-policy
- https://www.smilesourcespokane.com/spokane-valley-wa/about-us/our-technologies/ → no content-security-policy
- https://www.smilesourcespokane.com/spokane-valley-wa/about-us/office-gallery/ → 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.smilesourcespokane.com/ → no x-frame-options
- https://www.smilesourcespokane.com/dental-implants/ → no x-frame-options
- https://www.smilesourcespokane.com/spokane-valley-wa/ → no x-frame-options
- https://www.smilesourcespokane.com/north-side-wa/ → no x-frame-options
- https://www.smilesourcespokane.com/south-hill-wa/ → no x-frame-options
- https://www.smilesourcespokane.com/spokane-valley-wa/about-us/meet-our-doctors/ → no x-frame-options
- https://www.smilesourcespokane.com/terms-conditions/ → no x-frame-options
- https://www.smilesourcespokane.com/privacy-policy/ → no x-frame-options
- https://www.smilesourcespokane.com/accessibility-commitment/ → no x-frame-options
- https://www.smilesourcespokane.com/spokane-valley-wa/about-us/ → no x-frame-options
- https://www.smilesourcespokane.com/spokane-valley-wa/about-us/our-technologies/ → no x-frame-options
- https://www.smilesourcespokane.com/spokane-valley-wa/about-us/office-gallery/ → no x-frame-options
- 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.smilesourcespokane.com/ → no permissions-policy
- https://www.smilesourcespokane.com/dental-implants/ → no permissions-policy
- https://www.smilesourcespokane.com/spokane-valley-wa/ → no permissions-policy
- https://www.smilesourcespokane.com/north-side-wa/ → no permissions-policy
- https://www.smilesourcespokane.com/south-hill-wa/ → no permissions-policy
- https://www.smilesourcespokane.com/spokane-valley-wa/about-us/meet-our-doctors/ → no permissions-policy
- https://www.smilesourcespokane.com/terms-conditions/ → no permissions-policy
- https://www.smilesourcespokane.com/privacy-policy/ → no permissions-policy
- https://www.smilesourcespokane.com/accessibility-commitment/ → no permissions-policy
- https://www.smilesourcespokane.com/spokane-valley-wa/about-us/ → no permissions-policy
- https://www.smilesourcespokane.com/spokane-valley-wa/about-us/our-technologies/ → no permissions-policy
- https://www.smilesourcespokane.com/spokane-valley-wa/about-us/office-gallery/ → 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: Flywheel/5.1.0 (962 responses)
- FoundVulnerable JavaScript librariesMedium
1 library with published vulnerabilities: jQuery 3.3.1. Whether they are exploitable depends on how the site uses them, but each has a fixed release.
- jQuery 3.3.1 in https://code.jquery.com/jquery-3.3.1.min.js: 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…sA (39 chars) in https://www.smilesourcespokane.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 6 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.)
- code.jquery.com (40 script tags)
- www.googletagmanager.com (80 script tags)
- cdnjs.cloudflare.com (80 script tags)
- cdn.jsdelivr.net (45 script tags)
- cdn.userway.org (40 script tags)
- cdn.trustindex.io (1 script tag)
6 checks passed, 2 not applicable
- OKHTTPS
All 129 crawled pages were served over HTTPS.
- OKMIME sniffing protection
x-content-type-options is set on all 129 HTML pages.
- OKReferrer policy
referrer-policy is set on all 129 HTML pages.
- OKMixed content
No HTTPS page loads a script, stylesheet, font or image over plain HTTP.
- OKExposed files and listings
None of the crawled URLs is a configuration file, backup, dump, repository folder or directory listing.
- OKSensitive paths in robots.txt
robots.txt does not point at admin, backup or private paths.
- Not applicableCookie flags
The crawl set no cookies, so there are no cookie flags to check.
- Not applicableForms over HTTPS
No forms were found on the sampled pages.
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.smilesourcespokane.com 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.