Scanned sites / topazmel.bg

SEO report for topazmel.bg DR 5

The latest Site Spider scan of topazmel.bg, with 1 scan on record. Each scan is at its own address, for example /domain/topazmel-bg/2026-09-28-1322.

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

Latest scan

Scanned 2026-09-28 13:22:42 UTC, finished 2026-09-28 14:04:33 UTC

Site: https://topazmel.bg/

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

87/ 100Good

On September 28, 2026 the Site Spider crawled 301 pages and 678 assets of topazmel.bg, starting from https://topazmel.bg/. It scored 87 out of 100, a good result. 13 of 27 checks found something to fix, led by heavy assets (139), sitemap coverage (119), redirects (63); 4 checks passed. Most of the points went to heavy assets (−6), sitemap coverage (−3), redirects (−1.1). 10 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: Medium6 medium and 2 low findings. See the security findings ↓

Pages crawled
301
Assets fetched
678
Status
Completed
Checks with issues
13 of 27
CoverageComplete crawl

979 of 981 discovered URLs were fetched, 1 failed. The crawl reached everything it found. HTML only: nothing here ran JavaScript. 12 link destinations on other sites were checked.

  • Title tags12 issues
    12 of 12 pages have title issues. 225 noindex or canonicalized pages excluded.
    −0.5 points
  • Meta descriptions12 issues
    12 of 12 pages have meta description issues. 225 noindex or canonicalized pages excluded.
    −0.4 points
  • Headings12 issues
    12 of 12 pages have heading issues. 225 noindex or canonicalized pages excluded.
    −0.3 points
  • Broken links3 issues
    4 internal links point at 3 broken URLs.
    −0.3 points
  • Links to other sites1 issue
    1 destination answered with an error, 9 could not be determined (timeouts, rate limits or refusals), of 12 destinations checked.
    −0.2 points
  • Redirects63 issues
    96 redirecting URLs, 3 of them chained.
    −1.1 points
  • Non-200 responses3 issues
    101 URLs did not return a 2xx response. 65 of them are pages, 3 with an error status; the rest are assets or redirects.
    −0.1 points
  • Rate limitedOK
    The site did not rate limit the crawler.
  • Indexability12 issues
    12 of 12 indexable pages have indexability warnings. 225 pages noindex by design.
    −0.5 points
  • Image alt text92 issues
    92 of 2019 image references have no alt attribute. 725 use an empty alt (decorative), which is fine.
    −0.3 points
  • Heavy assets139 issues
    139 assets larger than 500 KB among 678 fetched assets. 1 document over that size is listed but not counted: downloads are not page weight.
    −6 points
  • Orphan pagesOK
    0 pages have no internal links pointing at them.
  • Sitemap coverage119 issues
    No sitemap found. Tried: https://topazmel.bg/sitemap.xml (301), https://topazmel.bg/wp-sitemap.xml (404). Add one at /sitemap.xml or list it in robots.txt.
    −3 points
  • Internal link counts226 noted
    Internal link counts for 237 pages; 226 worth a look.
  • Thin content5 issues
    5 of 12 pages have fewer than 200 words. 225 noindex or canonicalized pages excluded.
    −0.2 points
  • Duplicate content2 issues
    1 group of pages with identical HTML.
    −0.1 points
  • URL format77 noted
    77 of 301 page URLs are harder to read, share or cache than they need to be.
  • Canonicals61 noted
    61 of 237 pages have a canonical worth checking.
  • Robots directives225 noted
    225 pages carry a robots directive; 12 carry none.
  • Anchor text202 noted
    202 destinations are linked without useful anchor text, or with nofollow.
  • Title and heading structure12 noted
    12 of 12 pages could use the title, heading and snippet space better. 225 noindex or canonicalized pages excluded.
  • Image weight and alt length210 noted
    210 images over 100 KB; 0 with alt text over 100 characters.
  • Response anomalies1 noted
    1 URL 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 237 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 cookies1 noted
    1 cookie set by the site, 1 missing a protective flag; 11 response headers recorded across 979 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 237 pages; 21 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 63 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 site sits among all scanned sites

2903 sites, median 80%, average 79%

topazmel.bg scores 87%, higher than 76% of the 2903 scanned sites. See the full ranking.

0761520%: 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%: 2 sites37%: 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%: 10 sites55%: 10 sites56%: 8 sites57%: 17 sites58%: 18 sites59%: 10 sites60%: 16 sites61%: 13 sites62%: 20 sites63%: 29 sites64%: 22 sites65%: 33 sites66%: 43 sites67%: 43 sites68%: 42 sites69%: 55 sites70%: 48 sites71%: 79 sites72%: 77 sites73%: 82 sites74%: 82 sites75%: 87 sites76%: 95 sites77%: 109 sites78%: 133 sites79%: 113 sites80%: 129 sites81%: 123 sites82%: 136 sites83%: 121 sites84%: 130 sites85%: 105 sites86%: 96 sites87%: 94 sites88%: 82 sites89%: 75 sites90%: 58 sites91%: 62 sites92%: 44 sites93%: 31 sites94%: 25 sites95%: 16 sites96%: 18 sites97%: 16 sites98%: 8 sites99%: 3 sites100%: 152 sites87% 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 several SEO issues that need addressing, including broken links, redirect chains, and missing title tags. Implementing these fixes will improve your site's health and user experience.

  1. 1

    Fix Broken Links

    Why: 4 internal links lead to broken URLs, impacting user experience.

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

    Checks: broken-links

  2. 2

    Shorten Redirect Chains

    Why: 96 URLs are redirecting, some in chains, which slows down page speed.

    How: Reduce redirects by replacing old URLs with new ones in your content.

    Checks: redirects

  3. 3

    Create a Sitemap

    Why: A sitemap is missing, which helps search engines index your pages.

    How: Generate a sitemap and place it at /sitemap.xml. Also, list it in robots.txt.

    Evidence: One URL: no sitemap found.

    1 page affected

    Checks: sitemap-coverage

  4. 4

    Add Missing Title Tags

    Why: All pages lack unique and relevant title tags, affecting SEO.

    How: Create unique titles that accurately represent each page's content.

    Checks: titles

  5. 5

    Add Missing Meta Descriptions

    Why: Meta descriptions are missing, reducing click-through rates.

    How: Write unique meta descriptions for each page to summarize their content.

    Checks: meta-descriptions

  6. 6

    Correct Missing H1 Headings

    Why: All pages are missing H1 headings, which are important for SEO.

    How: Add a relevant H1 heading to each page to enhance content structure.

    Evidence: 12 pages: missing h1.

    12 pages affected

    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

Your website has several security gaps, primarily due to missing HTTP headers and outdated libraries. Implementing HTTP Strict Transport Security (HSTS) and Content Security Policy (CSP) will enhance protection against certain attacks. Additionally, updating vulnerable libraries and securing cookies is critical.

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

    Missing HTTP Strict Transport Security (HSTS)Medium

    Why it matters: Without HSTS, initial HTTP requests can be intercepted.

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

    Evidence: HTTP Strict Transport Security

  2. 2

    Missing Content Security Policy (CSP)Medium

    Why it matters: Absence of CSP allows any content to load, increasing XSS risk.

    Fix: Add the header: Content-Security-Policy: default-src 'self';.

    Evidence: Content Security Policy

  3. 3

    Missing Clickjacking ProtectionMedium

    Why it matters: No X-Frame-Options prevents framing and overlay attacks.

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

    Evidence: Clickjacking protection

  4. 4

    Missing Cookie Protection FlagsMedium

    Why it matters: Cookies are vulnerable to theft without Secure, HttpOnly, and SameSite flags.

    Fix: Set cookie attributes: Secure; HttpOnly; SameSite=Strict for _icl_current_language.

    Evidence: Cookie flags

  5. 5

    Outdated Vulnerable JavaScript LibrariesMedium

    Why it matters: Using outdated libraries exposes you to known vulnerabilities.

    Fix: Update jQuery to at least 3.5.0, jQuery UI to 1.13.2, and Bootstrap to 4.3.1.

    Evidence: Vulnerable JavaScript libraries

  6. 6

    Leaked API KeyMedium

    Why it matters: API keys visible on the site may lead to unauthorized access.

    Fix: Restrict the Google API key usage by HTTP referrer and set up authentication in Google Cloud console.

    Evidence: Keys and secrets in page code

  7. 7

    Missing MIME Sniffing ProtectionLow

    Why it matters: Lack of X-Content-Type-Options can lead to MIME type vulnerabilities.

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

    Evidence: MIME sniffing protection

  8. 8

    Missing Referrer PolicyLow

    Why it matters: Without a Referrer-Policy, sensitive information may be unintentionally shared.

    Fix: Add the header: Referrer-Policy: no-referrer.

    Evidence: Referrer policy

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://topazmel.bg/ → no strict-transport-security
    • https://topazmel.bg/about/ → no strict-transport-security
    • https://topazmel.bg/products/ → no strict-transport-security
    • https://topazmel.bg/%d1%81%d0%b5%d1%80%d1%82%d0%b8%d1%84%d0%b8%d0%ba%d0%b0%d1%82%d0%b8/ → no strict-transport-security
    • https://topazmel.bg/raw-materials/ → no strict-transport-security
    • https://topazmel.bg/%d1%82%d1%8a%d1%80%d0%b3%d0%be%d0%b2%d0%b8%d1%8f/ → no strict-transport-security
    • https://topazmel.bg/%d0%bb%d0%be%d1%8f%d0%bb%d0%bd%d0%b0-%d0%bf%d1%80%d0%be%d0%b3%d1%80%d0%b0%d0%bc%d0%b0/ → no strict-transport-security
    • https://topazmel.bg/contacts/ → no strict-transport-security
    • https://topazmel.bg/home/%d0%be%d0%b1%d1%89%d0%b8-%d1%83%d1%81%d0%bb%d0%be%d0%b2%d0%b8%d1%8f/ → no strict-transport-security
    • https://topazmel.bg/en/ → no strict-transport-security
    • https://topazmel.bg/el/ → no strict-transport-security
    • https://topazmel.bg/product-showcase/home-products/ → no strict-transport-security
  • FoundContent Security PolicyMedium

    None of the 237 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://topazmel.bg/ → no content-security-policy
    • https://topazmel.bg/about/ → no content-security-policy
    • https://topazmel.bg/products/ → no content-security-policy
    • https://topazmel.bg/%d1%81%d0%b5%d1%80%d1%82%d0%b8%d1%84%d0%b8%d0%ba%d0%b0%d1%82%d0%b8/ → no content-security-policy
    • https://topazmel.bg/raw-materials/ → no content-security-policy
    • https://topazmel.bg/%d1%82%d1%8a%d1%80%d0%b3%d0%be%d0%b2%d0%b8%d1%8f/ → no content-security-policy
    • https://topazmel.bg/%d0%bb%d0%be%d1%8f%d0%bb%d0%bd%d0%b0-%d0%bf%d1%80%d0%be%d0%b3%d1%80%d0%b0%d0%bc%d0%b0/ → no content-security-policy
    • https://topazmel.bg/contacts/ → no content-security-policy
    • https://topazmel.bg/home/%d0%be%d0%b1%d1%89%d0%b8-%d1%83%d1%81%d0%bb%d0%be%d0%b2%d0%b8%d1%8f/ → no content-security-policy
    • https://topazmel.bg/en/ → no content-security-policy
    • https://topazmel.bg/el/ → no content-security-policy
    • https://topazmel.bg/product-showcase/home-products/ → 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://topazmel.bg/ → no x-frame-options
    • https://topazmel.bg/about/ → no x-frame-options
    • https://topazmel.bg/products/ → no x-frame-options
    • https://topazmel.bg/%d1%81%d0%b5%d1%80%d1%82%d0%b8%d1%84%d0%b8%d0%ba%d0%b0%d1%82%d0%b8/ → no x-frame-options
    • https://topazmel.bg/raw-materials/ → no x-frame-options
    • https://topazmel.bg/%d1%82%d1%8a%d1%80%d0%b3%d0%be%d0%b2%d0%b8%d1%8f/ → no x-frame-options
    • https://topazmel.bg/%d0%bb%d0%be%d1%8f%d0%bb%d0%bd%d0%b0-%d0%bf%d1%80%d0%be%d0%b3%d1%80%d0%b0%d0%bc%d0%b0/ → no x-frame-options
    • https://topazmel.bg/contacts/ → no x-frame-options
    • https://topazmel.bg/home/%d0%be%d0%b1%d1%89%d0%b8-%d1%83%d1%81%d0%bb%d0%be%d0%b2%d0%b8%d1%8f/ → no x-frame-options
    • https://topazmel.bg/en/ → no x-frame-options
    • https://topazmel.bg/el/ → no x-frame-options
    • https://topazmel.bg/product-showcase/home-products/ → 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://topazmel.bg/ → no x-content-type-options
    • https://topazmel.bg/about/ → no x-content-type-options
    • https://topazmel.bg/products/ → no x-content-type-options
    • https://topazmel.bg/%d1%81%d0%b5%d1%80%d1%82%d0%b8%d1%84%d0%b8%d0%ba%d0%b0%d1%82%d0%b8/ → no x-content-type-options
    • https://topazmel.bg/raw-materials/ → no x-content-type-options
    • https://topazmel.bg/%d1%82%d1%8a%d1%80%d0%b3%d0%be%d0%b2%d0%b8%d1%8f/ → no x-content-type-options
    • https://topazmel.bg/%d0%bb%d0%be%d1%8f%d0%bb%d0%bd%d0%b0-%d0%bf%d1%80%d0%be%d0%b3%d1%80%d0%b0%d0%bc%d0%b0/ → no x-content-type-options
    • https://topazmel.bg/contacts/ → no x-content-type-options
    • https://topazmel.bg/home/%d0%be%d0%b1%d1%89%d0%b8-%d1%83%d1%81%d0%bb%d0%be%d0%b2%d0%b8%d1%8f/ → no x-content-type-options
    • https://topazmel.bg/en/ → no x-content-type-options
    • https://topazmel.bg/el/ → no x-content-type-options
    • https://topazmel.bg/product-showcase/home-products/ → no x-content-type-options
  • 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://topazmel.bg/ → no referrer-policy
    • https://topazmel.bg/about/ → no referrer-policy
    • https://topazmel.bg/products/ → no referrer-policy
    • https://topazmel.bg/%d1%81%d0%b5%d1%80%d1%82%d0%b8%d1%84%d0%b8%d0%ba%d0%b0%d1%82%d0%b8/ → no referrer-policy
    • https://topazmel.bg/raw-materials/ → no referrer-policy
    • https://topazmel.bg/%d1%82%d1%8a%d1%80%d0%b3%d0%be%d0%b2%d0%b8%d1%8f/ → no referrer-policy
    • https://topazmel.bg/%d0%bb%d0%be%d1%8f%d0%bb%d0%bd%d0%b0-%d0%bf%d1%80%d0%be%d0%b3%d1%80%d0%b0%d0%bc%d0%b0/ → no referrer-policy
    • https://topazmel.bg/contacts/ → no referrer-policy
    • https://topazmel.bg/home/%d0%be%d0%b1%d1%89%d0%b8-%d1%83%d1%81%d0%bb%d0%be%d0%b2%d0%b8%d1%8f/ → no referrer-policy
    • https://topazmel.bg/en/ → no referrer-policy
    • https://topazmel.bg/el/ → no referrer-policy
    • https://topazmel.bg/product-showcase/home-products/ → 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://topazmel.bg/ → no permissions-policy
    • https://topazmel.bg/about/ → no permissions-policy
    • https://topazmel.bg/products/ → no permissions-policy
    • https://topazmel.bg/%d1%81%d0%b5%d1%80%d1%82%d0%b8%d1%84%d0%b8%d0%ba%d0%b0%d1%82%d0%b8/ → no permissions-policy
    • https://topazmel.bg/raw-materials/ → no permissions-policy
    • https://topazmel.bg/%d1%82%d1%8a%d1%80%d0%b3%d0%be%d0%b2%d0%b8%d1%8f/ → no permissions-policy
    • https://topazmel.bg/%d0%bb%d0%be%d1%8f%d0%bb%d0%bd%d0%b0-%d0%bf%d1%80%d0%be%d0%b3%d1%80%d0%b0%d0%bc%d0%b0/ → no permissions-policy
    • https://topazmel.bg/contacts/ → no permissions-policy
    • https://topazmel.bg/home/%d0%be%d0%b1%d1%89%d0%b8-%d1%83%d1%81%d0%bb%d0%be%d0%b2%d0%b8%d1%8f/ → no permissions-policy
    • https://topazmel.bg/en/ → no permissions-policy
    • https://topazmel.bg/el/ → no permissions-policy
    • https://topazmel.bg/product-showcase/home-products/ → no permissions-policy
  • FoundCookie flagsMedium

    1 of 1 cookie are missing protective flags. Without HttpOnly a script can read the cookie; without Secure it travels over plain HTTP; without SameSite it is sent on cross-site requests.

    • _icl_current_language (set by https://topazmel.bg/) lacks Secure, HttpOnly, SameSite
  • FoundVulnerable JavaScript librariesMedium

    4 libraries with published vulnerabilities: jQuery 1.3.2, jQuery 1.9.1, jQuery UI 1.12.1, Bootstrap 4.1.3. Whether they are exploitable depends on how the site uses them, but each has a fixed release.

    • jQuery 1.3.2 in https://topazmel.bg/wp-content/themes/rttheme18/js/jquery.form.js?ver=7.1.2: CVE-2012-6708 (selector XSS), CVE-2015-9251, CVE-2019-11358, CVE-2020-11022, CVE-2020-11023; fixed in 3.5.0
    • jQuery 1.9.1 in https://www.topazmel.bg/master/data/js/bootstrap.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 UI 1.12.1 in https://www.topazmel.bg/master/data/js/jquery-ui.js: CVE-2021-41182, CVE-2021-41183, CVE-2021-41184, CVE-2022-31160 (XSS through widget options); fixed in 1.13.2
    • Bootstrap 4.1.3 in https://www.topazmel.bg/master/data/js/bootstrap.js: CVE-2018-14040, CVE-2018-14041, CVE-2018-14042, CVE-2019-8331 (XSS through data attributes in tooltip, popover, collapse and scrollspy); fixed in 4.3.1
  • FoundKeys and secrets in page codeMedium

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

    • Google API key AIzaSy…vw (39 chars) in https://topazmel.bg/contacts/: 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 2 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)
    • maps.googleapis.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/
5 checks passed
  • OKHTTPS

    All 237 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

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

  • OKExposed files and listings

    None of the crawled URLs is a configuration file, backup, dump, repository folder or directory listing.

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 topazmel.bg

No other scans of this site yet.

Sites scoring near topazmel.bg

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

Own topazmel.bg?