nextjs-seo — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited nextjs-seo (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Start from the page's task, production response and observed search behavior. Read the installed Next.js version and relevant node_modules/next/dist/docs/ pages (bundled from 16.2); otherwise use matching official documentation. Metadata, Viewport and MetadataRoute types are also in node_modules/next/dist/lib/metadata/types/metadata-interface.d.ts. Keep framework APIs, caching mode and deployment policy consistent with the project.
Useful, distinct content matters more than a longer page. Give titles, headings and descriptions separate jobs; add a FAQ, summary, badges or extra pages only when they help the reader. Publication dates must reflect meaningful changes. Verify authorship, credentials and factual claims.
and canonicals before adding markup. A sitemap supports discovery; it does not make a page indexable or guarantee indexing.
A Client Component can be server-prerendered; use client alone does not remove content from HTML.
metadata URLs with the correct production metadataBase and verify emitted absolute URLs. Do not rely on missing-base behavior across versions/hosts.
A database query alone does not guarantee publication updates reach them. With Cache Components enabled, follow the installed Next.js caching docs (node_modules/next/dist/docs/); caching is a freshness decision rather than a required SEO directive.
Check current rich-result eligibility instead of adding every schema type.
retrieval have different controls; robots rules are not access control.
Separate evidence in the report: a performance export shows queries/traffic; URL Inspection and indexing reports address crawl/index/canonical status; field measurements address Core Web Vitals. Lighthouse is a lab diagnostic and cannot establish field INP. Good field thresholds at the 75th percentile are LCP ≤ 2.5 s, INP ≤ 200 ms and CLS ≤ 0.1.
Verify status, headers and complete production HTML, including relevant bot responses, then open the route directly and test its interaction. A spoofed User-Agent tests response handling, not actual verified bot access. Report unavailable checks explicitly and avoid ranking, indexing or citation promises.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.