Scanned sites / seo.wrs.bg / 2026-11-11-1225

seo.wrs.bg scan from 2026-11-11 12:25:28 UTC DR 24

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

Scan 2026-11-11-1225

Scanned 2026-11-11 12:25:28 UTC, finished 2026-11-11 12:26:58 UTC. Found with 42backlinks.com tool directory

Site: https://seo.wrs.bg/

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

90/ 100Excellent

On November 11, 2026 the Site Spider crawled 79 pages and 15 assets of seo.wrs.bg, starting from https://seo.wrs.bg/. It scored 90 out of 100, an excellent result. 5 of 33 checks found something to fix, led by sitemap coverage (46), meta descriptions (30), title tags (23); 18 checks passed. Most of the points went to sitemap coverage (−3.5), meta descriptions (−3), title tags (−2.9). 10 checks found something the score does not count, listed as noted. 4 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, 2 low and 2 info findings. See the security findings ↓

Pages crawled
79
Assets fetched
15
Status
Completed
Checks with issues
5 of 33
CoverageComplete crawl

94 of 97 discovered URLs were fetched, 3 blocked by robots.txt. The crawl reached everything it found. HTML only: nothing here ran JavaScript. 3 link destinations on other sites were checked.

  • Title tags23 issues
    23 of 79 pages have title issues.
    −2.9 points
  • Meta descriptions30 issues
    30 of 79 pages have meta description issues.
    −3 points
  • HeadingsOK
    0 of 79 pages have heading issues.
  • Broken linksOK
    0 internal links point at 0 broken URLs.
  • Links to other sites77 noted
    0 destinations answered with an error, 1 could not be determined (timeouts, rate limits or refusals), of 3 destinations checked.
  • RedirectsOK
    0 redirecting URLs, 0 of them chained.
  • Non-200 responsesOK
    0 URLs did not return a 2xx response.
  • Rate limitedOK
    The site did not rate limit the crawler.
  • Indexability2 issues
    2 of 79 indexable pages have indexability warnings.
    −0.3 points
  • Image alt textOK
    0 of 10 image references have no alt attribute.
  • Heavy assetsOK
    0 assets larger than 500 KB among 15 fetched assets.
  • Orphan pagesOK
    0 pages have no internal links pointing at them.
  • Sitemap coverage46 issues
    1 sitemap listing 33 URLs: 46 crawled pages missing, 0 listed URLs broken or redirecting, 0 reachable only via the sitemap.
    −3.5 points
  • Internal link counts1 noted
    Internal link counts for 79 pages; 1 worth a look.
  • Thin content3 issues
    3 of 79 pages have fewer than 200 words.
    −0.3 points
  • Duplicate contentOK
    0 groups of pages with identical HTML.
  • URL formatOK
    All 79 page URLs are plain lowercase addresses without parameters.
  • Canonicals2 noted
    2 of 79 pages have a canonical worth checking.
  • Robots directives74 noted
    74 pages carry a robots directive; 5 carry none.
  • Anchor textOK
    Every internal link has descriptive, followed anchor text.
  • Title and heading structure16 noted
    16 of 79 pages could use the title, heading and snippet space better.
  • Image weight and alt length4 noted
    4 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 validationOK
    All 79 pages keep their head tags in <head>, once each, under Googlebot's 2 MB.
  • hreflang6 noted
    3 of 77 pages with hreflang have problems: 6 findings.
  • Structured data2 noted
    74 of 79 indexable pages carry structured data: Organization (74), WebSite (74), Article (70), SoftwareApplication (2), FAQPage (2). 2 pages with errors a rich result would fail on.
  • Near duplicatesOK
    No near duplicates among 76 pages with enough text to compare.
  • Soft 404sOK
    None of 79 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 positionsOK
    0 of 79 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 cookies1 noted
    2 cookies set by the site, 1 missing a protective flag; 7 response headers recorded across 94 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 79 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.
  • Spelling14 noted
    14 words an English dictionary does not know, on 16 pages. Product names and jargon will appear here too.

Where this scan sits among all scanned sites

2892 sites, median 80%, average 79%

seo.wrs.bg scores 90%, higher than 85% of the 2892 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%: 15 sites61%: 13 sites62%: 20 sites63%: 29 sites64%: 22 sites65%: 33 sites66%: 43 sites67%: 43 sites68%: 42 sites69%: 54 sites70%: 47 sites71%: 79 sites72%: 77 sites73%: 82 sites74%: 82 sites75%: 87 sites76%: 95 sites77%: 109 sites78%: 132 sites79%: 113 sites80%: 129 sites81%: 123 sites82%: 134 sites83%: 120 sites84%: 130 sites85%: 106 sites86%: 96 sites87%: 94 sites88%: 82 sites89%: 73 sites90%: 57 sites91%: 60 sites92%: 44 sites93%: 30 sites94%: 26 sites95%: 16 sites96%: 18 sites97%: 16 sites98%: 8 sites99%: 3 sites100%: 152 sites90% 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

The site has a solid health score, but there are critical improvements needed in titles, meta descriptions, and indexability. Implementing these changes will enhance your site's SEO performance significantly.

  1. 1

    Fix Title Tags

    Why: 23 pages have title issues affecting SEO.

    How: Customize or create unique titles for affected pages to meet SEO best practices.

    Evidence: 2 pages share the title "AI Results Tracker · Helpbook · WRS SEO", which usually means one template writes it for all of them.

    2 pages affected

    Depends on: If these pages really are the same content, the duplicate title is a symptom: canonicalise them to one URL instead.

    Checks: titles

  2. 2

    Improve Meta Descriptions

    Why: 30 pages have issues, impacting click-through rates.

    How: Write or update meta descriptions for pages missing them or with suboptimal lengths.

    Checks: meta-descriptions

  3. 3

    Resolve Indexability Warnings

    Why: 2 pages are flagged with no canonical, affecting indexing.

    How: Add canonical tags to the flagged pages to prevent indexing issues.

    Evidence: 2 pages flagged: No canonical.

    2 pages affected

    Depends on: Confirm the pages really share a cause before changing them together.

    Checks: indexability

  4. 4

    Enhance Sitemap Coverage

    Why: 46 crawled pages are missing from the sitemap, affecting discoverability.

    How: Update the sitemap to include all missing URLs for better indexation.

    Checks: sitemap-coverage

  5. 5

    Address Thin Content Issues

    Why: 3 pages have less than 200 words, possibly impacting quality perception.

    How: Add meaningful content to these pages to meet minimum word count requirements.

    Checks: thin-content

  6. 6

    Canonicalization of Duplicate Titles

    Why: Several pages share titles that may confuse search engines.

    How: Create canonical tags for duplicated titles if content is not unique.

    Checks: titles

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 risks that need attention. Key issues include the lack of headers for protection against attacks like clickjacking, MIME sniffing, and the absence of a Content Security Policy. Implementing these recommendations will enhance your site's security significantly.

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

    Missing HTTP Strict Transport Security (HSTS)Medium

    Why it matters: Without HSTS, users can be intercepted on their first request by typing the address without HTTPS.

    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 CSP allows unrestricted loading of scripts and resources, increasing the risk of XSS attacks.

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

    Evidence: Content Security Policy

  3. 3

    Missing X-Frame-Options for Clickjacking ProtectionMedium

    Why it matters: Pages can be embedded in frames on malicious sites, making users vulnerable to clickjacking.

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

    Evidence: Clickjacking protection

  4. 4

    Missing Cookie FlagsMedium

    Why it matters: Lack of flags like HttpOnly and Secure increases the risk of cookie theft and cross-site request forgery.

    Fix: Set cookie `wrs_ui_lang` with attributes: `HttpOnly; Secure; SameSite=Strict`.

    Evidence: Cookie flags

  5. 5

    Missing X-Content-Type-OptionsLow

    Why it matters: Without this, browsers may wrongly interpret files as scripts, potentially causing security issues.

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

    Evidence: MIME sniffing protection

  6. 6

    Missing Referrer-PolicyLow

    Why it matters: Without this policy, sensitive pages URLs may leak to third-party sites upon navigation.

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

    Evidence: Referrer policy

  7. 7

    Missing Permissions-PolicyInfo

    Why it matters: A Permissions-Policy can restrict browser features, which may mitigate risk from injected scripts.

    Fix: Add the header: `Permissions-Policy: interest-cohort=()`, or adjust as needed based on your site's features.

    Evidence: Permissions policy

  8. 8

    Sensitive paths in robots.txtInfo

    Why it matters: Listing private paths publicly can aid attackers in probing the site for vulnerabilities.

    Fix: Consider removing sensitive entries or securing them with proper access controls.

    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://seo.wrs.bg/ → no strict-transport-security
    • https://seo.wrs.bg/help → no strict-transport-security
    • https://seo.wrs.bg/privacy → no strict-transport-security
    • https://seo.wrs.bg/en → no strict-transport-security
    • https://seo.wrs.bg/help/project-overview → no strict-transport-security
    • https://seo.wrs.bg/help/rankings → no strict-transport-security
    • https://seo.wrs.bg/help/traffic-forecast → no strict-transport-security
    • https://seo.wrs.bg/help/traffic → no strict-transport-security
    • https://seo.wrs.bg/help/audit → no strict-transport-security
    • https://seo.wrs.bg/help/keywords → no strict-transport-security
    • https://seo.wrs.bg/help/competitors → no strict-transport-security
    • https://seo.wrs.bg/help/ai-tracker → no strict-transport-security
  • FoundContent Security PolicyMedium

    None of the 79 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://seo.wrs.bg/ → no content-security-policy
    • https://seo.wrs.bg/help → no content-security-policy
    • https://seo.wrs.bg/privacy → no content-security-policy
    • https://seo.wrs.bg/en → no content-security-policy
    • https://seo.wrs.bg/help/project-overview → no content-security-policy
    • https://seo.wrs.bg/help/rankings → no content-security-policy
    • https://seo.wrs.bg/help/traffic-forecast → no content-security-policy
    • https://seo.wrs.bg/help/traffic → no content-security-policy
    • https://seo.wrs.bg/help/audit → no content-security-policy
    • https://seo.wrs.bg/help/keywords → no content-security-policy
    • https://seo.wrs.bg/help/competitors → no content-security-policy
    • https://seo.wrs.bg/help/ai-tracker → 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://seo.wrs.bg/ → no x-frame-options
    • https://seo.wrs.bg/help → no x-frame-options
    • https://seo.wrs.bg/privacy → no x-frame-options
    • https://seo.wrs.bg/en → no x-frame-options
    • https://seo.wrs.bg/help/project-overview → no x-frame-options
    • https://seo.wrs.bg/help/rankings → no x-frame-options
    • https://seo.wrs.bg/help/traffic-forecast → no x-frame-options
    • https://seo.wrs.bg/help/traffic → no x-frame-options
    • https://seo.wrs.bg/help/audit → no x-frame-options
    • https://seo.wrs.bg/help/keywords → no x-frame-options
    • https://seo.wrs.bg/help/competitors → no x-frame-options
    • https://seo.wrs.bg/help/ai-tracker → 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://seo.wrs.bg/ → no x-content-type-options
    • https://seo.wrs.bg/help → no x-content-type-options
    • https://seo.wrs.bg/privacy → no x-content-type-options
    • https://seo.wrs.bg/en → no x-content-type-options
    • https://seo.wrs.bg/help/project-overview → no x-content-type-options
    • https://seo.wrs.bg/help/rankings → no x-content-type-options
    • https://seo.wrs.bg/help/traffic-forecast → no x-content-type-options
    • https://seo.wrs.bg/help/traffic → no x-content-type-options
    • https://seo.wrs.bg/help/audit → no x-content-type-options
    • https://seo.wrs.bg/help/keywords → no x-content-type-options
    • https://seo.wrs.bg/help/competitors → no x-content-type-options
    • https://seo.wrs.bg/help/ai-tracker → 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://seo.wrs.bg/ → no referrer-policy
    • https://seo.wrs.bg/help → no referrer-policy
    • https://seo.wrs.bg/privacy → no referrer-policy
    • https://seo.wrs.bg/en → no referrer-policy
    • https://seo.wrs.bg/help/project-overview → no referrer-policy
    • https://seo.wrs.bg/help/rankings → no referrer-policy
    • https://seo.wrs.bg/help/traffic-forecast → no referrer-policy
    • https://seo.wrs.bg/help/traffic → no referrer-policy
    • https://seo.wrs.bg/help/audit → no referrer-policy
    • https://seo.wrs.bg/help/keywords → no referrer-policy
    • https://seo.wrs.bg/help/competitors → no referrer-policy
    • https://seo.wrs.bg/help/ai-tracker → 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://seo.wrs.bg/ → no permissions-policy
    • https://seo.wrs.bg/help → no permissions-policy
    • https://seo.wrs.bg/privacy → no permissions-policy
    • https://seo.wrs.bg/en → no permissions-policy
    • https://seo.wrs.bg/help/project-overview → no permissions-policy
    • https://seo.wrs.bg/help/rankings → no permissions-policy
    • https://seo.wrs.bg/help/traffic-forecast → no permissions-policy
    • https://seo.wrs.bg/help/traffic → no permissions-policy
    • https://seo.wrs.bg/help/audit → no permissions-policy
    • https://seo.wrs.bg/help/keywords → no permissions-policy
    • https://seo.wrs.bg/help/competitors → no permissions-policy
    • https://seo.wrs.bg/help/ai-tracker → no permissions-policy
  • FoundCookie flagsMedium

    1 of 2 cookies 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.

    • wrs_ui_lang (set by https://seo.wrs.bg/en) lacks HttpOnly
  • 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: /login
7 checks passed, 1 not applicable
  • OKHTTPS

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

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

  • OKThird-party scripts

    The sampled pages load no scripts from other domains.

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

Own seo.wrs.bg?