Scanned sites / xclusivefireprotection.com / 2026-10-25-0306

xclusivefireprotection.com scan from 2026-10-25 03:06:05 UTC DR 0

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

Scan 2026-10-25-0306

Scanned 2026-10-25 03:06:05 UTC, finished 2026-10-25 03:07:09 UTC

Site: https://xclusivefireprotection.com/

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

58/ 100Needs work

On October 25, 2026 the Site Spider crawled 149 pages and 8 assets of xclusivefireprotection.com, starting from https://xclusivefireprotection.com/. It scored 58 out of 100, a result that needs work. 6 of 32 checks found something to fix, led by title tags (149), indexability (149), meta descriptions (149); 21 checks passed. Most of the points went to title tags (−10), indexability (−10), meta descriptions (−8). 5 checks found something the score does not count, listed as noted. 5 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, 1 low and 1 info findings. See the security findings ↓

Pages crawled
149
Assets fetched
8
Status
Completed
Checks with issues
6 of 32
CoverageComplete crawl

157 of 157 discovered URLs were fetched. The crawl reached everything it found. HTML only: nothing here ran JavaScript.

  • Title tags149 issues
    149 of 149 pages have title issues.
    −10 points
  • Meta descriptions149 issues
    149 of 149 pages have meta description issues.
    −8 points
  • HeadingsOK
    0 of 149 pages have heading issues.
  • Broken linksOK
    0 internal links point at 0 broken URLs.
  • Links to other sitesNot checked
    Not checked: the crawl fetched nothing this check can look at.
  • Redirects2 noted
    2 redirecting URLs, 0 of them chained.
  • Non-200 responses2 noted
    2 URLs did not return a 2xx response. 0 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.
  • Indexability149 issues
    149 of 149 indexable pages have indexability warnings.
    −10 points
  • Image alt textOK
    0 of 0 image references have no alt attribute.
  • Heavy assetsOK
    0 assets larger than 500 KB among 8 fetched assets.
  • Orphan pages116 issues
    116 pages have no internal links pointing at them.
    −3.1 points
  • Sitemap coverage116 issues
    1 sitemap listing 149 URLs: 0 crawled pages missing, 0 listed URLs broken or redirecting, 116 reachable only via the sitemap.
    −4.7 points
  • Internal link countsOK
    Internal link counts for 149 pages; none is a dead end or buried.
  • Thin contentOK
    0 of 149 pages have fewer than 200 words.
  • Duplicate content119 issues
    3 groups of pages with identical HTML.
    −6.4 points
  • URL formatOK
    All 149 page URLs are plain lowercase addresses without parameters.
  • Canonicals149 noted
    149 of 149 pages have a canonical worth checking.
  • Robots directivesOK
    No page carries a robots directive; all 149 pages are open to search engines.
  • Anchor textOK
    Every internal link has descriptive, followed anchor text.
  • Title and heading structure119 noted
    119 of 149 pages could use the title, heading and snippet space better.
  • Image weight and alt lengthOK
    No image is over 100 KB or carries 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 149 pages keep their head tags in <head>, once each, under Googlebot's 2 MB.
  • hreflangOK
    No page declares hreflang.
  • Structured dataOK
    No page carries structured data (149 indexable pages checked).
  • Near duplicatesOK
    No near duplicates among 0 pages with enough text to compare.
  • Soft 404sOK
    None of 149 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 positions33 noted
    33 of 33 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 157 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 149 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.
  • SpellingOK
    No unfamiliar lower-case words on 149 pages (English pages only).

Where this scan sits among all scanned sites

2315 sites, median 79%, average 78%

xclusivefireprotection.com scores 58%, higher than 5% of the 2315 scanned sites. See the full ranking.

0571140%: 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%: 8 sites60%: 16 sites61%: 12 sites62%: 19 sites63%: 27 sites64%: 22 sites65%: 32 sites66%: 36 sites67%: 34 sites68%: 35 sites69%: 46 sites70%: 44 sites71%: 68 sites72%: 70 sites73%: 69 sites74%: 69 sites75%: 71 sites76%: 86 sites77%: 92 sites78%: 107 sites79%: 85 sites80%: 106 sites81%: 105 sites82%: 114 sites83%: 98 sites84%: 108 sites85%: 86 sites86%: 69 sites87%: 73 sites88%: 59 sites89%: 62 sites90%: 34 sites91%: 44 sites92%: 37 sites93%: 23 sites94%: 16 sites95%: 11 sites96%: 9 sites97%: 12 sites98%: 4 sites99%: 1 site100%: 70 sites58% 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

Your site has several urgent SEO issues impacting visibility. Prioritize fixing the title and meta description issues, as well as addressing orphan pages to improve internal linking structure. Implementing these changes can significantly enhance your site's health score.

  1. 1

    Fix Redirects

    Why: Eliminating redirects improves page load speed and user experience.

    How: Replace URLs causing 302 redirects with direct links or correct the redirect target.

    Checks: redirects

  2. 2

    Create Unique Title Tags

    Why: Distinct titles improve click-through rates and search visibility.

    How: Craft unique titles for each of the 149 pages, reflecting their specific content.

    Checks: titles

  3. 3

    Write Unique Meta Descriptions

    Why: Unique meta descriptions can significantly increase CTR from search results.

    How: Develop unique descriptions for the 149 pages based on their content.

    Checks: meta-descriptions

  4. 4

    Resolve Indexability Issues

    Why: Making pages indexable assists in enhancing search engine visibility.

    How: Add canonical tags to the 149 pages to clarify the primary versions.

    Checks: indexability

  5. 5

    Address Orphan Pages

    Why: Linking to orphan pages improves their discoverability and SEO strength.

    How: Add internal links to the 116 orphan pages from relevant content.

    Checks: orphan-pages

  6. 6

    Handle Duplicate Content

    Why: Consolidating duplicate pages enhances their authority and ranking potential.

    How: Identify and canonicalize the duplicate pages to a single version.

    Checks: duplicate-content

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 essential security headers, specifically a Content Security Policy and Permissions Policy, which may increase vulnerability to cross-site scripting and other attacks. It also includes third-party scripts without Subresource Integrity. Implementing these security measures is crucial to protect user data and maintain integrity.

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

    Missing Content Security PolicyMedium

    Why it matters: The absence of a Content Security Policy allows unrestricted script and resource loading, increasing the risk of cross-site scripting attacks.

    Fix: Add a Content-Security-Policy header such as: `Content-Security-Policy: default-src 'self';` to all HTML pages.

    Evidence: Content Security Policy

  2. 2

    Third-party Scripts Without Subresource IntegrityLow

    Why it matters: The site loads scripts from external domains without Subresource Integrity, exposing it to risks if those scripts are compromised.

    Fix: Use Subresource Integrity for scripts from `www.googletagmanager.com`, or implement a Content Security Policy that limits where scripts can load from.

    Evidence: Third-party scripts

  3. 3

    Missing Permissions PolicyInfo

    Why it matters: Without a Permissions Policy, the site does not restrict access to sensitive browser features, increasing potential attack vectors for any injected scripts.

    Fix: Add a Permissions-Policy header like: `Permissions-Policy: geolocation=(), microphone=(), camera=();` to all HTML pages.

    Evidence: Permissions policy

What the checks found

  • FoundContent Security PolicyMedium

    None of the 149 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://xclusivefireprotection.com/ → no content-security-policy
    • https://xclusivefireprotection.com/services → no content-security-policy
    • https://xclusivefireprotection.com/services/commercial-kitchen-suppression → no content-security-policy
    • https://xclusivefireprotection.com/services/commercial-kitchen-hoods-exhaust-systems → no content-security-policy
    • https://xclusivefireprotection.com/services/ansul-fire-suppression-system-service → no content-security-policy
    • https://xclusivefireprotection.com/services/kitchen-suppression-inspection → no content-security-policy
    • https://xclusivefireprotection.com/services/ul-300-fire-suppression-upgrade → no content-security-policy
    • https://xclusivefireprotection.com/services/kitchen-suppression-repairs → no content-security-policy
    • https://xclusivefireprotection.com/services/kitchen-suppression-installation → no content-security-policy
    • https://xclusivefireprotection.com/services/hydrostatic-testing → no content-security-policy
    • https://xclusivefireprotection.com/services/restaurant-fire-code-compliance → no content-security-policy
    • https://xclusivefireprotection.com/services/fire-extinguishers → no content-security-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://xclusivefireprotection.com/ → no permissions-policy
    • https://xclusivefireprotection.com/services → no permissions-policy
    • https://xclusivefireprotection.com/services/commercial-kitchen-suppression → no permissions-policy
    • https://xclusivefireprotection.com/services/commercial-kitchen-hoods-exhaust-systems → no permissions-policy
    • https://xclusivefireprotection.com/services/ansul-fire-suppression-system-service → no permissions-policy
    • https://xclusivefireprotection.com/services/kitchen-suppression-inspection → no permissions-policy
    • https://xclusivefireprotection.com/services/ul-300-fire-suppression-upgrade → no permissions-policy
    • https://xclusivefireprotection.com/services/kitchen-suppression-repairs → no permissions-policy
    • https://xclusivefireprotection.com/services/kitchen-suppression-installation → no permissions-policy
    • https://xclusivefireprotection.com/services/hydrostatic-testing → no permissions-policy
    • https://xclusivefireprotection.com/services/restaurant-fire-code-compliance → no permissions-policy
    • https://xclusivefireprotection.com/services/fire-extinguishers → no permissions-policy
  • 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)
10 checks passed, 3 not applicable
  • OKHTTPS

    All 149 crawled pages were served over HTTPS.

  • OKHTTP Strict Transport Security

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

  • OKClickjacking protection

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

  • OKMIME sniffing protection

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

  • OKReferrer policy

    referrer-policy is set on all 149 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.

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

  • Not applicableVulnerable JavaScript libraries

    No recognisable library versions were found in the sampled scripts.

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

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