Technical SEO audit for Next.js and React sites
I'm a technical SEO consultant who also writes the code. I audit JavaScript sites the way Google and AI crawlers see them, then tell you exactly what to change and where.
Read access to Google Search Console is all I need to start.
$349.
- fixed price
- About 5 working days.
- The report is yours, whether or not you hire me for the fixes.
When an audit is worth it
Google indexes only part of your site, and nobody can say why.
Traffic dropped after a redesign, a rebuild or a framework change.
You're about to relaunch, and want to know what could break first.
Your SEO team has a list of problems, and needs someone who can find the cause in the code.
If you want keyword research, content plans or link building, this isn't that audit. I look at how the site is built.
What I check
| Area | What I look at |
|---|---|
| Rendering and indexing | Raw HTML against rendered HTML on each key template. What's missing before JavaScript runs. What Search Console says is indexed, and why the rest isn't. |
| Metadata | Titles, descriptions, canonical tags, robots rules and hreflang, per template. Whether they're set on the server or patched in later. |
| Links and site structure | Whether navigation uses real links, how deep important pages sit, and orphan pages. |
| Status codes and redirects | Soft 404s, redirect chains, temporary redirects that should be permanent. |
| Structured data | Which schema types you use, whether they're valid, and whether they match the visible page. |
| Speed | Core Web Vitals from real user data where Google has it, and the likely cause of each failing metric. |
| AI crawlers | Whether GPTBot, OAI-SearchBot, ClaudeBot and PerplexityBot can reach your pages, what they actually get, and whether Bing has indexed you. |
I start with your most important page templates. Twenty templates checked properly beat 500 generic warnings from a tool.
What a finding looks like
Every finding in the report follows the same format. Here's a made-up example, so you know what to expect.
A developer can act on that the same day. That's the point.
Product pages send the same description to every crawler
- Priority: fix now
- Effort: small
- What's wrong
the description is set in a client component, so the first HTML on every product page carries the default site description.
- Why it matters
Google may write its own snippet, and AI crawlers that don't run JavaScript see the wrong summary.
- Where
app/products/[slug]/page.tsxand the shared layout.- Fix
move the description into
generateMetadata, built from the product data on the server.
What you get
The audit is paid when you order it. If you hire me for the fixes within 30 days, the $349 is credited toward them.
A written report, with findings ranked by impact and effort.
A short video walkthrough of the most important findings.
A fixed quote for the fixes, if you want me to do them. No obligation.
How it works
You send your URL and a short note on what worries you.
You give me read access to Google Search Console. Repo access helps, but isn't required.
I audit the site over the next few working days, and may send a few questions.
You get the report and the video, usually within 5 working days.
- You decide what's next
Fix it with your team, or with me.
What this audit isn't
Not a content or keyword audit.
I won't tell you what to write about.
Not a backlink audit.
Links from other sites are outside its scope.
Not a code security review.
For that, see the code audit.
If your site is in the middle of a move, migration SEO is the better place to start.
The audit is the starting point for most of my JavaScript SEO work.
Questions about the technical SEO audit
Tools list hundreds of warnings without knowing which ones matter. I check your key templates by hand, find the cause in the code, and rank fixes by what they're worth. Most tools also don't compare what crawlers see before and after JavaScript runs.
Yes, at the level of finding which metric fails and why. If speed is the main problem, the Core Web Vitals work goes deeper and includes the fixes.
Yes. Crawler access, what AI crawlers see on your key pages, and Bing indexing are all part of it. For the wider picture, see AI search readiness.
Yes, if it's built with React, Vue, Angular or another JavaScript framework. The audit looks at what crawlers actually get, which works the same on any framework. Code fixes I take on for React and Next.js sites. For WordPress or Shopify themes, an SEO agency is a better fit.
Not for the audit. Search Console access is enough to start. With repo access, the report can point to exact files instead of page templates.
Yes. The report is written for developers, with the file, the problem and a suggested fix for each finding.
Order an audit
Send me your URL and tell me what changed, or what you're worried about. I'll confirm the timing before you pay.
Order an auditI reply within one business day.
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