H1 Updated by JavaScript

What Is This Issue?

This issue occurs when JavaScript modifies the H1 tag content after the page loads. The H1 exists in the raw HTML, but JavaScript changes it to something different. This can cause search engines to index the original H1 while users see a different heading.

Why This Matters for Your Website

Indexing Inconsistency

If Google indexes the original H1 from raw HTML but users see a different heading after JavaScript executes, there's a mismatch between what appears in search results and what's on the page. This can hurt user experience and may be seen as misleading.

Common Causes

• Personalization scripts that customize headings
• A/B testing frameworks modifying content
• Dynamic content based on user location or preferences
• CMS plugins that manipulate headings

How to Check

1. Compare Sources: View Page Source shows raw HTML; Inspect Element shows rendered DOM
2. Screaming Frog: Run crawl with and without JavaScript rendering, compare H1 columns
3. Browser Console: Watch for DOM mutations to heading elements

How to Fix This Issue

1. Keep Critical H1 Static: The primary H1 should not be modified by JavaScript
2. Use Separate Elements: If you need dynamic content, use a different element, not the H1
3. Server-Side Personalization: Handle personalization before sending HTML when possible
4. Ensure Consistency: If H1 must change, ensure it changes to something closely related