Scanned sites / www.smilesourcespokane.com / 2026-09-26-1713

www.smilesourcespokane.com scan from 9/26/2026, 5:13:30 PM

Scan 2026-09-26-1713

Scanned 9/26/2026, 5:13:30 PM, finished 9/26/2026, 5:30:30 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 26, 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 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
699
Status
Completed
Checks with issues
9 of 14
  • Title tags25 issues
    25 of 126 pages have title issues. 3 noindex or canonicalized pages excluded.
  • Meta descriptions119 issues
    119 of 126 pages have meta description issues. 3 noindex or canonicalized pages excluded.
  • Headings6 issues
    6 of 126 pages have heading issues. 3 noindex or canonicalized pages excluded.
  • Broken linksOK
    0 internal links point at 0 broken URLs.
  • Redirects232 issues
    137 redirecting URLs, 103 of them chained.
  • Non-200 responsesOK
    137 URLs did not return a 2xx response.
  • 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.
  • Heavy assets24 issues
    24 assets larger than 500 KB among the 100 heaviest.
  • Orphan pages25 issues
    25 pages have no internal links pointing at them.
  • Sitemap coverage25 issues
    15 sitemaps listing 126 URLs: 0 crawled pages missing, 0 listed URLs broken or redirecting, 25 reachable only via the sitemap.
  • Thin content5 issues
    5 of 126 pages have fewer than 200 words. 3 noindex or canonicalized pages excluded.
  • Duplicate contentOK
    0 groups of pages with identical HTML.

Where this scan sits among all scanned sites

1289 sites, median 82%, average 80%

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

035700%: 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%: 0 sites38%: 0 sites39%: 0 sites40%: 0 sites41%: 0 sites42%: 0 sites43%: 0 sites44%: 0 sites45%: 2 sites46%: 2 sites47%: 1 site48%: 1 site49%: 0 sites50%: 4 sites51%: 4 sites52%: 4 sites53%: 5 sites54%: 4 sites55%: 2 sites56%: 2 sites57%: 3 sites58%: 8 sites59%: 4 sites60%: 7 sites61%: 9 sites62%: 12 sites63%: 5 sites64%: 9 sites65%: 10 sites66%: 11 sites67%: 16 sites68%: 29 sites69%: 14 sites70%: 26 sites71%: 25 sites72%: 29 sites73%: 28 sites74%: 34 sites75%: 30 sites76%: 41 sites77%: 42 sites78%: 40 sites79%: 38 sites80%: 53 sites81%: 60 sites82%: 57 sites83%: 55 sites84%: 60 sites85%: 54 sites86%: 50 sites87%: 53 sites88%: 61 sites89%: 48 sites90%: 70 sites91%: 42 sites92%: 27 sites93%: 20 sites94%: 19 sites95%: 11 sites96%: 11 sites97%: 5 sites98%: 3 sites99%: 2 sites100%: 23 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 requires some important SEO fixes to improve visibility and user experience. Prioritize these tasks for optimal impact.

  1. 1

    Fix Redirect Chains

    Why: Chained redirects can slow down user experience and diminish link equity.

    How: Identify the final URL of each chain and update links to point directly to that URL.

    Checks: redirects

  2. 2

    Resolve Non-200 Responses

    Why: Non-200 responses hinder user access to content and affect SEO rankings.

    How: Review and correct or remove URLs returning non-200 responses.

    Checks: status-codes

  3. 3

    Add Missing Title Tags

    Why: Title tags are critical for SEO and influence click-through rates.

    How: Create unique, keyword-rich title tags for the 25 pages missing or with issues.

    Checks: titles

  4. 4

    Create Meta Descriptions

    Why: Meta descriptions improve organic search visibility and user engagement.

    How: Write compelling meta descriptions for the 119 pages with issues.

    Checks: meta-descriptions

  5. 5

    Add H1 Headings

    Why: Missing H1 tags affect content structure and SEO.

    How: Add relevant H1 headings to the 6 pages lacking them.

    Checks: headings

  6. 6

    Link Orphan Pages Internally

    Why: Orphan pages may not be indexed due to lack of internal linking.

    How: Add internal links to the 25 orphan 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 crawl

The website has several important security issues that need addressing. It lacks critical response headers for secure HTTP connections, and permissions policies, potentially exposing users to attacks. Additionally, it reveals server version information and contains a vulnerable JavaScript library. These findings should be prioritized to enhance the website'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, users can be intercepted when accessing the site without HTTPS.

    Fix: Add the header: `Strict-Transport-Security: max-age=31536000; includeSubDomains; preload`.

    Evidence: HTTP Strict Transport Security

  2. 2

    No Content Security Policy (CSP)Medium

    Why it matters: Absence of CSP allows unrestricted loading of scripts and styles, increasing XSS risk.

    Fix: Add the header: `Content-Security-Policy: default-src 'self';`.

    Evidence: Content Security Policy

  3. 3

    No X-Frame-OptionsMedium

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

    Fix: Add the header: `X-Frame-Options: DENY` or use a CSP directive.

    Evidence: Clickjacking protection

  4. 4

    Vulnerable JavaScript LibraryMedium

    Why it matters: The outdated jQuery version is susceptible to known vulnerabilities.

    Fix: Upgrade jQuery to version 3.5.0 or later.

    Evidence: Vulnerable JavaScript libraries

  5. 5

    Leaked Google API KeyMedium

    Why it matters: An exposed API key can lead to unauthorized use of Google services.

    Fix: Restrict the API key in the Google Cloud console by HTTP referrer.

    Evidence: Keys and secrets in page code

  6. 6

    Server Version DisclosureLow

    Why it matters: Exposing the server version aids attackers in identifying vulnerabilities.

    Fix: Remove or alter the `Server` header in response to hide version info.

    Evidence: Software version disclosure

  7. 7

    Third-party Scripts Without Subresource IntegrityLow

    Why it matters: Loading scripts without integrity checks can lead to compromised assets.

    Fix: Implement Subresource Integrity (SRI) or use a strict CSP to define allowed scripts.

    Evidence: Third-party scripts

  8. 8

    Missing Permissions PolicyInfo

    Why it matters: No permissions policy can allow compromised scripts excessive access to features.

    Fix: Add the header: `Permissions-Policy: not-allowed` to restrict unused features.

    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-26-1713 | DIY SEO Hub