Observed Signal · Aug 11, 2026 · Technical Guidance · Source: DEV Community · Impact: 2/5 · Sentiment: Positive
Next.js JSON-LD May Be Invisible to Crawlers
A developer found JSON-LD structured data injected with Next.js's next/script was not present in the server HTML because next/script defaults to strategy="afterInteractive" (client-side injection after hydration). This caused crawlers that parse the initial HTML (e.g., Bing and many scrapers) to miss the structured data. The author demonstrates a simple curl check to detect the issue, shows that replacing next/script with a plain <script type="application/ld+json"> renders JSON-LD into server HTML (including from client components), and recommends verifying crawler-visible markup with curl against the raw server output rather than relying on DevTools or headless validators.
Practical technical fix for Next.js sites that affects search indexing and structured data visibility; relevant to web developers and publishers but not industry-shifting.
Track Bing Signals & Market Shifts in Real-Time
Polaris7 autonomous intelligence agents track regulatory filings, primary sources, executive changes, and deal flow 24/7. Create your Polaris7 workspace to monitor these entities.
Key Takeaways & Evidence Grounding
- next/script defaults to strategy="afterInteractive", which injects tags client-side after hydration.
- JSON-LD placed via next/script can be absent from the server-rendered HTML and thus invisible to crawlers that parse initial HTML.
- A one-line curl check (curl -s https://example.com/ | grep -c 'application/ld+json') can detect whether application/ld+json appears in server HTML.
- Replacing next/script JSON-LD with a plain <script type="application/ld+json"> causes React to render the JSON-LD into the server HTML, including when used in client components.
- The author's site went from 0 JSON-LD blocks per page to 2–5 per page after fixing the implementation and validating JSON parseability for each block.
Connected Companies & Entities
2 Entities mapped“I spent a while wondering why a site of mine had almost nothing indexed in Bing.”
“Google can render JavaScript, so this isn't guaranteed to be fatal there.”
Ontology Mapping & Concepts
Related Market Signals & Shifts
Recent verified developments and strategic activity across this market segment.
SEO Mistakes Killing Developer Projects
A developer describes debugging a React app that Googlebot saw as a blank page and outlines common SEO mistakes in developer-built projects. The post highlights four frequent issues: empty or generic <head> metadata, reliance on client-side rendering (which can be invisible to crawlers), lack of structured data (JSON-LD), and missing or stale sitemap.xml files. It gives concrete fixes and code examples: add meaningful meta tags, use SSR/SSG or prerendering (Next.js examples and tools like prerender.io or vite-plugin-ssr), include JSON-LD for rich results, and generate/submit sitemaps at build time. The article mentions tools and libraries such as react-helmet-async, Next.js <Head>/metadata, prerender.io, vite-plugin-ssr and the @power-seo npm package, and recommends testing with JavaScript disabled to emulate Googlebot's view.
Technical SEO Checklist for Full-Stack Developers 2026
A practical technical SEO checklist for full-stack developers focused on 2026-era search powered by LLMs and RAG. The guide recommends moving away from pure client-side rendering toward ISR or SSR to ensure core content is present in initial HTML, and it sets performance targets for Core Web Vitals (LCP <2.5s, INP <200ms, CLS <0.1). It advises automating JSON-LD schema generation and validating schema values against the DOM in CI, and recommends modern bot governance (explicit robots tokens for OAI-SearchBot, GPTBot, Google-Extended) to control LLM/AI crawler access. The article also prescribes engineering practices (fetchpriority attribute, AVIF/WebP, avoid lazy-loading above the fold, offload noncritical JS with scheduler.postTask/requestIdleCallback), and a performance budget (JS <150KB gzipped, CSS <50KB, TTFB <600ms via Edge CDNs).
Next.js 15 SEO: Metadata, OG Images, Sitemaps, Structured Data
A technical guide to Next.js 15 App Router SEO patterns in TypeScript, covering co-located metadata, two metadata-definition approaches (static export and generateMetadata), dynamic Open Graph image generation using ImageResponse, automatic sitemap.xml and robots.txt routes, and JSON‑LD structured data insertion. The article shows production patterns such as title templates, canonical alternate URLs, caching to deduplicate data fetches between generateMetadata and page components, and common pitfalls (missing descriptions, generic OG images, duplicate titles, invalid JSON‑LD). It includes code examples for metadata, dynamic OG images, sitemap and robots generation, and recommendations for verification using platform validators.
Receive all future signals for Bing & competitors in your briefing
Never miss material M&A deals, leadership changes, account wins, or product rollouts. Polaris7 monitors 20,000+ primary sources 24/7, delivering verified telemetry directly into your executive briefing.