Scanned sites / www.smilesourcespokane.com / 2026-09-18-0233
www.smilesourcespokane.com scan from 9/18/2026, 2:33:19 AM
A newer scan exists. See the latest report for www.smilesourcespokane.com.
Scan 2026-09-18-0233
Scanned 9/18/2026, 2:33:19 AM, finished 9/18/2026, 2:56:06 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 18, 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, 2 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
1079 sites, median 82%, average 80%
www.smilesourcespokane.com scores 78%, higher than 33% of the 1079 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 SEO issues that need addressing, primarily related to redirects, titles, and meta descriptions. Fixing these will improve your site’s visibility significantly.
- 1
Fix Redirects
Why: Chained redirects can confuse search engines and hurt rankings.
How: Eliminate 103 chained redirects by updating links to direct to the final destination.
Checks: redirects
- 2
Resolve Non-200 Responses
Why: 137 URLs return errors, which impacts user experience and SEO.
How: Correct or remove these non-200 URLs to ensure they return a proper 2xx response.
Checks: status-codes
- 3
Optimize Title Tags
Why: 25 pages have title issues, affecting click-through rates.
How: Revise them to be concise (50-60 characters) and descriptive.
Checks: titles
- 4
Update Meta Descriptions
Why: 119 pages lack meta descriptions, making them less appealing in search results.
How: Create engaging meta descriptions (150-160 characters) for each page.
Checks: meta-descriptions
- 5
Add Missing Headings
Why: 6 pages are missing H1 tags, crucial for SEO structure.
How: Add a unique H1 tag to each of these pages for better organization.
Checks: headings
- 6
Link to Orphan Pages
Why: 25 orphan pages lack internal links and are hard to find.
How: Add internal links pointing to these pages from relevant content.
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 site has several important security shortcomings including missing HTTP Strict Transport Security, Content Security Policy, and clickjacking protection. Additionally, it discloses server version details and uses a vulnerable jQuery library. Addressing these issues will enhance the site's security stance.
- 0 high
- 5 medium
- 2 low
- 1 info
- 1
Missing HTTP Strict Transport Security (HSTS)Medium
Why it matters: Without HSTS, users may be intercepted if they forget to use HTTPS.
Fix: Add the header 'Strict-Transport-Security: max-age=31536000; includeSubDomains'.
Evidence: HTTP Strict Transport Security
- 2
Missing Content Security PolicyMedium
Why it matters: Absence of CSP allows scripts and resources to be loaded from any source, increasing XSS risks.
Fix: Add the header 'Content-Security-Policy: default-src 'self'; script-src 'self';'.
Evidence: Content Security Policy
- 3
Missing Clickjacking ProtectionMedium
Why it matters: Without X-Frame-Options, your site may be embedded in malicious frames.
Fix: Add the header 'X-Frame-Options: DENY'.
Evidence: Clickjacking protection
- 4
Vulnerable JavaScript LibraryMedium
Why it matters: jQuery 3.3.1 has known vulnerabilities that could be exploited depending on use.
Fix: Upgrade jQuery to version 3.5.0 or later.
Evidence: Vulnerable JavaScript libraries
- 5
Leaked Google API KeyMedium
Why it matters: Exposing API keys can lead to unauthorized access if not properly limited.
Fix: Restrict the API key in the Google Cloud console and consider removing it from public pages.
Evidence: Keys and secrets in page code
- 6
Server Version DisclosureLow
Why it matters: Revealing the server version can aid attackers in exploiting known vulnerabilities.
Fix: Hide server version details by configuring the server to not disclose this information.
Evidence: Software version disclosure
- 7
Third-Party Scripts Without SRILow
Why it matters: Using third-party scripts without Subresource Integrity can lead to script injection if compromised.
Fix: Implement a Content Security Policy that specifies trusted sources.
Evidence: Third-party scripts
- 8
No Permissions PolicyInfo
Why it matters: Lack of a permissions policy exposes features like camera or microphone unnecessarily.
Fix: Add the header 'Permissions-Policy: interest-cohort=()'.
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.