Scanned sites / beeg.com / 2026-09-28-0119

beeg.com scan from 9/28/2026, 1:19:58 AM

Scan 2026-09-28-0119

Scanned 9/28/2026, 1:19:58 AM, finished 9/28/2026, 2:18:21 AM

Site: https://beeg.com/

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

38/ 100Poor

On September 28, 2026 the Site Spider crawled 5000 pages and 8 assets of beeg.com, starting from https://beeg.com/. It scored 38 out of 100, a poor result. 9 of 15 checks found something to fix, led by title tags (4,999), indexability (4,999), meta descriptions (4,999); 3 checks passed. Most of the points went to title tags (−10), indexability (−10), meta descriptions (−8). 3 checks found something the score does not count, listed as noted. 1 check was not run because the crawl fetched nothing for it. 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: Medium3 medium, 2 low and 1 info findings. See the security findings ↓

Pages crawled
5000
Assets fetched
8
Status
Completed
Checks with issues
9 of 15
CoverageComplete crawl

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

  • Title tags4,999 issues
    4999 of 4999 pages have title issues.
    −10 points
  • Meta descriptions4,999 issues
    4999 of 4999 pages have meta description issues.
    −8 points
  • Headings4,999 issues
    4999 of 4999 pages have heading issues.
    −6 points
  • 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.
  • Redirects1 noted
    1 redirecting URL, 0 of them chained.
  • Non-200 responses1 noted
    1 URL did not return a 2xx response. 1 of them is a page, 0 with an error status; the rest are assets or redirects.
  • Rate limitedOK
    The site did not rate limit the crawler.
  • Indexability4,999 issues
    4999 of 4999 indexable pages have indexability warnings.
    −10 points
  • Image alt textOK
    0 of 0 image references have no alt attribute.
  • Heavy assets3 issues
    3 assets larger than 500 KB among 8 fetched assets.
    −1.8 points
  • Orphan pages4,998 issues
    4998 pages have no internal links pointing at them.
    −4 points
  • Sitemap coverage4,999 issues
    1 sitemap listing 4999 URLs: 1 crawled page missing, 1 listed URL broken or redirecting, 4997 reachable only via the sitemap.
    −6 points
  • Internal link countsOK
    Internal link counts for 500 pages.
  • Thin content4,999 issues
    4999 of 4999 pages have fewer than 200 words.
    −8 points
  • Duplicate content4,999 issues
    1 group of pages with identical HTML.
    −8 points

Where this scan sits among all scanned sites

1689 sites, median 80%, average 79%

beeg.com scores 38%, higher than 0% of the 1689 scanned sites. See the full ranking.

0511020%: 0 sites1%: 0 sites2%: 0 sites3%: 0 sites4%: 0 sites5%: 0 sites6%: 0 sites7%: 0 sites8%: 0 sites9%: 0 sites10%: 0 sites11%: 0 sites12%: 0 sites13%: 0 sites14%: 0 sites15%: 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%: 1 site37%: 2 sites38%: 2 sites39%: 0 sites40%: 2 sites41%: 1 site42%: 0 sites43%: 1 site44%: 0 sites45%: 3 sites46%: 2 sites47%: 3 sites48%: 2 sites49%: 5 sites50%: 3 sites51%: 5 sites52%: 7 sites53%: 6 sites54%: 7 sites55%: 4 sites56%: 5 sites57%: 6 sites58%: 11 sites59%: 6 sites60%: 9 sites61%: 11 sites62%: 15 sites63%: 15 sites64%: 10 sites65%: 19 sites66%: 19 sites67%: 32 sites68%: 26 sites69%: 24 sites70%: 38 sites71%: 37 sites72%: 48 sites73%: 46 sites74%: 47 sites75%: 53 sites76%: 66 sites77%: 60 sites78%: 78 sites79%: 61 sites80%: 82 sites81%: 102 sites82%: 80 sites83%: 78 sites84%: 73 sites85%: 59 sites86%: 60 sites87%: 54 sites88%: 59 sites89%: 49 sites90%: 32 sites91%: 34 sites92%: 22 sites93%: 11 sites94%: 12 sites95%: 7 sites96%: 7 sites97%: 8 sites98%: 2 sites99%: 2 sites100%: 54 sites38% 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 website has several critical SEO issues affecting its health score. Prioritizing fixes like title tags, meta descriptions, and indexability can significantly improve visibility and ranking.

  1. 1

    Fix Title Tags

    Why: 4999 pages share the same title, hurting SEO.

    How: Assign unique, descriptive titles to each page.

    Checks: titles

  2. 2

    Add Meta Descriptions

    Why: Lack of meta descriptions affects click-through rates.

    How: Create unique meta descriptions for all pages.

    Checks: meta-descriptions

  3. 3

    Include H1 Headings

    Why: Missing H1 tags on all pages impacts content clarity.

    How: Add relevant H1 headings to each page.

    Checks: headings

  4. 4

    Resolve Indexability Issues

    Why: No canonical tags on pages complicate indexing.

    How: Implement appropriate canonical tags to avoid confusion.

    Checks: indexability

  5. 5

    Improve Sitemap Coverage

    Why: Pages missing from the sitemap limit their visibility.

    How: Update the sitemap to include all indexable pages.

    Checks: sitemap-coverage

  6. 6

    Shrink Heavy Assets

    Why: Large assets can slow down your site and affect user experience.

    How: Optimize or reduce the size of heavy assets served to users.

    Checks: heavy-assets

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 is missing crucial security headers that protect users from various attacks. Implementing these headers can significantly enhance your site's security and user privacy.

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

    Missing HTTP Strict Transport SecurityMedium

    Why it matters: Without HSTS, visitors typing the site’s address without HTTPS could be intercepted.

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

    Evidence: HTTP Strict Transport Security

  2. 2

    Missing Content Security PolicyMedium

    Why it matters: The absence of a CSP allows any scripts and styles to load, increasing risks of XSS attacks.

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

    Evidence: Content Security Policy

  3. 3

    Missing X-Frame-OptionsMedium

    Why it matters: Without X-Frame-Options, clickjacking attacks can occur, allowing other sites to embed your pages.

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

    Evidence: Clickjacking protection

  4. 4

    Missing X-Content-Type-OptionsLow

    Why it matters: Without this option, browsers may execute files as scripts based on their content, leading to risks.

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

    Evidence: MIME sniffing protection

  5. 5

    Missing Referrer PolicyLow

    Why it matters: Lack of a Referrer-Policy can expose users' previous page URLs to third-party sites.

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

    Evidence: Referrer policy

  6. 6

    Missing Permissions PolicyInfo

    Why it matters: Not configuring Permissions Policy can leave browser features available to potentially malicious scripts.

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

    Evidence: Permissions 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://beeg.com/ → no strict-transport-security
    • https://beeg.com/0093999 → no strict-transport-security
    • https://beeg.com/0791742575 → no strict-transport-security
    • https://beeg.com/1000Facials → no strict-transport-security
    • https://beeg.com/101074117 → no strict-transport-security
    • https://beeg.com/1027897 → no strict-transport-security
    • https://beeg.com/1055460 → no strict-transport-security
    • https://beeg.com/1080p → no strict-transport-security
    • https://beeg.com/1160635 → no strict-transport-security
    • https://beeg.com/1229201 → no strict-transport-security
    • https://beeg.com/1242624 → no strict-transport-security
    • https://beeg.com/1262300 → no strict-transport-security
  • FoundContent Security PolicyMedium

    None of the 4999 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://beeg.com/ → no content-security-policy
    • https://beeg.com/0093999 → no content-security-policy
    • https://beeg.com/0791742575 → no content-security-policy
    • https://beeg.com/1000Facials → no content-security-policy
    • https://beeg.com/101074117 → no content-security-policy
    • https://beeg.com/1027897 → no content-security-policy
    • https://beeg.com/1055460 → no content-security-policy
    • https://beeg.com/1080p → no content-security-policy
    • https://beeg.com/1160635 → no content-security-policy
    • https://beeg.com/1229201 → no content-security-policy
    • https://beeg.com/1242624 → no content-security-policy
    • https://beeg.com/1262300 → 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://beeg.com/ → no x-frame-options
    • https://beeg.com/0093999 → no x-frame-options
    • https://beeg.com/0791742575 → no x-frame-options
    • https://beeg.com/1000Facials → no x-frame-options
    • https://beeg.com/101074117 → no x-frame-options
    • https://beeg.com/1027897 → no x-frame-options
    • https://beeg.com/1055460 → no x-frame-options
    • https://beeg.com/1080p → no x-frame-options
    • https://beeg.com/1160635 → no x-frame-options
    • https://beeg.com/1229201 → no x-frame-options
    • https://beeg.com/1242624 → no x-frame-options
    • https://beeg.com/1262300 → 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://beeg.com/ → no x-content-type-options
    • https://beeg.com/0093999 → no x-content-type-options
    • https://beeg.com/0791742575 → no x-content-type-options
    • https://beeg.com/1000Facials → no x-content-type-options
    • https://beeg.com/101074117 → no x-content-type-options
    • https://beeg.com/1027897 → no x-content-type-options
    • https://beeg.com/1055460 → no x-content-type-options
    • https://beeg.com/1080p → no x-content-type-options
    • https://beeg.com/1160635 → no x-content-type-options
    • https://beeg.com/1229201 → no x-content-type-options
    • https://beeg.com/1242624 → no x-content-type-options
    • https://beeg.com/1262300 → 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://beeg.com/ → no referrer-policy
    • https://beeg.com/0093999 → no referrer-policy
    • https://beeg.com/0791742575 → no referrer-policy
    • https://beeg.com/1000Facials → no referrer-policy
    • https://beeg.com/101074117 → no referrer-policy
    • https://beeg.com/1027897 → no referrer-policy
    • https://beeg.com/1055460 → no referrer-policy
    • https://beeg.com/1080p → no referrer-policy
    • https://beeg.com/1160635 → no referrer-policy
    • https://beeg.com/1229201 → no referrer-policy
    • https://beeg.com/1242624 → no referrer-policy
    • https://beeg.com/1262300 → 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://beeg.com/ → no permissions-policy
    • https://beeg.com/0093999 → no permissions-policy
    • https://beeg.com/0791742575 → no permissions-policy
    • https://beeg.com/1000Facials → no permissions-policy
    • https://beeg.com/101074117 → no permissions-policy
    • https://beeg.com/1027897 → no permissions-policy
    • https://beeg.com/1055460 → no permissions-policy
    • https://beeg.com/1080p → no permissions-policy
    • https://beeg.com/1160635 → no permissions-policy
    • https://beeg.com/1229201 → no permissions-policy
    • https://beeg.com/1242624 → no permissions-policy
    • https://beeg.com/1262300 → no permissions-policy
7 checks passed, 3 not applicable
  • OKHTTPS

    All 4999 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.

  • 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

    Scripts from 1 other domain all carry Subresource Integrity hashes.

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

Their neighbours in the SEO rank table, which orders every scanned site by health score.

This report was produced by the DIY SEO Hub Site Spider crawling beeg.com from its pages as published, the way a search engine does. It shows summary figures only.

Own beeg.com?

beeg.com scan 2026-09-28-0119 | DIY SEO Hub