Crawl errors after moving platform

Joined
Dec 17, 2015
Messages
144
Likes
75
Degree
0
#1
Hey folks

So I have just moved on ecommerce site from opencart to wordpress and made it live. Google console is now showing a load of crawl errors from the old opencart pages. Do I just let them fade away or is there something that needs to be done. A lot of 301's have been done so these are mainly just catalogue/model or catalogue/controller type files rather than actual pages.

Will Google just realise it's been moved to a new platform? Don't want rankings to tank any more than they already have.
 
Joined
Apr 7, 2016
Messages
252
Likes
156
Degree
1
#2
As long as they are pages you didn't intend have indexed, like a category or product page, you'll be fine leaving those as 404 errors. You can mark them fixed, just don't be surprised if they come back. Google revisits 404s on your site to see if they have changed, even if your site is no longer linking to those pages.
 
Joined
Dec 17, 2015
Messages
144
Likes
75
Degree
0
#3
I have now added the https property as it now uses SSL and submitted the Yoast sitemap so hopefully G will begin to recognise the new structure.
 
Joined
Dec 17, 2015
Messages
144
Likes
75
Degree
0
#4
One thing I have noticed using pingdom to test the new pages is some heavy wait times on things like this:

Code:
http://www.mysite.co.uk/automotive
https://www.mysite.co.uk/automotive   2.5 secs
https://www.mysite.co.uk/automotive/   7 secs
How to fix?
 
Last edited by a moderator:
Joined
Dec 17, 2015
Messages
144
Likes
75
Degree
0
#5
Also I'm having issues with regular expression redirects using a plugin. Typically, I'm trying to move a category from the old site to a new slug, so say /automotive to /cars but also all the old product urls too, so /automotive/fiat-panda to /cars/fiat-panda so I have setup:

/automotive/(.*) to go to /cars/$1 as per the instructions but it gives a 404 error. Happy to pay someone to go in and fix the issue but I'd like to learn to fish :wink:
 

Ryuzaki

女性以上のお金
Staff member
BuSo Pro
Digital Strategist
Joined
Sep 3, 2014
Messages
3,159
Likes
5,772
Degree
7
#6
One thing I have noticed using pingdom to test the new pages is some heavy wait times on things like this
Sounds like the server itself is slow to manage the redirects. It also looks like you have a redirect chain in place, routing users through several hops to end up where you want them to go. Try this out: http://www.redirect-checker.org

Start with http://www. and try variations like http:// and https://www. and make sure they all go directly to the desired result without bouncing through each other in a sequence.

/automotive/(.*) to go to /cars/$1
That looks correct to me. (.*) captures as many characters of any type at the end of that string, then $1 places them at the end of the other. Have you made sure to declare it as a RewriteRule and put the 301 flag on it?
Code:
RewriteEngine On
RewriteRule /automotive/(.*)$ /cars/$1 [R=301,L]
Make sure you declare the end of the line too using $ after the /automotive/ part. Also, full disclaimer, I suck at Regex.