Owner tools

For the owner of HeyNews (Visit site).

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: Referrer-Policy, X-Frame-Options, Permissions-Policy, Content-Security-Policy
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:
- Content-Security-Policy: Controls which scripts, styles, and fonts are allowed to run on your pages. Without it, an injected <script> tag runs with full access to your users' sessions and cookies.
- X-Frame-Options: Stops other sites loading yours inside an invisible iframe to trick users into clicking buttons they can't see (clickjacking).
- 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.
CSP rollout: Content-Security-Policy is the hardest to get right. Start with Content-Security-Policy-Report-Only, which logs violations without blocking. Open DevTools Console, reload each page, and relax the policy until the console is clean. Rename the header to Content-Security-Policy to enforce. For real-user monitoring, point a report-to directive at a free collector (report-uri.com, Sentry, or a /api/csp-report route).

Starter Content-Security-Policy

We didn't see a Content-Security-Policy header on your site. Here's a starter policy built from the 7 third-party vendors we detected (cookieyes, google-analytics, google-consent-mode, google-fonts, google-tag-manager, mixpanel, segment).

Content-Security-Policy-Report-Only:
default-src 'self';
script-src 'self' 'unsafe-inline' https://cdn-cookieyes.com https://cdn.mxpnl.com https://cdn.segment.com https://log.cookieyes.com https://www.google-analytics.com https://www.googletagmanager.com;
style-src 'self' 'unsafe-inline' https://fonts.googleapis.com;
img-src 'self' data: https://www.google-analytics.com https://www.googletagmanager.com;
font-src 'self' https://fonts.gstatic.com;
connect-src 'self' https://analytics.google.com https://api.mixpanel.com https://api.segment.io https://stats.g.doubleclick.net https://www.google-analytics.com;
frame-ancestors 'none';
base-uri 'self';
form-action 'self';

Test before enforcing. This is a starting point based on what we could detect from a public crawl, not a finished policy. Deploy as Content-Security-Policy-Report-Only first (as shown above), walk through your site with DevTools Console open, and relax the policy until no CSP violations fire. Only then rename the header to Content-Security-Policy to enforce.

We probably don't cover everything. Vendors that only load behind auth, self-hosted scripts, custom analytics, and anything we haven't fingerprinted yet won't appear here. Inline scripts work because we've included 'unsafe-inline'; you can tighten that later with nonces once the basic policy is stable. The Report-Only walkthrough will flag anything we missed. That's the whole point of starting there.

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

MEDIUMMove DMARC from p=none to quarantine or reject
DMARC policy is p=none (monitoring only).
Whyp=none lets receivers log failures but still deliver spoofed mail. Real protection only kicks in at quarantine or reject.
WhereAfter reviewing a few weeks of rua= reports and confirming your real senders pass, change to p=quarantine (sends spoofs to spam) and then p=reject (blocks them outright).
Learn more
MEDIUMFix or remove the broken MTA-STS deployment
DNS record is published but the policy file couldn't be fetched.
WhyReceivers expect a policy whenever the DNS record exists. If they can't fetch it, they ignore MTA-STS entirely, so your deployment effort is wasted.
WhereEither fix the policy host (DNS, HTTPS cert, file path) or remove the _mta-sts TXT record so receivers stop checking.
Learn more
Why this matters & sources
Common causes: the policy host (mta-sts.{your-domain}) doesn't have a working A/AAAA/CNAME record, the host has no HTTPS certificate, or the path returns 404. The policy file must be at https://mta-sts.{your-domain}/.well-known/mta-sts.txt and contain a mode: line.

Page basics & SEO

LOWTrim your <title> tag to under 60 characters
Currently 61 characters: "Your Newsletter, Your Voice. Published in 5 Minutes | HeyNews"
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 230 characters: "HeyNews learns your writing style from past newsletters, curates stories from RSS, Reddit, social media, and blogs, then generates publish-ready issues in minutes. 14-day free trial. Free Growth Audit ($99 value) when you sign up."
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

Agent / AI

LOWAdd an llms.txt file
WhyHelps AI models understand your site's content and how to use it. Not yet a standard but gaining adoption.
WhereCreate /llms.txt at the site root with a brief overview and key URLs.
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://heynews.co. StackScope (https://stackscope.dev) analysed it on 12 May 2026 and scored it 8.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):
affonso, apollo-io, arcade, cloudflare, cloudflare-bot-management, cloudflare-dns, cookieyes, customer-io, facebook-pixel, gist, google-analytics, google-consent-mode, google-fonts, google-site-verification, google-tag-manager, google-workspace, hsts, http3, hubspot, icloud-mail, mixpanel, openai-chatkit, partnero, pinterest, reddit-ads, segment, shadcn-ui, tailwindcss, vite

Score-affecting fixes (these improve the StackScope score; [HIGH] = most impact):
- [HIGH] Add the missing security response headers. Missing: Referrer-Policy, X-Frame-Options, Permissions-Policy, Content-Security-Policy 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/i5lfc1f3/heynews

I own https://heynews.co. StackScope (https://stackscope.dev) analysed it on 12 May 2026 and scored it 8.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):
affonso, apollo-io, arcade, cloudflare, cloudflare-bot-management, cloudflare-dns, cookieyes, customer-io, facebook-pixel, gist, google-analytics, google-consent-mode, google-fonts, google-site-verification, google-tag-manager, google-workspace, hsts, http3, hubspot, icloud-mail, mixpanel, openai-chatkit, partnero, pinterest, reddit-ads, segment, shadcn-ui, tailwindcss, vite

Score-affecting fixes (these improve the StackScope score; [HIGH] = most impact):
- [HIGH] Add the missing security response headers. Missing: Referrer-Policy, X-Frame-Options, Permissions-Policy, Content-Security-Policy 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):
- [MEDIUM] Move DMARC from p=none to quarantine or reject. DMARC policy is `p=none` (monitoring only). Why: p=none lets receivers log failures but still deliver spoofed mail. Real protection only kicks in at quarantine or reject. Where: After reviewing a few weeks of `rua=` reports and confirming your real senders pass, change to `p=quarantine` (sends spoofs to spam) and then `p=reject` (blocks them outright). (https://dmarc.org/overview/)
- [MEDIUM] Fix or remove the broken MTA-STS deployment. DNS record is published but the policy file couldn't be fetched. Why: Receivers expect a policy whenever the DNS record exists. If they can't fetch it, they ignore MTA-STS entirely, so your deployment effort is wasted. Where: Either fix the policy host (DNS, HTTPS cert, file path) or remove the `_mta-sts` TXT record so receivers stop checking. (https://datatracker.ietf.org/doc/html/rfc8461)
- [LOW] Trim your <title> tag to under 60 characters. Currently 61 characters: "Your Newsletter, Your Voice. Published in 5 Minutes | HeyNews" 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 230 characters: "HeyNews learns your writing style from past newsletters, curates stories from RSS, Reddit, social media, and blogs, then generates publish-ready issues in minutes. 14-day free trial. Free Growth Audit ($99 value) when you sign up." 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 an llms.txt file. Why: Helps AI models understand your site's content and how to use it. Not yet a standard but gaining adoption. Where: Create `/llms.txt` at the site root with a brief overview and key URLs. (https://llmstxt.org/)

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/i5lfc1f3/heynews

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/i5lfc1f3/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/i5lfc1f3/heynews"><img src="https://stackscope.dev/badge/i5lfc1f3/current.svg" alt="StackScope score for HeyNews" 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/i5lfc1f3/heynews"><img src="https://stackscope.dev/badge/i5lfc1f3.svg" alt="StackScope launch score for HeyNews" 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.