: Using MongoDB objectID in query parameter, does it affect SEO? If we use object id of MongoDB in query parameter like for example, In browser URL, http://example.com/get-details/507f191e810c19729de860ea
If we use object id of MongoDB in query parameter like for example,
In browser URL,
example.com/get-details/507f191e810c19729de860ea
to pass this objectID from one state to another state, I am using $stateparam
then,in $http the URL will be
"/get_details?id="+$stateParams.detail_id
$http.get("/get_details?id="+$stateParams.detail_id).then(...);
Is there any problem with the URL in browser in terms of SEO,
i.e, example.com/get-details/507f191e810c19729de860ea? If so then what could be the solution?
More posts by @Cofer257
1 Comments
Sorted by latest first Latest Oldest Best
There is a great misconception that in order to have better SEO you must have a human readable URL written as a statement or as the page title. There is absolutely no issue with having a record ID number in the URL if that is the logical identifier for the content being displayed. There are many sites out there that use integers, and even GUID's in the URL to identify a file uniquely (in database driven systems). This is not an issue with SEO as SEO focuses on the value of the content. Yes the URL does play a part in the ranking but having a record ID number in the URL is not a huge issue against the value of the page content itself.
Terms of Use Create Support ticket Your support tickets Stock Market News! © vmapp.org2024 All Rights reserved.