Websites built with JavaScript frameworks can look complete to a visitor and incomplete to a search engine. A JavaScript SEO audit establishes what a search engine actually receives when it requests a page, and what it sees only after running the page’s scripts. Hartzer Consulting provides it as a focused engagement and as one part of a full technical SEO audit.
Why JavaScript Creates Search Problems
A traditional web page arrives from the server as finished HTML. A JavaScript-driven page often arrives nearly empty, and the browser builds the content by running scripts. This step is called rendering. Google can render JavaScript, but it does so in a second pass after the initial crawl, and that pass can be delayed, can time out, and can fail on script errors. Other search engines render less reliably than Google. Many AI crawlers, the systems that collect pages for AI search tools, do not execute JavaScript at all. Content that exists only after rendering may be invisible to them.
Sites That Need This Audit
- Sites built on React, Angular, Vue, or similar frameworks
- Single-page applications, where one HTML page loads all content through scripts
- Headless builds, where the content management system is separate from the front end
- E-commerce sites that load products, prices, or reviews through scripts
- Any site that lost rankings after being rebuilt on a JavaScript framework
What Hartzer Consulting Examines
- Raw HTML compared with the rendered page. Which content, links, and tags are present before scripts run, and which appear only afterward.
- Links. Whether navigation uses standard anchor tags with real URLs, or click handlers that a crawler cannot follow.
- Head elements. Title tags, meta descriptions, canonical tags, and robots directives that scripts insert or change after the page loads.
- URLs. Whether every view has its own crawlable URL, and whether the site depends on fragments (the part of a URL after the # symbol) that search engines ignore.
- Status codes. Whether missing pages return a true 404 (not found) response, or a 200 (OK) response with an error message, which Google treats as a soft 404.
- Lazy loading. Content and images that load only when a visitor scrolls or clicks.
- Blocked resources. Script and API requests that robots.txt prevents Googlebot from fetching.
- Structured data. Schema markup added by scripts, and whether it survives rendering.
How the Audit Is Done
Bill Hartzer crawls the site twice with Screaming Frog: once reading only the raw HTML, and once with JavaScript rendering enabled. The two crawls are compared page by page. Differences in word count, links, titles, canonical tags, and directives show exactly what depends on rendering. The URL Inspection tool in Google Search Console then shows the rendered HTML as Google produced it, along with any resources that failed to load. Pages are also requested with scripts disabled, which approximates what a crawler that does not render will receive.
Common Findings
- Body content missing from the raw HTML on every page of a template
- Internal links that work for visitors and do not exist for crawlers
- A canonical tag or noindex directive in the raw HTML that a script later changes, leaving search engines with two conflicting instructions
- One title tag and meta description shared by every page until scripts run
- Error pages that return a 200 status code
- Content that requires a click or a scroll before it loads
Recommendations
The fix depends on the framework and on how the site is built. Hartzer Consulting most often recommends server-side rendering (the server sends finished HTML), static generation (pages are built in advance), or prerendering for crawlers, and specifies which templates need it. The report is written for developers and states what the raw HTML of each template must contain. For background, see SEO for websites built with React.
What the Client Receives
- A template-by-template comparison of raw and rendered HTML
- A list of content, links, and tags that depend on rendering
- A fix list for the developers, ordered by impact
- A retest after the changes are deployed
To request a JavaScript SEO audit, contact Hartzer Consulting or call +1 214 236 4378.