Scanned sites / abundantmontana.com / 2026-09-12-1907

abundantmontana.com scan from 2026-09-12 19:07:20 UTC DR 43

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

Scan 2026-09-12-1907

Scanned 2026-09-12 19:07:20 UTC, finished 2026-09-12 23:05:57 UTC. Found on page 5 of brave web search results

Not a full crawl. The scan was concluded early by the site operator with 2742 URLs left unfetched. This is not a full crawl: results cover only what was crawled before it stopped.

Site: https://abundantmontana.com/

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

81/ 100GoodNot a full crawl

On September 12, 2026 the Site Spider crawled 1823 pages and 269 assets of abundantmontana.com, starting from https://abundantmontana.com/. It scored 81 out of 100, a good result. 13 of 26 checks found something to fix, led by meta descriptions (925), heavy assets (7), indexability (697); 5 checks passed. Most of the points went to meta descriptions (−4.3), heavy assets (−4.2), indexability (−4.1). 8 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: Medium3 medium, 2 low and 1 info findings. See the security findings ↓

Pages crawled
1823
Assets fetched
269
Status
Completed
Checks with issues
13 of 26
CoverageJob finished, partial coverage

2,092 of 4,834 discovered URLs were fetched, 29,376 left out by the 5,000-page and 1,000-asset budget, 2,742 skipped when the crawl was cut short. The job finished, but the crawl did not reach everything it found. HTML only: nothing here ran JavaScript. 312 link destinations on other sites were checked, 3998 left unchecked.

  • Title tags217 issues
    217 of 937 pages have title issues. 776 noindex or canonicalized pages excluded.
    −1.3 points
  • Meta descriptions925 issues
    925 of 937 pages have meta description issues. 776 noindex or canonicalized pages excluded.
    −4.3 points
  • Headings302 issues
    302 of 937 pages have heading issues. 776 noindex or canonicalized pages excluded.
    −1.1 points
  • Broken links28 issues
    62 internal links point at 28 broken URLs.
    −0.3 points
  • Links to other sites8 issues
    8 destinations answered with an error, 146 could not be determined (timeouts, rate limits or refusals), 3998 were left unchecked by the per-scan cap, of 300 destinations checked.
    −0.2 points
  • Redirects83 issues
    83 redirecting URLs, 2 of them chained.
    −0.2 points
  • Non-200 responses28 issues
    111 URLs did not return a 2xx response. 110 of them are pages, 28 with an error status; the rest are assets or redirects.
    −0.2 points
  • Rate limitedOK
    The site did not rate limit the crawler.
  • Indexability697 issues
    697 of 1692 indexable pages have indexability warnings. 21 pages noindex by design.
    −4.1 points
  • Image alt text762 issues
    762 of 12080 image references have no alt attribute. 9843 use an empty alt (decorative), which is fine.
    −0.4 points
  • Heavy assets7 issues
    7 assets larger than 500 KB among 269 fetched assets. 1 document over that size is listed but not counted: downloads are not page weight.
    −4.2 points
  • Orphan pages11 issues
    11 pages have no internal links pointing at them.
  • Sitemap coverage857 issues
    No sitemap found. Tried: https://abundantmontana.com/sitemap.xml (301), https://abundantmontana.com/sitemap_index.xml (skipped). Add one at /sitemap.xml or list it in robots.txt.
    −3 points
  • Internal link counts179 noted
    Internal link counts for 500 pages; 179 worth a look.
  • Thin contentOK
    0 of 937 pages have fewer than 200 words. 776 noindex or canonicalized pages excluded.
  • Duplicate content22 issues
    1 group of pages with identical HTML.
    −0.1 points
  • URL format186 noted
    186 of 1823 page URLs are harder to read, share or cache than they need to be.
  • Canonicals774 noted
    774 of 1713 pages have a canonical worth checking.
  • Robots directives1,713 noted
    1713 pages carry a robots directive; 0 carry none.
  • Anchor text1,689 noted
    1689 destinations are linked without useful anchor text, or with nofollow.
  • Title and heading structure143 noted
    143 of 937 pages could use the title, heading and snippet space better. 776 noindex or canonicalized pages excluded.
  • Image weight and alt length9 noted
    5 images over 100 KB; 4 with alt text over 100 characters.
  • Response anomalies14 noted
    14 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 1713 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; 15 response headers recorded across 2092 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 1713 pages; 1672 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 scan sits among all scanned sites

2342 sites, median 79%, average 78%

abundantmontana.com scores 81%, higher than 55% of the 2342 scanned sites. See the full ranking.

0581160%: 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%: 70 sites72%: 71 sites73%: 70 sites74%: 68 sites75%: 72 sites76%: 87 sites77%: 92 sites78%: 107 sites79%: 84 sites80%: 108 sites81%: 105 sites82%: 116 sites83%: 100 sites84%: 106 sites85%: 87 sites86%: 71 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 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. 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.

Significant SEO issues were identified, particularly broken links and missing sitemaps. Addressing these high-impact areas will enhance user experience and search visibility.

  1. 1

    Fix Broken Links

    Why: 62 broken internal links damage user experience and hinder SEO.

    How: Identify broken links and update or remove them. Use a tool like Screaming Frog to list all broken URLs.

    Checks: broken-links

  2. 2

    Set Up Sitemap

    Why: No sitemap found limits search engine indexing efficiency.

    How: Create and submit a sitemap at /sitemap.xml. Use a plugin or website service to generate it.

    Checks: sitemap-coverage

  3. 3

    Reduce Redirects

    Why: 83 redirects can slow down site performance and reduce crawl efficiency.

    How: Eliminate unnecessary redirects and fix chaining by updating links directly to the final destination.

    Checks: redirects

  4. 4

    Correct Title Tags

    Why: 214 pages have title issues that can hinder click-through rates.

    How: Edit titles to make them more relevant and under 60 characters. Check in the CMS or HTML.

    Checks: titles

  5. 5

    Add Meta Descriptions

    Why: 924 pages lack meta descriptions, affecting click-through rates from search results.

    How: Write unique and relevant meta descriptions for each page that summarize the content accurately.

    Checks: meta-descriptions

  6. 6

    Fix Heading Structure

    Why: 302 pages have heading issues that can confuse search engines and users.

    How: Ensure each page has one H1 tag and utilizes H2/H3 tags appropriately for subheadings.

    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 crawl

The website lacks important security headers, putting visitors at risk for interception and clickjacking. Additionally, a leaked Google API key should be restricted to enhance security. Implementing suggested fixes will significantly improve site security.

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

    Missing HTTP Strict Transport Security (HSTS)Medium

    Why it matters: Without HSTS, users can be intercepted when accessing the site without HTTPS.

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

    Evidence: HTTP Strict Transport Security

  2. 2

    Missing X-Frame-OptionsMedium

    Why it matters: Absence of this header makes the site vulnerable to clickjacking attacks.

    Fix: Add the header: X-Frame-Options: DENY or use Content-Security-Policy: frame-ancestors 'none'.

    Evidence: Clickjacking protection

  3. 3

    Leaked Google API KeyMedium

    Why it matters: The exposed API key can lead to unauthorized usage and should be restricted.

    Fix: Restrict the key in the Google Cloud console and ensure it only works under the site's domains.

    Evidence: Keys and secrets in page code

  4. 4

    Missing X-Content-Type-OptionsLow

    Why it matters: Not using this header allows browsers to execute files based on content type, creating security risks.

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

    Evidence: MIME sniffing protection

  5. 5

    Third-party Scripts Lack Subresource IntegrityLow

    Why it matters: Without integrity checks, compromised third-party scripts may harm users.

    Fix: Consider implementing a Content-Security-Policy that restricts known script sources.

    Evidence: Third-party scripts

  6. 6

    Sensitive Paths in robots.txtInfo

    Why it matters: The robots.txt file exposes private paths, which can aid malicious users.

    Fix: Remove sensitive paths from robots.txt or ensure proper access control is applied.

    Evidence: Sensitive paths in robots.txt

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://abundantmontana.com/ → no strict-transport-security
    • https://abundantmontana.com/search/ → no strict-transport-security
    • https://abundantmontana.com/wholesale/ → no strict-transport-security
    • https://abundantmontana.com/our-mission/ → no strict-transport-security
    • https://abundantmontana.com/our-story/ → no strict-transport-security
    • https://abundantmontana.com/our-team/ → no strict-transport-security
    • https://abundantmontana.com/localfoodguide/ → no strict-transport-security
    • https://abundantmontana.com/find-the-magazine/ → no strict-transport-security
    • https://abundantmontana.com/blog/ → no strict-transport-security
    • https://abundantmontana.com/events/ → no strict-transport-security
    • https://abundantmontana.com/33x33/ → no strict-transport-security
    • https://abundantmontana.com/shop/ → no strict-transport-security
  • FoundClickjacking protectionMedium

    7 of 1713 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://abundantmontana.com/ → no x-frame-options
    • https://abundantmontana.com/search/ → no x-frame-options
    • https://abundantmontana.com/wholesale/ → no x-frame-options
    • https://abundantmontana.com/our-mission/ → no x-frame-options
    • https://abundantmontana.com/our-story/ → no x-frame-options
    • https://abundantmontana.com/our-team/ → no x-frame-options
    • https://abundantmontana.com/localfoodguide/ → no x-frame-options
    • https://abundantmontana.com/find-the-magazine/ → no x-frame-options
    • https://abundantmontana.com/blog/ → no x-frame-options
    • https://abundantmontana.com/events/ → no x-frame-options
    • https://abundantmontana.com/33x33/ → no x-frame-options
    • https://abundantmontana.com/shop/ → 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://abundantmontana.com/ → no x-content-type-options
    • https://abundantmontana.com/search/ → no x-content-type-options
    • https://abundantmontana.com/wholesale/ → no x-content-type-options
    • https://abundantmontana.com/our-mission/ → no x-content-type-options
    • https://abundantmontana.com/our-story/ → no x-content-type-options
    • https://abundantmontana.com/our-team/ → no x-content-type-options
    • https://abundantmontana.com/localfoodguide/ → no x-content-type-options
    • https://abundantmontana.com/find-the-magazine/ → no x-content-type-options
    • https://abundantmontana.com/blog/ → no x-content-type-options
    • https://abundantmontana.com/events/ → no x-content-type-options
    • https://abundantmontana.com/33x33/ → no x-content-type-options
    • https://abundantmontana.com/shop/ → no x-content-type-options
  • FoundKeys and secrets in page codeMedium

    1 credential-like value found in code served to every visitor: Google API key.

    • Google API key AIzaSy…q8 (39 chars) in https://abundantmontana.com/: 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 8 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 (80 script tags)
    • giving.classy.org (40 script tags)
    • api.bloomerang.co (40 script tags)
    • ajax.googleapis.com (40 script tags)
    • www.google.com (11 script tags)
    • online.flippingbook.com (1 script tag)
    • s3.amazonaws.com (1 script tag)
    • js.stripe.com (1 script tag)
  • 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/
7 checks passed, 3 not applicable
  • OKHTTPS

    All 1713 crawled pages were served over HTTPS.

  • OKContent Security Policy

    A Content-Security-Policy is set on 7 of 1713 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

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

  • OKVulnerable JavaScript libraries

    1 library version recognised, none with known vulnerabilities.

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

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