Why You Should Avoid document.write(): Complete Guide (2026)

document.write() Patterns and Their Modern Replacements

How to Find document.write() in Your Site

1. Run an automated audit and check the Best Practices result "Avoids `document.write()`."
2. Search your codebase: `git grep -nE "document\\.write\\b"`.
3. Open Chrome DevTools Console and reload; intervention messages appear as "A Parser-blocking, cross site... script... was invoked via document.write."
4. Check third-party tags listed in the Network tab; legacy ad and analytics scripts are the biggest source.
5. For our companion guides, see fixing console errors and DevTools Issues panel warnings.

How to Replace document.write(): Code Examples

1. Replace a Synchronous Script Injection

// Bad: blocks parser, fails the Best Practices audit, intervened on slow networks
document.write('<script src="https://cdn.example.com/widget.js"></script>');

// Good: non-blocking, runs after parsing
const s = document.createElement('script');
s.src = 'https://cdn.example.com/widget.js';
s.async = true;
document.head.appendChild(s);

2. Replace HTML Insertion

// Bad
document.write('<div class="banner">Sale!</div>');

// Good
document.getElementById('banner-slot')
  .insertAdjacentHTML('beforeend', '<div class="banner">Sale!</div>');

3. Replace User-Generated Content

// Bad: XSS hole
document.write('<p>Welcome ' + name + '</p>');

// Good: textContent escapes everything
const p = document.createElement('p');
p.textContent = 'Welcome ' + name;
document.body.appendChild(p);

Common Mistakes (Bad vs Good)

// Bad: "fixing" by wrapping in a setTimeout — STILL erases the page
setTimeout(() => document.write('<p>Late content</p>'), 1000);

// Good: target a known container after DOMContentLoaded
document.addEventListener('DOMContentLoaded', () => {
  document.getElementById('content').insertAdjacentHTML(
    'beforeend',
    '<p>Late content</p>'
  );
});

How to Test That document.write() Is Gone

1. Run an automated audit limited to `no-document-write` (e.g. via a CI audit runner). The audit should pass.
2. `git grep -nE "document\\.write\\b"` should return only test fixtures or comments.
3. Throttle the Network tab to Slow 3G and reload; no intervention messages should appear in the Console.
4. Run a Playwright test that asserts `page.on('console', msg => ...)` does not include the string "document.write."

FAQ

Is document.write() removed from browsers?

No. It is still in the HTML spec for backwards compatibility, but Chrome intervenes on slow networks and the automated Best Practices audit fails the page. Treat it as deprecated for new code.

What does Chrome's "intervention" do?

On 2G or Lite Mode, Chrome blocks the parser-blocking, cross-origin script that was injected by `document.write()`. Your script never runs.

Can I keep document.write() for ads?

Most major ad platforms (Google Ad Manager, Prebid) ship modern async tags. Update to the current vendor snippet; legacy `document.write` ad tags are progressively blocked.

Is innerHTML safer than document.write?

Yes for parsing (it does not erase the document), but not for XSS. Always sanitize untrusted strings or use `textContent` for plain text.

Does document.write() hurt Core Web Vitals?

Yes. It blocks parsing and rendering, hurting LCP and INP. Removing it is one of the highest-leverage fixes for a slow page.

Can I polyfill document.write()?

Some libraries (e.g. Postscribe) emulate it for legacy snippets, but they add their own parser overhead. Replace the source snippet instead.

Is document.write() ever safe?

Only inside the same parsing pass it was issued in (e.g. an inline script in the head writing into the document being parsed). Anywhere else it is dangerous.

Does this affect AI search engines like ChatGPT and Perplexity?

Yes. Content injected via `document.write()` often renders after initial DOM construction, sometimes after AI crawler timeouts, so the ChatGPT crawler, PerplexityBot, and Google AI Overviews can miss it entirely. AI search engines also preferentially cite well-ranked pages, and the parser-blocking behavior hurts Core Web Vitals, indirectly lowering your citation odds.