Scanned sites / www.smilesourcespokane.com / 2026-10-04-1112

www.smilesourcespokane.com scan from 10/4/2026, 11:12:37 AM

Scan 2026-10-04-1112

Scanned 10/4/2026, 11:12:37 AM, finished 10/4/2026, 11:33:47 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.

77/ 100Good

On October 4, 2026 the Site Spider crawled 261 pages and 699 assets of www.smilesourcespokane.com, starting from https://www.smilesourcespokane.com/. It scored 77 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, 17 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

2060 sites, median 79%, average 78%

www.smilesourcespokane.com scores 77%, higher than 37% of the 2060 scanned sites. See the full ranking.

0531050%: 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%: 1 site28%: 0 sites29%: 0 sites30%: 0 sites31%: 0 sites32%: 0 sites33%: 1 site34%: 0 sites35%: 1 site36%: 2 sites37%: 2 sites38%: 3 sites39%: 1 site40%: 2 sites41%: 1 site42%: 0 sites43%: 1 site44%: 1 site45%: 4 sites46%: 5 sites47%: 4 sites48%: 3 sites49%: 3 sites50%: 5 sites51%: 5 sites52%: 8 sites53%: 5 sites54%: 7 sites55%: 8 sites56%: 5 sites57%: 10 sites58%: 14 sites59%: 6 sites60%: 10 sites61%: 11 sites62%: 18 sites63%: 19 sites64%: 18 sites65%: 34 sites66%: 27 sites67%: 40 sites68%: 33 sites69%: 26 sites70%: 39 sites71%: 53 sites72%: 66 sites73%: 54 sites74%: 58 sites75%: 76 sites76%: 81 sites77%: 78 sites78%: 96 sites79%: 86 sites80%: 105 sites81%: 97 sites82%: 102 sites83%: 95 sites84%: 85 sites85%: 68 sites86%: 73 sites87%: 68 sites88%: 67 sites89%: 50 sites90%: 37 sites91%: 41 sites92%: 25 sites93%: 18 sites94%: 16 sites95%: 8 sites96%: 6 sites97%: 8 sites98%: 1 site99%: 2 sites100%: 56 sites77% 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

There are several areas for improvement that can enhance your site's SEO. Key priorities include resolving redirects, improving title tags, and adding meta descriptions. Implementing these changes will help boost site health and usability.

  1. 1

    Fix Redirects

    Why: Chained redirects can hurt site performance and crawl efficiency.

    How: Identify and eliminate chained redirects by directly linking URLs without intermediate steps.

    Checks: redirects

  2. 2

    Add Meta Descriptions

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

    How: Create unique and concise meta descriptions for all affected pages, focusing on keywords and relevance.

    Evidence: 119 pages have no meta description at all.

    119 pages affected

    Checks: meta-descriptions

  3. 3

    Improve Title Tags

    Why: Improperly formatted title tags can lead to lower search visibility.

    How: Revise titles to ensure optimal length (30-60 characters) and relevance to the page content.

    Checks: titles

  4. 4

    Resolve Heading Issues

    Why: Missing H1 headings can hinder page ranking and user navigation.

    How: Ensure each page has a clear and relevant H1 heading that accurately describes the content.

    Evidence: 6 pages: missing h1.

    6 pages affected

    Checks: headings

  5. 5

    Reduce Heavy Assets

    Why: Large files can slow down page load times, negatively impacting user experience.

    How: Optimize or compress large media files to improve loading speed.

    Checks: heavy-assets

  6. 6

    Link Orphan Pages

    Why: Orphan pages can't be crawled effectively and may not rank.

    How: Add internal links to these orphan pages from relevant sections within your site.

    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 gaps, including the absence of HTTP Strict Transport Security and Content Security Policy, making it vulnerable to attacks. Immediate implementation of security headers is recommended to enhance protection against data interception and clickjacking. Additionally, outdated libraries and exposed API keys should be addressed promptly.

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

    Missing HTTP Strict Transport SecurityMedium

    Why it matters: Without this, visitors can be intercepted on their first request when accessing without HTTPS.

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

    Evidence: HTTP Strict Transport Security

  2. 2

    Missing Content Security PolicyMedium

    Why it matters: This allows browsers to load scripts without restrictions, increasing the risk of XSS attacks.

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

    Evidence: Content Security Policy

  3. 3

    Missing Clickjacking ProtectionMedium

    Why it matters: Pages can be embedded in frames, posing risks of clickjacking.

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

    Evidence: Clickjacking protection

  4. 4

    Outdated jQuery LibraryMedium

    Why it matters: Vulnerabilities in jQuery 3.3.1 could be exploited depending on usage.

    Fix: Upgrade jQuery to at least version 3.5.0.

    Evidence: Vulnerable JavaScript libraries

  5. 5

    Exposed Google API KeyMedium

    Why it matters: The API key could be misused if proper restrictions are not applied.

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

    Evidence: Keys and secrets in page code

  6. 6

    Server Version DisclosureLow

    Why it matters: Revealing the server version can aid attackers in targeting specific vulnerabilities.

    Fix: Consider hiding the version by altering server configurations.

    Evidence: Software version disclosure

  7. 7

    Usage of Third-Party Scripts without SRILow

    Why it matters: Without Subresource Integrity, compromised scripts can introduce vulnerabilities.

    Fix: Implement a Content-Security-Policy specifying trusted domains for scripts.

    Evidence: Third-party scripts

  8. 8

    Missing Permissions PolicyInfo

    Why it matters: This could allow unnecessary access to browser features by third-party scripts.

    Fix: Add the header: Permissions-Policy: geolocation=(self).

    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-10-04-1112 | DIY SEO Hub