Welcome to the Q&A Forum

Hi Dale, Nigel is right here - it's best practice to leave the Titles/Descriptions on these archive pages as-is and follow Google's guidelines (use next/prev link tags) to indicate paginated content. If your concern is duplicate content, next/prev tags give Google a clear signal of the relationship between these pages. Best, Mike

Long URLs is a pet peeve! But I agree with Martin on the traffic analogy. Modify the pages that need the most help and measure against the pages you do not change.

Hello there, Actually, I think this article could really help you! https://www.danielmorell.com/guides/htaccess-seo/https-www-and-trailing-slash Alternatively, if you want to get the rules right away, just copy below, change the "example.com" to your domain then it should be working. Force HTTPS Force WWW Remove trailing / from file Turn on rewrite engine RewriteEngine on Check if not directory and ends in / RewriteCond %{REQUEST_FILENAME} !-d RewriteCond %{REQUEST_URI} (.+)/$ If not a directory skip next RewriteRule RewriteRule ^ - [S=2] Check if HTTPS and WWW RewriteCond %{HTTP_HOST} !^www.(.*)$ [OR,NC] RewriteCond %{https} off This RewriteRule skipped if URI was a directory RewriteRule ^(.*)$ https://www.example.com/$1 [R=301,L] This RewriteRule used if URI was a directory RewriteCond %{REQUEST_FILENAME} -d RewriteRule ^ - [S=1] RewriteRule ^(.*)/$ https://www.example.com/$1 [R=301,L] Do note, this 301 redirect your URL to the version with trailing slash, and because Google sees the trailing slash and non-trailing slash version of your pages as a different page, you should be doing a 301 to the right one. Read more about it here: https://www.seroundtable.com/google-trailing-slashes-url-24943.html Of course, you can choose to remove the trailing slash 301 redirecting, Moz doesn't redirect to either version, and they rank well. But sites like Neilpatel (they have unnecessary redirects) and Backlinko does redirect, and they rank well too. So it's up to you if you want Google to help you identify which version you prefer or you tell Google yourself. Finally, you can use this tool to check if your redirects are working as you expected: https://httpstatus.io/ (When you test, use a blog page or a specific page to test all the 8 variations because trailing slash doesn't matter at the homepage, take a look at screenshots below) uPeMS8X.jpg ugDMJZ9.jpg 0wtlmAX.jpg HV2Byd5.jpg

Good to hear. Although this is solved, I did want to say the "Redirection" plugin is Wordpress is free and easy to use. Best of success to you!

Hi There, The duplicity of keywords can be due to meta tags and their usage. Please share the code of the website if possible. Best Regards, Vijay

Hi Dale If that loop you have specified there was true then the homepage wouldn't show up. https://www.theirsite.com/keyword>https://www.theirsite.com/>https://www.theirsite.com/keyword ad infinitum... It would just keep on going and Google wouldn't be able to show the page. You could use Screaming Frog to check for redirect chains - SEMrush and MOZ also pick them up so scanning the site would be my preferred option before touching it. Failing that I would remove it and see what happens. Regards Nigel

Both issues are on ALL WordPress sites. xmlrpc.php return 405 because it's work under HTTP POST but bot crawl under HTTP GET. And error 405 mean switch from GET to POST. But bot can't do that. admin-ajax.php return 400 because it's not designed for direct use. You must make call with some parameter and it will return some information. But as name says - it's responsible for AJAX calls and it's not for direct use that's why it return 400 when it's called w/o parameters. So - that issues are not related to your issue. For example mine WP sites also return same error codes to the bot. Peter

Nope, sorry, that site doesn't have Jetpack installed.