Scanned sites / www.smilesourcespokane.com / 2026-09-29-1441

www.smilesourcespokane.com scan from 9/29/2026, 2:41:41 PM

Scan 2026-09-29-1441

Scanned 9/29/2026, 2:41:41 PM, finished 9/29/2026, 2:54:27 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.

78/ 100Good

On September 29, 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. 10 of 16 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). 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: Medium5 medium, 2 low and 1 info findings. See the security findings ↓

Pages crawled
261
Assets fetched
699
Status
Completed
Checks with issues
10 of 16
CoverageComplete crawl

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. 52 link destinations on other sites were checked.

  • Title tags25 issues
    25 of 126 pages have title issues. 3 noindex or canonicalized pages excluded.
    −1.9 points
  • Meta descriptions120 issues
    120 of 126 pages have meta description issues. 3 noindex or canonicalized pages excluded.
    −7.4 points
  • Headings6 issues
    6 of 126 pages have heading issues. 3 noindex or canonicalized pages excluded.
    −0.3 points
  • Broken linksOK
    0 internal links point at 0 broken URLs.
  • Links to other sites1 issue
    1 destination answered with an error, 14 could not be determined (timeouts, rate limits or refusals), of 52 destinations checked.
    −0.3 points
  • Redirects232 issues
    137 redirecting URLs, 103 of them chained.
    −4 points
  • Non-200 responses137 noted
    137 URLs did not return a 2xx response. 132 of them are pages, 0 with an error status; the rest are assets or redirects.
  • Rate limitedOK
    The site did not rate limit the crawler.
  • IndexabilityOK
    0 of 126 indexable pages have indexability warnings. 3 pages noindex by design.
  • Image alt text83 issues
    83 of 1199 image references have no alt attribute. 989 use an empty alt (decorative), which is fine.
    −0.4 points
  • Heavy assets24 issues
    24 assets larger than 500 KB among 699 fetched assets.
    −6 points
  • Orphan pages25 issues
    25 pages have no internal links pointing at them.
    −0.8 points
  • Sitemap coverage25 issues
    15 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 countsOK
    Internal link counts for 129 pages.
  • Thin content5 issues
    5 of 126 pages have fewer than 200 words. 3 noindex or canonicalized pages excluded.
    −0.3 points
  • Duplicate contentOK
    0 groups of pages with identical HTML.

Where this scan sits among all scanned sites

1357 sites, median 80%, average 79%

www.smilesourcespokane.com scores 78%, higher than 38% of the 1357 scanned sites. See the full ranking.

039780%: 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%: 1 site36%: 1 site37%: 1 site38%: 1 site39%: 0 sites40%: 1 site41%: 0 sites42%: 0 sites43%: 0 sites44%: 0 sites45%: 3 sites46%: 2 sites47%: 2 sites48%: 2 sites49%: 2 sites50%: 3 sites51%: 4 sites52%: 7 sites53%: 5 sites54%: 5 sites55%: 4 sites56%: 3 sites57%: 5 sites58%: 9 sites59%: 5 sites60%: 8 sites61%: 10 sites62%: 14 sites63%: 12 sites64%: 8 sites65%: 14 sites66%: 14 sites67%: 27 sites68%: 24 sites69%: 14 sites70%: 32 sites71%: 29 sites72%: 39 sites73%: 33 sites74%: 41 sites75%: 41 sites76%: 49 sites77%: 45 sites78%: 59 sites79%: 48 sites80%: 68 sites81%: 78 sites82%: 67 sites83%: 62 sites84%: 61 sites85%: 44 sites86%: 49 sites87%: 47 sites88%: 50 sites89%: 36 sites90%: 29 sites91%: 31 sites92%: 19 sites93%: 8 sites94%: 10 sites95%: 6 sites96%: 7 sites97%: 3 sites98%: 1 site99%: 2 sites100%: 50 sites78% 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 website has several areas needing improvement, particularly with redirects, title/meta tags, and heading structures. Focus on fixing these high-impact issues to enhance SEO performance.

  1. 1

    Fix Redirect Chains

    Why: Chained redirects slow down loading time and affect crawl efficiency.

    How: Identify and resolve 103 chained redirects by linking directly to the final URL from the original.

    Checks: redirects

  2. 2

    Add Missing Title Tags

    Why: Title tags are crucial for SEO; improving 25 pages will enhance visibility.

    How: Create unique, concise titles for the affected pages, keeping within 50-60 characters.

    Checks: titles

  3. 3

    Complete Meta Descriptions

    Why: 120 pages lack meta descriptions, impacting click-through rates.

    How: Draft and implement unique meta descriptions for each of the 120 affected pages.

    Checks: meta-descriptions

  4. 4

    Add H1 Headings

    Why: 6 pages are missing H1 headings, which can hurt their SEO rankings.

    How: Add appropriate H1 tags to the 6 identified pages, ensuring relevance to page content.

    Checks: headings

  5. 5

    Optimize Heavy Assets

    Why: 24 large assets can degrade site performance.

    How: Reduce file sizes or consider serving them via a different method; review the 4 identified heavy assets.

    Checks: heavy-assets

  6. 6

    Address Orphan Pages

    Why: 25 orphan pages are inaccessible via internal links, risking their discoverability.

    How: Add internal links from relevant pages to connect and enhance user navigation to these orphan pages.

    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 crawl

The website has several critical security weaknesses. Key protections like HTTP Strict Transport Security, Content Security Policy, and Clickjacking protection are missing, increasing the risk of attacks. Additionally, outdated JavaScript libraries and exposed API keys can lead to vulnerabilities. Immediate action is necessary to enhance the site's security posture.

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

    Missing HTTP Strict Transport Security (HSTS)Medium

    Why it matters: Without HSTS, unsecured requests can be intercepted, compromising users.

    Fix: Implement HSTS by adding the header: Strict-Transport-Security: max-age=63072000; includeSubDomains.

    Evidence: HTTP Strict Transport Security

  2. 2

    Missing Content Security Policy (CSP)Medium

    Why it matters: Lack of CSP allows unrestricted loading of scripts and content, increasing XSS risks.

    Fix: Add a CSP header: Content-Security-Policy: default-src 'self';

    Evidence: Content Security Policy

  3. 3

    Missing Clickjacking Protection (X-Frame-Options)Medium

    Why it matters: No X-Frame-Options header exposes the site to clickjacking attacks.

    Fix: Add X-Frame-Options header: X-Frame-Options: DENY.

    Evidence: Clickjacking protection

  4. 4

    Exposed Google API KeyMedium

    Why it matters: An exposed API key can be abused by malicious users if not restricted properly.

    Fix: Restrict the API key usage via the Google Cloud console with appropriate referrer restrictions.

    Evidence: Keys and secrets in page code

  5. 5

    Vulnerable JavaScript Library DetectedMedium

    Why it matters: Using an outdated version of jQuery with known vulnerabilities increases the risk of exploitation.

    Fix: Upgrade jQuery to version 3.5.0 or later.

    Evidence: Vulnerable JavaScript libraries

  6. 6

    Server Version DisclosureLow

    Why it matters: Revealing server version can assist attackers in targeting known vulnerabilities.

    Fix: Consider configuring your server to hide version information.

    Evidence: Software version disclosure

  7. 7

    Third-party Scripts Without Subresource IntegrityLow

    Why it matters: Scripts from other domains may change unexpectedly, potentially compromising site security.

    Fix: Implement a Content-Security-Policy that specifies trusted domains.

    Evidence: Third-party scripts

  8. 8

    Missing Permissions PolicyInfo

    Why it matters: Without permissions policy, scripts could misuse browser features like camera and geolocation.

    Fix: Add Permissions-Policy 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.

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.
www.smilesourcespokane.com scan 2026-09-29-1441 | DIY SEO Hub