Scanned sites / www.valleylandscape.ca / 2026-11-03-0912

www.valleylandscape.ca scan from 2026-11-03 09:12:20 UTC DR 0

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

Scan 2026-11-03-0912

Scanned 2026-11-03 09:12:20 UTC, finished 2026-11-04 05:10:58 UTC. Found on page 3 of brave web search results

Site: https://www.valleylandscape.ca/

Download SQLite databaseEvery page and asset from this scan, with the crawl events, in one file.

69/ 100Needs work

On November 3, 2026 the Site Spider crawled 15 pages and 341 assets of www.valleylandscape.ca, starting from https://www.valleylandscape.ca/. It scored 69 out of 100, a result that needs work. 6 of 33 checks found something to fix, led by title tags (13), meta descriptions (13), heavy assets (40); 18 checks passed. Most of the points went to title tags (−10), meta descriptions (−8), headings (−6). 9 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: Medium3 medium, 4 low and 1 info findings. See the security findings ↓

Pages crawled
15
Assets fetched
341
Status
Completed
Checks with issues
6 of 33
CoverageComplete crawl

356 of 356 discovered URLs were fetched. The crawl reached everything it found. HTML only: nothing here ran JavaScript. 2 link destinations on other sites were checked.

  • Title tags13 issues
    13 of 13 pages have title issues.
    −10 points
  • Meta descriptions13 issues
    13 of 13 pages have meta description issues.
    −8 points
  • Headings13 issues
    13 of 13 pages have heading issues.
    −6 points
  • Broken linksOK
    0 internal links point at 0 broken URLs.
  • Links to other sites1 noted
    0 destinations answered with an error, 1 could not be determined (timeouts, rate limits or refusals), of 2 destinations checked.
  • Redirects3 noted
    3 redirecting URLs, 0 of them chained.
  • Non-200 responses7 noted
    7 URLs did not return a 2xx response. 2 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 13 indexable pages have indexability warnings.
  • Image alt textOK
    0 of 143 image references have no alt attribute. 128 use an empty alt (decorative), which is fine.
  • Heavy assets40 issues
    40 assets larger than 500 KB among 341 fetched assets.
    −6 points
  • Orphan pagesOK
    0 pages have no internal links pointing at them.
  • Sitemap coverage2 issues
    3 sitemaps listing 15 URLs: 0 crawled pages missing, 2 listed URLs broken or redirecting, 0 reachable only via the sitemap.
    −0.9 points
  • Internal link countsOK
    Internal link counts for 13 pages; none is a dead end or buried.
  • Thin content1 issue
    1 of 13 pages have fewer than 200 words.
    −0.6 points
  • Duplicate contentOK
    0 groups of pages with identical HTML.
  • URL formatOK
    All 15 page URLs are plain lowercase addresses without parameters.
  • CanonicalsOK
    0 of 13 pages have a canonical worth checking.
  • Robots directives13 noted
    13 pages carry a robots directive; 0 carry none.
  • Anchor text6 noted
    6 destinations are linked without useful anchor text, or with nofollow.
  • Title and heading structureOK
    0 of 13 pages could use the title, heading and snippet space better.
  • Image weight and alt length65 noted
    65 images over 100 KB; 0 with alt text over 100 characters.
  • Response anomaliesOK
    No redirect loops, header redirects or pages served as something other than HTML.
  • HTML and head validationOK
    All 13 pages keep their head tags in <head>, once each, under Googlebot's 2 MB.
  • hreflangOK
    No page declares hreflang.
  • Structured dataOK
    13 of 13 indexable pages carry structured data: WPHeader (13), WPFooter (13). 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 13 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 positions2 noted
    2 of 13 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; 12 response headers recorded across 356 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 13 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.
  • Spelling32 noted
    32 words an English dictionary does not know, on 8 pages. Product names and jargon will appear here too.

Where this scan sits among all scanned sites

2839 sites, median 80%, average 79%

www.valleylandscape.ca scores 69%, higher than 14% of the 2839 scanned sites. See the full ranking.

0721430%: 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%: 0 sites34%: 0 sites35%: 2 sites36%: 1 site37%: 1 site38%: 3 sites39%: 2 sites40%: 3 sites41%: 1 site42%: 2 sites43%: 3 sites44%: 2 sites45%: 6 sites46%: 5 sites47%: 5 sites48%: 6 sites49%: 8 sites50%: 6 sites51%: 6 sites52%: 8 sites53%: 9 sites54%: 9 sites55%: 9 sites56%: 8 sites57%: 16 sites58%: 18 sites59%: 10 sites60%: 15 sites61%: 13 sites62%: 20 sites63%: 29 sites64%: 21 sites65%: 33 sites66%: 42 sites67%: 42 sites68%: 42 sites69%: 52 sites70%: 46 sites71%: 79 sites72%: 76 sites73%: 81 sites74%: 79 sites75%: 87 sites76%: 96 sites77%: 108 sites78%: 129 sites79%: 112 sites80%: 125 sites81%: 123 sites82%: 132 sites83%: 121 sites84%: 129 sites85%: 107 sites86%: 94 sites87%: 95 sites88%: 79 sites89%: 74 sites90%: 54 sites91%: 57 sites92%: 42 sites93%: 28 sites94%: 25 sites95%: 14 sites96%: 17 sites97%: 15 sites98%: 7 sites99%: 3 sites100%: 143 sites69% 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

The website has several critical SEO issues that need addressing to improve its health score. Prioritizing these fixes will enhance search visibility and user experience.

  1. 1

    Fix Title Tag Issues

    Why: All pages have problem title tags that affect SEO.

    How: Shorten title tags to under 60 characters and ensure they are unique for each page.

    Checks: titles

  2. 2

    Add Meta Descriptions

    Why: Missing meta descriptions can lower click-through rates.

    How: Write compelling meta descriptions for each page using relevant keywords, keeping them under 160 characters.

    Checks: meta-descriptions

  3. 3

    Add H1 Tags

    Why: All pages lack proper H1 tags which are important for SEO.

    How: Ensure each page has one clear H1 that describes the content accurately.

    Checks: headings

  4. 4

    Resolve Non-200 Response URLs

    Why: Two pages return a 301 status, impacting page accessibility and SEO.

    How: Redirect the outdated URLs to relevant pages or fix the links in the sitemap.

    Checks: status-codes

  5. 5

    Shrink Heavy Assets

    Why: Large assets can slow down page loading speeds.

    How: Compress images and scripts over 500 KB and consider removing unnecessary files.

    Evidence: 314 KB of script, loaded by 13 pages, so every visitor to any of them downloads it.

    13 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

    Fix Sitemap Issues

    Why: Redirects in the sitemap can confuse search engine crawlers.

    How: Update the sitemap to contain only valid URLs and check that no URL in the sitemap redirects.

    Checks: sitemap-coverage

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

The site www.valleylandscape.ca has several missing security headers that could expose it to various vulnerabilities. Most critical are the lack of HSTS, CSP, and X-Frame-Options, which help protect against protocol downgrades and clickjacking attacks. Implementing these headers is essential to bolster the site’s security.

  • 0 high
  • 3 medium
  • 4 low
  • 1 info
  1. 1

    Missing HTTP Strict Transport Security (HSTS)Medium

    Why it matters: Without HSTS, an attacker can intercept data during initial HTTP requests.

    Fix: Add the header: "Strict-Transport-Security: max-age=31536000; includeSubDomains".

    Evidence: HTTP Strict Transport Security

  2. 2

    Missing Content Security Policy (CSP)Medium

    Why it matters: Lack of a CSP allows uncontrolled loading of scripts which can lead to cross-site scripting (XSS) attacks.

    Fix: Add the header: "Content-Security-Policy: default-src 'self';".

    Evidence: Content Security Policy

  3. 3

    Missing X-Frame-Options HeaderMedium

    Why it matters: Without this protection, the site is vulnerable to clickjacking attacks.

    Fix: Add the header: "X-Frame-Options: DENY".

    Evidence: Clickjacking protection

  4. 4

    Missing X-Content-Type-Options HeaderLow

    Why it matters: Lack of this header can lead to MIME sniffing and executing malicious files.

    Fix: Add the header: "X-Content-Type-Options: nosniff".

    Evidence: MIME sniffing protection

  5. 5

    Missing Referrer-Policy HeaderLow

    Why it matters: Without a referrer policy, sensitive URL information may be shared with external sites.

    Fix: Add the header: "Referrer-Policy: no-referrer".

    Evidence: Referrer policy

  6. 6

    Disclosure of Server VersionLow

    Why it matters: Revealing server details can aid attackers in exploiting known vulnerabilities.

    Fix: Consider using a reverse proxy or configuring the server to remove version information.

    Evidence: Software version disclosure

  7. 7

    Third-party Scripts Without Subresource IntegrityLow

    Why it matters: Compromised third-party scripts can alter site behavior maliciously.

    Fix: Implement Subresource Integrity where possible or use a Content-Security-Policy to allow only trusted sources.

    Evidence: Third-party scripts

  8. 8

    No Permissions Policy SetInfo

    Why it matters: Absence of a Permissions Policy may allow unnecessary access to browser features.

    Fix: Add the header: "Permissions-Policy: geolocation=(self), microphone=()".

    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.valleylandscape.ca/ → no strict-transport-security
    • https://www.valleylandscape.ca/about-valley/ → no strict-transport-security
    • https://www.valleylandscape.ca/our-approach/ → no strict-transport-security
    • https://www.valleylandscape.ca/projects/ → no strict-transport-security
    • https://www.valleylandscape.ca/projects/oem-manufacturing/ → no strict-transport-security
    • https://www.valleylandscape.ca/projects/saskatchewan-drive-oasis/ → no strict-transport-security
    • https://www.valleylandscape.ca/contact/ → no strict-transport-security
    • https://www.valleylandscape.ca/projects/project-1/ → no strict-transport-security
    • https://www.valleylandscape.ca/projects/project-2/ → no strict-transport-security
    • https://www.valleylandscape.ca/projects/project-3/ → no strict-transport-security
    • https://www.valleylandscape.ca/projects/project-4/ → no strict-transport-security
    • https://www.valleylandscape.ca/projects/project-5/ → no strict-transport-security
  • FoundContent Security PolicyMedium

    None of the 13 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.valleylandscape.ca/ → no content-security-policy
    • https://www.valleylandscape.ca/about-valley/ → no content-security-policy
    • https://www.valleylandscape.ca/our-approach/ → no content-security-policy
    • https://www.valleylandscape.ca/projects/ → no content-security-policy
    • https://www.valleylandscape.ca/projects/oem-manufacturing/ → no content-security-policy
    • https://www.valleylandscape.ca/projects/saskatchewan-drive-oasis/ → no content-security-policy
    • https://www.valleylandscape.ca/contact/ → no content-security-policy
    • https://www.valleylandscape.ca/projects/project-1/ → no content-security-policy
    • https://www.valleylandscape.ca/projects/project-2/ → no content-security-policy
    • https://www.valleylandscape.ca/projects/project-3/ → no content-security-policy
    • https://www.valleylandscape.ca/projects/project-4/ → no content-security-policy
    • https://www.valleylandscape.ca/projects/project-5/ → 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.valleylandscape.ca/ → no x-frame-options
    • https://www.valleylandscape.ca/about-valley/ → no x-frame-options
    • https://www.valleylandscape.ca/our-approach/ → no x-frame-options
    • https://www.valleylandscape.ca/projects/ → no x-frame-options
    • https://www.valleylandscape.ca/projects/oem-manufacturing/ → no x-frame-options
    • https://www.valleylandscape.ca/projects/saskatchewan-drive-oasis/ → no x-frame-options
    • https://www.valleylandscape.ca/contact/ → no x-frame-options
    • https://www.valleylandscape.ca/projects/project-1/ → no x-frame-options
    • https://www.valleylandscape.ca/projects/project-2/ → no x-frame-options
    • https://www.valleylandscape.ca/projects/project-3/ → no x-frame-options
    • https://www.valleylandscape.ca/projects/project-4/ → no x-frame-options
    • https://www.valleylandscape.ca/projects/project-5/ → 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://www.valleylandscape.ca/ → no x-content-type-options
    • https://www.valleylandscape.ca/about-valley/ → no x-content-type-options
    • https://www.valleylandscape.ca/our-approach/ → no x-content-type-options
    • https://www.valleylandscape.ca/projects/ → no x-content-type-options
    • https://www.valleylandscape.ca/projects/oem-manufacturing/ → no x-content-type-options
    • https://www.valleylandscape.ca/projects/saskatchewan-drive-oasis/ → no x-content-type-options
    • https://www.valleylandscape.ca/contact/ → no x-content-type-options
    • https://www.valleylandscape.ca/projects/project-1/ → no x-content-type-options
    • https://www.valleylandscape.ca/projects/project-2/ → no x-content-type-options
    • https://www.valleylandscape.ca/projects/project-3/ → no x-content-type-options
    • https://www.valleylandscape.ca/projects/project-4/ → no x-content-type-options
    • https://www.valleylandscape.ca/projects/project-5/ → no x-content-type-options
  • FoundReferrer policyLow

    No HTML page sends 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://www.valleylandscape.ca/ → no referrer-policy
    • https://www.valleylandscape.ca/about-valley/ → no referrer-policy
    • https://www.valleylandscape.ca/our-approach/ → no referrer-policy
    • https://www.valleylandscape.ca/projects/ → no referrer-policy
    • https://www.valleylandscape.ca/projects/oem-manufacturing/ → no referrer-policy
    • https://www.valleylandscape.ca/projects/saskatchewan-drive-oasis/ → no referrer-policy
    • https://www.valleylandscape.ca/contact/ → no referrer-policy
    • https://www.valleylandscape.ca/projects/project-1/ → no referrer-policy
    • https://www.valleylandscape.ca/projects/project-2/ → no referrer-policy
    • https://www.valleylandscape.ca/projects/project-3/ → no referrer-policy
    • https://www.valleylandscape.ca/projects/project-4/ → no referrer-policy
    • https://www.valleylandscape.ca/projects/project-5/ → 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://www.valleylandscape.ca/ → no permissions-policy
    • https://www.valleylandscape.ca/about-valley/ → no permissions-policy
    • https://www.valleylandscape.ca/our-approach/ → no permissions-policy
    • https://www.valleylandscape.ca/projects/ → no permissions-policy
    • https://www.valleylandscape.ca/projects/oem-manufacturing/ → no permissions-policy
    • https://www.valleylandscape.ca/projects/saskatchewan-drive-oasis/ → no permissions-policy
    • https://www.valleylandscape.ca/contact/ → no permissions-policy
    • https://www.valleylandscape.ca/projects/project-1/ → no permissions-policy
    • https://www.valleylandscape.ca/projects/project-2/ → no permissions-policy
    • https://www.valleylandscape.ca/projects/project-3/ → no permissions-policy
    • https://www.valleylandscape.ca/projects/project-4/ → no permissions-policy
    • https://www.valleylandscape.ca/projects/project-5/ → 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: nginx/1.31.8 (356 responses)
    • x-powered-by: WP Rocket/3.13.1 (1 response)
  • NoteThird-party scripts

    Scripts run from 1 other domain 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.)

    • static.elfsight.com (13 script tags)
6 checks passed, 2 not applicable
  • OKHTTPS

    All 13 crawled pages were served over HTTPS.

  • OKMixed content

    No HTTPS page loads a script, stylesheet, font or image over plain HTTP.

  • OKVulnerable JavaScript libraries

    2 library versions recognised, none with known vulnerabilities.

  • OKKeys and secrets in page code

    No API keys, tokens or private keys were found in the sampled HTML and scripts.

  • 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.valleylandscape.ca

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.valleylandscape.ca from its pages as published, the way a search engine does. It shows summary figures only.

Own www.valleylandscape.ca?

  • 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.valleylandscape.ca. Removal needs no account and no proof of purchase.