Scanned sites / spokanegreenscape.com / 2026-09-12-0551
spokanegreenscape.com scan from 2026-09-12 05:51:50 UTC DR 22
DR is Ahrefs Domain Rating (0-100, backlink strength), used under its Domain Rating License.
Scan 2026-09-12-0551
Scanned 2026-09-12 05:51:50 UTC, finished 2026-09-12 07:30:44 UTC
Site: https://spokanegreenscape.com/
Download SQLite databaseEvery page and asset from this scan, with the crawl events, in one file.
On September 12, 2026 the Site Spider crawled 77 pages and 274 assets of spokanegreenscape.com, starting from https://spokanegreenscape.com/. It scored 92 out of 100, an excellent result. 10 of 26 checks found something to fix, led by meta descriptions (20), title tags (15), sitemap coverage (16); 8 checks passed. Most of the points went to meta descriptions (−2.2), title tags (−2), sitemap coverage (−1.3). 8 checks found something the score does not count, listed as noted. 11 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: Medium2 medium, 1 low and 1 info findings. See the security findings ↓
- Pages crawled
- 77
- Assets fetched
- 274
- Status
- Completed
- Checks with issues
- 10 of 26
351 of 351 discovered URLs were fetched. The crawl reached everything it found. HTML only: nothing here ran JavaScript. 18 link destinations on other sites were checked.
- Title tags15 issues15 of 73 pages have title issues. 1 noindex or canonicalized page excluded.−2 points
- Meta descriptions20 issues20 of 73 pages have meta description issues. 1 noindex or canonicalized page excluded.−2.2 points
- Headings3 issues3 of 73 pages have heading issues. 1 noindex or canonicalized page excluded.−0.2 points
- Broken links1 issue1 internal link point at 1 broken URL.−0.3 points
- Links to other sites1 issue1 destination answered with an error, 4 could not be determined (timeouts, rate limits or refusals), of 14 destinations checked.−0.4 points
- Redirects2 issues6 redirecting URLs, 0 of them chained.−0.1 points
- Non-200 responses1 issue7 URLs did not return a 2xx response. 3 of them are pages, 1 with an error status; the rest are assets or redirects.−0.1 points
- Rate limitedOKThe site did not rate limit the crawler.
- IndexabilityOK0 of 73 indexable pages have indexability warnings. 1 page noindex by design.
- Image alt textOK0 of 311 image references have no alt attribute. 18 use an empty alt (decorative), which is fine.
- Heavy assets1 issue1 asset larger than 500 KB among 274 fetched assets.−0.6 points
- Orphan pages15 issues15 pages have no internal links pointing at them.−0.8 points
- Sitemap coverage16 issues4 sitemaps listing 74 URLs: 0 crawled pages missing, 0 listed URLs broken or redirecting, 16 reachable only via the sitemap.−1.3 points
- Internal link counts4 notedInternal link counts for 74 pages; 4 worth a look.
- Thin contentOK0 of 73 pages have fewer than 200 words. 1 noindex or canonicalized page excluded.
- Duplicate contentOK0 groups of pages with identical HTML.
- URL format2 noted2 of 77 page URLs are harder to read, share or cache than they need to be.
- Canonicals1 noted1 of 74 pages have a canonical worth checking.
- Robots directives74 noted74 pages carry a robots directive; 0 carry none.
- Anchor text11 noted11 destinations are linked without useful anchor text, or with nofollow.
- Title and heading structure7 noted7 of 73 pages could use the title, heading and snippet space better. 1 noindex or canonicalized page excluded.
- Image weight and alt length48 noted48 images over 100 KB; 0 with alt text over 100 characters.
- Response anomalies1 noted1 URL answered in a way worth looking at.
- HTML and head validationNot checkedNot checked: this scan was crawled before this check existed. Scan the site again to run it.
- hreflangNot checkedNot checked: this scan was crawled before this check existed. Scan the site again to run it.
- Structured dataNot checkedNot checked: this scan was crawled before this check existed. Scan the site again to run it.
- Near duplicatesNot checkedNot checked: this scan was crawled before this check existed. Scan the site again to run it.
- Soft 404sOKNone of 74 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 positionsNot checkedNot checked: this scan was crawled before link positions were recorded. Scan the site again to run it.
- PaginationNot checkedNot checked: this scan was crawled before this check existed. Scan the site again to run it.
- Headers and cookiesOK0 cookies set by the site; 15 response headers recorded across 351 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 74 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.
- SpellingNot checkedNot checked: this scan was crawled before this check existed. Scan the site again to run it.
Where this scan sits among all scanned sites
2331 sites, median 79%, average 78%
spokanegreenscape.com scores 92%, higher than 92% of the 2331 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 findingsWritten from an earlier version of the analysis. The findings on this page have been recomputed since, so counts and labels here may differ from what the plan describes. The advice still points at the same checks.
Your site's health score is excellent, but there are a few important items to address. Prioritize fixing broken links, redirect issues, title and meta description optimization, heading fixes, and improving orphan page visibility.
- 1
Fix Broken Link
Why: Repairing broken links enhances user experience and SEO.
How: Update or remove the broken link on the page: https://spokanegreenscape.com/rain-collection-systems-spokane-greenscapes/.
Checks: broken-links
- 2
Consolidate Redirects
Why: Minimizing redirects improves page speed and user experience.
How: Update links for the 6 URLs to direct to their final destinations without unnecessary redirects.
Checks: redirects
- 3
Optimize Title Tags
Why: Improving title tags enhances SEO and click-through rates.
How: Revise the 14 pages with issues to ensure titles are under 60 characters and unique.
Checks: titles
- 4
Enhance Meta Descriptions
Why: Unique meta descriptions improve visibility and SEO.
How: Revise the 4 pages with meta description issues for uniqueness and concise length.
Checks: meta-descriptions
- 5
Add Missing Heading Tags
Why: Proper headings improve content structure and user readability.
How: Add <h1> tags to the 3 pages where it’s missing.
Checks: headings
- 6
Link to Orphan Pages
Why: Linking helps search engines crawl these important pages.
How: Add internal links to the 15 orphan pages from relevant existing pages.
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 crawlThe security review of spokanegreenscape.com reveals several vulnerabilities, including the absence of a Content Security Policy and exposure of a Google API key. Addressing these issues will improve the site's resilience against attacks and unauthorized access.
- 0 high
- 2 medium
- 1 low
- 1 info
- 1
Missing Content Security PolicyMedium
Why it matters: The site lacks a Content Security Policy (CSP), allowing scripts and styles to load from any source, increasing the risk of XSS attacks.
Fix: Implement a CSP header in your server configuration. An example header: 'Content-Security-Policy: default-src 'self';'.
Evidence: Content Security Policy
- 2
Leaked Google API KeyMedium
Why it matters: A Google API key found in the site's code is exposed to all visitors, risking misuse.
Fix: Restrict the API key to specific HTTP referrers in the Google Cloud console to limit its use.
Evidence: Keys and secrets in page code
- 3
Third-party Scripts Without Subresource IntegrityLow
Why it matters: Scripts from external domains can be compromised, affecting site security; they lack Subresource Integrity checks.
Fix: Consider implementing a CSP to specify permitted script sources, which can mitigate risks from such scripts.
Evidence: Third-party scripts
- 4
Sensitive Paths in robots.txtInfo
Why it matters: The robots.txt file discloses a potentially sensitive path, which could aid attackers in gaining insight into the site's structure.
Fix: Limit access to sensitive paths through proper server-side authentication and authorization instead of relying solely on robots.txt.
Evidence: Sensitive paths in robots.txt
What the checks found
- FoundContent Security PolicyMedium
None of the 74 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://spokanegreenscape.com/ → no content-security-policy
- https://spokanegreenscape.com/customer-accounts/ → no content-security-policy
- https://spokanegreenscape.com/contact-us/ → no content-security-policy
- https://spokanegreenscape.com/landscape-installation-spokane-greenscape/ → no content-security-policy
- https://spokanegreenscape.com/landscape-design-spokane-greenscape/ → no content-security-policy
- https://spokanegreenscape.com/pavers-patios-walkways-spokane-greenscape/ → no content-security-policy
- https://spokanegreenscape.com/retaining-walls-spokane-greenscape/ → no content-security-policy
- https://spokanegreenscape.com/water-features-spokane-greenscape/ → no content-security-policy
- https://spokanegreenscape.com/planting-services-spokane-greenscapes/ → no content-security-policy
- https://spokanegreenscape.com/fire-pit-installation/ → no content-security-policy
- https://spokanegreenscape.com/landscape-lighting-installation-greenscape/ → no content-security-policy
- https://spokanegreenscape.com/garden-box-installation/ → no content-security-policy
- FoundKeys and secrets in page codeMedium
1 credential-like value found in code served to every visitor: Google API key.
- Google API key AIzaSy…Yk (39 chars) in https://spokanegreenscape.com/contact-us/: 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 5 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.)
- www.googletagmanager.com (40 script tags)
- cdn.trustindex.io (42 script tags)
- script.bullseye.so (40 script tags)
- a320d538.delivery.rocketcdn.me (10 script tags)
- challenges.cloudflare.com (38 script tags)
- NoteSensitive paths in robots.txt
robots.txt lists 1 path that look private. robots.txt is public and does not restrict access, so it doubles as a map for anyone probing the site; those paths need real access control.
- Disallow: /wp-admin/
9 checks passed, 3 not applicable
- OKHTTPS
All 74 crawled pages were served over HTTPS.
- OKHTTP Strict Transport Security
strict-transport-security is set on all 74 HTML pages.
- OKClickjacking protection
x-frame-options is set on all 74 HTML pages.
- OKMIME sniffing protection
x-content-type-options is set on all 74 HTML pages.
- OKSoftware version disclosure
The Server header names a product without a version, and there is no X-Powered-By header.
- OKMixed content
No HTTPS page loads a script, stylesheet, font or image over plain HTTP.
- OKForms over HTTPS
38 forms found, all on HTTPS pages posting to HTTPS addresses.
- OKVulnerable JavaScript libraries
2 library versions recognised, none with known vulnerabilities.
- OKExposed files and listings
None of the crawled URLs is a configuration file, backup, dump, repository folder or directory listing.
- Not applicableReferrer policy
This scan predates the crawler recording the headers this check needs. Rescan the site to check it.
- Not applicablePermissions policy
This scan predates the crawler recording the headers this check needs. Rescan the site to check it.
- Not applicableCookie flags
This scan predates the crawler recording the headers this check needs. Rescan the site to check it.
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 spokanegreenscape.com
Their neighbours in the SEO rank table, which orders every scanned site by health score.
- www.firstchoicephoto.caDR 1092/100 · rank 151 · 70 pages
- sonsofelectric.caDR 192/100 · rank 151 · 26 pages
- www.spokanechiro.comDR 292/100 · rank 151 · 126 pages
- alpinedds.comDR 892/100 · rank 151 · 22 pages
- sportclips.caDR 6892/100 · rank 151 · 1,217 pages
- nexusvisioncentre.caDR 192/100 · rank 151 · 20 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 spokanegreenscape.com from its pages as published, the way a search engine does. It shows summary figures only.
Own spokanegreenscape.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 spokanegreenscape.com. Removal needs no account and no proof of purchase.