OK...I am going crazy...
I have a Magento store in a /store/ directory. The homepage displays fine and users are able to make purchases, but to bots it's showing a 404 status code.
So /store/ and /store/index.php are both 404 header responses but I can navigate to those pages and browse the website from there. I've never seen this before.....blah
When I crawl the site with Xenu from the http://www.mywebsite.com/store/ URL it says it's 404 and the title shows, "redir" so I am assuming there is some redirect somewhere that I am missing(?)....
Any help is appreciated...I may need to explain this better so if so, I will gladly :)
Thanks in advance!
I appreciate all the help!
Somehow, changing the CMS page assigned as the homepage fixed the problem. The original homepage was calling some entity that returned a 404 error in turn giving a 404 error for the entire page.
Really not sure what happened...but like I said, changing the CMS homepage solved the problem!
Have you tried browsing your site with browser and a user agent switcher? There are examples of Magento being unable to build collections when the user agent is one of the bots which is explicitly left out of the log information.
Related
Getting 404 while redirecting to mydomain.com/web/guest/home
But if given mydomain.com/web/guest/ i am getting redirected properly. To be consistent across environments i want the redirection to mydomain.com/web/guest/home work properly.
I don't have any specific settings in my portal-ext.properties for auth.server.url
What could be the issue?
Regards,
Sankar
I am a newbie to smf forums. I just transferred all my smf forum files and database to my new host. After setting all my path to urls and directories through my repair_settings.php , I am getting my home page without any errors, but all other pages except this page shows a 404 error.
I really don't understand the problem. Could any please suggest me to get out of this prroblem. Thanks in advance.
Okay, so everything really worked for me, after I placed .htaccess into my folder and changed the RewriteBase.
Google detected a significant increase in the number of URLs that
return a 404 (Page Not Found) error. Investigating these errors and
fixing them where appropriate ensures that Google can successfully
crawl your site's pages.
And Let me know why google gives such Errors while crawl that website. I would like to keep in the notice that as I have rewrite the rules for the .php pages
Where I am doing wrong with the internal links between pages and content? As I have updated and correct the links after getting this message from webmaster staff team.
Kindly Check and investigate for the internal links and confirm me if I have missed something again?
Kindly Advice.
I will appreciate.
just find broken links and fix them
you can then mark these 404 pages as Fixed in Webmaster Tools
I've recently restructured my site and in the process have removed many pages.
I've put in .htaccess 301 redirects to reflect the changed structure where new pages directly replace old pages; have put in a custom 404 page and have included the following .htaccess command: ErrorDocument 404 /page-not-found.html.
For pages removed altogether that have no new equivalent page, I've used .htaccess to redirect to the 'page not found' custom page.
In webmaster tools, though, I'm seeing soft 404s reported - pages not found that are not returning 404 response codes.
Can anybody please advise a way forward on this?
Should I not redirect references to the deleted pages and let the 'pages not found' stack up in the webmaster tools report, or is there a way of returning a 404 code from the server for my deleted pages even though a redirect exists?
Any advice would be much appreciated.
Thanks,
Andrew
I think if the page doesn't have a new equivalent, then let it fall through not found, and return a 404 (which should show your custom page).
Google is showing a soft 404 because of the redirect (which is a 301, not a 404), as you say.
If you did redirect to the custom page, and somehow returned a 404, that's essentially the same thing as just letting them not be found.
The pages not found will stack up, but if they really aren't found anymore, then that's the correct response.
The alternative would be a 301 to a different page, that was a real "hey this moved, try this instead" page, but it would have to look like something other than "not found", to avoid google treating it as a soft 404.
I would like to block my website and probably redirect them to a 404 page while i am updating it which can take some time.
Could a redirect to the 404 page everytime a user goes to my website work?
You shouldn't do that. Status code 503 "Temporarily Unavailable" is much better in this case.
RewriteRule . - [R=503,L]
This might work.
If it's just a temporary redirect during site-down maintenance then you probably don't want to use a 404 code. Take a look at the other codes available to you. For a scenario such as this, 307 (temporary redirect) would make a lot more sense. It would also be better if you have any SEO or rely on search crawlers at all, as they will remove results which now produce a 404 but are smart enough to keep results which temporarily produce a 307.
The redirect itself will work fine, just redirect all traffic to a static page. (Did you need advice on how to do that, or were you just looking for alternative options and viability? It's unclear from the question. If the former, I can't help much. It's been years since I've cracked open an .htaccess file.)
Basically, a 404 tells visitors: "This resource isn't here. Don't both asking again." Whereas a 307 tells visitors: "This resource is temporarily being handled by something else, but it hasn't really moved, please try again later."
Here's a simpler idea: just make a new index page that's your original, except with the content replaced with a "site currently being updated; please come back later" sort of message. And then you'd redirect all hits to your site to that index page.
That's what many sites I've seen tend to do, at least. And it makes sense, at least to me. I mean, would you rather your users not know why the pages they want to access are no longer there, or that they know the reason is because the site is being updated? It's basically the same as a 404 page, just with the specific information of why the desired pages aren't there.
EDIT: It seems I'm basically talking about a 503 page, going by David's link and Roland's answer.
That would work, but that would not only be wrong information (the page is not 'not found' - it's just currently being updated), but also mislead your users and crawlers. I would redirect them to a 'Update in progress' page and send this with the http status code 423 (LOCKED) to the client to provide a standard conform answer to exactly your scenario.