JavaScript SEO for React and Next.js sites
Built your site with React or Next.js, and Google isn't showing it the way it should? The cause is usually in the code.
I'm Munim, a Next.js developer who has also done SEO for years. I fix the search problems that live in the code: rendering, metadata, internal links, redirects and structured data.
You get the diagnosis and the fix from one person. Nothing gets lost between an SEO report and a dev ticket.
I reply within one business day. No obligation.
When this makes sense
Your React or Next.js site is live, but Google indexes only part of it.
Traffic dropped after a redesign, a rebuild or a move to a new framework.
Your SEO team found problems, and the fixes need a developer who understands why they matter.
You want ChatGPT, Perplexity and Google's AI features to be able to read your pages.
When I'm not the right fit
You need content writing, link building or local SEO. I work on the code side.
Your site runs on a WordPress or Shopify theme, and the problem isn't custom JavaScript.
You want guaranteed rankings. Nobody can honestly promise that.
What usually goes wrong on JavaScript sites
Most of these look fine in a browser. They only show up when you look at the page the way a crawler does.
Content only appears after JavaScript runs.
Google renders it later, when its resources allow. Most AI crawlers never run JavaScript at all (Vercel, 2024).
Every page shares one title or canonical tag.
It was set once in a layout and never changed per page.
Links aren't links.
Navigation built with buttons and
onClickgives crawlers nothing to follow. Google only follows<a>tags with anhref.Missing pages return a 200 status.
The page says "not found", but Google sees a normal page and may index it.
noindexis added or removed with JavaScript.When Google sees
noindexin the first HTML, it may skip rendering, so your change never counts (Google).Old URLs were never redirected.
A rebuild changed the URL structure, and years of links now point to 404s.
Heavy JavaScript slows the page.
Large client bundles push Largest Contentful Paint and Interaction to Next Paint into the red.
Each of these has a known fix. The hard part is finding which ones apply to your site.
Check your own site in five minutes
You don't need me for a first look. These four checks catch most problems.
If any of these look wrong, that's what the audit digs into properly.
View the page source
Right-click your page and choose View Page Source. If your main text isn't there, it only appears after JavaScript runs.
Use the URL Inspection tool
In Google Search Console, inspect a key page and open the rendered HTML. Check that the content and links are in it.
Compare indexed pages with your sitemap
The Pages report in Search Console shows how many pages Google indexed. A big gap with your sitemap means something is blocking them.
Check titles across templates
Open three different pages and look at the browser tab. If the titles match, your metadata is set once in a layout.
JavaScript SEO services
Technical SEO audit
I check your site the way Google and AI crawlers see it. You get a written report with fixes ranked by impact.
Technical SEO auditFixes in your code
I make the changes myself in your repo, or write clear tickets for your developers.
Core Web Vitals
Finding why LCP, INP or CLS fails in real user data, then fixing it in your code.
Core Web VitalsWebsite migration SEO
Moving to Next.js or a new platform without losing traffic. URL mapping, redirects and launch checks.
Website migration SEOAI search readiness
Making sure ChatGPT, Perplexity and Google's AI features can read and cite your pages. Crawler access, server rendering and structured data.
AI search optimizationNeed a new build instead?
If the site needs rebuilding rather than fixing, that's Next.js development.
Next.js development
Where most projects start: the audit
Before anyone changes code, I check your key page templates the way Google and AI crawlers see them.
Raw HTML against rendered HTML, and what crawlers miss before JavaScript runs.
Metadata, canonicals and robots rules on every template.
Links, status codes and redirects.
Core Web Vitals and AI crawler access.
- What you get
a written report with fixes ranked by impact, and a short video walkthrough.
- Price and timing
$349, delivered in about 5 working days. If you hire me for the fixes within 30 days, the $349 is credited toward them.
What's checked, a sample finding and how it works: Technical SEO audit.
A developer or an SEO agency?
An SEO agency is the better choice if you need content, links and ongoing campaigns. That's not my work.
The gap shows up when the problem is in the code. Agencies often send a report, and the fixes sit in a developer's backlog for months. Sometimes the fix breaks something else, because nobody explained why it mattered.
I write the report and I can write the fix. If you already work with an SEO agency, I'm happy to work alongside them, or white-label for them.
How it works
- You send your URL
Tell me what changed and what worries you, through the contact form.
- I reply within one business day
If an audit makes sense, I'll ask for Search Console access.
- You get the audit
A written report and a short video walkthrough.
- We fix it
I make the changes, or your team does with my tickets. You choose.
- I check again
After Google recrawls the fixed pages, I compare Search Console with the starting point.
Payment terms for larger fix projects work the same way as my development projects.
Pricing
- Option
- Technical SEO audit
- Price
- $349, fixed
- Good for
- Finding what's wrong and what to fix first
- Option
- Fixes
- Price
- $25/hour, or a fixed quote
- Good for
- Making the changes in your code
- Option
- Website migration SEO
- Price
- From $1,500
- Good for
- Moving to a new framework or platform
The audit is paid when you order it. The price is agreed in writing before any fix work starts.
Background
- Years of SEO and blogging. I've worked on the marketing side, so I know what a search problem costs a business.
- Every Next.js site I build ships with these checks. Server rendering, unique metadata, redirects, sitemaps and structured data.
- About 4 years building custom Next.js storefronts for e-commerce, where search traffic was revenue.
- More about my background About me
Questions about JavaScript SEO
JavaScript SEO is making sure search engines can crawl, render and index a site built with JavaScript. It covers how pages render, how links and metadata are set, and how fast the page loads. On React and Next.js sites, most of these problems live in the code.
Yes, when pages render on the server. Next.js can send complete HTML with titles, links and content on the first request. The problems start when content is fetched in the browser, or when metadata is set once in a layout.
Not by itself. A React app that only renders in the browser sends an almost empty page first. Google can render it later, but most AI crawlers can't. Server rendering or pre-rendering fixes this.
Yes. Google renders pages with a headless Chrome browser and indexes the result. But rendering can happen later than crawling, and blocked scripts, broken links or a noindex tag can stop it.
Only the HTML your server sends. Most AI crawlers, including GPTBot and ClaudeBot, don't run JavaScript. If your content loads in the browser, they see an empty page. Server-rendered Next.js pages don't have this problem.
My audit is $349, fixed price, delivered in about 5 working days. If you hire me for the fixes within 30 days, the $349 is credited toward them. Fixes are $25 an hour or a fixed quote.
Not for the audit. I need your URL and read access to Google Search Console. For fixes, I work in your repo, or I write tickets for your developers.
No, and nobody honestly can. I can make sure search engines can read and index every page you want found. Rankings then depend on your content, links and competition.
Yes. I can handle the technical fixes while the agency handles content and links. I'm happy to work white-label, under the agency's name.
Tell me about your site
Send me your URL and a short note on what changed or what worries you.
Tell me about your siteI reply within one business day. No obligation.
Get in Touch
Other ways to reach me
I'm available via email and messaging platforms.
Chat with me
Quick questions or follow-ups
Munim Rahman
Fullstack Developer • Next.js & Nest.js
Dhaka, Bangladesh