Scanned sites / www.smilesourcespokane.com / 2026-09-24-0434

www.smilesourcespokane.com scan from 9/24/2026, 4:34:38 AM

A newer scan exists. See the latest report for www.smilesourcespokane.com.

Scan 2026-09-24-0434

Scanned 9/24/2026, 4:34:38 AM, finished 9/24/2026, 5:26:03 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 24, 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, 1 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

1217 sites, median 82%, average 80%

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

031620%: 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%: 1 site47%: 1 site48%: 1 site49%: 0 sites50%: 3 sites51%: 4 sites52%: 4 sites53%: 3 sites54%: 4 sites55%: 1 site56%: 2 sites57%: 3 sites58%: 8 sites59%: 4 sites60%: 7 sites61%: 9 sites62%: 12 sites63%: 4 sites64%: 9 sites65%: 10 sites66%: 9 sites67%: 15 sites68%: 28 sites69%: 15 sites70%: 26 sites71%: 25 sites72%: 25 sites73%: 28 sites74%: 33 sites75%: 27 sites76%: 41 sites77%: 41 sites78%: 38 sites79%: 36 sites80%: 50 sites81%: 57 sites82%: 55 sites83%: 50 sites84%: 60 sites85%: 53 sites86%: 50 sites87%: 51 sites88%: 55 sites89%: 42 sites90%: 62 sites91%: 40 sites92%: 24 sites93%: 21 sites94%: 15 sites95%: 10 sites96%: 11 sites97%: 4 sites98%: 3 sites99%: 1 site100%: 20 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 site has several SEO issues needing attention, especially around redirects, title tags, and meta descriptions. The following priority fixes will enhance your site's performance.

  1. 1

    Fix Redirect Chains

    Why: Chained redirects can cause slow loading and harm SEO.

    How: Eliminate intermediary redirects by updating your links to point directly to the target URL.

    Checks: redirects

  2. 2

    Resolve Non-200 Responses

    Why: Pages returning errors can harm user experience and SEO rankings.

    How: Identify and fix pages with non-200 responses by correcting links or restoring deleted content.

    Checks: status-codes

  3. 3

    Update Title Tags

    Why: Missing or excessive title lengths hurt visibility on search engines.

    How: Revise titles to fit between 30-60 characters, reflecting the page's content.

    Checks: titles

  4. 4

    Add Missing Meta Descriptions

    Why: Descriptions help improve click-through rates from search results.

    How: Create unique meta descriptions for pages with missing ones, aiming for 50-160 characters.

    Checks: meta-descriptions

  5. 5

    Add Missing H1 Tags

    Why: H1 tags improve content structure and SEO clarity.

    How: Ensure each page has a unique H1 tag that summarizes its content.

    Checks: headings

  6. 6

    Link to Orphan Pages

    Why: Orphan pages are difficult for users to find and crawl.

    How: Embed internal links to the orphan pages from relevant sections of 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

This security review identifies several important areas where your website could improve its security posture. Key missing headers can leave your site vulnerable to interception, clickjacking, and exploitation of known vulnerabilities. Immediate attention to these issues is recommended to protect user data and enhance overall security.

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

    Missing HTTP Strict Transport Security (HSTS)Medium

    Why it matters: Without HSTS, users can be intercepted on their first request when accessing via HTTP.

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

    Evidence: HTTP Strict Transport Security

  2. 2

    Missing Content Security Policy (CSP)Medium

    Why it matters: The absence of CSP allows scripts and resources to load from any source, increasing XSS risks.

    Fix: Implement a Content-Security-Policy header: Content-Security-Policy: default-src 'self'; script-src 'self'; to restrict sources.

    Evidence: Content Security Policy

  3. 3

    Missing Clickjacking Protection (X-Frame-Options)Medium

    Why it matters: No X-Frame-Options header can lead to clickjacking vulnerabilities if embedded in other sites.

    Fix: Add the header: X-Frame-Options: DENY to prevent framing your content.

    Evidence: Clickjacking protection

  4. 4

    Vulnerable JavaScript Library PresentMedium

    Why it matters: Using jQuery 3.3.1 exposes your site to known vulnerabilities, potentially leading to exploitation.

    Fix: Upgrade jQuery to version 3.5.0 or later to mitigate these vulnerabilities.

    Evidence: Vulnerable JavaScript libraries

  5. 5

    Leaked Google API KeyMedium

    Why it matters: An exposed API key could allow unauthorized access and usage leading to additional costs or data exposure.

    Fix: Restrict this API key in the Google Cloud console to specific referrers to enhance security.

    Evidence: Keys and secrets in page code

  6. 6

    Exposed Server Banner Reveals VersionLow

    Why it matters: The server banner discloses your software version, making it easier for attackers to target known vulnerabilities.

    Fix: Configure your server to hide the exact version, such as by modifying the server settings to remove version from response.

    Evidence: Software version disclosure

  7. 7

    Missing Permissions PolicyInfo

    Why it matters: Without a permissions policy, unnecessary browser features remain enabled, increasing the risk from injected scripts.

    Fix: Add the header: Permissions-Policy: interest-cohort=() to disable certain features that are not needed.

    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-24-0434 | DIY SEO Hub