JavaScript SEO for sites built on modern frameworks
We check what Google and other crawlers actually see on your React, Vue or Angular site, and fix the gaps.
In plain English.
Many modern sites build their pages in the browser with JavaScript. To a visitor the page looks complete. To a search engine that reads the raw HTML first, it can look almost empty until the scripts run, and some crawlers never run them at all.
Google does render JavaScript, but it queues pages for rendering and can miss content loaded after a click, a scroll or a slow API call. Many AI crawlers and social preview bots read only the initial HTML. That makes it important to know what is in your HTML before any scripts run.
We compare the raw source with the rendered page using Search Console's URL Inspection tool and a JavaScript-enabled crawl. Where content or links are missing, we recommend server-side rendering, static generation or targeted fixes, and work with your developers to put them in place.
It suits you if.
- Your site is a single-page app built in React, Vue or Angular
- Google shows the wrong title or no description for your pages
- Links between pages use click handlers instead of real links
- You are planning a move to Next.js, Nuxt or another framework
- Content loads from an API after the page appears
What we do.
Raw versus rendered comparison
We compare the initial HTML with the rendered page to see which titles, text and links depend on scripts.
Crawlable links
Navigation checked for proper anchor links with an href, since search engines do not click buttons to find pages.
Rendering strategy advice
Server-side rendering, static generation and pre-rendering compared for your framework and hosting.
Metadata handling
Titles, descriptions, canonicals and structured data output in the server response, instead of being added later by scripts.
Status code checks
Soft 404s from single-page apps fixed so missing pages return a real 404 status.
How it runs.
- 01
Inspect key templates
We run URL Inspection and a rendered crawl on your main page types to see what search engines receive.
- 02
Find what depends on scripts
Content, links and tags that only exist after JavaScript runs are listed by template.
- 03
Agree the fix
With your developers, we choose between server rendering, pre-rendering or smaller targeted changes.
- 04
Verify after release
A crawl with scripts disabled confirms the important content is now in the HTML.
Questions people ask.
Does Google not handle JavaScript fine now?
Google renders most JavaScript well, but not instantly and not always completely. Other search engines, AI crawlers and link preview tools are less capable. Putting key content in the initial HTML removes the risk for all of them at once.
Do we need to rebuild the site?
Rarely. Frameworks like Next.js and Nuxt can render on the server with configuration changes. Older single-page apps sometimes need pre-rendering for their public pages. We look for the smallest change that gets the job done and explain why.
Can you work with our in-house developers?
That is the usual way. We provide the audit, explain the reasoning and write tickets with acceptance tests. If you would rather we made the changes ourselves, we can quote for that as well, depending on your stack and hosting.
How is a JavaScript SEO audit priced?
The audit is a fixed price based on the number of page templates. Implementation is quoted separately once the fixes are known, or handed to your own team with nothing further to pay beyond the audit.
Your next chapter starts with a conversation.
Nottingham & Derby / UK-wideLet’s build
what’s next.
15 minutes with Garreth.
A real conversation about your business.