gabier

Hello Nintechnet,
I did disable plugins one by one as you suggested. It did not change anything until the last one. When I disabled the last one (WP All import Pro), the Ninja button “Activate full WAF” did work, the page with full waf options appeared. But when I clicked on “End” (“Finaliser” in french), an error message popped up : “Erreur: NinjaFirewall est désactivé” (NinjaFirewall is dis-activated) and I cannot go further.
This not true indeed because I cannot access to Ninja dashboard if it is not activated.
what next ?
?? gabier

• This reply was modified 4 years, 6 months ago by gabier.

Thank you Gary Barrett, very interesting stuff.
I have found the rel=canonical tag in the posts’ pages of my blog! It seems to work as you said;

?? Gabier

Thank you Gary Barrett

I will take you at your word.

Maybe you have a link to the “technicalities” somewhere ? Or just give me a hint ? I like to understand things if they are not too complicated.

?? Gabier

Hello t31os_

Yes, of course it redirects me to “example.com/testing”, but my point is :

If the correct/new url is “example.com/testing” and my browser sends a request with “example.com/?p=55” (old url), does wordpress

1. sends back directly the page with the post #55 as if the correct url had been sent ?

2. sends to my browser a 301 error with the alternate URL “example.com/testing”, and then my browser automatically sends a new request with the correct URL.

The result for the user is the same, but for a robot it is not the same. Because in the case 1 the requests with old or new URL both work independantly, and then it is “duuplicate content”, a situation that robots do not like, I have been said.

Is that clear ? I have not found the answerin the codex or forums that is why I ask the question.

?? Gabier

Hello jimisaacs,

Thank you for answer. I will consider this plugin, but I have seen in its description/FAQ that “The plugin works in a similar manner to how WordPress handles permalinks “, thus I am not sure it solves my problem.

My problem is not to make the redirections easier, but to be sure that WordPress handles the permalink change as the redirection of a changed URL so that Google and other robots know it is a changed URL and not a duplicate content.

More precisely, when receiving a request with an “old” URL, does WordPress send back the correct page because it has translated internally the “old” URL into the “new” one, or a 301 error with the alternate (“new”) URL ?
The later way is correct, and in this case there is no problem. The former way is bad because the user (which can be a robot) has no way to relate the old and the new url. Both work and thus it is labeled as “duplicate content”.
I would expect WordPress to behave the right way, but I could find nowhere a description of its action in this case.

?? Gabier