Scanned sites / www.smilesourcespokane.com / 2026-10-30-0600

www.smilesourcespokane.com scan from 2026-10-30 06:00:02 UTC DR 7

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

DR is Ahrefs Domain Rating (0-100, backlink strength), used under its Domain Rating License.

Scan 2026-10-30-0600

Scanned 2026-10-30 06:00:02 UTC, finished 2026-10-30 11:08:08 UTC. 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 30, 2026 the Site Spider crawled 261 pages and 734 assets of www.smilesourcespokane.com, starting from https://www.smilesourcespokane.com/. It scored 77 out of 100, a good result. 10 of 33 checks found something to fix, led by meta descriptions (120), heavy assets (24), redirects (232); 11 checks passed. Most of the points went to meta descriptions (−7.4), heavy assets (−6), redirects (−4). 12 checks found something the score does not count, listed as noted. 4 checks were not run because the crawl fetched nothing for them. 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
734
Status
Completed
Checks with issues
10 of 33
CoverageComplete crawl

995 of 1,028 discovered URLs were fetched, 33 blocked by robots.txt. The crawl reached everything it found. HTML only: nothing here ran JavaScript. 47 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 47 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 1378 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 734 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 counts22 noted
    Internal link counts for 129 pages; 22 worth a look.
  • 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.
  • URL format106 noted
    106 of 261 page URLs are harder to read, share or cache than they need to be.
  • Canonicals3 noted
    3 of 129 pages have a canonical worth checking.
  • Robots directives129 noted
    129 pages carry a robots directive; 0 carry none.
  • Anchor text159 noted
    159 destinations are linked without useful anchor text, or with nofollow.
  • Title and heading structure73 noted
    73 of 126 pages could use the title, heading and snippet space better. 3 noindex or canonicalized pages excluded.
  • Image weight and alt length38 noted
    38 images over 100 KB; 0 with alt text over 100 characters.
  • Response anomalies3 noted
    3 URLs answered in a way worth looking at.
  • HTML and head validationOK
    All 129 pages keep their head tags in <head>, once each, under Googlebot's 2 MB.
  • hreflangOK
    No page declares hreflang.
  • Structured dataOK
    129 of 126 indexable pages carry structured data: BreadcrumbList (129), ListItem (129), WebSite (129), WebPage (120), ImageObject (73). 0 pages with errors a rich result would fail on.
  • Near duplicates3 noted
    3 pages in 1 group read almost the same as another page (95% alike or more).
  • Soft 404sOK
    None of 129 pages answering 200 reads like an error page.
  • AccessibilityNot checked
    Not checked: the accessibility audit runs in the browser. Tick "Include JavaScript rendering checks" when you request a scan to run it.
  • Link positions22 noted
    22 of 101 linked pages are linked only from the template, never from another page's content.
  • PaginationOK
    No page declares rel=next or rel=prev pagination.
  • Headers and cookiesOK
    0 cookies set by the site; 15 response headers recorded across 995 URLs.
  • Orphans in searchNot checked
    Not checked: import a Search Console Pages export on the scan page to find pages Google shows that the site does not link to.
  • Link ScoreOK
    Link Score (internal PageRank, 0-100) for 129 pages; 0 hold almost none (10 or less).
  • JavaScript renderingNot checked
    Not checked: this scan did not render pages. Tick "Include JavaScript rendering checks" when you request a scan to compare the served HTML with what a browser builds.
  • PageSpeed InsightsNot checked
    Not checked yet: PageSpeed Insights runs on the top pages once the crawl has finished.
  • Spelling18 noted
    18 words an English dictionary does not know, on 33 pages. Product names and jargon will appear here too.

Where this scan sits among all scanned sites

2345 sites, median 79%, average 78%

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

0581150%: 0 sites1%: 0 sites2%: 0 sites3%: 0 sites4%: 0 sites5%: 0 sites6%: 0 sites7%: 0 sites8%: 0 sites9%: 1 site10%: 0 sites11%: 0 sites12%: 0 sites13%: 0 sites14%: 1 site15%: 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%: 1 site34%: 0 sites35%: 2 sites36%: 2 sites37%: 1 site38%: 3 sites39%: 1 site40%: 3 sites41%: 1 site42%: 1 site43%: 3 sites44%: 1 site45%: 4 sites46%: 5 sites47%: 5 sites48%: 3 sites49%: 7 sites50%: 5 sites51%: 4 sites52%: 10 sites53%: 7 sites54%: 8 sites55%: 10 sites56%: 8 sites57%: 12 sites58%: 17 sites59%: 9 sites60%: 16 sites61%: 12 sites62%: 20 sites63%: 27 sites64%: 22 sites65%: 32 sites66%: 35 sites67%: 35 sites68%: 34 sites69%: 47 sites70%: 44 sites71%: 69 sites72%: 71 sites73%: 70 sites74%: 68 sites75%: 72 sites76%: 87 sites77%: 92 sites78%: 107 sites79%: 85 sites80%: 107 sites81%: 105 sites82%: 115 sites83%: 102 sites84%: 106 sites85%: 88 sites86%: 71 sites87%: 73 sites88%: 59 sites89%: 65 sites90%: 36 sites91%: 46 sites92%: 39 sites93%: 24 sites94%: 16 sites95%: 12 sites96%: 12 sites97%: 12 sites98%: 5 sites99%: 2 sites100%: 68 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

Your site's health score is good, but there are several key areas for improvement that will enhance SEO and user experience.

  1. 1

    Fix Redirect Chains

    Why: Chained redirects can slow down loading speed and affect crawlers.

    How: Identify unnecessary redirects and consolidate them to create direct links.

    Checks: redirects, status-codes

  2. 2

    Add Meta Descriptions

    Why: 120 pages lack meta descriptions, affecting CTR and SEO.

    How: Write unique, keyword-rich meta descriptions for each page following best practices.

    Checks: meta-descriptions

  3. 3

    Improve Title Tags

    Why: 25 pages have issues with title tags, harming SEO performance.

    How: Revise title tags to be unique, concise, and within optimal length.

    Checks: titles

  4. 4

    Add Missing H1 Tags

    Why: 6 pages lack H1 tags, which affects structure and SEO.

    How: Add appropriate H1 tags to the missing pages to establish content hierarchy.

    Checks: headings

  5. 5

    Shrink Heavy Assets

    Why: Large assets slow down page load times and can hinder user experience.

    How: Optimize or replace heavy assets to improve loading speed.

    Evidence: 327 KB of document, loaded by 35 pages, so every visitor to any of them downloads it.

    35 pages affected

    Depends on: If it is a download rather than part of the page, weight matters less; move it out of the page instead.

    Checks: heavy-assets

  6. 6

    Address Orphan Pages

    Why: 25 pages are not linked internally, reducing their visibility.

    How: Add internal links to these orphan pages from relevant content to enhance discoverability.

    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 potential vulnerabilities in your website that could expose sensitive information or allow attacks. Immediate action is recommended to implement security headers and update any vulnerable libraries to protect both the site and its visitors.

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

    Missing HTTP Strict Transport Security HeaderMedium

    Why it matters: This header helps ensure that users only connect to your site securely over HTTPS, preventing man-in-the-middle attacks.

    Fix: Add the header 'Strict-Transport-Security: max-age=31536000; includeSubDomains' to your server configuration.

    Evidence: HTTP Strict Transport Security

  2. 2

    Missing Content Security Policy HeaderMedium

    Why it matters: A Content Security Policy reduces the risk of cross-site scripting (XSS) attacks by controlling which resources can be loaded.

    Fix: Implement 'Content-Security-Policy: default-src 'self';' in your server response headers.

    Evidence: Content Security Policy

  3. 3

    Lack of Clickjacking ProtectionMedium

    Why it matters: Without protection, your pages can be embedded in malicious sites, enabling clickjacking attacks.

    Fix: Add 'X-Frame-Options: DENY' to your HTTP response headers.

    Evidence: Clickjacking protection

  4. 4

    Vulnerable JavaScript Library DetectedMedium

    Why it matters: Using an outdated version of jQuery introduces known vulnerabilities that could be exploited.

    Fix: Update jQuery from 3.3.1 to at least 3.5.0 to mitigate these vulnerabilities.

    Evidence: Vulnerable JavaScript libraries

  5. 5

    Exposure of Google API KeyMedium

    Why it matters: Distributing API keys in publicly accessible code can allow unauthorized use, potentially leading to data exposure or API misuse.

    Fix: Restrict the API key in the Google Cloud console by setting allowed referrers based on where it can be used.

    Evidence: Keys and secrets in page code

  6. 6

    Server Software Version DisclosureLow

    Why it matters: Revealing the server version can provide attackers with information about potential vulnerabilities.

    Fix: Consider obscuring your server version by updating server configuration or using a reverse proxy.

    Evidence: Software version disclosure

  7. 7

    No Permissions Policy HeaderInfo

    Why it matters: Absence of this header means the site allows all browser features, increasing risk if scripts are compromised.

    Fix: Add 'Permissions-Policy: fullscreen=(self)' to restrict features only to trusted origins.

    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 (995 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.

DR is Ahrefs Domain Rating (0-100, backlink strength), used under its Domain Rating License.

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.