Improve SEO

[franky47]

A lot of feedback recently has been about people struggling to find nuqs (they know what it is, but can't remember the name).

Some examples:

• https://www.reddit.com/r/reactjs/comments/1nmnsr2/comment/nfe8m2q/
• https://x.com/ddunderfelt/status/1969871642424705293
• https://x.com/ericclemmons/status/1969950944621367764

I'm not knowledgeable in SEO enough to know how to help here, but it feels like the docs, the NPM metadata, and some other things on the GitHub repository (labels, README etc) could help in ranking on keywords that people actually search for.

I don't want any paid or LLM-generated programmatic SEO sloppy articles though.

[HimanshuKumarDutt094]

i think adding proper jsonLD structure would be better.
google dev link for json ld
tldr:

Google uses structured data that it finds on the web to understand the content of the page, as well as to gather information about the web and the world in general, such as information about the people, books, or companies that are included in the markup. For example, when a recipe page has JSON-LD structured data (describing the title of the recipe, the author of the recipe, and other details), Google Search can use that information to display a rich result for the recipe.

heres one i got from dumping nuqs docs codebase into copilot: https://gist.github.com/HimanshuKumarDutt094/04f40f67db12ac005c462e1b0dffac87

[HimanshuKumarDutt094]

they also have tools
https://developers.google.com/search/docs/appearance/structured-data
https://search.google.com/test/rich-results
i tested nuqs.dev on both and the results are
https://search.google.com/test/rich-results/result?id=okXMsUkKHsbPpl_NGwpN8w

https://validator.schema.org/
and

[HimanshuKumarDutt094]

Although I think this applies less to nuqs any tiny seo boost to crawler might be better, given unless explicitly searching nuqs it barely appear in intital results.
SEO 100 in lighthouse doesn't help at all 💀

[franky47]

Poll time: what would be the search terms you'd use to look for nuqs? (ie: how do you describe what it does in your own terms)

Reply below ⬇️

[yoannfleurydev]

• react url state
• (react|next) search param

[Scglia]

Agree with the ones suggested above. One word that hasn't been mentioned is "query" parameters.

[franky47]

One word that hasn't been mentioned is "query" parameters.

I blame React Router for pushing that invalid semantic to the world, but alas I feel like it's engrained in everyone's brains now so I'll have to support it. 😓

[Scglia]

I just went into a rabbit hole because I had no idea "query parameters" wasn't an "official" name and realized that indeed JS functions and frameworks tend to use "searchParams". So in case you're interested by a bit of random Web history here's what I found:

It seems that "query params" is more popular than "search params" according to google trends
And I can confidently say that "query parameters" predates React Router: https://datatracker.ietf.org/doc/html/rfc3987

But I was also curious about the term "search parameters", and it turns out the URL specs uses searchParams:
https://url.spec.whatwg.org/

The reason behind it can be found in the commits: "Rename query to searchParams because it conflicts with ParentNode's query." The discussion that lead to that choice is kind of fascinating actually, literally 4 people having a quick chat about it:
https://www.w3.org/Bugs/Public/show_bug.cgi?id=23586

Funnily, I have no clue what "ParentNode's query" refers to, there's nothing about it in the URL spec or in ParentNode's MDN page.

tl;dr: web specs history is surprisingly fun, and yes you should support "query parameters"!

[franky47]

Haha I just went on the same rabbit hole of deep research on the origin of the term today too! 😅

Thanks for the findings, we definitely want to include query param(eter)s in the keywords.

[franky47]

Since this discussion is acting like a honeypot for SEO spam (which as per the initial message is not a way I want to go to), I'm locking it for now.