Scanned sites / www.smilesourcespokane.com / 2026-10-27-0733
www.smilesourcespokane.com scan from 2026-10-27 07:33:48 UTC DR 7
DR is Ahrefs Domain Rating (0-100, backlink strength), used under its Domain Rating License.
Scan 2026-10-27-0733
Scanned 2026-10-27 07:33:48 UTC, finished 2026-10-27 11:37:47 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.
On October 27, 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
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 issues25 of 126 pages have title issues. 3 noindex or canonicalized pages excluded.−1.9 points
- Meta descriptions120 issues120 of 126 pages have meta description issues. 3 noindex or canonicalized pages excluded.−7.4 points
- Headings6 issues6 of 126 pages have heading issues. 3 noindex or canonicalized pages excluded.−0.3 points
- Broken linksOK0 internal links point at 0 broken URLs.
- Links to other sites1 issue1 destination answered with an error, 17 could not be determined (timeouts, rate limits or refusals), of 47 destinations checked.−0.3 points
- Redirects232 issues137 redirecting URLs, 103 of them chained.−4 points
- Non-200 responses137 noted137 URLs did not return a 2xx response. 132 of them are pages, 0 with an error status; the rest are assets or redirects.
- Rate limitedOKThe site did not rate limit the crawler.
- IndexabilityOK0 of 126 indexable pages have indexability warnings. 3 pages noindex by design.
- Image alt text83 issues83 of 1378 image references have no alt attribute. 989 use an empty alt (decorative), which is fine.−0.4 points
- Heavy assets24 issues24 assets larger than 500 KB among 734 fetched assets.−6 points
- Orphan pages25 issues25 pages have no internal links pointing at them.−0.8 points
- Sitemap coverage25 issues15 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 notedInternal link counts for 129 pages; 22 worth a look.
- Thin content5 issues5 of 126 pages have fewer than 200 words. 3 noindex or canonicalized pages excluded.−0.3 points
- Duplicate contentOK0 groups of pages with identical HTML.
- URL format106 noted106 of 261 page URLs are harder to read, share or cache than they need to be.
- Canonicals3 noted3 of 129 pages have a canonical worth checking.
- Robots directives129 noted129 pages carry a robots directive; 0 carry none.
- Anchor text159 noted159 destinations are linked without useful anchor text, or with nofollow.
- Title and heading structure73 noted73 of 126 pages could use the title, heading and snippet space better. 3 noindex or canonicalized pages excluded.
- Image weight and alt length38 noted38 images over 100 KB; 0 with alt text over 100 characters.
- Response anomalies3 noted3 URLs answered in a way worth looking at.
- HTML and head validationOKAll 129 pages keep their head tags in <head>, once each, under Googlebot's 2 MB.
- hreflangOKNo page declares hreflang.
- Structured dataOK129 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 noted3 pages in 1 group read almost the same as another page (95% alike or more).
- Soft 404sOKNone of 129 pages answering 200 reads like an error page.
- AccessibilityNot checkedNot checked: the accessibility audit runs in the browser. Tick "Include JavaScript rendering checks" when you request a scan to run it.
- Link positions22 noted22 of 101 linked pages are linked only from the template, never from another page's content.
- PaginationOKNo page declares rel=next or rel=prev pagination.
- Headers and cookiesOK0 cookies set by the site; 15 response headers recorded across 995 URLs.
- Orphans in searchNot checkedNot checked: import a Search Console Pages export on the scan page to find pages Google shows that the site does not link to.
- Link ScoreOKLink Score (internal PageRank, 0-100) for 129 pages; 0 hold almost none (10 or less).
- JavaScript renderingNot checkedNot 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 checkedNot checked yet: PageSpeed Insights runs on the top pages once the crawl has finished.
- Spelling18 noted18 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
2328 sites, median 79%, average 78%
www.smilesourcespokane.com scores 77%, higher than 38% of the 2328 scanned sites. See the full ranking.
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...
Fix plan
Written by gpt-4o-mini from the scan findingsThe site has several SEO issues needing attention, focusing primarily on redirects, metadata, and content quality. Addressing these will significantly improve SEO performance.
- 1
Fix Chained Redirects
Why: Chained redirects can slow down site access and harm SEO.
How: Identify and eliminate unnecessary redirects. Use 301 redirects to point directly to the final URL.
Checks: redirects
- 2
Resolve Non-200 Responses
Why: Non-200 responses hinder user accessibility and search engine crawling.
How: Update or remove URLs returning 301 status that are not actively used or needed.
Checks: status-codes
- 3
Add Missing Meta Descriptions
Why: Meta descriptions improve click-through rates from search results.
How: Write unique, concise meta descriptions for all pages missing them.
Evidence: 119 pages have no meta description at all.
119 pages affected
Checks: meta-descriptions
- 4
Add H1 Headings
Why: Missing H1 headings affect content structure and SEO.
How: Add a descriptive H1 tag to the affected pages to improve content hierarchy.
Evidence: 6 pages: missing h1.
6 pages affected
- https://www.smilesourcespokane.com/
- https://www.smilesourcespokane.com/north-side-wa/new-patients/special-offers/
- https://www.smilesourcespokane.com/south-hill-wa/home-2/
- https://www.smilesourcespokane.com/south-hill-wa/new-patients/special-offers/
- https://www.smilesourcespokane.com/spokane-valley-wa/new-patients/special-offers/
Checks: headings
- 5
Reduce Heavy Assets
Why: Large assets can slow down webpage loading times, negatively affecting user experience.
How: Compress or host large files like videos externally to reduce page load size.
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
Improve Thin Content Pages
Why: Low word count pages may not provide enough value for users or search engines.
How: Enhance the thin content pages with additional relevant information or eliminate them if not necessary.
Checks: thin-content
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 crawlYour website has several key security issues that need addressing, including missing headers that protect against various attacks and disclose software versions. Implementing these changes will help strengthen your site against potential vulnerabilities and misuse.
- 0 high
- 5 medium
- 1 low
- 1 info
- 1
Missing HTTP Strict Transport Security (HSTS)Medium
Why it matters: Without HSTS, users can be intercepted before using HTTPS.
Fix: Add the header: Strict-Transport-Security: max-age=31536000; includeSubDomains
Evidence: HTTP Strict Transport Security
- 2
Lack of Content Security Policy (CSP)Medium
Why it matters: No CSP allows unrestricted script and style loading, increasing XSS risks.
Fix: Add the header: Content-Security-Policy: default-src 'self'
Evidence: Content Security Policy
- 3
Missing X-Frame-OptionsMedium
Why it matters: Without it, your site is vulnerable to clickjacking attacks.
Fix: Add the header: X-Frame-Options: DENY
Evidence: Clickjacking protection
- 4
Vulnerable JavaScript LibraryMedium
Why it matters: Using outdated jQuery (3.3.1) has known vulnerabilities.
Fix: Upgrade to jQuery version 3.5.0 or higher.
Evidence: Vulnerable JavaScript libraries
- 5
Leaked Google API KeyMedium
Why it matters: Exposing this key increases risk of misuse by unauthorized other parties.
Fix: Restrict the API key usage to specified HTTP referrers in the Google Cloud console.
Evidence: Keys and secrets in page code
- 6
Server Version DisclosureLow
Why it matters: Revealing server details can help attackers find vulnerabilities.
Fix: Hide the server version by changing the server configuration.
Evidence: Software version disclosure
- 7
Missing Permissions PolicyInfo
Why it matters: Absence of this header allows injected scripts to misuse browser features.
Fix: Add the header: Permissions-Policy: interest-cohort=()
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.
- saskflowers.comDR 078/100 · rank 1237 · 215 pages
- myconceptdentistry.comDR 1178/100 · rank 1237 · 36 pages
- subzerotechnical.comDR 378/100 · rank 1237 · 43 pages
- arvow.comDR 5877/100 · rank 1343 · 750 pages
- www.tendingtoes.comDR 777/100 · rank 1343 · 21 pages
- www.voyeurshd.comDR 4677/100 · rank 1343 · 4,627 pages
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.