fix(docs,marketing): stop blocking /_next/ in robots.txt so Google can fetch render assets

Author: Kitenite

apps/docs/src/app/robots.ts

@@ -6,8 +6,10 @@ export default function robots(): MetadataRoute.Robots {
 		rules: [
 			{
 				userAgent: "*",
+				// No /_next/ block: Google needs build assets (CSS, JS, fonts) to
+				// render pages, and blocking them triggers Search Console reports.
 				allow: "/",
-				disallow: ["/api/", "/_next/", "/llms.mdx/", "/llms-full.txt"],
+				disallow: ["/api/", "/llms.mdx/", "/llms-full.txt"],
 			},
 		],
 		sitemap: `${COMPANY.DOCS_URL}/sitemap.xml`,

apps/marketing/src/app/robots.txt/route.ts

@@ -26,7 +26,6 @@ User-Agent: *
 Allow: /
 Allow: /api/llms.txt
 Disallow: /api/
-Disallow: /_next/
 
 # AI assistants and AI search crawlers: explicitly welcome
 ${WELCOME_AI_AGENTS.map((agent) => `User-Agent: ${agent}\nAllow: /`).join("\n\n")}