Scanned sites / www.projectlandscape.ca

SEO report for www.projectlandscape.ca DR 37

The latest Site Spider scan of www.projectlandscape.ca, with 2 scans on record. Each scan is at its own address, for example /domain/www-projectlandscape-ca/2026-10-02-2047.

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

Latest scan

Scanned 2026-10-02 20:47:18 UTC, finished 2026-10-02 23:46:26 UTC. Found on page 1 of brave web search results

Site: https://www.projectlandscape.ca/

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

81/ 100Good

On October 2, 2026 the Site Spider crawled 270 pages and 1079 assets of www.projectlandscape.ca, starting from https://www.projectlandscape.ca/. It scored 81 out of 100, a good result. 8 of 27 checks found something to fix, led by heavy assets (19), sitemap coverage (226), title tags (90); 10 checks passed. Most of the points went to heavy assets (−6), sitemap coverage (−5.6), title tags (−3.7). 9 checks found something the score does not count, listed as noted. 10 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: Medium1 medium, 2 low and 1 info findings. See the security findings ↓

Pages crawled
270
Assets fetched
1079
Status
Completed
Checks with issues
8 of 27
CoverageJob finished, partial coverage

1,349 of 1,350 discovered URLs were fetched, 2,323 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. 120 link destinations on other sites were checked.

  • Title tags90 issues
    90 of 226 pages have title issues. 15 noindex or canonicalized pages excluded.
    −3.7 points
  • Meta descriptions38 issues
    38 of 226 pages have meta description issues. 15 noindex or canonicalized pages excluded.
    −1.3 points
  • Headings14 issues
    14 of 226 pages have heading issues. 15 noindex or canonicalized pages excluded.
    −0.3 points
  • Broken linksOK
    0 internal links point at 0 broken URLs.
  • Links to other sites9 issues
    9 destinations answered with an error, 29 could not be determined (timeouts, rate limits or refusals), of 120 destinations checked.
    −1.5 points
  • Redirects29 issues
    30 redirecting URLs, 0 of them chained.
    −0.5 points
  • Non-200 responses30 noted
    30 URLs did not return a 2xx response. 29 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.
  • Indexability5 issues
    5 of 230 indexable pages have indexability warnings. 11 pages noindex by design.
    −0.2 points
  • Image alt textOK
    0 of 514 image references have no alt attribute. 2 use an empty alt (decorative), which is fine.
  • Heavy assets19 issues
    19 assets larger than 500 KB among 1079 fetched assets.
    −6 points
  • Orphan pagesOK
    0 pages have no internal links pointing at them.
  • Sitemap coverage226 issues
    1 sitemap listing 0 URLs: 226 crawled pages missing, 0 listed URLs broken or redirecting, 0 reachable only via the sitemap.
    −5.6 points
  • Internal link counts96 noted
    Internal link counts for 241 pages; 96 worth a look.
  • Thin contentOK
    0 of 226 pages have fewer than 200 words. 15 noindex or canonicalized pages excluded.
  • Duplicate contentOK
    0 groups of pages with identical HTML.
  • URL formatOK
    All 270 page URLs are plain lowercase addresses without parameters.
  • Canonicals15 noted
    15 of 241 pages have a canonical worth checking.
  • Robots directives241 noted
    241 pages carry a robots directive; 0 carry none.
  • Anchor text20 noted
    20 destinations are linked without useful anchor text, or with nofollow.
  • Title and heading structure32 noted
    32 of 226 pages could use the title, heading and snippet space better. 15 noindex or canonicalized pages excluded.
  • Image weight and alt length30 noted
    30 images over 100 KB; 0 with alt text over 100 characters.
  • Response anomalies5 noted
    5 URLs answered in a way worth looking at.
  • HTML and head validationNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.
  • hreflangNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.
  • Structured dataNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.
  • Near duplicatesNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.
  • Soft 404sOK
    None of 241 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 positionsNot checked
    Not checked: this scan was crawled before link positions were recorded. Scan the site again to run it.
  • PaginationNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.
  • Headers and cookiesOK
    0 cookies set by the site; 14 response headers recorded across 1349 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 241 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 Insights5 noted
    Mobile performance 64 on average across 5 pages; 5 below Google's good thresholds.
  • SpellingNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.

What changed since the last scan

Score unchanged

www.projectlandscape.ca scored 81 out of 100 in both of its last two scans. That is a steady score, not an unchanged site: 102 findings changed between the two scans. The two crawls did not cover the same ground, so part of the difference is coverage rather than change. 713 URLs the earlier crawl reached were not reached this time. The crawl reached 4 more pages than last time, 270 in total, so some of the change is a change in what was crawled.

  • Pages: 4 new
  • Internal links to the page: 76 changed
  • Crawl depth: 22 changed
  • 713 URLs from the earlier crawl were not reached this time
  • Crawl coverage differed between the two scans; some differences may be coverage rather than change
  1. 2026-09-12 11:12:03 UTC81/100266 pages
  2. 2026-10-02 20:47:18 UTC81/100270 pages

Where this site sits among all scanned sites

2332 sites, median 79%, average 78%

www.projectlandscape.ca scores 81%, higher than 55% of the 2332 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%: 6 sites50%: 5 sites51%: 5 sites52%: 10 sites53%: 7 sites54%: 8 sites55%: 9 sites56%: 8 sites57%: 12 sites58%: 17 sites59%: 9 sites60%: 16 sites61%: 12 sites62%: 19 sites63%: 27 sites64%: 22 sites65%: 31 sites66%: 35 sites67%: 35 sites68%: 34 sites69%: 47 sites70%: 44 sites71%: 70 sites72%: 71 sites73%: 69 sites74%: 68 sites75%: 72 sites76%: 87 sites77%: 92 sites78%: 106 sites79%: 85 sites80%: 107 sites81%: 105 sites82%: 115 sites83%: 99 sites84%: 106 sites85%: 86 sites86%: 70 sites87%: 75 sites88%: 58 sites89%: 64 sites90%: 34 sites91%: 47 sites92%: 38 sites93%: 24 sites94%: 16 sites95%: 12 sites96%: 11 sites97%: 12 sites98%: 4 sites99%: 2 sites100%: 69 sites81% 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

Written from an earlier version of the analysis (rules v4). 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 website has good health but needs some improvements. Focus on fixing redirect issues, enhancing titles, improving meta descriptions, addressing heading problems, and fixing sitemap coverage.

  1. 1

    Fix Redirects

    Why: 30 URLs redirect, potentially affecting user experience and SEO.

    How: Update links to direct to the final URL instead of the redirected ones.

    Checks: redirects

  2. 2

    Enhance Title Tags

    Why: 90 pages have title issues, impacting CTR and SEO ranking.

    How: Revise titles to keep under 60 characters and ensure they are descriptive.

    Checks: titles

  3. 3

    Improve Meta Descriptions

    Why: 38 pages have issues, limiting search visibility.

    How: Rewrite meta descriptions to be concise and under 155 characters.

    Checks: meta-descriptions

  4. 5

    Update Sitemap Coverage

    Why: 226 pages are not listed in the sitemap, reducing indexability.

    How: Generate an updated sitemap including all crawled and indexable pages.

    Checks: sitemap-coverage

  5. 6

    Compress Heavy Assets

    Why: 19 assets are larger than 500 KB, slowing page load times.

    How: Optimize images using compression tools or reconsider their usage on pages.

    Evidence: 1.1 MB of image, loaded by 63 pages, so every visitor to any of them downloads it.

    63 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

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 lacks critical security headers that protect against various attacks, including script injection. It also discloses server software versions, which can aid attackers. Immediate implementation of security headers and version hiding is recommended for better protection.

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

    Missing Content Security PolicyMedium

    Why it matters: No Content Security Policy adds risk of XSS attacks, as scripts can load from any source.

    Fix: Add a 'Content-Security-Policy' header with a restrictive policy, e.g., "default-src 'self'; script-src 'self';".

    Evidence: Content Security Policy

  2. 2

    Missing Referrer PolicyLow

    Why it matters: Absence of referrer policy exposes full URLs to external sites, risking data leakage.

    Fix: Set a 'Referrer-Policy' header, e.g., 'no-referrer'.

    Evidence: Referrer policy

  3. 3

    Server Version DisclosureLow

    Why it matters: Revealing server versions may help attackers exploit known vulnerabilities.

    Fix: Remove or change 'X-Powered-By' header to hide version info, or set it to a generic value.

    Evidence: Software version disclosure

  4. 4

    Missing Permissions PolicyInfo

    Why it matters: Not using a Permissions Policy can allow attackers to misuse browser APIs if they inject scripts.

    Fix: Include a 'Permissions-Policy' header, e.g., 'geolocation=(self)' to restrict API access.

    Evidence: Permissions policy

What the checks found

  • FoundContent Security PolicyMedium

    None of the 241 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.projectlandscape.ca/ → no content-security-policy
    • https://www.projectlandscape.ca/contact/ → no content-security-policy
    • https://www.projectlandscape.ca/residential-services/hardscaping/ → no content-security-policy
    • https://www.projectlandscape.ca/residential-services/landscape-construction/patio-surfaces/ → no content-security-policy
    • https://www.projectlandscape.ca/paver-sealing-refresh-program/ → no content-security-policy
    • https://www.projectlandscape.ca/retaining-walls/ → no content-security-policy
    • https://www.projectlandscape.ca/residential-services/outdoor-living/garden-walls/ → no content-security-policy
    • https://www.projectlandscape.ca/residential-services/hardscaping/garden-bed-edging/ → no content-security-policy
    • https://www.projectlandscape.ca/concrete-curbing/ → no content-security-policy
    • https://www.projectlandscape.ca/staircases-stepping-stones/ → no content-security-policy
    • https://www.projectlandscape.ca/residential-services/landscape-construction/seating/ → no content-security-policy
    • https://www.projectlandscape.ca/residential-services/hardscaping/water-management/ → no content-security-policy
  • 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.projectlandscape.ca/ → no referrer-policy
    • https://www.projectlandscape.ca/contact/ → no referrer-policy
    • https://www.projectlandscape.ca/residential-services/hardscaping/ → no referrer-policy
    • https://www.projectlandscape.ca/residential-services/landscape-construction/patio-surfaces/ → no referrer-policy
    • https://www.projectlandscape.ca/paver-sealing-refresh-program/ → no referrer-policy
    • https://www.projectlandscape.ca/retaining-walls/ → no referrer-policy
    • https://www.projectlandscape.ca/residential-services/outdoor-living/garden-walls/ → no referrer-policy
    • https://www.projectlandscape.ca/residential-services/hardscaping/garden-bed-edging/ → no referrer-policy
    • https://www.projectlandscape.ca/concrete-curbing/ → no referrer-policy
    • https://www.projectlandscape.ca/staircases-stepping-stones/ → no referrer-policy
    • https://www.projectlandscape.ca/residential-services/landscape-construction/seating/ → no referrer-policy
    • https://www.projectlandscape.ca/residential-services/hardscaping/water-management/ → 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.projectlandscape.ca/ → no permissions-policy
    • https://www.projectlandscape.ca/contact/ → no permissions-policy
    • https://www.projectlandscape.ca/residential-services/hardscaping/ → no permissions-policy
    • https://www.projectlandscape.ca/residential-services/landscape-construction/patio-surfaces/ → no permissions-policy
    • https://www.projectlandscape.ca/paver-sealing-refresh-program/ → no permissions-policy
    • https://www.projectlandscape.ca/retaining-walls/ → no permissions-policy
    • https://www.projectlandscape.ca/residential-services/outdoor-living/garden-walls/ → no permissions-policy
    • https://www.projectlandscape.ca/residential-services/hardscaping/garden-bed-edging/ → no permissions-policy
    • https://www.projectlandscape.ca/concrete-curbing/ → no permissions-policy
    • https://www.projectlandscape.ca/staircases-stepping-stones/ → no permissions-policy
    • https://www.projectlandscape.ca/residential-services/landscape-construction/seating/ → no permissions-policy
    • https://www.projectlandscape.ca/residential-services/hardscaping/water-management/ → 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.

    • x-powered-by: PHP/7.4.33 (272 responses)
    • x-powered-by: WP Rocket/3.18.1.3 (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.)

    • www.googletagmanager.com (40 script tags)
  • NoteSensitive paths in robots.txt

    robots.txt lists 2 paths 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/
    • Disallow: /login/
9 checks passed, 1 not applicable
  • OKHTTPS

    All 241 crawled pages were served over HTTPS.

  • OKHTTP Strict Transport Security

    strict-transport-security is set on all 241 HTML pages.

  • OKClickjacking protection

    x-frame-options is set on all 241 HTML pages.

  • OKMIME sniffing protection

    x-content-type-options is set on all 241 HTML pages.

  • OKMixed content

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

  • OKForms over HTTPS

    42 forms found, all on HTTPS pages posting to HTTPS addresses.

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

  • Not applicableCookie flags

    The crawl set no cookies, so there are no cookie flags to check.

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 www.projectlandscape.ca

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

Own www.projectlandscape.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.projectlandscape.ca. Removal needs no account and no proof of purchase.