Avoid using JavaScript-generated internal links without server-side rendering support.
- Avoid using JavaScript-generated internal links without server-side rendering support3 cited sources2 categories
Save for later 0
Use × to move an item here. You can restore it when you’re ready.
Your checks and saved items stay in this browser. Nothing is submitted.
Why this matters
Internal links rendered only via JavaScript may be missed by crawlers in the initial crawl pass, delaying or preventing equity flow.
Hypothetical standard operating procedure
Adapt this example to your site, access, tools, and change process. It is our suggested procedure, informed by the sources below.
- Review site navigation and article bodies for JS-dependent links.
- Implement server-side rendering or static pre-rendering to output anchor tags in HTML.
- Test with Googlebot's fetch and render tool to confirm link visibility without JS.
- Use crawler tools to detect missing links in raw HTML.
- Eliminate onclick-only or <div>-styled links in favor of href anchors.
Watch for
Client-side rendered links cause incomplete crawl maps and orphaned pages without server-side fallback.
Definition of done
All critical internal links appear in initial HTML response anchor tags accessible without JS execution.
Sources & attribution
Original checklist wording and example SOP by Best SEO Checklist, using source-grounded AI assistance. Editorial contact: Ted Kubaitis, @tedkubaitis on Teams. Check current source guidance before implementation.