Owner tools

For the owner of web3vacancy (web3vacancy.com).

Ownership

This launch is unclaimed.

Claim this launch to get an owner link, re-scan after fixes, track your score improvements, or remove your site from StackScope entirely.

Claim this launch

Fixes that improve your score

Security

HIGHAdd the missing security response headers
Missing: Permissions-Policy, Strict-Transport-Security
WhyEach header limits a class of browser-side attack: clickjacking, XSS, MIME sniffing, plaintext fallback. Missing headers leave default-permissive behaviour in place.
WhereMost are one line each in your server config, reverse proxy, CDN, or framework headers.
Learn more
Why this matters & sources
Per-header consequence:
- Strict-Transport-Security: Tells browsers to only ever load your site over HTTPS, even if a user types the URL without https://. Without it, a first-visit on coffee-shop wifi can be silently downgraded to HTTP and intercepted.
- Permissions-Policy: Turns off browser features your site doesn't use (camera, microphone, geolocation, payment) so an injected script can't trigger them.

Optional improvements

These don't change your StackScope score but cover SEO, agent-readiness, security-researcher discoverability, and compliance items worth addressing.

Security

LOWAdd /.well-known/security.txt
WhyLets security researchers report vulnerabilities responsibly through a published contact channel.
WhereCreate /.well-known/security.txt with a Contact: email and Expires: date.
Learn more

Legal & compliance

HIGHAdd a cookie-consent banner
Analytics detected on this site without a consent manager.
WhyUK/EU GDPR requires opt-in before analytics scripts fire; about half of US state privacy laws now require honouring the Global Privacy Control browser signal as a universal opt-out.
WhereDrop in Cookiebot, Usercentrics, Osano, or Iubenda Consent, or hand-roll a banner plus Google's Consent Mode v2.
Learn more
Why this matters & sources
The legal landscape: UK/EU GDPR treats analytics as personal-data processing that requires opt-in consent before scripts fire. About half the US state privacy laws now in force (California, Colorado, Texas, Connecticut, Oregon, Montana, Delaware, New Hampshire, New Jersey, Nebraska) require honouring the Global Privacy Control (GPC) browser signal as a universal opt-out, and California's January 2026 regulations require visibly indicating when a GPC signal has been honoured.
Sources: IAPP US state privacy tracker (iapp.org/resources/article/us-state-privacy-legislation-tracker), California AG on GPC (oag.ca.gov/privacy/ccpa/gpc), EDPB consent guidelines (edpb.europa.eu).

Email security

LOWAdd MTA-STS
No MTA-STS DNS record published.
WhyPrevents mail to your domain being downgraded to plaintext mid-flight by a network attacker. Most launches don't have this, so deploying it puts you a tier above generic email-security checks.
WherePublish a TXT record at _mta-sts.{your-domain} plus a policy file at https://mta-sts.{your-domain}/.well-known/mta-sts.txt.
Learn more
LOWAdd a TLS-RPT record
No TLS-RPT record at _smtp._tls.{domain}.
WhyReceivers can tell you when STARTTLS handshakes to your mail server fail. Without it, silent TLS failures are invisible.
WherePublish one TXT record at _smtp._tls.{your-domain} like v=TLSRPTv1; rua=mailto:[email protected].
Learn more

Page basics & SEO

LOWTrim your <title> tag to under 60 characters
Currently 72 characters: "Web3 Jobs & Crypto Jobs — #1 Blockchain Job Board 2026 | Web3Vacancy"
WhyGoogle truncates titles around 60 characters in search results, so anything past that gets cut off mid-sentence and costs click-through rate.
WhereAim for 50-60 characters that include your main keyword and brand.
Learn more
LOWTrim your meta description to under 160 characters
Currently 198 characters: "Browse 2,400+ web3 jobs and crypto jobs at top blockchain protocols, DAOs & DeFi projects. The #1 web3 job board for Solidity, Rust, ZK, and remote blockchain careers. New crypto job listings daily."
WhyGoogle truncates around 155-160 characters on desktop SERPs (less on mobile), so anything past that won't appear in the snippet.
WhereEdit your <meta name="description"> tag. Put the most click-worthy phrase first.
Learn more

Performance

MEDIUMSet width and height on your images
487 images render without explicit width/height.
WhyWithout intrinsic dimensions the browser can't reserve space before the image loads, so content jumps as it arrives (cumulative layout shift).
WhereAdd width and height attributes (or an aspect-ratio CSS rule). Framework image components set these for you.
Learn more
LOWServe right-sized images
408 images are downloaded at more than twice the displayed size.
WhyShipping a 2000px image into a 400px slot wastes bandwidth and slows loading, especially on mobile.
WhereResize to the displayed dimensions, or use srcset/sizes (or a framework image component) to serve per-viewport variants.
Learn more
LOWAdd alt text to your images
62 images have no alt attribute.
WhyScreen-reader users get no description, and search engines lose a signal about the image content.
WhereAdd a concise alt="..." to each image (an empty alt="" is correct only for purely decorative images).
Learn more

Agent / AI

LOWDeclare a Content-Signal in robots.txt
WhyStates how you'd like AI systems to use your content (training, search, agent input). Without it, AI crawlers fall back to whatever default policy each vendor applies.
WhereAdd a Content-Signal: line to your robots.txt.
Learn more
LOWAdd Link response headers
WhyLets agents discover your sitemap, privacy policy, and docs without parsing HTML, which most lightweight agents skip.
WhereSet Link: response headers in your server config or framework middleware.
Learn more

If a tip looks wrong (for example it says "add a consent banner" and you already have one) the detection's the bug, not you. StackScope sees what's public from the outside: HTTP response, rendered HTML, cookies, and DNS. We can miss vendors that load behind consent, are self-hosted, or use an install shape we haven't fingerprinted yet. Email [email protected] and we'll look into it.

Copy into Cursor, Claude, or ChatGPT

This prompt includes the detected stack and only the fixes StackScope found. It asks the AI to make concrete file-level changes, not a vague website review.

Score-affecting basics only. Ask your AI to handle these first; come back for the optional hardening once they're done.

Everything: score-affecting fixes plus optional email security, agent metadata, and best-practice items. Longer prompt, more for an "all in one" agent run.

I own https://web3vacancy.com. StackScope (https://stackscope.dev) analysed it on 4 June 2026 and scored it 9.1/10 against their production-readiness checklist. Please help me apply the fixes below. These are the score-affecting basics. We'll circle back to the optional hardening (email security, advanced agent metadata) later.

Tech stack StackScope detected on the site (use this when suggesting where each fix lives in the codebase):
amazon-ses, amplitude, cloudflare, cloudflare-bot-management, cloudflare-dns, coinzilla, google-analytics, google-fonts, google-site-verification, http3, resend, yandex-ads, yandex-metrica

Score-affecting fixes (these improve the StackScope score; [HIGH] = most impact):
- [HIGH] Add the missing security response headers. Missing: Permissions-Policy, Strict-Transport-Security Why: Each header limits a class of browser-side attack: clickjacking, XSS, MIME sniffing, plaintext fallback. Missing headers leave default-permissive behaviour in place. Where: Most are one line each in your server config, reverse proxy, CDN, or framework headers. (https://owasp.org/www-project-secure-headers/)

For each item, tell me exactly which file to create or which code to change, and where it lives in a project using the stack above. If my framework has a native API for the task (e.g. Next.js metadata exports, `app/sitemap.ts`, Astro layouts, Nuxt `useHead`), prefer that over raw HTML or server config.

Full analysis: https://stackscope.dev/launch/a50n5twh/web3vacancy

I own https://web3vacancy.com. StackScope (https://stackscope.dev) analysed it on 4 June 2026 and scored it 9.1/10 against their production-readiness checklist. Please help me apply the fixes below. This is a checklist, not a blocker list; Score-affecting fixes are the ones that move the number, Optional items are nice-to-haves with zero score impact that I can skip for an MVP.

Tech stack StackScope detected on the site (use this when suggesting where each fix lives in the codebase):
amazon-ses, amplitude, cloudflare, cloudflare-bot-management, cloudflare-dns, coinzilla, google-analytics, google-fonts, google-site-verification, http3, resend, yandex-ads, yandex-metrica

Score-affecting fixes (these improve the StackScope score; [HIGH] = most impact):
- [HIGH] Add the missing security response headers. Missing: Permissions-Policy, Strict-Transport-Security Why: Each header limits a class of browser-side attack: clickjacking, XSS, MIME sniffing, plaintext fallback. Missing headers leave default-permissive behaviour in place. Where: Most are one line each in your server config, reverse proxy, CDN, or framework headers. (https://owasp.org/www-project-secure-headers/)

Optional best-practice improvements (no score impact):
- [HIGH] Add a cookie-consent banner. Analytics detected on this site without a consent manager. Why: UK/EU GDPR requires opt-in before analytics scripts fire; about half of US state privacy laws now require honouring the Global Privacy Control browser signal as a universal opt-out. Where: Drop in Cookiebot, Usercentrics, Osano, or Iubenda Consent, or hand-roll a banner plus Google's `Consent Mode v2`. (https://iapp.org/resources/article/us-state-privacy-legislation-tracker)
- [MEDIUM] Set width and height on your images. 487 images render without explicit width/height. Why: Without intrinsic dimensions the browser can't reserve space before the image loads, so content jumps as it arrives (cumulative layout shift). Where: Add `width` and `height` attributes (or an `aspect-ratio` CSS rule). Framework image components set these for you. (https://web.dev/articles/cls)
- [LOW] Trim your <title> tag to under 60 characters. Currently 72 characters: "Web3 Jobs &amp; Crypto Jobs — #1 Blockchain Job Board 2026 | Web3Vacancy" Why: Google truncates titles around 60 characters in search results, so anything past that gets cut off mid-sentence and costs click-through rate. Where: Aim for 50-60 characters that include your main keyword and brand. (https://developers.google.com/search/docs/appearance/title-link)
- [LOW] Trim your meta description to under 160 characters. Currently 198 characters: "Browse 2,400+ web3 jobs and crypto jobs at top blockchain protocols, DAOs & DeFi projects. The #1 web3 job board for Solidity, Rust, ZK, and remote blockchain careers. New crypto job listings daily." Why: Google truncates around 155-160 characters on desktop SERPs (less on mobile), so anything past that won't appear in the snippet. Where: Edit your `<meta name="description">` tag. Put the most click-worthy phrase first. (https://developers.google.com/search/docs/appearance/snippet)
- [LOW] Add /.well-known/security.txt. Why: Lets security researchers report vulnerabilities responsibly through a published contact channel. Where: Create `/.well-known/security.txt` with a `Contact:` email and `Expires:` date. (https://securitytxt.org/)
- [LOW] Declare a Content-Signal in robots.txt. Why: States how you'd like AI systems to use your content (training, search, agent input). Without it, AI crawlers fall back to whatever default policy each vendor applies. Where: Add a `Content-Signal:` line to your `robots.txt`. (https://contentsignals.org/)
- [LOW] Add Link response headers. Why: Lets agents discover your sitemap, privacy policy, and docs without parsing HTML, which most lightweight agents skip. Where: Set `Link:` response headers in your server config or framework middleware. (https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Link)
- [LOW] Add MTA-STS. No MTA-STS DNS record published. Why: Prevents mail to your domain being downgraded to plaintext mid-flight by a network attacker. Most launches don't have this, so deploying it puts you a tier above generic email-security checks. Where: Publish a TXT record at `_mta-sts.{your-domain}` plus a policy file at `https://mta-sts.{your-domain}/.well-known/mta-sts.txt`. (https://datatracker.ietf.org/doc/html/rfc8461)
- [LOW] Add a TLS-RPT record. No TLS-RPT record at `_smtp._tls.{domain}`. Why: Receivers can tell you when STARTTLS handshakes to your mail server fail. Without it, silent TLS failures are invisible. Where: Publish one TXT record at `_smtp._tls.{your-domain}` like `v=TLSRPTv1; rua=mailto:tls-reports@yourdomain.com`. (https://datatracker.ietf.org/doc/html/rfc8460)
- [LOW] Serve right-sized images. 408 images are downloaded at more than twice the displayed size. Why: Shipping a 2000px image into a 400px slot wastes bandwidth and slows loading, especially on mobile. Where: Resize to the displayed dimensions, or use `srcset`/`sizes` (or a framework image component) to serve per-viewport variants. (https://developer.mozilla.org/en-US/docs/Web/HTML/Element/img#srcset)
- [LOW] Add alt text to your images. 62 images have no alt attribute. Why: Screen-reader users get no description, and search engines lose a signal about the image content. Where: Add a concise `alt="..."` to each image (an empty `alt=""` is correct only for purely decorative images). (https://developer.mozilla.org/en-US/docs/Web/HTML/Element/img#alt)

For each item, tell me exactly which file to create or which code to change, and where it lives in a project using the stack above. If my framework has a native API for the task (e.g. Next.js metadata exports, `app/sitemap.ts`, Astro layouts, Nuxt `useHead`), prefer that over raw HTML or server config.

Full analysis: https://stackscope.dev/launch/a50n5twh/web3vacancy

Using an autonomous agent?

Point the agent at this SKILL.md URL and ask it to follow the skill. The framing stops agents defaulting to an open-ended page review.

https://stackscope.dev/launch/a50n5twh/skill.md

Share your score

Your score card renders automatically when you share the link.

Or embed a badge

Two badge options. Pick whichever fits your story.

Current score

Shows the latest score and updates within a few minutes of any recrawl. Best for ongoing display: if you fix something and recrawl, the badge reflects the new score automatically.

<a href="https://stackscope.dev/launch/a50n5twh/web3vacancy"><img src="https://stackscope.dev/badge/a50n5twh/current.svg" alt="StackScope score for web3vacancy" height="24" /></a>

Launch score

Pinned to your launch-day snapshot and never changes. Marked with a small gold corner ribbon. Best for press kits, launch retrospectives, or anywhere you want a permanent record of how you shipped.

<a href="https://stackscope.dev/launch/a50n5twh/web3vacancy"><img src="https://stackscope.dev/badge/a50n5twh.svg" alt="StackScope launch score for web3vacancy" height="24" /></a>

Using a Content-Security-Policy? Both badges are <img> tags from our domain, so your CSP needs to allow them. Add stackscope.dev to your img-src directive (example: img-src 'self' stackscope.dev;). Without it, browsers silently block the badge and visitors see a broken image.