Scanned sites / capitollandscape.com / 2026-09-13-0337

capitollandscape.com scan from 2026-09-13 03:37:17 UTC DR 11

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

Scan 2026-09-13-0337

Scanned 2026-09-13 03:37:17 UTC, finished 2026-09-13 04:40:18 UTC. Found on page 3 of brave web search results

Site: https://capitollandscape.com/

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

61/ 100Needs work

On September 13, 2026 the Site Spider crawled 176 pages and 1118 assets of capitollandscape.com, starting from https://capitollandscape.com/. It scored 61 out of 100, a result that needs work. 12 of 27 checks found something to fix, led by indexability (133), meta descriptions (140), thin content (139); 7 checks passed. Most of the points went to indexability (−9), meta descriptions (−7.6), thin content (−7.5). 8 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: Medium2 medium, 1 low and 1 info findings. See the security findings ↓

Pages crawled
176
Assets fetched
1118
Status
Completed
Checks with issues
12 of 27
CoverageJob finished, partial coverage

1,294 of 1,294 discovered URLs were fetched, 183 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. 2 link destinations on other sites were checked.

  • Title tags95 issues
    95 of 145 pages have title issues. 3 noindex or canonicalized pages excluded.
    −6.4 points
  • Meta descriptions140 issues
    140 of 145 pages have meta description issues. 3 noindex or canonicalized pages excluded.
    −7.6 points
  • Headings1 issue
    1 of 145 pages have heading issues. 3 noindex or canonicalized pages excluded.
  • Broken links6 issues
    6 internal links point at 6 broken URLs.
    −0.8 points
  • Links to other sites148 noted
    0 destinations answered with an error, 1 could not be determined (timeouts, rate limits or refusals), of 2 destinations checked.
  • Redirects22 issues
    156 redirecting URLs, 0 of them chained.
    −0.6 points
  • Non-200 responses6 issues
    209 URLs did not return a 2xx response. 28 of them are pages, 6 with an error status; the rest are assets or redirects.
    −0.4 points
  • Rate limitedOK
    The site did not rate limit the crawler.
  • Indexability133 issues
    133 of 145 indexable pages have indexability warnings. 3 pages noindex by design. 3 noindex pages are listed in the sitemap, which asks search engines both to visit and to ignore them.
    −9 points
  • Image alt text6 issues
    6 of 508 image references have no alt attribute. 200 use an empty alt (decorative), which is fine.
    −0.1 points
  • Heavy assets20 issues
    20 assets larger than 500 KB among 1118 fetched assets.
    −6 points
  • Orphan pages9 issues
    9 pages have no internal links pointing at them.
    −0.2 points
  • Sitemap coverage12 issues
    6 sitemaps listing 148 URLs: 0 crawled pages missing, 0 listed URLs broken or redirecting, 9 reachable only via the sitemap.
    −0.5 points
  • Internal link countsOK
    Internal link counts for 148 pages; none is a dead end or buried.
  • Thin content139 issues
    139 of 145 pages have fewer than 200 words. 3 noindex or canonicalized pages excluded.
    −7.5 points
  • Duplicate contentOK
    0 groups of pages with identical HTML.
  • URL format46 noted
    46 of 176 page URLs are harder to read, share or cache than they need to be.
  • Canonicals130 noted
    130 of 148 pages have a canonical worth checking.
  • Robots directives3 noted
    3 pages carry a robots directive; 145 carry none.
  • Anchor text150 noted
    150 destinations are linked without useful anchor text, or with nofollow.
  • Title and heading structure141 noted
    141 of 145 pages could use the title, heading and snippet space better. 3 noindex or canonicalized pages excluded.
  • Image weight and alt length113 noted
    113 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 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 148 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 1294 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 148 pages; 142 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 58 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.

Where this scan sits among all scanned sites

2867 sites, median 80%, average 79%

capitollandscape.com scores 61%, higher than 6% of the 2867 scanned sites. See the full ranking.

0751490%: 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%: 7 sites52%: 8 sites53%: 9 sites54%: 9 sites55%: 9 sites56%: 8 sites57%: 17 sites58%: 18 sites59%: 10 sites60%: 15 sites61%: 13 sites62%: 20 sites63%: 29 sites64%: 22 sites65%: 33 sites66%: 43 sites67%: 42 sites68%: 42 sites69%: 52 sites70%: 46 sites71%: 79 sites72%: 76 sites73%: 81 sites74%: 82 sites75%: 87 sites76%: 95 sites77%: 109 sites78%: 132 sites79%: 111 sites80%: 128 sites81%: 124 sites82%: 132 sites83%: 119 sites84%: 131 sites85%: 105 sites86%: 96 sites87%: 95 sites88%: 80 sites89%: 76 sites90%: 55 sites91%: 58 sites92%: 43 sites93%: 29 sites94%: 25 sites95%: 15 sites96%: 17 sites97%: 16 sites98%: 7 sites99%: 3 sites100%: 149 sites61% 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. 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.

Several issues need addressing to enhance site SEO, particularly regarding broken links, redirects, and meta tags. Focus on high-impact changes first.

  1. 1

    Fix Broken Links

    Why: Resolve 6 broken internal links to improve user experience and prevent loss of SEO value.

    How: Update or remove the broken URLs identified in the crawl.

    Checks: broken-links

  2. 2

    Resolve Non-200 Responses

    Why: 209 URLs return non-200 responses, impacting site accessibility and SEO rankings.

    How: Check each URL and ensure they return a proper 200 status or redirect appropriately.

    Checks: status-codes

  3. 3

    Optimize Title Tags

    Why: 95 pages have title issues; optimizing them will improve search visibility.

    How: Rewrite title tags to be unique, descriptive, and between 30-60 characters.

    Checks: titles

  4. 4

    Correct Meta Descriptions

    Why: 140 pages have missing or problematic meta descriptions, affecting click-through rates.

    How: Add unique, concise meta descriptions (150-160 characters) to each page.

    Checks: meta-descriptions

  5. 5

    Add H1 Tags

    Why: The homepage is missing an H1 tag, crucial for content hierarchy.

    How: Ensure each page, especially the homepage, has a single, relevant H1 tag.

    Checks: headings

  6. 6

    Address Indexability Issues

    Why: 130 pages have indexability warnings; resolving these will improve search engine access.

    How: Identify pages needing canonical tags or other adjustments to enhance crawling.

    Checks: indexability

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 security review for capitollandscape.com highlights several important areas for improvement. A lack of a Content Security Policy increases the risk of cross-site scripting attacks. Additionally, the use of a vulnerable version of jQuery presents further security concerns. It is recommended to implement necessary headers and update libraries to mitigate these risks.

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

    Missing Content Security PolicyMedium

    Why it matters: Without a Content Security Policy, the site is vulnerable to various attacks, including cross-site scripting.

    Fix: Add a Content-Security-Policy header in your server settings to restrict content sources, like 'default-src 'self';'.

    Evidence: Content Security Policy

  2. 2

    Vulnerable JavaScript LibraryMedium

    Why it matters: The site uses jQuery 2.4.24, which has known vulnerabilities that could be exploited depending on site usage.

    Fix: Upgrade jQuery to version 3.5.0 or later to mitigate these vulnerabilities.

    Evidence: Vulnerable JavaScript libraries

  3. 3

    Third-party Scripts Lack Integrity ChecksLow

    Why it matters: Scripts run from external domains without Subresource Integrity can be compromised, potentially affecting your site.

    Fix: Implement Subresource Integrity for third-party scripts or use a Content-Security-Policy that includes these sources.

    Evidence: Third-party scripts

  4. 4

    Sensitive Paths in robots.txtInfo

    Why it matters: The robots.txt file lists sensitive paths, which could aid malicious actors in probing the site.

    Fix: Ensure actual access control is implemented for the /wp-admin/ directory and remove it from the robots.txt if not necessary.

    Evidence: Sensitive paths in robots.txt

What the checks found

  • FoundContent Security PolicyMedium

    None of the 148 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://capitollandscape.com/ → no content-security-policy
    • https://capitollandscape.com/about/ → no content-security-policy
    • https://capitollandscape.com/the-process/ → no content-security-policy
    • https://capitollandscape.com/services/ → no content-security-policy
    • https://capitollandscape.com/gallery/ → no content-security-policy
    • https://capitollandscape.com/contact/ → no content-security-policy
    • https://capitollandscape.com/privacy-policy/ → no content-security-policy
    • https://capitollandscape.com/terms-of-service/ → no content-security-policy
    • https://capitollandscape.com/testimonial/j-d/ → no content-security-policy
    • https://capitollandscape.com/testimonial/m-r/ → no content-security-policy
    • https://capitollandscape.com/testimonial/t-s/ → no content-security-policy
    • https://capitollandscape.com/testimonial/c-s/ → no content-security-policy
  • FoundVulnerable JavaScript librariesMedium

    1 library with published vulnerabilities: jQuery 2.4.24. Whether they are exploitable depends on how the site uses them, but each has a fixed release.

    • jQuery 2.4.24 in https://capitollandscape.com/wp-content/plugins/gravityforms/js/placeholders.jq…: CVE-2015-9251 (XSS via cross-domain AJAX), CVE-2019-11358 (prototype pollution), CVE-2020-11022, CVE-2020-11023 (XSS via HTML passed to DOM methods); fixed in 3.5.0
  • NoteThird-party scripts

    Scripts run from 4 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)
    • c0.wp.com (167 script tags)
    • unpkg.com (40 script tags)
    • cdn.jsdelivr.net (40 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 148 crawled pages were served over HTTPS.

  • OKHTTP Strict Transport Security

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

  • OKClickjacking protection

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

  • OKMIME sniffing protection

    x-content-type-options is set on all 148 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

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

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

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

Own capitollandscape.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 capitollandscape.com. Removal needs no account and no proof of purchase.