Scanned sites / visitboise.com
SEO report for visitboise.com
The latest Site Spider scan of visitboise.com, with 1 scan on record. Each scan is at its own address, for example /domain/visitboise-com/2026-10-01-0101.
Latest scan
Scanned 10/1/2026, 1:01:49 AM, finished 10/1/2026, 6:42:46 AM. Found on page 4 of brave web search results
Site: https://visitboise.com/
Download SQLite databaseEvery page and asset from this scan, with the crawl events, in one file.
On October 1, 2026 the Site Spider crawled 732 pages and 1021 assets of visitboise.com, starting from https://visitboise.com/. It scored 74 out of 100, a result that needs work. 13 of 16 checks found something to fix, led by meta descriptions (406), heavy assets (65), sitemap coverage (492); 2 checks passed. Most of the points went to meta descriptions (−6.5), heavy assets (−6), sitemap coverage (−5.9). 1 check 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, 3 low and 1 info findings. See the security findings ↓
- Pages crawled
- 732
- Assets fetched
- 1021
- Status
- Completed
- Checks with issues
- 13 of 16
1,753 of 1,754 discovered URLs were fetched, 6,946 left out by the 5,000-page and 1,000-asset budget. The job finished, but the crawl did not reach everything it found. HTML only: nothing here ran JavaScript. 300 link destinations on other sites were checked, 1202 left unchecked.
- Title tags188 issues188 of 492 pages have title issues. 8 noindex or canonicalized pages excluded.−3.8 points
- Meta descriptions406 issues406 of 492 pages have meta description issues. 8 noindex or canonicalized pages excluded.−6.5 points
- Headings28 issues28 of 492 pages have heading issues. 8 noindex or canonicalized pages excluded.−0.3 points
- Broken links4 issues17 internal links point at 4 broken URLs.−0.2 points
- Links to other sites3 issues3 destinations answered with an error, 55 could not be determined (timeouts, rate limits or refusals), 1202 were left unchecked by the per-scan cap, of 300 destinations checked.−0.2 points
- Redirects229 issues226 redirecting URLs, 9 of them chained.−1.8 points
- Non-200 responses7 issues233 URLs did not return a 2xx response. 232 of them are pages, 7 with an error status; the rest are assets or redirects.−0.1 points
- Rate limitedOKThe site did not rate limit the crawler.
- Indexability2 issues2 of 497 indexable pages have indexability warnings. 3 pages noindex by design.
- Image alt text1,022 issues1022 of 13359 image references have no alt attribute. 3494 use an empty alt (decorative), which is fine.−0.5 points
- Heavy assets65 issues65 assets larger than 500 KB among 1021 fetched assets. 13 documents over that size are listed but not counted: downloads are not page weight.−6 points
- Orphan pages103 issues103 pages have no internal links pointing at them.−0.8 points
- Sitemap coverage492 issues1 sitemap listing 0 URLs: 492 crawled pages missing, 0 listed URLs broken or redirecting, 0 reachable only via the sitemap.−5.9 points
- Internal link countsOKInternal link counts for 500 pages.
- Thin content4 issues4 of 492 pages have fewer than 200 words. 8 noindex or canonicalized pages excluded.−0.1 points
- Duplicate contentOK0 groups of pages with identical HTML.
Where this site sits among all scanned sites
1754 sites, median 80%, average 79%
visitboise.com scores 74%, higher than 26% of the 1754 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 findingsYour website requires urgent fixes for broken links, redirects, and meta descriptions. Addressing these will enhance user experience and SEO performance significantly.
- 1
Fix Broken Links
Why: 17 internal links are broken, leading to 404 errors that harm user experience and SEO.
How: Update links used in your content to point to valid pages. Use a site link check tool to identify broken URLs.
Checks: broken-links
- 2
Reduce Redirects
Why: 226 redirects can slow down your site, affecting user experience.
How: Identify and consolidate unnecessary redirects. Aim to eliminate chained redirects by linking users directly to the final destination.
Checks: redirects
- 3
Create Meta Descriptions
Why: 406 pages have missing or duplicated meta descriptions, impacting click-through rates in search results.
How: Write unique meta descriptions for each affected page that summarize the content in under 160 characters.
Checks: meta-descriptions
- 4
Sitemap Update
Why: A sitemap listing 0 URLs reduces your site's discoverability by search engines.
How: Ensure all 492 crawled pages are included in the sitemap, then resubmit it to search engines.
Checks: sitemap-coverage
- 5
Address Non-200 Responses
Why: 233 URLs are not returning a 2xx response, leading to poor user experience and SEO issues.
How: Review the URLs and fix any broken or improperly configured pages to ensure they return 200 OK status.
Checks: status-codes
- 6
Fix Heading Issues
Why: 28 pages with heading issues can confuse search engines about page structure.
How: Ensure each page contains a single H1 heading and organize subsections with H2/H3 headings appropriately.
Checks: headings
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 security issues that need attention. Most critically, strict transport security is missing, which can expose users to risk during initial connections. Other concerns include lack of clickjacking protection, cookie safety flags, and an outdated JavaScript library. Addressing these issues will significantly improve your site's security.
- 0 high
- 5 medium
- 3 low
- 1 info
- 1
Missing HTTP Strict Transport Security (HSTS)Medium
Why it matters: Without HSTS, users can be intercepted on initial requests to non-HTTPS URLs.
Fix: Add the header 'Strict-Transport-Security: max-age=31536000; includeSubDomains' to all responses.
Evidence: HTTP Strict Transport Security
- 2
Missing X-Frame-Options HeaderMedium
Why it matters: Without clickjacking protection, malicious sites can frame your pages, risking user interaction.
Fix: Add the header 'X-Frame-Options: DENY' or set a CSP frame-ancestors directive.
Evidence: Clickjacking protection
- 3
Cookies Missing Security FlagsMedium
Why it matters: Cookies without Secure, HttpOnly, or SameSite flags are at risk of exploitation.
Fix: Set your cookies with Secure; HttpOnly; SameSite=Strict or SameSite=Lax.
Evidence: Cookie flags
- 4
Outdated JavaScript LibraryMedium
Why it matters: Using jQuery 3.1.2 exposes you to known vulnerabilities that could be exploited.
Fix: Upgrade jQuery to at least version 3.5.0 to close these vulnerabilities.
Evidence: Vulnerable JavaScript libraries
- 5
Exposed Google API KeyMedium
Why it matters: Public API keys can be exploited; they should have referrer restrictions.
Fix: Restrict the Google API key usage to authorized HTTP referrers in the Google Cloud console.
Evidence: Keys and secrets in page code
- 6
Missing X-Content-Type-Options HeaderLow
Why it matters: Without this header, browsers may misinterpret files leading to security vulnerabilities.
Fix: Add the header 'X-Content-Type-Options: nosniff' to all HTML responses.
Evidence: MIME sniffing protection
- 7
Missing Referrer-Policy HeaderLow
Why it matters: Not having a referrer policy can expose users' full URLs to third parties.
Fix: Add the header 'Referrer-Policy: no-referrer-when-downgrade' to all responses.
Evidence: Referrer policy
- 8
Third-party Scripts Missing Subresource IntegrityLow
Why it matters: Without SRI, compromised third-party scripts can change site behavior.
Fix: Implement a Content-Security-Policy that includes the domains of third-party scripts.
Evidence: Third-party scripts
- 9
Missing Permissions-Policy HeaderInfo
Why it matters: A permissions-policy could limit undesired browser feature access for injected scripts.
Fix: Add 'Permissions-Policy: interest-cohort=()' to restrict unused features.
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://visitboise.com/ → no strict-transport-security
- https://visitboise.com/play/ → no strict-transport-security
- https://visitboise.com/play/arts-and-culture/ → no strict-transport-security
- https://visitboise.com/play/arts-and-culture/basque/ → no strict-transport-security
- https://visitboise.com/play/arts-and-culture/performing-arts/ → no strict-transport-security
- https://visitboise.com/play/arts-and-culture/museums/ → no strict-transport-security
- https://visitboise.com/play/family-fun/ → no strict-transport-security
- https://visitboise.com/play/nightlife/ → no strict-transport-security
- https://visitboise.com/play/outdoor/ → no strict-transport-security
- https://visitboise.com/play/outdoor/biking/ → no strict-transport-security
- https://visitboise.com/play/outdoor/fishing/ → no strict-transport-security
- https://visitboise.com/play/outdoor/golf/ → no strict-transport-security
- FoundClickjacking protectionMedium
3 of 500 HTML pages send 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://visitboise.com/ → no x-frame-options
- https://visitboise.com/play/ → no x-frame-options
- https://visitboise.com/play/arts-and-culture/ → no x-frame-options
- https://visitboise.com/play/arts-and-culture/basque/ → no x-frame-options
- https://visitboise.com/play/arts-and-culture/performing-arts/ → no x-frame-options
- https://visitboise.com/play/arts-and-culture/museums/ → no x-frame-options
- https://visitboise.com/play/family-fun/ → no x-frame-options
- https://visitboise.com/play/nightlife/ → no x-frame-options
- https://visitboise.com/play/outdoor/ → no x-frame-options
- https://visitboise.com/play/outdoor/biking/ → no x-frame-options
- https://visitboise.com/play/outdoor/fishing/ → no x-frame-options
- https://visitboise.com/play/outdoor/golf/ → no x-frame-options
- FoundMIME sniffing protectionLow
No HTML page sends x-content-type-options. Without X-Content-Type-Options: nosniff a browser may run a file as a script because of its contents rather than its declared type.
- https://visitboise.com/ → no x-content-type-options
- https://visitboise.com/play/ → no x-content-type-options
- https://visitboise.com/play/arts-and-culture/ → no x-content-type-options
- https://visitboise.com/play/arts-and-culture/basque/ → no x-content-type-options
- https://visitboise.com/play/arts-and-culture/performing-arts/ → no x-content-type-options
- https://visitboise.com/play/arts-and-culture/museums/ → no x-content-type-options
- https://visitboise.com/play/family-fun/ → no x-content-type-options
- https://visitboise.com/play/nightlife/ → no x-content-type-options
- https://visitboise.com/play/outdoor/ → no x-content-type-options
- https://visitboise.com/play/outdoor/biking/ → no x-content-type-options
- https://visitboise.com/play/outdoor/fishing/ → no x-content-type-options
- https://visitboise.com/play/outdoor/golf/ → no x-content-type-options
- FoundReferrer policyLow
3 of 500 HTML pages send referrer-policy. Without a Referrer-Policy the full page address, including any query string, is sent to every site a visitor clicks through to.
- https://visitboise.com/ → no referrer-policy
- https://visitboise.com/play/ → no referrer-policy
- https://visitboise.com/play/arts-and-culture/ → no referrer-policy
- https://visitboise.com/play/arts-and-culture/basque/ → no referrer-policy
- https://visitboise.com/play/arts-and-culture/performing-arts/ → no referrer-policy
- https://visitboise.com/play/arts-and-culture/museums/ → no referrer-policy
- https://visitboise.com/play/family-fun/ → no referrer-policy
- https://visitboise.com/play/nightlife/ → no referrer-policy
- https://visitboise.com/play/outdoor/ → no referrer-policy
- https://visitboise.com/play/outdoor/biking/ → no referrer-policy
- https://visitboise.com/play/outdoor/fishing/ → no referrer-policy
- https://visitboise.com/play/outdoor/golf/ → no referrer-policy
- 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://visitboise.com/ → no permissions-policy
- https://visitboise.com/play/ → no permissions-policy
- https://visitboise.com/play/arts-and-culture/ → no permissions-policy
- https://visitboise.com/play/arts-and-culture/basque/ → no permissions-policy
- https://visitboise.com/play/arts-and-culture/performing-arts/ → no permissions-policy
- https://visitboise.com/play/arts-and-culture/museums/ → no permissions-policy
- https://visitboise.com/play/family-fun/ → no permissions-policy
- https://visitboise.com/play/nightlife/ → no permissions-policy
- https://visitboise.com/play/outdoor/ → no permissions-policy
- https://visitboise.com/play/outdoor/biking/ → no permissions-policy
- https://visitboise.com/play/outdoor/fishing/ → no permissions-policy
- https://visitboise.com/play/outdoor/golf/ → no permissions-policy
- FoundCookie flagsMedium
9 of 9 cookies are missing protective flags. Without HttpOnly a script can read the cookie; without Secure it travels over plain HTTP; without SameSite it is sent on cross-site requests.
- wordpress_test_cookie (set by https://visitboise.com/wp-login.php?redirect_to=https%3A%2F%2Fwww.visitboise.co…) lacks SameSite
- wordpress_4ffa2e32dc26d27e19a588f2d28580bd (set by https://visitboise.com/wp-login.php?redirect_to=https%3A%2F%2Fwww.visitboise.co…) lacks Secure, HttpOnly, SameSite
- wordpress_sec_4ffa2e32dc26d27e19a588f2d28580bd (set by https://visitboise.com/wp-login.php?redirect_to=https%3A%2F%2Fwww.visitboise.co…) lacks Secure, HttpOnly, SameSite
- wordpress_logged_in_4ffa2e32dc26d27e19a588f2d28580bd (set by https://visitboise.com/wp-login.php?redirect_to=https%3A%2F%2Fwww.visitboise.co…) lacks Secure, HttpOnly, SameSite
- wp-settings-0 (set by https://visitboise.com/wp-login.php?redirect_to=https%3A%2F%2Fwww.visitboise.co…) lacks Secure, HttpOnly, SameSite
- wp-settings-time-0 (set by https://visitboise.com/wp-login.php?redirect_to=https%3A%2F%2Fwww.visitboise.co…) lacks Secure, HttpOnly, SameSite
- wordpressuser_4ffa2e32dc26d27e19a588f2d28580bd (set by https://visitboise.com/wp-login.php?redirect_to=https%3A%2F%2Fwww.visitboise.co…) lacks Secure, HttpOnly, SameSite
- wordpresspass_4ffa2e32dc26d27e19a588f2d28580bd (set by https://visitboise.com/wp-login.php?redirect_to=https%3A%2F%2Fwww.visitboise.co…) lacks Secure, HttpOnly, SameSite
- wp-postpass_4ffa2e32dc26d27e19a588f2d28580bd (set by https://visitboise.com/wp-login.php?redirect_to=https%3A%2F%2Fwww.visitboise.co…) lacks Secure, HttpOnly, SameSite
- FoundVulnerable JavaScript librariesMedium
1 library with published vulnerabilities: jQuery 3.1.2. Whether they are exploitable depends on how the site uses them, but each has a fixed release.
- jQuery 3.1.2 in https://visitboise.com/wp-content/plugins/gravityforms/js/placeholders.jquery.m…: 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…kY (39 chars) in https://visitboise.com/play/outdoor/: 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 3 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.)
- maps.googleapis.com (3 script tags)
- explore.visitboise.com (3 script tags)
- elements.playeasy.com (1 script tag)
7 checks passed
- OKHTTPS
All 500 crawled pages were served over HTTPS.
- OKContent Security Policy
A Content-Security-Policy is set on 3 of 500 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
74 forms found, all on HTTPS pages posting to HTTPS addresses.
- 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.
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.
Earlier scans of visitboise.com
No other scans of this site yet.
Sites scoring near visitboise.com
Their neighbours in the SEO rank table, which orders every scanned site by health score.
- www.whalencpa.com74/100 · rank 1253 · 2,627 pages
- givens.ca74/100 · rank 1253 · 137 pages
- sagecreekmassagetherapy.ca74/100 · rank 1253 · 53 pages
- www.timetocare.ca74/100 · rank 1253 · 114 pages
- www.jvftransport.com74/100 · rank 1253 · 5 pages
- lan-farms.com74/100 · rank 1253 · 19 pages
This report was produced by the DIY SEO Hub Site Spider crawling visitboise.com from its pages as published, the way a search engine does. It shows summary figures only.
Own visitboise.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 visitboise.com. Removal needs no account and no proof of purchase.