Welcome to WebmasterWorld Guest from 126.96.36.199
awk -F\" '($6 ~ /Macintosh/)' *.com | awk '($1 ~ /^70\.90\.219|^70\.89\.39|^70\.32\.|^64\.233\.|216\.239\.|209\.85\.|199\.87\.|173\.194\.|^74\.125\.|^72\.14\.|^66\.249\.|^66\.102\./)' > ~/google_visits_on_Mac_most_IPs.txt
I want to see the site!The rules of that forum require me to review two sites by others and I don't feel qualified. Having enough confusion about my own. I can PM the URL to you if you like, just to remove the suspense. Additionally, I have an experience in submitting a site to the Google Help forum for review and that turned out to be just a beating that got me nowhere in terms of constructive changes I could make. I learned that I have no Web design skills (as if I didn't know that) and I have too many ads (fair) but as far as why the ban - that's still an open question.
Review My Site
See if there is any hits on the page "this_page_should_not_exist.fake", then you have the IP. Seems like they sometimes do check for a proper 404 response using this filename.
I do believe Google interprets that directive as a 301.Thanks, Pageone! Well, what do you know: this 404.shtml was on the server for at least the last four years. The critical mass of junk redirecting to the homepage got to the banning point? Fixed that, looks like another recon request is in order...
I wonder what the introduction of the META Refresh Element would do in this instance? Any ideas? For example, a page that returns a 404 Status and then has a 1 second refresh to the home page.
You and I had this discussion over a year ago!Darn it, Pageone, I envy your memory! I do remember now that as a result of that exchange I've changed the CMS to return better 404s (410s in my case) for all plausible URLs i.e. those that could have been content pages but the particular record cannot be found in the DB, most likely deleted spam. What I forgot to check for was implausible URLs - those that could not be formed into a proper DB lookup and therefore CMS could not handle those. Those URLs received the system default 404 that, it turns out, had a meta refresh to the homepage in the content returned following the 404 header.