For Nuxt.js sites
SEO for Nuxt.js Without Pretending the Platform Can Do What It Cannot
Search work on a Nuxt site is routes, metadata, and how the page is rendered. If the page is client-rendered, we say so. The fix is rendering, not another meta tag. Softix does not promise a ranking.
- routes, metadata, and how the page is rendered, named specifically
- Limits of the platform said in the audit
- No plugin or app added without saying what it changes
- Index and pages on the report, not a ranking promise
Search engine blueprint
How search work is done on Nuxt.js
The usual leak is client-only text, trailing-slash duplicates, and a CMS payload that never becomes HTML. The work stays inside the Nuxt rendering mode you ship. If the page is client-rendered, we say so. The fix is rendering, not another meta tag.
Name the URLs that should be the answer
We list the pages that match real demand: routes, metadata, and how the page is rendered. A URL that is only a filter, a tag, or a copy does not stay in that list.
Say what Nuxt.js will let us change
If the page is client-rendered, we say so. The fix is rendering, not another meta tag. If the platform blocks the fix, the audit says the limit instead of implying a setting that does not exist.
Clean what competes
The leak we start from is client-only text, trailing-slash duplicates, and a CMS payload that never becomes HTML. Duplicates are canonicalized, noindexed, or redirected. The choice is written down with the URL.
Report the index, not a promise
The monthly note is which URLs are indexed, which were consolidated, and which pages now match a query. We will not promise a ranking or revenue.
Where Nuxt.js sites usually leak
The problems teams describe before they hire search help
The platform is the Nuxt rendering mode you ship. The leak is client-only text, trailing-slash duplicates, and a CMS payload that never becomes HTML.
Defaults are still on: archives, filters, or app pages no one meant to rank.
Each one is kept, canonicalized, or removed, with the URL in the fix list.
The homepage and an inner page fight for the same query.
One URL is the answer. The other links to it.
A plugin, app, or module was added to “do SEO.”
We name what it changes. If it only adds a meta tag, it is not the fix.
Content was written for a keyword the catalog or the CMS does not have.
Pages match routes, metadata, and how the page is rendered that exist. We do not invent a collection.
The team was told the platform guarantees rankings.
It does not. Softix will not say that either.
| Channel | Plugin or app only | Work on the URLs |
|---|---|---|
| What changes | A settings screen | routes, metadata, and how the page is rendered |
| What you can see | A score inside the app | URLs indexed, consolidated, or left alone |
| What it cannot do | Override the platform | Pretend Nuxt.js has a control it does not |
| What we will not say | Guaranteed rankings | Guaranteed rankings |
What the engagement covers
Technical tactics for SEO for Nuxt.js
Six pieces of work on a Nuxt site. If the page is client-rendered, we say so. The fix is rendering, not another meta tag.
URL map
The pages that should answer a query are listed against routes, metadata, and how the page is rendered.
Only real locations
A map pin exists if the business has a place. A platform site with no stores does not get city pages.
Claims the owner will sign
Copy states what the page is. Softix does not invent reviews, awards, or a ranking.
Index the URLs that matter
The leak we clean is client-only text, trailing-slash duplicates, and a CMS payload that never becomes HTML.
Mentions you can explain
Earned links only. A plugin does not create them. Paid networks are not part of the work.
From the query to the page
The monthly note is indexed URLs and the pages that match a query. Revenue and rankings are not promised.
One engagement, with the limit in writing
Index results a Nuxt.js site can audit
What a platform engagement looks like
This is a representative description of the work on a Nuxt site, not a promise and not a traffic number we will invent. The leak was client-only text, trailing-slash duplicates, and a CMS payload that never becomes HTML. The constraint was the Nuxt rendering mode you ship.
If the page is client-rendered, we say so. The fix is rendering, not another meta tag. Every fix named a URL. The report did not include a ranking guarantee. Where Nuxt.js could not do the change, the note said so.
A different theme, catalog, or release will change the list. We will not promise a ranking or revenue.
What Softix will put in writing
- A written audit of URLs before a retainer starts
- A technical fix list in the first 30 days, with owners and URLs
- Monthly reporting on what was indexed, consolidated, or left alone
- No ranking guarantee, and no claim that the platform can do what it blocks
What teams usually ask before they sign
SEO for Nuxt.js, in plain language
How long before SEO for Nuxt.js shows up in the index?
Duplicate and default URLs can be cleaned within weeks. New pages that match routes, metadata, and how the page is rendered more often take a few months before they are the URL Google keeps. The report names URLs. It does not promise a position.
Will an SEO plugin fix the site?
A plugin can edit a title. It does not decide which of routes, metadata, and how the page is rendered should exist. That is the work.
What if Nuxt.js cannot do the change?
If the page is client-rendered, we say so. The fix is rendering, not another meta tag. The audit says the limit. We do not hide it.
Do you add city pages?
Only if there is a real place. A store or an office that does not exist does not get a page.
Will you promise rankings?
No. The platform does not guarantee them, and neither do we.
First look, before a retainer