Owner tools

For the owner of Mon Petit Portfolio (mon-petit-portfolio.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

Page basics & SEO

MEDIUMUse HTML5 semantic elements
Page uses mostly generic <div>s with no semantic landmarks detected.
WhyScreen-reader users can't reliably skip past navigation to your primary content. Search engines also use these to identify which part of the page is the actual content for snippet generation.
WhereReplace outermost <div>s with <nav>, <main>, <article>, <section>, <header>, <footer> where the structure fits.
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

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
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

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://mon-petit-portfolio.com. StackScope (https://stackscope.dev) analysed it on 11 April 2026 and scored it 9.7/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):
flagcdn, google-site-verification, hsts, improvmx, nextjs, react, resend, vercel, vercel-analytics, vercel-dns

Score-affecting fixes (these improve the StackScope score; [HIGH] = most impact):
- [MEDIUM] Use HTML5 semantic elements. Page uses mostly generic `<div>`s with no semantic landmarks detected. Why: Screen-reader users can't reliably skip past navigation to your primary content. Search engines also use these to identify which part of the page is the actual content for snippet generation. Where: Replace outermost `<div>`s with `<nav>`, `<main>`, `<article>`, `<section>`, `<header>`, `<footer>` where the structure fits. (https://developer.mozilla.org/en-US/docs/Web/HTML/Element#content_sectioning)

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/xwelqcuf/mon-petit-portfolio

I own https://mon-petit-portfolio.com. StackScope (https://stackscope.dev) analysed it on 11 April 2026 and scored it 9.7/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):
flagcdn, google-site-verification, hsts, improvmx, nextjs, react, resend, vercel, vercel-analytics, vercel-dns

Score-affecting fixes (these improve the StackScope score; [HIGH] = most impact):
- [MEDIUM] Use HTML5 semantic elements. Page uses mostly generic `<div>`s with no semantic landmarks detected. Why: Screen-reader users can't reliably skip past navigation to your primary content. Search engines also use these to identify which part of the page is the actual content for snippet generation. Where: Replace outermost `<div>`s with `<nav>`, `<main>`, `<article>`, `<section>`, `<header>`, `<footer>` where the structure fits. (https://developer.mozilla.org/en-US/docs/Web/HTML/Element#content_sectioning)

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/)
- [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)

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/xwelqcuf/mon-petit-portfolio

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/xwelqcuf/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/xwelqcuf/mon-petit-portfolio"><img src="https://stackscope.dev/badge/xwelqcuf/current.svg" alt="StackScope score for Mon Petit Portfolio" 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/xwelqcuf/mon-petit-portfolio"><img src="https://stackscope.dev/badge/xwelqcuf.svg" alt="StackScope launch score for Mon Petit Portfolio" 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.