Welcome to the Q&A Forum

Howdy. Yes, canonical or 301 redirect would be your friend. How much time did you give google to reindex before your verdict was "canonical didn't work"? Also, have you "fetched as Google" after you've done canonical? Also, here is another question, why is having paginated version in SERPs bad? Another way to influence your inner rankings is internal links. When you link to job offers page, which link do you use? The one which has more links and more relevant anchor text will be more likely to show in SERPs. Hope this helps.

Those links are made into hrefs (eg made clickable) by xml styling that's been applied. It's purely for user convenience - doesn't matter to search engines either way. There is actually a massive benefit to having multiple sub-sitemaps like that though. Once you've submitted the sitemap index to Google Search Console, it will break out the crawling and indexing report for each sub-sitemap. Which means you will now be able to monitor and asses each of different sections of your site separately. Vastly easier to detect and fix crawl errors that way than when everything's lumped into a single sitemap. Paul

Is there a redirect on the page that is ranking with the term? We experienced the same thing and we found that the 301 redirect we had got erased somehow. Once we put it back in, we returned to the same position.

Hey Britney, No, the old (ColdFusion) site and the new (PHP) site are on the same linux (CentOS) server. The 301 redirect rule I described above in my original post is applying '.cfm' to the end of the destination URL - thats the main issue we're trying to tackle here. Thanks for responding!

This is fine, as long as you don't want to exclude robots from crawling any part of your site.

Hi Joao, One thing that you might try to do to differentiate the content from search engines' perspective is add schema markup designed for job postings. Schema helps search engines understand what the content on a page is or is describing, and you can specify things like: Date posted (do you have this information if you are pulling from a newspaper?) Experience requirements Hiring organization Industry Job location Job title The date the offer expires Adding this information will give search engines much more context about what the content is about, and may help your issue. Hope this helps!

Thank you very much! I'm going to recommend a target of 2 sec with an average between 2 - 5 sec and 800ms for first visual. I'll let them know that they can accomplish reducing page size by: leveraging browser caching setting up HTTP caching optimizing images using gzip compression minifying CSS combining javascript files using a CDN to serve static files

Hi Olivia - Thanks for the question. It's definitely a good one to wrap your head around as anytime you change URLs it's a large undertaking and a lot that can go wrong. What should happen when you move from HTTP -> HTTPS and have done everything correctly (not chaining redirects, etc) is that your HTTP pages will stop ranking in favor of your HTTPS pages which should take their place. Some people have seen a small improvement in rankings from moving to HTTPS, but for the most part people just saw a swapping out of the ranking URL to the HTTPS URL. Make sure you annotate Analytics when this goes live so you can make some correlations from the move. Sometimes people have seen an increase in clickthrough rate because users subconsciously trust HTTPS sites more. Good luck!

Hey there ArisGrast, Personally, I would probably canonicalise the category pages to the original base category to reduce the risk of duplicate content. But that is just me. I would also suggest setting up your website in Google's Search Console. Once in here you can then set the crawl rate and other crawl elements such as URL Parameters. First if not already done - add your website. Once your site is verified - either by a meta tag, google tag manager or maybe a hosted file, you can then edit what happens. On the side menu of the profile in question select -> Crawl -> URL Parameters Once in this section you can add the variables you do not want indexing. While in here I would also suggest submitting an XML Sitemap and checking a few other things. If you also have Google Analytics set up you can link your profiles together for added benefits. Hope this is off use and answers some parts of your question.

Try this for a complete site wide redirect to HTTPS:// RewriteEngine On RewriteCond %{HTTPS} off RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301] I have also updated all my exiting 301 redirect to point to the new location. All older pages should be caught under this rule. Also remember to update your Search Console profiles, sitemap, robots etc I would also update all internal links to point to https:// rather than relying purely on the redirect.

Thanks Logan Ray! That makes sense. So without a strong DA the url is practically useless right now. I think we better sell this nice url than.

Hey, You don't need to delete any thing. Just go SC and use as default. If you already used canonical tag, you don't need to worry for the same. Thanks Rajesh

Thanks again for the response. Looks like it just took a little more time for Google to resolve the issue. No more errors. Didn't do anything but resubmit Sitemap and Robots.txt. Thanks for the tips as well. I am going to post one more question in another thread.

Glad it works!

Thanks!

Thank you for the feedback, I appreciate it.

Thanks again for taking the time to help us!