Owner tools

For the owner of Stripe.Directory (docs.stripe.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

Start here

Two fast-win fixes from the list below, ordered by impact. Each is a drop-in change you can finish in under 30 minutes.

Add Open Graph tags Missing on your page: all three Open Graph tags.
Add Twitter card meta tags No Twitter card tags were detected on your page.

1 more score-affecting fix below, plus advisory items.

Fixes that improve your score

Security

HIGHAdd the missing security response headers
Missing: Referrer-Policy, Permissions-Policy, X-Content-Type-Options
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:
- X-Content-Type-Options: Tells browsers not to guess file types. Without it, a user-uploaded image can be sniffed as JavaScript and executed.
- Referrer-Policy: Controls how much of the current URL is sent to third-party sites and analytics. The default leaks the full path, including query strings that may contain tokens or user IDs.
- Permissions-Policy: Turns off browser features your site doesn't use (camera, microphone, geolocation, payment) so an injected script can't trigger them.

Page basics & SEO

MEDIUMAdd Open Graph tags
Missing on your page: all three Open Graph tags.
WhyWithout og:title, og:description, and og:image, links to your site render as bare text on Facebook, LinkedIn, and most chat apps instead of rich previews with an image.
WhereAdd <meta property="og:title" content="..."> (and the other two) to each page's <head>. Frameworks usually have a metadata API for this.
Learn more
MEDIUMAdd Twitter card meta tags
No Twitter card tags were detected on your page.
WhyWithout them, links shared on X render as bare text instead of a rich preview card with image, title, and description. Rich cards have meaningfully higher CTR.
WhereAdd <meta name="twitter:card" content="summary_large_image">, plus twitter:title, twitter:description, and twitter:image to your <head>.
Learn more

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

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 meta description to under 160 characters
Currently 235 characters: "Stripe Directory is a single discovery layer for developers and AI agents to find businesses on Stripe—including Stripe Apps, Projects.dev providers, and mpp.dev services—and integrate them without the need to manually search for them."
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

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://docs.stripe.com/directory. StackScope (https://stackscope.dev) analysed it on 24 June 2026 and scored it 6.9/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):
algolia, baidu-analytics, cloudflare, cloudflare-bot-management, hsts, nginx, prismjs, sentry, stripe, youtube

Score-affecting fixes (these improve the StackScope score; [HIGH] = most impact):
- [HIGH] Add the missing security response headers. Missing: Referrer-Policy, Permissions-Policy, X-Content-Type-Options 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/)
- [MEDIUM] Add Open Graph tags. Missing on your page: all three Open Graph tags. Why: Without `og:title`, `og:description`, and `og:image`, links to your site render as bare text on Facebook, LinkedIn, and most chat apps instead of rich previews with an image. Where: Add `<meta property="og:title" content="...">` (and the other two) to each page's `<head>`. Frameworks usually have a metadata API for this. (https://ogp.me/)
- [MEDIUM] Add Twitter card meta tags. No Twitter card tags were detected on your page. Why: Without them, links shared on X render as bare text instead of a rich preview card with image, title, and description. Rich cards have meaningfully higher CTR. Where: Add `<meta name="twitter:card" content="summary_large_image">`, plus `twitter:title`, `twitter:description`, and `twitter:image` to your `<head>`. (https://developer.mozilla.org/en-US/docs/Web/HTML/Element/meta/name)

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/tv56z5ck/stripedirectory

I own https://docs.stripe.com/directory. StackScope (https://stackscope.dev) analysed it on 24 June 2026 and scored it 6.9/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):
algolia, baidu-analytics, cloudflare, cloudflare-bot-management, hsts, nginx, prismjs, sentry, stripe, youtube

Score-affecting fixes (these improve the StackScope score; [HIGH] = most impact):
- [HIGH] Add the missing security response headers. Missing: Referrer-Policy, Permissions-Policy, X-Content-Type-Options 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/)
- [MEDIUM] Add Open Graph tags. Missing on your page: all three Open Graph tags. Why: Without `og:title`, `og:description`, and `og:image`, links to your site render as bare text on Facebook, LinkedIn, and most chat apps instead of rich previews with an image. Where: Add `<meta property="og:title" content="...">` (and the other two) to each page's `<head>`. Frameworks usually have a metadata API for this. (https://ogp.me/)
- [MEDIUM] Add Twitter card meta tags. No Twitter card tags were detected on your page. Why: Without them, links shared on X render as bare text instead of a rich preview card with image, title, and description. Rich cards have meaningfully higher CTR. Where: Add `<meta name="twitter:card" content="summary_large_image">`, plus `twitter:title`, `twitter:description`, and `twitter:image` to your `<head>`. (https://developer.mozilla.org/en-US/docs/Web/HTML/Element/meta/name)

Optional best-practice improvements (no score impact):
- [LOW] Trim your meta description to under 160 characters. Currently 235 characters: "Stripe Directory is a single discovery layer for developers and AI agents to find businesses on Stripe—including Stripe Apps, Projects.dev providers, and mpp.dev services—and integrate them without the need to manually search for them." 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] 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)

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/tv56z5ck/stripedirectory

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/tv56z5ck/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/tv56z5ck/stripedirectory"><img src="https://stackscope.dev/badge/tv56z5ck/current.svg" alt="StackScope score for Stripe.Directory" 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/tv56z5ck/stripedirectory"><img src="https://stackscope.dev/badge/tv56z5ck.svg" alt="StackScope launch score for Stripe.Directory" 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.