Scanned sites / seo.wrs.bg / 2026-10-30-1149
seo.wrs.bg scan from 2026-10-30 11:49:34 UTC DR 24
DR is Ahrefs Domain Rating (0-100, backlink strength), used under its Domain Rating License.
Scan 2026-10-30-1149
Scanned 2026-10-30 11:49:34 UTC, finished 2026-10-30 11:52:40 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.
On October 30, 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
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 issues22 of 77 pages have title issues.−2.9 points
- Meta descriptions28 issues28 of 77 pages have meta description issues.−2.9 points
- HeadingsOK0 of 77 pages have heading issues.
- Broken linksOK0 internal links point at 0 broken URLs.
- Links to other sitesOK0 destinations answered with an error, of 3 destinations checked.
- RedirectsOK0 redirecting URLs, 0 of them chained.
- Non-200 responsesOK0 URLs did not return a 2xx response.
- Rate limitedOKThe site did not rate limit the crawler.
- Indexability2 issues2 of 77 indexable pages have indexability warnings.−0.3 points
- Image alt textOK0 of 10 image references have no alt attribute.
- Heavy assetsOK0 assets larger than 500 KB among 14 fetched assets.
- Orphan pagesOK0 pages have no internal links pointing at them.
- Sitemap coverage44 issues1 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 notedInternal link counts for 77 pages; 1 worth a look.
- Thin content3 issues3 of 77 pages have fewer than 200 words.−0.3 points
- Duplicate contentOK0 groups of pages with identical HTML.
- URL formatOKAll 77 page URLs are plain lowercase addresses without parameters.
- Canonicals2 noted2 of 77 pages have a canonical worth checking.
- Robots directives74 noted74 pages carry a robots directive; 3 carry none.
- Anchor textOKEvery internal link has descriptive, followed anchor text.
- Title and heading structure16 noted16 of 77 pages could use the title, heading and snippet space better.
- Image weight and alt length4 noted4 images over 100 KB; 0 with alt text over 100 characters.
- Response anomaliesOKNo redirect loops, header redirects or pages served as something other than HTML.
- HTML and head validationOKAll 77 pages keep their head tags in <head>, once each, under Googlebot's 2 MB.
- hreflang6 noted3 of 77 pages with hreflang have problems: 6 findings.
- Structured data2 noted74 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 duplicatesOKNo near duplicates among 74 pages with enough text to compare.
- Soft 404sOKNone of 77 pages answering 200 reads like an error page.
- AccessibilityNot checkedNot checked: the accessibility audit runs in the browser. Tick "Include JavaScript rendering checks" when you request a scan to run it.
- Link positions2 noted2 of 77 linked pages are linked only from the template, never from another page's content.
- PaginationOKNo page declares rel=next or rel=prev pagination.
- Headers and cookies1 noted2 cookies set by the site, 1 missing a protective flag; 7 response headers recorded across 91 URLs.
- Orphans in searchNot checkedNot checked: import a Search Console Pages export on the scan page to find pages Google shows that the site does not link to.
- Link ScoreOKLink Score (internal PageRank, 0-100) for 77 pages; 0 hold almost none (10 or less).
- JavaScript renderingNot checkedNot 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 checkedNot checked yet: PageSpeed Insights runs on the top pages once the crawl has finished.
- Spelling13 noted13 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
2346 sites, median 79%, average 78%
seo.wrs.bg scores 90%, higher than 88% of the 2346 scanned sites. See the full ranking.
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...
Fix plan
Written by gpt-4o-mini from the scan findingsYour site has issues with title tags, meta descriptions, indexability, and sitemap coverage. Prioritize optimizing these elements to enhance SEO performance.
- 1
Fix Title Tags
Why: 22 pages have title issues affecting SEO.
How: Assign unique titles to pages currently sharing titles and ensure they comply with length guidelines.
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
Revise Meta Descriptions
Why: 28 pages have meta description issues that can hinder click-through rates.
How: Create and optimize meta descriptions for pages lacking them and adjust those that are too short.
Evidence: 3 pages have no meta description at all.
3 pages affected
Checks: meta-descriptions
- 3
Resolve Indexability Warnings
Why: 2 pages lack canonical tags, which can cause indexing issues.
How: Implement a canonical tag for the identified pages to improve indexing.
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
Update Sitemap Coverage
Why: 44 crawled pages are not listed in the sitemap, potentially missing traffic.
How: Add the missing pages to the sitemap to ensure search engines index all relevant content.
Evidence: 44 URLs: not in sitemap.
44 pages affected
Checks: sitemap-coverage
- 5
Enhance Thin Content
Why: 3 pages with less than 200 words can limit visibility.
How: Add more relevant content to these pages to meet or exceed the 200-word minimum.
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 crawlThis review highlights several security vulnerabilities in your website that could expose users and data. Key areas of concern include missing security headers, which can increase the risk of attacks such as data interception and clickjacking. Addressing these issues will enhance your site's resilience and protect user information.
- 0 high
- 4 medium
- 2 low
- 2 info
- 1
Missing HTTP Strict Transport Security (HSTS)Medium
Why it matters: Lack of HSTS can allow interception of unencrypted connections.
Fix: Add 'Strict-Transport-Security: max-age=63072000; includeSubDomains' to response headers.
Evidence: HTTP Strict Transport Security
- 2
Missing Content Security Policy (CSP)Medium
Why it matters: Absence of CSP allows unrestricted resource loading, increasing risk of XSS.
Fix: Implement 'Content-Security-Policy: default-src 'self'' in your headers.
Evidence: Content Security Policy
- 3
Missing X-Frame-Options HeaderMedium
Why it matters: Without it, the site is vulnerable to clickjacking attacks.
Fix: Add 'X-Frame-Options: DENY' to response headers.
Evidence: Clickjacking protection
- 4
Missing Cookie FlagsMedium
Why it matters: Cookies lacking flags can be read by scripts or sent insecurely.
Fix: Set HttpOnly, Secure, and SameSite attributes for cookies.
Evidence: Cookie flags
- 5
Missing X-Content-Type-Options HeaderLow
Why it matters: Lack of this header can lead to content type sniffing issues.
Fix: Include 'X-Content-Type-Options: nosniff' in your headers.
Evidence: MIME sniffing protection
- 6
Missing Referrer Policy HeaderLow
Why it matters: Without a Referrer-Policy, sensitive information may be exposed.
Fix: Add 'Referrer-Policy: no-referrer' to response headers.
Evidence: Referrer policy
- 7
Missing Permissions Policy HeaderInfo
Why it matters: This header controls feature access and can limit attack vectors.
Fix: Implement 'Permissions-Policy: geolocation=(self), microphone=()' to reduce risks.
Evidence: Permissions policy
- 8
Sensitive Paths in robots.txtInfo
Why it matters: Public paths in robots.txt can help attackers discover sensitive areas.
Fix: Consider implementing access controls for sensitive areas listed in robots.txt.
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.
- calgaryoptometry.comDR 1391/100 · rank 191 · 170 pages
- orchardvetcare.caDR 1191/100 · rank 191 · 50 pages
- www.gcoc.caDR 3890/100 · rank 238 · 163 pages
- www.oxydermlaserclinic.caDR 290/100 · rank 238 · 254 pages
- laroucheraymond.comDR 090/100 · rank 238 · 1,142 pages
- www.richmonddentalcalgary.comDR 1190/100 · rank 238 · 125 pages
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?
- 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 seo.wrs.bg. Removal needs no account and no proof of purchase.