This update focuses on making preflight checks more accurate across real-world app structures, especially for Next.js projects that generate metadata and web standard files dynamically.
More reliable detection for Next.js apps
SEO, Open Graph, and Twitter checks now recognize Next.js Metadata API usage more broadly, including generateMetadata and metadata exports found anywhere within the app directory. This helps your project pass checks when metadata is configured outside the main layout file.
Web standard routes like robots and sitemap are now detected even when they are dynamically generated or placed in nested locations (including route groups). This reduces missed detections for frameworks and routing styles that do not keep these files at the app root.
Favicon detection now also finds dynamic icon files used by Next.js app router setups, so projects using file-based icon definitions are less likely to be flagged as missing a favicon.
Legal page checks: broader coverage, fewer false positives
Privacy and terms detection now checks a wider set of common URLs and filename patterns, including additional legal and policy paths. This makes it more likely to recognize the legal pages you already have without requiring renames.
Flexible scanning for legal pages was tightened to avoid matching unrelated files that only contain similar words, such as privacy settings or context utilities. This reduces false positives and makes results easier to trust.
Documentation updates
The documentation now lists a broader set of ignorable service IDs under a unified “all services have validation checks” description, and adds PHP to the supported backend frameworks list.