Google Webmaster Tools is giving me loads of crawl Errors of a certain type but I just can't see where its getting it from
Its reporting that the error is a 404 on this page (which definitely doesn't exist)
http://www.soundshelter.net/artist/www.soundshelter.net/artist/Arnold+Jarvis
and its being linked to from this page
http://www.soundshelter.net/artist/Arnold+Jarvis
There is no link to the first page anywhere on that second page. I am getting the same error for so many of the pages on my site (all dynamically created)
Any ideas why this is happening? Could it be something to do with the way I'm creating links in the code?
Arnold Jarvis
Cheers!
Hay Franco the problem is in your canonical code in your website thats create all the 404 errors.
For example take this page
http://www.soundshelter.net/artist/Arnold+Jarvis
on line 33 you will see this line
<link rel="canonical" href="www.soundshelter.net/artist/Arnold+Jarvis" />
This line create the 404 page across all of your CMS system its probably some of the system addons if you will add there http:// all of your 404 pages will be fixed:)
Related
my website is on React and when I refresh a page it shows 404 found find. I tried many times but have not got a solution yet.
you might want to check all services , sometimes due to this just might be the issue
I have been trying to figure out Netlify redirects. My Netlify app is at this link (however this is a blockchain application and requires that you have metamask, so I will try to explain my problem so that you don't have to install it to actually answer my question): rekt.netlify.app
I have two main problems:
I have already tried the whole _redirects file with /* /index.html 200 in it. This works when I go to rekt.netlify.app/games and refresh, it will actually come back to that page. That's good. The issue is when I then go to rekt.netlify.app/games/Valorant for example, it will be a white page on refresh, and I cannot figure out why. In my react application, I have react router set up so the path is path="/games/:game"
I went to the Networks tab in the google inspect and I found that this was the request URL when I refresh the page on /games/Valorant: https://rekt.netlify.app/games/static/css/2.80dce9aa.chunk.css
As you can see, the issue is probably something to do with that /games/ comes before /static/ in the URL. I'm a beginner so I don't know what that actually means.
The second issue I am having is that, the img tags of the games load on the /games page, however, when you click on a specific game and attempt to go to a /games/Valorant for example the image will not load. I believe this is due to a similar problem. I have gone into Network tab of google inspect and when I look at the image being loaded in the /games page, it attempts to GET https://rekt.netlify.app/static/media/league_wallpaper.f5e6bf5f.jpg which works. However, when being loaded in the /games/Valorant page, it attempts to GET https://rekt.netlify.app/games/static/media/league_wallpaper.f5e6bf5f.jpg and this does not work, it's a blank page.
You can notice that the second link there has /games/ in it which I believe is preventing it from getting the image. Potentially the problem here is that anything more than one / in the URL is messing things up? I'm not sure. This is the link to my github project: https://github.com/jacob-tucker/ReKt
Edit: Here are some screenshots that will hopefully help. This first one shows that the request URL is trying to get the image from /games/static (which I don't think makes sense). This is happening on the /games/Valorant page.
And then here is a screenshot of /games/Valorant trying to load as well after I refresh the page and get a blank white screen (it returns a status code of 200 because I have /* /index.html 200 in my _redirects file.
I had a the same issue a while ago, I've just added
"homepage": "https://my-app.netlify.app",
in package.json and it worked perfectly.
My website is setup on Angular served by an Apache server. I load the content dynamically onto the main page via views.
Now following is my problem :
My main aim of setting up this website was to monetize the content through google adsense. However, my content keeps on getting rejected due to "Insufficient Content". When i run a tool like feedthebot.com all i can see that the bot comes up with only 64 words. I think this might be the reason why google adsense is getting rejected for my page. I was thinking when google [or other bots] crawl the page prerender.io would return static content also back to the bots. But it seems this does not happen and only the main page gets returned.
Is there anything wrong with the setup iam using, which could be resulting in adsense rejection ?
You have to use ?_escaped_fragment_= and !# to get indexed correctly.
There is a great tutorial for that here.
i am having a strange issue. I am seeing a lot of people visiting my 404 page of the website. but i am not able to track from where are they being referred to the 404 page.
the website has been made on cakephp framework.
in the page controller code when the page object is null we are redirecting it to the 404 page.
We are not able to find the referrence url from where the 404 page i being loaded.
the analytics gives keywords and landing pages. but we have checked all of them and none of them are going to 404
can anyone help.
www.vresorts.in
If you'd like to know the referrer, you can use $this->referer()
I have deployed my website to a production server... When inspected through firebug i found lot 404 not found errors in my requests.... Mainly from ajax libraries like scriptResource.axd files....
I saw the load time was greater for all the files which was a 404 Not Found...
How expensive is a 404(File Not Found) Error?
Why Timeline is greater for files with status 404 not found.....
I suppose it all depends in what your 404 page does : if it logs a lot of stuff, or does a lot of SQL queries, or is enourmous, it will take time to generate -- like for any other page, actually.
(I've seen a website on which the "error page" was the one that took the most time to generate, as there were a lot of calculations made to try to "suggest" interesting pages to the user)
A 404 request should not be particularly expensive. However, if the 404s are for static content like stylesheets and images, then the browser would normally cache the result. When a 404 is returned this does not happen and the item is requested time and time again. This can have a big effect on page load times.