Crawl budget and JavaScript: technical SEO for modern PR sites
Rendering, sitemaps, and canonicals on SPAs and Next.js to avoid losing Google indexation.
JavaScript-heavy sites — partial Next.js CSR, legacy SPAs — compete for Google crawl budget while Puerto Rico agencies publish hundreds of duplicate filter URLs. Smashing Magazine and Google Search Central document: Google renders JS but with delay and limits; Puerto Rico tourism and ecommerce sites cannot wait weeks to index seasonal offers.
Crawl budget basics: prioritize valuable URLs — services, destinations, products — not infinite sort/filter parameters. robots.txt disallow low-value facets; canonical tag on legitimate variants. Dynamic XML sitemap with real lastmod, submit in Search Console, monitor "Discovered - currently not indexed".
Next.js rendering strategy: SSG/ISR for static landings; SSR for personalized content worth indexing; avoid pure CSR on money pages. Critical prerender with generateStaticParams where applicable. Verify rendered HTML with Google URL Inspection — not just dev local view-source in Condado on fiber.
Hreflang if serving EN/ES for mainland and Puerto Rico market; wrong hreflang confuses crawl. OWASP is not SEO, but infinite scroll without crawlable pagination is shared technical problem — use paginated URLs or load-more with real links.
Metrics: GSC crawl stats, indexed/discovered ratio, time-to-index post-publish. Isla Verde hotel client lost season on new landing not indexed in three weeks — crawl budget wasted on junk URLs. JS technical SEO in PR is platform discipline, not magic plugin.
Writes about practical cybersecurity for SMBs in Puerto Rico and the Caribbean — no fluff, just what actually needs to get done.
