What a Next.js SEO audit checks and what it costs

Public pages are the focus of a Next.js SEO audit. The HTML response and rendered page reveal gaps in content delivery. Loading speed is also part of the review.1, 2
Rendering architecture and bot discovery
Next.js supports several ways to build page HTML. Static generation, or SSG, builds it ahead of requests. Server-side rendering, or SSR, builds it for each request.3
ISR serves cached content and updates it through revalidation. Client-side rendering, or CSR, builds content in the browser using JavaScript. Static rendering suits blogs and landing pages; revalidated content suits product and CMS pages.3, 4
Search crawlers prefer HTML that already contains the page's content. Googlebot fetches raw HTML before it runs JavaScript. When meaningful content is missing, the page enters a queue for later rendering.3
That later stage can take minutes or days, delaying indexing. Avoid making client-side rendering the only source of important content for search. For pages with request-time data, server rendering can put content in the response.3, 4
Establish the Next.js version and whether the site uses App Router or Pages Router. Choose checks around the site's actual responses, page templates and metadata behaviour.1
App Router uses Server Components by default. Data fetching happens on the server, and HTML arrives already rendered. Metadata is generated before the response.3
Inspect the server response from a production page. Compare the initial HTML with the rendered page, looking for missing text and links. A Client Component alone is not an SEO error.4, 1
Check navigation and internal links in the rendered HTML when they rely on JavaScript. Google Search Console's URL Inspection tool can show that output.5
Crawlability, status codes and routing controls
Check robots.txt so it does not block important public pages. Review XML sitemaps, HTTP responses, redirects and internal links across the agreed page templates.5, 1
Separate a deliberate exclusion from a fault on a public page. Record affected URLs, response evidence and a proposed change.1
Staging pages often use noindex tags to keep unfinished work out of search. Those tags can reach production during a launch, migration or platform switch.5
A crawl or Search Console coverage report can find these tags. Confirm that pages intended for search are not blocked by an unintended noindex tag.5
A page can look correct in a browser but return the wrong status. JavaScript apps sometimes show a not-found screen while returning 200 OK.4
A deleted product page returning 200 creates a soft-404 problem. Long redirect chains add crawl and loading overhead.4
URL filters can create many near-identical pages and waste crawl budget. Canonical tags help bring those variants under a preferred URL.5
The same content may appear at several paths or with tracking and sorting parameters. Google treats a canonical tag as a signal, not an absolute command.4
Metadata management and social tags
The App Router Metadata API supports fixed and dynamically generated metadata. A marketing landing page can use a fixed title. A product page can build its title and description from product data.4
Review page titles, descriptions, canonical URLs and language alternatives. Include robots metadata and the page's h1 in the HTML review.1
Open Graph metadata can include a title, description, URL and image. It supports consistent share previews and Google Discover visibility.3
For Twitter cards, use summary_large_image and match the image to the Open Graph image. Next.js can also generate Open Graph images dynamically.3
Performance tuning and Core Web Vitals
Lighthouse audits a URL in a simulated environment and produces a performance report. Its findings identify areas where page performance can improve.6
Use a production build for accurate Lighthouse reports. Build with next build, then start the production server with next start.6
Open the page in an incognito Chrome window, then open DevTools and select Lighthouse. Select Generate Report to run the audit. Browser extensions can affect results, while ad blockers can stop scripts loading.6
Convert PNG and JPEG images to WebP or AVIF to reduce page weight. Set explicit width and height on images to avoid layout shifts.5
Reserve space for embeds and ads as well as images. Use useful alt text and surrounding content to give search engines context. Take particular care with the hero image or largest visible image.4
Tag managers, chat widgets and analytics scripts add JavaScript execution time. Load non-critical scripts with async or defer. Delay chat widgets until after the first user interaction.5
Review the tag manager container quarterly. Remove unnecessary client-side JavaScript and reduce costly hydration work. Measure field data again after performance work.5, 4
Commercial audit scope and cost
A commercial Next.js SEO audit package is priced at $1,050 to $2,100 USD, excluding applicable taxes. Its scope covers up to 1,000 agreed URLs and manual review of 20 to 50 priority pages. The exact scope is set in the proposal.1
For that package, delivery is targeted at 10 to 15 business days after payment, the brief and agreed access. Implementation is scoped separately. Large apps, migrations and extensive custom code work need a separate estimate.1
An audit can verify access, rendered content and agreed fixes, but cannot guarantee Google indexing. Google decides whether and when to index a page. If access works but useful content or relevant demand is missing, another technical change may not be the next priority.1
Kraftwire development and migration services
Kraftwire offers platform migration and website development services. MVP development is also among Kraftwire's services.
Kraftwire offers moves from WordPress, Framer or Webflow with SEO and content preservation as part of the offer. Its website development service offers custom sites designed for speed, security and scale.7
Kraftwire advertises six-week deliverables through its AI digital engineering system. The offer pairs developers with language models to speed up the work.7
Kraftwire's process starts with discovery to define goals, constraints and what done means. Design follows, with approval before development starts.7
The development stage offers regular updates and working software to view during the build. Launch and support include deployment and monitoring.7
Sources
FAQ
Why does client-side rendering delay page indexing?
Googlebot fetches HTML first and runs JavaScript later. If meaningful content is missing from the HTML, the page enters a rendering queue that can take minutes or days.
How do accidental noindex tags reach production deployments?
Development and staging pages often use noindex tags to keep unfinished work out of search. Those tags can carry over during launches, migrations or platform switches.
What does a commercial Next.js SEO audit typically cost?
A commercial package is priced at $1,050 to $2,100 USD, excluding applicable taxes. That package covers up to 1,000 agreed URLs and manual review of 20 to 50 priority pages. Implementation is separate, and larger or more complex work needs its own estimate.
How should developers test Next.js Core Web Vitals in Lighthouse?
Use a production build, built with next build and started with next start. Open the page in an incognito Chrome window, then use the Lighthouse tab in DevTools to generate a report. Incognito mode helps avoid browser extensions affecting the results.