Scanned sites / www.smilesourcespokane.com / 2026-10-05-1718
www.smilesourcespokane.com scan from 10/5/2026, 5:18:40 PM
Scan 2026-10-05-1718
Scanned 10/5/2026, 5:18:40 PM, finished 10/5/2026, 5:37:50 PM. 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 October 5, 2026 the Site Spider crawled 261 pages and 699 assets of www.smilesourcespokane.com, starting from https://www.smilesourcespokane.com/. It scored 78 out of 100, a good result. 9 of 22 checks found something to fix, led by meta descriptions (120), heavy assets (24), redirects (232); 4 checks passed. Most of the points went to meta descriptions (−7.4), heavy assets (−6), redirects (−4). 9 checks found something the score does not count, listed as noted. 1 check was not run because the crawl fetched nothing for it. 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
- 699
- Status
- Completed
- Checks with issues
- 9 of 22
960 of 1,018 discovered URLs were fetched, 58 blocked by robots.txt. The crawl reached everything it found. HTML only: nothing here ran JavaScript. 47 link destinations on other sites have not been checked.
- Title tags25 issues25 of 126 pages have title issues. 3 noindex or canonicalized pages excluded.−1.9 points
- Meta descriptions120 issues120 of 126 pages have meta description issues. 3 noindex or canonicalized pages excluded.−7.4 points
- Headings6 issues6 of 126 pages have heading issues. 3 noindex or canonicalized pages excluded.−0.3 points
- Broken linksOK0 internal links point at 0 broken URLs.
- Links to other sitesNot checkedNot checked: the crawl fetched nothing this check can look at.
- Redirects232 issues137 redirecting URLs, 103 of them chained.−4 points
- Non-200 responses137 noted137 URLs did not return a 2xx response. 132 of them are pages, 0 with an error status; the rest are assets or redirects.
- 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 1199 image references have no alt attribute. 989 use an empty alt (decorative), which is fine.−0.4 points
- Heavy assets24 issues24 assets larger than 500 KB among 699 fetched assets.−6 points
- Orphan pages25 issues25 pages have no internal links pointing at them.−0.8 points
- Sitemap coverage25 issues15 sitemaps listing 126 URLs: 0 crawled pages missing, 0 listed URLs broken or redirecting, 25 reachable only via the sitemap.−1.2 points
- Internal link counts22 notedInternal link counts for 129 pages; 22 worth a look.
- Thin content5 issues5 of 126 pages have fewer than 200 words. 3 noindex or canonicalized pages excluded.−0.3 points
- Duplicate contentOK0 groups of pages with identical HTML.
- URL format106 noted106 of 261 page URLs are harder to read, share or cache than they need to be.
- Canonicals3 noted3 of 129 pages have a canonical worth checking.
- Robots directives129 noted129 pages carry a robots directive; 0 carry none.
- Anchor text184 noted184 destinations are linked without useful anchor text, or with nofollow.
- Title and heading structure73 noted73 of 126 pages could use the title, heading and snippet space better. 3 noindex or canonicalized pages excluded.
- Image weight and alt length38 noted38 images over 100 KB; 0 with alt text over 100 characters.
- Response anomalies3 noted3 URLs answered in a way worth looking at.
Where this scan sits among all scanned sites
2081 sites, median 79%, average 78%
www.smilesourcespokane.com scores 78%, higher than 43% of the 2081 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 findingsSeveral critical SEO issues need immediate attention, including improving redirects, enhancing meta descriptions, and addressing heading issues. Implement these fixes to enhance your site's performance.
- 1
Fix Redirect Chains
Why: Chained redirects can slow down your site and are detrimental to SEO.
How: Eliminate unnecessary redirects by directing users to the final destination URL.
Checks: redirects
- 2
Resolve Non-200 Responses
Why: Non-200 responses can hinder user experience and SEO rankings.
How: Identify and fix or remove URLs returning a 301 status, ensuring they lead to valid content.
Checks: status-codes
- 3
Improve Meta Descriptions
Why: Missing meta descriptions can affect click-through rates from search engines.
How: Write and implement concise, relevant meta descriptions for the 119 affected pages.
Evidence: 119 pages have no meta description at all.
119 pages affected
Checks: meta-descriptions
- 4
Add Missing Headings
Why: Missing headings can impact SEO and accessibility.
How: Add an H1 tag to the 6 pages lacking it to improve their structure.
Evidence: 6 pages: missing h1.
6 pages affected
- https://www.smilesourcespokane.com/
- https://www.smilesourcespokane.com/north-side-wa/new-patients/special-offers/
- https://www.smilesourcespokane.com/south-hill-wa/home-2/
- https://www.smilesourcespokane.com/south-hill-wa/new-patients/special-offers/
- https://www.smilesourcespokane.com/spokane-valley-wa/new-patients/special-offers/
Checks: headings
- 5
Address Orphan Pages
Why: Orphan pages are difficult for users and search engines to find.
How: Create internal links to the 25 orphan pages to improve navigation.
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 lacks essential security headers and uses outdated libraries, which could expose users and the site to risks. Critical improvements include adding HTTP Strict Transport Security, a Content Security Policy, and upgrading JavaScript libraries. Addressing these vulnerabilities will enhance security significantly.
- 0 high
- 5 medium
- 1 low
- 1 info
- 1
Missing HTTP Strict Transport Security (HSTS)Medium
Why it matters: Without HSTS, initial requests can be intercepted when users do not type 'https://'.
Fix: Add the header 'Strict-Transport-Security: max-age=31536000; includeSubDomains'.
Evidence: HTTP Strict Transport Security
- 2
Missing Content Security Policy (CSP)Medium
Why it matters: Absent CSP allows unrestricted script and style sources, increasing the risk of XSS attacks.
Fix: Add the header 'Content-Security-Policy: default-src 'self';'.
Evidence: Content Security Policy
- 3
Missing Clickjacking ProtectionMedium
Why it matters: Pages can be embedded in a frame by attackers, leading to clickjacking vulnerabilities.
Fix: Add the header 'X-Frame-Options: DENY'.
Evidence: Clickjacking protection
- 4
Outdated JavaScript Library FoundMedium
Why it matters: jQuery 3.3.1 contains known vulnerabilities that could be exploited.
Fix: Upgrade jQuery to at least version 3.5.0.
Evidence: Vulnerable JavaScript libraries
- 5
Exposed Google API KeyMedium
Why it matters: The public API key can be exploited if not properly restricted.
Fix: Restrict usage by HTTP referrer in the Google Cloud console.
Evidence: Keys and secrets in page code
- 6
Revealing Server VersionLow
Why it matters: The server response exposes version details, aiding attackers in finding vulnerabilities.
Fix: Consider adjusting server settings to hide version details.
Evidence: Software version disclosure
- 7
Missing Permissions PolicyInfo
Why it matters: No permissions policy limits browser feature access, increasing potential risks.
Fix: Add the header 'Permissions-Policy: geolocation=(), microphone=(), camera=()'.
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 (960 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.
Sites scoring near www.smilesourcespokane.com
Their neighbours in the SEO rank table, which orders every scanned site by health score.
- integratedtherapies.ca79/100 · rank 1001 · 50 pages
- normanviewdental.com79/100 · rank 1001 · 128 pages
- gtplumbingfargo.com79/100 · rank 1001 · 28 pages
- www.advancedhealthphysio.com78/100 · rank 1086 · 76 pages
- www.eitherorpdx.com78/100 · rank 1086 · 14 pages
- www.furnasmanright-time.ca78/100 · rank 1086 · 861 pages
This report was produced by the DIY SEO Hub Site Spider crawling www.smilesourcespokane.com from its pages as published, the way a search engine does. It shows summary figures only.
Own www.smilesourcespokane.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.smilesourcespokane.com. Removal needs no account and no proof of purchase.