Scanned sites / seo.wrs.bg / 2026-10-27-1147

seo.wrs.bg scan from 2026-10-27 11:47:20 UTC DR 24

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

Scan 2026-10-27-1147

Scanned 2026-10-27 11:47:20 UTC, finished 2026-10-27 11:49:16 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 October 27, 2026 the Site Spider crawled 77 pages and 14 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 (44), meta descriptions (28), title tags (22); 18 checks passed. Most of the points went to sitemap coverage (−3.4), title tags (−2.9), meta descriptions (−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
77
Assets fetched
14
Status
Completed
Checks with issues
5 of 33
CoverageComplete crawl

91 of 94 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 tags22 issues
    22 of 77 pages have title issues.
    −2.9 points
  • Meta descriptions28 issues
    28 of 77 pages have meta description issues.
    −2.9 points
  • HeadingsOK
    0 of 77 pages have heading issues.
  • Broken linksOK
    0 internal links point at 0 broken URLs.
  • Links to other sitesOK
    0 destinations answered with an error, 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 77 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 14 fetched assets.
  • Orphan pagesOK
    0 pages have no internal links pointing at them.
  • Sitemap coverage44 issues
    1 sitemap listing 33 URLs: 44 crawled pages missing, 0 listed URLs broken or redirecting, 0 reachable only via the sitemap.
    −3.4 points
  • Internal link counts1 noted
    Internal link counts for 77 pages; 1 worth a look.
  • Thin content3 issues
    3 of 77 pages have fewer than 200 words.
    −0.3 points
  • Duplicate contentOK
    0 groups of pages with identical HTML.
  • URL formatOK
    All 77 page URLs are plain lowercase addresses without parameters.
  • Canonicals2 noted
    2 of 77 pages have a canonical worth checking.
  • Robots directives74 noted
    74 pages carry a robots directive; 3 carry none.
  • Anchor textOK
    Every internal link has descriptive, followed anchor text.
  • Title and heading structure16 noted
    16 of 77 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 77 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 77 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 74 pages with enough text to compare.
  • Soft 404sOK
    None of 77 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 positions2 noted
    2 of 77 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 91 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 77 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.
  • Spelling13 noted
    13 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

2328 sites, median 79%, average 78%

seo.wrs.bg scores 90%, higher than 89% of the 2328 scanned sites. See the full ranking.

0581150%: 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%: 19 sites63%: 27 sites64%: 22 sites65%: 32 sites66%: 35 sites67%: 35 sites68%: 34 sites69%: 47 sites70%: 44 sites71%: 69 sites72%: 71 sites73%: 69 sites74%: 68 sites75%: 72 sites76%: 87 sites77%: 92 sites78%: 106 sites79%: 85 sites80%: 107 sites81%: 105 sites82%: 115 sites83%: 99 sites84%: 107 sites85%: 85 sites86%: 69 sites87%: 75 sites88%: 59 sites89%: 63 sites90%: 34 sites91%: 47 sites92%: 38 sites93%: 24 sites94%: 16 sites95%: 11 sites96%: 10 sites97%: 12 sites98%: 4 sites99%: 2 sites100%: 69 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

There are several key issues to address, primarily around titles and meta descriptions, which could improve your site's SEO performance. Prioritize fixing the identified problems to enhance visibility and user experience.

  1. 1

    Fix Duplicate Title Tags

    Why: Duplicate titles can confuse search engines and dilute page relevance.

    How: Assign unique titles for each affected page. Review each page's content and set descriptive, individual titles based on their unique focus.

    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 Missing Meta Descriptions

    Why: Meta descriptions improve click-through rates and provide essential info in search results.

    How: Create unique, engaging meta descriptions for the pages missing them. Keep under 160 characters and summarize the page content accurately.

    Evidence: 3 pages have no meta description at all.

    3 pages affected

    Checks: meta-descriptions

  3. 3

    Resolve Indexability Warnings

    Why: Proper indexability ensures that search engines can effectively crawl and rank pages.

    How: Add canonical tags to the pages flagged with 'No canonical' to prevent duplication and clarify the primary source.

    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

    Update Sitemap Coverage

    Why: Including all pages in your sitemap improves discovery and indexing by search engines.

    How: Add the 44 missing pages to your sitemap. Regularly update the sitemap to reflect all crawled URLs.

    Evidence: 44 URLs: not in sitemap.

    44 pages affected

    Checks: sitemap-coverage

  5. 5

    Enhance Thin Content Pages

    Why: Thin content can adversely affect rankings and user engagement.

    How: Expand the content on the three identified pages to meet or exceed 200 words. Aim to provide valuable information relevant to visitors.

    Checks: thin-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 important security headers, making it vulnerable to various attacks. Key issues include missing HTTP Strict Transport Security, Content Security Policy, and cookie protections. Implementing these security features can greatly improve your website's resilience against threats.

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

    Missing HTTP Strict Transport Security (HSTS)Medium

    Why it matters: Without HSTS, visitors may be intercepted on the first request to your site via non-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: No CSP allows unrestricted loading of scripts, styles, and frames, increasing XSS risk.

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

    Evidence: Content Security Policy

  3. 3

    Missing X-Frame-Options HeaderMedium

    Why it matters: Absence of X-Frame-Options allows clickjacking attacks by embedding your pages in iframes.

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

    Evidence: Clickjacking protection

  4. 4

    Missing Cookie FlagsMedium

    Why it matters: Cookies lacking flags are vulnerable to access from scripts and insecure transmission.

    Fix: Set HttpOnly and Secure flags for the wrs_ui_lang cookie, and SameSite attribute: SameSite=Lax.

    Evidence: Cookie flags

  5. 5

    Missing X-Content-Type-Options HeaderLow

    Why it matters: Lacking this header could lead to browsers misinterpreting files as scripts.

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

    Evidence: MIME sniffing protection

  6. 6

    Missing Referrer-Policy HeaderLow

    Why it matters: Not sending a referrer policy can expose full URLs of your pages.

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

    Evidence: Referrer policy

  7. 7

    Missing Permissions-Policy HeaderInfo

    Why it matters: Lack of this header exposes browser features that could be abused by malicious scripts.

    Fix: Add the header: Permissions-Policy: geolocation=(self)

    Evidence: Permissions policy

  8. 8

    Sensitive Paths in robots.txtInfo

    Why it matters: Sensitive paths may aid attackers in probing your site since robots.txt is public.

    Fix: Consider restricting access to sensitive paths like /login with proper access control.

    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/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
    • https://seo.wrs.bg/help/share-of-voice → no strict-transport-security
  • FoundContent Security PolicyMedium

    None of the 77 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/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
    • https://seo.wrs.bg/help/share-of-voice → 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/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
    • https://seo.wrs.bg/help/share-of-voice → 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/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
    • https://seo.wrs.bg/help/share-of-voice → 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/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
    • https://seo.wrs.bg/help/share-of-voice → 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/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
    • https://seo.wrs.bg/help/share-of-voice → 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 77 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

    5 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?