Scanned sites / wrenmissoula.com

SEO report for wrenmissoula.com DR 31

The latest Site Spider scan of wrenmissoula.com, with 1 scan on record. Each scan is at its own address, for example /domain/wrenmissoula-com/2026-09-13-0832.

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

Latest scan

Scanned 2026-09-13 08:32:08 UTC, finished 2026-09-13 10:43:25 UTC. Found on page 3 of brave web search results

Site: https://wrenmissoula.com/

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

71/ 100Needs work

On September 13, 2026 the Site Spider crawled 60 pages and 423 assets of wrenmissoula.com, starting from https://wrenmissoula.com/. It scored 71 out of 100, a result that needs work. 10 of 26 checks found something to fix, led by meta descriptions (50), title tags (35), heavy assets (12); 10 checks passed. Most of the points went to meta descriptions (−7.4), title tags (−6.5), heavy assets (−6). 6 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: Medium4 medium and 1 low findings. See the security findings ↓

Pages crawled
60
Assets fetched
423
Status
Completed
Checks with issues
10 of 26
CoverageComplete crawl

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

  • Title tags35 issues
    35 of 54 pages have title issues.
    −6.5 points
  • Meta descriptions50 issues
    50 of 54 pages have meta description issues.
    −7.4 points
  • Headings47 issues
    47 of 54 pages have heading issues.
    −5.2 points
  • Broken linksOK
    0 internal links point at 0 broken URLs.
  • Links to other sites3 issues
    3 destinations answered with an error, 43 could not be determined (timeouts, rate limits or refusals), of 168 destinations checked.
    −1.2 points
  • Redirects6 issues
    7 redirecting URLs, 0 of them chained.
    −0.4 points
  • Non-200 responses48 noted
    48 URLs did not return a 2xx response. 6 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 54 indexable pages have indexability warnings.
  • Image alt text26 issues
    26 of 973 image references have no alt attribute. 240 use an empty alt (decorative), which is fine.
    −0.2 points
  • Heavy assets12 issues
    12 assets larger than 500 KB among 423 fetched assets.
    −6 points
  • Orphan pages6 issues
    6 pages have no internal links pointing at them.
    −0.4 points
  • Sitemap coverage7 issues
    5 sitemaps listing 55 URLs: 0 crawled pages missing, 1 listed URL broken or redirecting, 6 reachable only via the sitemap.
    −0.8 points
  • Internal link countsOK
    Internal link counts for 54 pages; none is a dead end or buried.
  • Thin content9 issues
    9 of 54 pages have fewer than 200 words.
    −1.3 points
  • Duplicate contentOK
    0 groups of pages with identical HTML.
  • URL formatOK
    All 60 page URLs are plain lowercase addresses without parameters.
  • CanonicalsOK
    0 of 54 pages have a canonical worth checking.
  • Robots directives54 noted
    54 pages carry a robots directive; 0 carry none.
  • Anchor text3 noted
    3 destinations are linked without useful anchor text, or with nofollow.
  • Title and heading structure2 noted
    2 of 54 pages could use the title, heading and snippet space better.
  • Image weight and alt length109 noted
    107 images over 100 KB; 2 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 404s1 noted
    1 page answer 200 but say they are not there.
  • 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; 12 response headers recorded across 483 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 54 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.
  • SpellingNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.

Where this site sits among all scanned sites

2343 sites, median 79%, average 78%

wrenmissoula.com scores 71%, higher than 20% of the 2343 scanned sites. See the full ranking.

0591170%: 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%: 6 sites54%: 8 sites55%: 9 sites56%: 8 sites57%: 12 sites58%: 17 sites59%: 9 sites60%: 16 sites61%: 12 sites62%: 20 sites63%: 27 sites64%: 22 sites65%: 32 sites66%: 35 sites67%: 35 sites68%: 34 sites69%: 47 sites70%: 44 sites71%: 69 sites72%: 71 sites73%: 70 sites74%: 68 sites75%: 72 sites76%: 87 sites77%: 92 sites78%: 107 sites79%: 84 sites80%: 108 sites81%: 105 sites82%: 117 sites83%: 100 sites84%: 107 sites85%: 88 sites86%: 70 sites87%: 73 sites88%: 59 sites89%: 65 sites90%: 36 sites91%: 47 sites92%: 38 sites93%: 24 sites94%: 16 sites95%: 12 sites96%: 12 sites97%: 12 sites98%: 5 sites99%: 2 sites100%: 68 sites71% 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.

Your site requires improvements in redirects, non-200 responses, title tags, and more. Addressing priority issues will enhance user experience and search visibility.

  1. 1

    Fix Non-200 Responses

    Why: 48 URLs return non-2xx status, harming accessibility.

    How: Update or remove pages causing these responses to ensure all URLs return a 200 status.

    Checks: status-codes

  2. 2

    Resolve Redirects

    Why: 7 URLs redirect, affecting user experience.

    How: Eliminate unnecessary redirects and link directly to the final URLs instead.

    Checks: redirects

  3. 3

    Improve Title Tags

    Why: 35 pages have title issues affecting SEO.

    How: Update titles for duplicates and those that are too short, aiming for unique lengths of 50-60 characters.

    Checks: titles

  4. 4

    Enhance Meta Descriptions

    Why: 39 pages have meta description issues impacting click-through rates.

    How: Craft unique meta descriptions for pages, keeping them under 160 characters.

    Checks: meta-descriptions

  5. 5

    Add Missing Headings

    Why: 47 pages lack H1 tags, affecting SEO structure.

    How: Ensure each page includes a clear H1 tag relevant to its content.

    Checks: headings

  6. 6

    Implement Internal Links for Orphan Pages

    Why: 6 orphan pages lack internal links, reducing visibility.

    How: Link to these pages from relevant content on your site to improve their accessibility.

    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 crawl

Your website has several critical security shortfalls that could expose users to risks. Key issues include the absence of protections like HTTP Strict Transport Security and Content Security Policy. Additionally, you're using outdated JavaScript libraries with known vulnerabilities. Implementing recommended headers and updating libraries will greatly enhance your site's security.

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

    Missing HTTP Strict Transport Security (HSTS)Medium

    Why it matters: Without HSTS, visitors typing your URL without 'https://' can be intercepted during the first request.

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

    Evidence: HTTP Strict Transport Security

  2. 2

    Missing Content Security Policy (CSP)Medium

    Why it matters: Lack of a CSP allows any scripts or frames to load, increasing risk of XSS attacks.

    Fix: Add a CSP header, e.g., Content-Security-Policy: default-src 'self'; script-src 'self';

    Evidence: Content Security Policy

  3. 3

    Missing X-Frame-Options HeaderMedium

    Why it matters: Without this, your pages can be embedded in frames on malicious sites, risking clickjacking.

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

    Evidence: Clickjacking protection

  4. 4

    Use of Vulnerable JavaScript LibrariesMedium

    Why it matters: Two libraries in use have known vulnerabilities that could potentially be exploited.

    Fix: Update jQuery from versions 1.9.1 and 1.11.3 to 3.5.0 or later.

    Evidence: Vulnerable JavaScript libraries

  5. 5

    Missing X-Content-Type-Options HeaderLow

    Why it matters: Without this, browsers may incorrectly process files, potentially leading to script execution threats.

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

    Evidence: MIME sniffing protection

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://wrenmissoula.com/ → no strict-transport-security
    • https://wrenmissoula.com/about-missoula-hotel/ → no strict-transport-security
    • https://wrenmissoula.com/compendium/ → no strict-transport-security
    • https://wrenmissoula.com/about-missoula-hotel/amenities/ → no strict-transport-security
    • https://wrenmissoula.com/about-missoula-hotel/dogs-welcome/ → no strict-transport-security
    • https://wrenmissoula.com/about-missoula-hotel/earn-stash-rewards-points/ → no strict-transport-security
    • https://wrenmissoula.com/about-missoula-hotel/health-safety/ → no strict-transport-security
    • https://wrenmissoula.com/about-missoula-hotel/faqs-policies/ → no strict-transport-security
    • https://wrenmissoula.com/accessibility-statement/ → no strict-transport-security
    • https://wrenmissoula.com/coffee-shop/ → no strict-transport-security
    • https://wrenmissoula.com/missoula-montana-hotel-rooms/ → no strict-transport-security
    • https://wrenmissoula.com/missoula-hotel-meetings-events/ → no strict-transport-security
  • FoundContent Security PolicyMedium

    None of the 54 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://wrenmissoula.com/ → no content-security-policy
    • https://wrenmissoula.com/about-missoula-hotel/ → no content-security-policy
    • https://wrenmissoula.com/compendium/ → no content-security-policy
    • https://wrenmissoula.com/about-missoula-hotel/amenities/ → no content-security-policy
    • https://wrenmissoula.com/about-missoula-hotel/dogs-welcome/ → no content-security-policy
    • https://wrenmissoula.com/about-missoula-hotel/earn-stash-rewards-points/ → no content-security-policy
    • https://wrenmissoula.com/about-missoula-hotel/health-safety/ → no content-security-policy
    • https://wrenmissoula.com/about-missoula-hotel/faqs-policies/ → no content-security-policy
    • https://wrenmissoula.com/accessibility-statement/ → no content-security-policy
    • https://wrenmissoula.com/coffee-shop/ → no content-security-policy
    • https://wrenmissoula.com/missoula-montana-hotel-rooms/ → no content-security-policy
    • https://wrenmissoula.com/missoula-hotel-meetings-events/ → 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://wrenmissoula.com/ → no x-frame-options
    • https://wrenmissoula.com/about-missoula-hotel/ → no x-frame-options
    • https://wrenmissoula.com/compendium/ → no x-frame-options
    • https://wrenmissoula.com/about-missoula-hotel/amenities/ → no x-frame-options
    • https://wrenmissoula.com/about-missoula-hotel/dogs-welcome/ → no x-frame-options
    • https://wrenmissoula.com/about-missoula-hotel/earn-stash-rewards-points/ → no x-frame-options
    • https://wrenmissoula.com/about-missoula-hotel/health-safety/ → no x-frame-options
    • https://wrenmissoula.com/about-missoula-hotel/faqs-policies/ → no x-frame-options
    • https://wrenmissoula.com/accessibility-statement/ → no x-frame-options
    • https://wrenmissoula.com/coffee-shop/ → no x-frame-options
    • https://wrenmissoula.com/missoula-montana-hotel-rooms/ → no x-frame-options
    • https://wrenmissoula.com/missoula-hotel-meetings-events/ → 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://wrenmissoula.com/ → no x-content-type-options
    • https://wrenmissoula.com/about-missoula-hotel/ → no x-content-type-options
    • https://wrenmissoula.com/compendium/ → no x-content-type-options
    • https://wrenmissoula.com/about-missoula-hotel/amenities/ → no x-content-type-options
    • https://wrenmissoula.com/about-missoula-hotel/dogs-welcome/ → no x-content-type-options
    • https://wrenmissoula.com/about-missoula-hotel/earn-stash-rewards-points/ → no x-content-type-options
    • https://wrenmissoula.com/about-missoula-hotel/health-safety/ → no x-content-type-options
    • https://wrenmissoula.com/about-missoula-hotel/faqs-policies/ → no x-content-type-options
    • https://wrenmissoula.com/accessibility-statement/ → no x-content-type-options
    • https://wrenmissoula.com/coffee-shop/ → no x-content-type-options
    • https://wrenmissoula.com/missoula-montana-hotel-rooms/ → no x-content-type-options
    • https://wrenmissoula.com/missoula-hotel-meetings-events/ → no x-content-type-options
  • FoundVulnerable JavaScript librariesMedium

    2 libraries with published vulnerabilities: jQuery 1.9.1, jQuery 1.11.3. Whether they are exploitable depends on how the site uses them, but each has a fixed release.

    • jQuery 1.9.1 in https://wrenmissoula.com/js/bootstrap.bundle.min.js: 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
    • jQuery 1.11.3 in https://wrenmissoula.com/wp-content/plugins/robo-gallery/js/robo_gallery_alt.js…: 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 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.)

    • www.googletagmanager.com (40 script tags)
    • contact-api.inguest.com (41 script tags)
    • app.helloshift.com (40 script tags)
7 checks passed, 3 not applicable
  • OKHTTPS

    All 54 crawled pages were served over HTTPS.

  • 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

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

  • OKSensitive paths in robots.txt

    robots.txt does not point at admin, backup or private paths.

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

Earlier scans of wrenmissoula.com

No other scans of this site yet.

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

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