Platforms
The document the crawler receives.
Next.js SEO makes sure the HTML response contains the title, the links, and the copy. A hydrated screen is not enough.
The same URL has to rank, be quotable, be named in chat, and be a source in the overview.
A named result is published when that client clears the figure.
Next.js SEO
01 — The gap
The main copy arrives after hydration.
View source shows a spinner or an empty main. The title is there. The answer is not.
02 — The work
Fetch comparison
First HTML versus the rendered screen, on the templates that matter.
03 — The close
Reporting
The comparison, the metadata map, and the deploy that changed the HTML.
The work
What this is
Next.js can render on the server, at the edge, or mostly on the client. Teams ship a polished app whose first response is a shell. Search and answer engines that do not run the full app never see the offer. The fix is in the rendering and the metadata, not in another blog post.
ShoutRank’s own site is a Next.js app. We still specify changes for your developers to ship. This is not a theme install. It sits under technical SEO.
The problem
What usually breaks
01
The main copy arrives after hydration.
View source shows a spinner or an empty main. The title is there. The answer is not.
02
Metadata is set in two places.
A legacy Head and the Metadata API disagree. Canonicals flip between deploys.
03
Client-side routes have no document.
Filters and tabs change the view without a URL, or with a URL that returns an empty shell.
The practice
How ShoutRank approaches it
We fetch the production URL the way a bot would and compare it to what a person sees. Metadata has a single source. Routes that should be indexed return their content in the first response. Routes that are application state do not pretend to be documents.
We do not require a specific Next.js version. We read the one you run.
Included
What the work includes
01
Fetch comparison
First HTML versus the rendered screen, on the templates that matter.
02
Metadata map
Where title, canonical, and robots are set, and which source wins.
03
Route classes
Documents to index, and app states that should not be URLs.
04
Release check
The same fetches after the next production deploy.
Sequence
Process
- 1
Discovery
List the templates behind revenue and category queries.
- 2
Audit
Fetch them and read the HTML, including status codes.
- 3
Strategy
Name the metadata source of truth.
- 4
Implementation
Specify render and metadata changes for the team that owns the repo.
- 5
Monitoring
Refetch after deploy.
- 6
Optimization
Reclassify routes that are still shells.
- 7
Reporting
The comparison, the metadata map, and the deploy that changed the HTML.
The desk
Why ShoutRank
View source counts
If the offer is not in the response, we do not call the page indexable.
Your repo, your release
We do not fork the app to sneak in tags.
App states are not pages
Not every click needs a URL. The ones that do need a document.
The report
How success is measured
Priority templates whose main copy is in the first HTML.
One canonical source, confirmed after deploy.
Shell URLs removed from the sitemap.
A named client result is published when that client clears the figure. Until then the report is the measurement.
ShoutRank does not guarantee a ranking or a citation.
Related
Questions
Next
Check the page you want people to find.
The free check shows the gaps on one public page. If the gap is this service, a neighboring one, or a two-week review, we will say so after you ask.
A named result is published when that client clears the figure. ShoutRank does not guarantee a ranking or a citation.