Scanned sites / www.smilesourcespokane.com / 2026-09-16-0027

www.smilesourcespokane.com scan from 9/16/2026, 12:27:17 AM

Scan 2026-09-16-0027

Scanned 9/16/2026, 12:27:17 AM, finished 9/16/2026, 12:45:41 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.

78/ 100Good

On September 16, 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 and 1 info findings. See the security findings ↓

Pages crawled
261
Assets fetched
701
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 1202 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

1039 sites, median 82%, average 80%

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

028550%: 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%: 1 site46%: 1 site47%: 0 sites48%: 1 site49%: 0 sites50%: 3 sites51%: 3 sites52%: 1 site53%: 1 site54%: 1 site55%: 1 site56%: 2 sites57%: 3 sites58%: 6 sites59%: 3 sites60%: 4 sites61%: 8 sites62%: 12 sites63%: 4 sites64%: 8 sites65%: 9 sites66%: 7 sites67%: 14 sites68%: 27 sites69%: 11 sites70%: 20 sites71%: 19 sites72%: 23 sites73%: 23 sites74%: 30 sites75%: 26 sites76%: 39 sites77%: 34 sites78%: 31 sites79%: 29 sites80%: 41 sites81%: 52 sites82%: 45 sites83%: 44 sites84%: 47 sites85%: 46 sites86%: 42 sites87%: 46 sites88%: 55 sites89%: 36 sites90%: 50 sites91%: 37 sites92%: 23 sites93%: 17 sites94%: 16 sites95%: 7 sites96%: 9 sites97%: 4 sites98%: 3 sites99%: 1 site100%: 9 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

Several areas of improvement exist on your site, particularly in redirects, meta descriptions, titles, and headings. Addressing these issues will enhance user experience and SEO performance.

  1. 1

    Fix Redirect Chains

    Why: Chained redirects can dilute link equity and create slower loading times.

    How: Identify and resolve chains by redirecting directly from the source URL to the final URL.

    Checks: redirects

  2. 2

    Resolve Non-200 Responses

    Why: Non-200 URLs can harm user experience and SEO.

    How: Check the listed URLs and ensure they return a 200 status. Redirect or remove as necessary.

    Checks: status-codes

  3. 3

    Update Meta Descriptions

    Why: Missing meta descriptions can reduce click-through rates from search results.

    How: Craft unique meta descriptions (150-160 characters) for each page without one.

    Checks: meta-descriptions

  4. 4

    Correct Title Tag Issues

    Why: Improper title lengths can confuse search engines and users.

    How: Revise short titles to be more descriptive and lengthen them (50-60 characters).

    Checks: titles

  5. 5

    Add Missing H1 Headings

    Why: H1s provide structure and context for pages, aiding SEO.

    How: Add clear H1s to pages lacking them, summarizing the page content effectively.

    Checks: headings

  6. 6

    Enhance Orphan Pages

    Why: Orphan pages lack visibility and may not receive indexed traffic.

    How: Add internal links to improve their discoverability and integrate them into 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

Your website has several critical security vulnerabilities that need attention. Key headers for transport security, content security policies, and clickjacking protection are missing, which could expose visitors to risks. Additionally, a vulnerable JavaScript library is in use and a sensitive API key is leaked. Implementing the recommended changes will help secure your site.

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

    Missing HTTP Strict Transport Security (HSTS)Medium

    Why it matters: Without HSTS, visitors can be intercepted on the first request if they don't use HTTPS.

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

    Evidence: HTTP Strict Transport Security

  2. 2

    Missing Content Security Policy (CSP)Medium

    Why it matters: Without CSP, browsers have no restrictions on loading scripts/styles which could lead to XSS attacks.

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

    Evidence: Content Security Policy

  3. 3

    Missing X-Frame-OptionsMedium

    Why it matters: Without this header, your pages can be embedded in malicious frames, risking clickjacking.

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

    Evidence: Clickjacking protection

  4. 4

    Leaked Google API KeyMedium

    Why it matters: An exposed API key can lead to unauthorized usage and potential abuse.

    Fix: Restrict the API key by referrer and configure limits in the Google Cloud console.

    Evidence: Keys and secrets in page code

  5. 5

    Vulnerable JavaScript LibraryMedium

    Why it matters: Using an outdated jQuery version exposes your site to known vulnerabilities.

    Fix: Upgrade jQuery to version 3.5.0 or newer.

    Evidence: Vulnerable JavaScript libraries

  6. 6

    Missing Permissions PolicyInfo

    Why it matters: Without a permissions policy, browser features remain enabled which could be exploited.

    Fix: Add the header: Permissions-Policy: geolocation=(none), microphone=(none), camera=(none)

    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.

www.smilesourcespokane.com scan 2026-09-16-0027 | DIY SEO Hub